Deploying vCenter Server Appliance 6.0 using vmware provided scripts (Part-1)

 Deployment of vCenter Server Appliance 6.0 can also be performed using a script, VMware itself provides four script templates each for Embedded, External PSC, External vCenter and PSC replication with the installation media . The executables that are required to run the scripts are also provided with installation media.

In every template there are two classes namely deployment and vcsa, details regarding the ESXi host on which the appliance would be deployed are provided in the deployment class.

“deployment”:
{
“esx.hostname”:”<esx host name or ip>”,
“esx.datastore”:”<esx datastore>”,
“esx.username”:”root”,
“esx.password”:”<esx password>”,
“deployment.option”:”tiny”,
“deployment.network”:”VM Network”,
“appliance.name”:”embedded-node”,
“appliance.thin.disk.mode”:true
},

Note: The network that is assigned to “deployment.network”: must be configured with a valid VLAN ID to it.

And the second class is vcsa under which four sub classes system, database, sso and networking are specified. Sub classes are optional for example database is only required when using external oracle database.

“vcsa”:
{
“system”:
{
“root.password”:”password”,
“ssh.enable”:true,
“time.tools-sync”:false,
“ntp.servers”:””,
“platform.service.controller”:””
},

Note: It is recommend to use NTP servers otherwise the installation of management node would fail with time skew problem. Also it is important to note that ESXi Server on which the deployment would be done must also use the same NTP server.

“database”:
{
“type”:”external”,
“user”:”vpxuser”,
“password”:”password”,
“servername”:”servername”,
“serverport”:null,
“provider”:”oracle”,
“instance”:”VCDB”
},

“sso”:
{
“password”:””,
“domain-name”:”vsphere.local”,
“site-name”:”Default-First-Site”,
“first-instance”:true,
“replication-partner-hostname”:”replication host”
},

Note:  While deploying a Platform Services Controller node, it is very important to specify “first-instance”: to true or false, otherwise management node might fail.

“networking”:
{
“ip.family”:”ipv4″,
“mode”:”dhcp”,
“ip”:””,
“prefix”:””,
“gateway”:””,
“dns.servers”:””,
“system.name”:””
}
}

Note:If more than one DNS server are provided during the execution of script, the deployment will fail. As a workaround specify single DNS during deployment and add multiple DNS servers after the deployment.

Once a template is populated with required details save it to a desired location (for example c:\samplepsc.json) on the machine from where the script would be executed. Do not forget to save it with .json extension.

Power Shell command prompt is used to run the script.

  • Open Power Shell command prompt as an administrator.
  • Change to the installation media directory and open the vcsa-cli-installer>win32
  • Now, call the executable with command vcsa-deploy.exe and supply the script location as an input (Ex: D:\ vcsa-cli-installer\win32\vcsa-deploy.exe c:\samplepsc.json).
  • Once the script start to execute, if the host SSL certificate is an untrusted one, a message is displayed awaiting a response of yes or no where yes is to trust the certificate and proceed, no to say the certificate is untrusted and abort.
  • After accepting the certificate, the deployment begins.
  • After PSC is deployed, once again call the executable with command vcsa-deploy.exe and supply the vCenter script location as an input (Ex: D:\ vcsa-cli-installer\win32\vcsa-deploy.exe c:\samplevca.json).

Upon successful vCenter appliance installation, one can login to Web Client using the provided credentials.

Sample scripts for external PSC and vCenter Deployment are provided in the next pages.

One thought on “Deploying vCenter Server Appliance 6.0 using vmware provided scripts (Part-1)

  1. Hello,Can you please pvroide me details of your Home LAB. I am planning to build one and has limited budget currently. So your inputs will be valuable to me as you already have one.

Leave a Reply

Your email address will not be published. Required fields are marked *

*
*
Website