{"id":2207,"date":"2015-08-08T17:42:30","date_gmt":"2015-08-08T15:42:30","guid":{"rendered":"http:\/\/possiblelossofprecision.net\/?p=2207"},"modified":"2021-05-15T11:46:37","modified_gmt":"2021-05-15T09:46:37","slug":"deploy-vcenter-appliance-vcsa-6-0-from-the-command-line","status":"publish","type":"post","link":"https:\/\/possiblelossofprecision.net\/?p=2207","title":{"rendered":"Command-line deploy vCenter appliance (VCSA) 6.0 on a Linux machine"},"content":{"rendered":"<p>Up to version 5.5 a vCenter appliance was usually deployed by importing the corresponding ovf template that could be downloaded from the VMware website. That process changed with version 6.0 since there is <a href=\"https:\/\/kb.vmware.com\/kb\/2110730\">no longer an ovf template<\/a>. Instead, VMWare provides and <a href=\"https:\/\/my.vmware.com\/en\/web\/vmware\/info\/slug\/datacenter_cloud_infrastructure\/vmware_vsphere\/6_0\">ISO image<\/a> that contains the necessary data and tools to deploy a vCenter appliance, even directly from the command line.<\/p>\n<p>After downloading the ISO image file from the <a href=\"https:\/\/www.vmware.com\/go\/download-vsphere\">my vmware portal<\/a> mount it, e.g. to <code>\/mnt<\/code><\/p>\n<pre class=\"brush: bash; title: ; notranslate\" title=\"\">\r\n# mount -o loop \/var\/lib\/libvirt\/images\/VMware-VCSA-all-6.0.0-3343019.iso \/mnt\/\r\n<\/pre>\n<p>The vcsa command line deployment tool can be found at <code>vcsa-cli-installer\/lin64\/vcsa-deploy<\/code>. Since the available options and arguments to this tool are tucked away in one of the many <a href=\"http:\/\/www.vmware.com\/files\/pdf\/products\/vsphere\/VMware-vsphere-60-vcenter-server-appliance-cmdline-install.pdf\">vCenter documentation pdfs<\/a>, here&#8217;s the output of <code>vcsa-deploy --help<\/code><\/p>\n<pre class=\"brush: bash; title: ; notranslate\" title=\"\">\r\n$ vcsa-cli-installer\/lin64\/vcsa-deploy --help\r\nusage: vcsa-deploy install &#x5B;-h] &#x5B;--template-help] &#x5B;-v] &#x5B;-t]\r\n                           &#x5B;--log-dir LOG_DIR] &#x5B;--verify-only]\r\n                           &#x5B;--skip-ovftool-verification] &#x5B;--no-esx-ssl-verify]\r\n                           &#x5B;--sso-ssl-thumbprint SSL-SHA1-THUMBPRINT]\r\n                           &#x5B;--accept-eula]\r\n                           template\r\n\r\nDeploy vCSA to a remote host.\r\n\r\noptional arguments:\r\n  -h, --help            Show this help message and exit.\r\n\r\nOther Arguments:\r\n  --template-help       Print out the help for template settings.\r\n  -v, --verbose         Debug information will be displayed in the console. If you set this parameter, you cannot set --terse.\r\n  -t, --terse           Only warning and error information will be displayed in the console. If you set this paramter, you cannot set --verbose.\r\n  --log-dir LOG_DIR     Directory for log and other output files.\r\n  --verify-only         Perform only the basic template verification and OVF Tool parameter verification, but do not deploy the vCenter Server Appliance.\r\n  --skip-ovftool-verification\r\n                        Deploy the vCenter Server Appliance directly through OVF Tool without performing parameter verification. Basic template verification will still be performed.\r\n  --no-esx-ssl-verify   Skip the SSL verification for ESXi connections.\r\n  --sso-ssl-thumbprint SSL-SHA1-THUMBPRINT\r\n                        Validates server certificate against the supplied SHA1 thumbprint.\r\n  --accept-eula         Accept the end-user license agreement. This argument is required to deploy the appliance.\r\n\r\nRequired Arguments:\r\n  template              Path of a JSON file that describes the vCenter Server Appliance deployment procedure.\r\n\r\nUse --template-help for a list of template settings.\r\n\r\nThe exit codes and their meanings are:\r\n0: Command ran successfully.\r\n1: Runtime error.\r\n2: Validation error.\r\n<\/pre>\n<p>You can find sample json templates for the deployment in <code>vcsa-cli-installer\/templates\/install\/<\/code>. The options should be quite self-explanatory and cover<\/p>\n<ul>\n<li> Networking<\/li>\n<li>SSO<\/li>\n<li>System<\/li>\n<li>Database<\/li>\n<li>Deployment<\/li>\n<\/ul>\n<p>A comprehensive list of valid parameters of the json file is available as well by invoking <code>vcsa-cli-installer\/lin64\/vcsa-deploy --template -h<\/code><\/p>\n<p>The <em>deployment.option<\/em> parameter specifies, how much virtual harware (CPUs, RAM) should be allocated for the vCenter appliance. Here&#8217;s a table of the available options (taken from the <a href=\"https:\/\/pubs.vmware.com\/vsphere-60\/index.jsp?topic=%2Fcom.vmware.vsphere.install.doc%2FGUID-E278E0F2-8983-4246-9903-50C4022F1273.html\">VMware vSphere 6.0 Documentation Center<\/a>)<\/p>\n<h2 id=\"tablepress-9-name\" class=\"tablepress-table-name tablepress-table-name-id-9\">vCenter Server Appliance size<\/h2>\n\n<table id=\"tablepress-9\" class=\"tablepress tablepress-id-9\" aria-labelledby=\"tablepress-9-name\">\n<thead>\n<tr class=\"row-1\">\n\t<th class=\"column-1\">Option<\/th><th class=\"column-2\">max. hosts<\/th><th class=\"column-3\">max. VMs<\/th><th class=\"column-4\">appliance CPUs<\/th><th class=\"column-5\">appliance Memory<\/th>\n<\/tr>\n<\/thead>\n<tbody class=\"row-striping row-hover\">\n<tr class=\"row-2\">\n\t<td class=\"column-1\">tiny<\/td><td class=\"column-2\">10<\/td><td class=\"column-3\">100<\/td><td class=\"column-4\">2<\/td><td class=\"column-5\">8 GB<\/td>\n<\/tr>\n<tr class=\"row-3\">\n\t<td class=\"column-1\">small<\/td><td class=\"column-2\">100<\/td><td class=\"column-3\">1.000<\/td><td class=\"column-4\">4<\/td><td class=\"column-5\">16 GB<\/td>\n<\/tr>\n<tr class=\"row-4\">\n\t<td class=\"column-1\">medium<\/td><td class=\"column-2\">400<\/td><td class=\"column-3\">4.000<\/td><td class=\"column-4\">8<\/td><td class=\"column-5\">24 GB<\/td>\n<\/tr>\n<tr class=\"row-5\">\n\t<td class=\"column-1\">large<\/td><td class=\"column-2\">1.000<\/td><td class=\"column-3\">10.000<\/td><td class=\"column-4\">16<\/td><td class=\"column-5\">32 GB<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<!-- #tablepress-9 from cache -->\n<p>Note that the <em>hostname<\/em> parameter in the <em>network<\/em> section needs to have a <strong>forward and reverse DNS entry<\/strong> (see <a href=\"https:\/\/www.vmware.com\/files\/pdf\/techpaper\/vmware-vcenter-server6-deployment-guide.pdf\">VMware vCenter server 6 deployment guide<\/a>) to work. An <strong>IP address<\/strong> is also fine though.<\/p>\n<p>After editing the json file to reflect your configuration you can deploy the vCenter appliance by running <code>vcsa-cli-installer\/lin64\/vcsa-deploy path_to_config_file.json --accept-eula<\/code><\/p>\n<pre class=\"brush: bash; collapse: true; light: false; title: ; toolbar: true; notranslate\" title=\"\">\r\n# vcsa-cli-installer\/lin64\/vcsa-deploy ~\/vcenter.json --accept-eula\r\nPerforming basic template verification...\r\nStarting vCenter Server Appliance installer to deploy\r\n&quot;vCenter-Server-Appliance&quot;...\r\nThis appliance is a vCenter Server instance with an embedded Platform Services\r\nController.\r\nSee \/tmp\/vcsaCliInstaller-2016-03-08-15-06-xXUT2j\/vcsa-cli-installer.log for the\r\ninstaller logs.\r\nRun the installer with &quot;-v&quot; or &quot;--verbose&quot; to log detailed information\r\nRunning OVF Tool to deploy the OVF...\r\nOpening vCenter Server Appliance image: \/mnt\/vcsa\/vmware-vcsa\r\nOpening VI target: vi:\/\/root@esxihost:443\/\r\nDeploying to VI: vi:\/\/root@esxihost:443\/\r\n\r\nProgress: 99%\r\nTransfer Completed\r\nPowering on VM: vCenter-Server-Appliance\r\n\r\nProgress: 98%\r\nPower On completed.\r\nWaiting for IP address...\r\nReceived IP address: 172.30.0.23\r\n\r\nInstalling services...\r\nvCSA firstboot: Progress: 5% Setting up storage\r\nvCSA firstboot: Progress: 50% Installing RPMs\r\nvCSA firstboot: Progress: 55% Installed\r\noracle-instantclient11.2-odbc-11.2.0.2.0.x86_64.rpm\r\nvCSA firstboot: Progress: 63% Installed rvc_1.4.0-3196809_x86_64.rpm\r\nvCSA firstboot: Progress: 64% Installed\r\nVMware-rhttpproxy-6.0.0-3339084.x86_64.rpm\r\nvCSA firstboot: Progress: 65% Installed\r\nvmware-certificate-server-6.0.0.2457-3242066.x86_64.rpm\r\nvCSA firstboot: Progress: 66% Installed\r\nvmware-identity-sts-6.0.0.6360-3208448.noarch.rpm\r\nvCSA firstboot: Progress: 67% Installed\r\nVMware-cis-license-6.0.0-3242064.x86_64.rpm\r\nvCSA firstboot: Progress: 70% Installed\r\nvmware-esx-netdumper-6.0.0-0.0.2981910.i386.rpm\r\nvCSA firstboot: Progress: 73% Installed\r\nVMware-Postgres-9.3.9.0-2921310.x86_64.rpm\r\nvCSA firstboot: Progress: 77% Installed\r\nVMware-Postgres-plpython-9.3.9.0-2921310.x86_64.rpm\r\nvCSA firstboot: Progress: 79% Installed\r\nVMware-Postgres-client-jdbc-9.3.9.0-2921310.noarch.rpm\r\nvCSA firstboot: Progress: 80% Installed VMware-invsvc-6.0.0-3242064.x86_64.rpm\r\nvCSA firstboot: Progress: 81% Installed VMware-vpxd-6.0.0-3339084.x86_64.rpm\r\nvCSA firstboot: Progress: 81% Installed\r\nVMware-vpxd-client-6.0.0-3339084.x86_64.rpm\r\nvCSA firstboot: Progress: 83% Installed\r\nVMware-vpxd-vctop-6.0.0-3339084.x86_64.rpm\r\nvCSA firstboot: Progress: 84% Installed\r\nVMware-cloudvm-vimtop-6.0.0-3339084.x86_64.rpm\r\nvCSA firstboot: Progress: 85% Installed ipxe-1.0.0-1.2882051.vmw.i686.rpm\r\nvCSA firstboot: Progress: 86% Installed\r\nvmware-autodeploy-6.0.0-0.0.3253919.noarch.rpm\r\nvCSA firstboot: Progress: 86% Installed VMware-sps-6.0.0-3339084.x86_64.rpm\r\nvCSA firstboot: Progress: 87% Installed VMware-vdcs-6.0.0-3242353.x86_64.rpm\r\nvCSA firstboot: Progress: 89% Installed\r\nVMware-vsanmgmt-6.0.0-0.1.3339084.x86_64.rpm\r\nvCSA firstboot: Progress: 90% Installed vmware-vsm-6.0.0-3339084.x86_64.rpm\r\nvCSA firstboot: Progress: 90% Installed vsphere-client-6.0.0-3338001.noarch.rpm\r\nvCSA firstboot: Progress: 91% Installed\r\nVMware-perfcharts-6.0.0-3339084.x86_64.rpm\r\nvCSA firstboot: Progress: 95% Configuring the machine\r\nServices installations succeeded.\r\nConfiguring services for first time use...\r\nvCSA firstboot: Progress: 3% Starting VMware Authentication Framework...\r\nvCSA firstboot: Progress: 10% Starting VMware Identity Management Service...\r\nvCSA firstboot: Progress: 17% Starting VMware Component Manager...\r\nvCSA firstboot: Progress: 20% Starting VMware License Service...\r\nvCSA firstboot: Progress: 24% Starting VMware Platform Services Controller\r\nClient...\r\nvCSA firstboot: Progress: 27% Starting VMware Service Control Agent...\r\nvCSA firstboot: Progress: 31% Starting VMware vAPI Endpoint...\r\nvCSA firstboot: Progress: 34% Starting VMware System and Hardware Health\r\nManager...\r\nvCSA firstboot: Progress: 37% Starting VMware Appliance Management Service...\r\nvCSA firstboot: Progress: 44% Starting VMware Common Logging Service...\r\nvCSA firstboot: Progress: 48% Starting VMware Postgres...\r\nvCSA firstboot: Progress: 55% Starting VMware Inventory Service...\r\nvCSA firstboot: Progress: 58% Starting VMware Message Bus Configuration\r\nService...\r\nvCSA firstboot: Progress: 63% Starting VMware vSphere Web Client...\r\nvCSA firstboot: Progress: 64% Starting VMware vSphere Web Client...\r\nvCSA firstboot: Progress: 65% Starting VMware vSphere Web Client...\r\nvCSA firstboot: Progress: 68% Starting VMware ESX Agent Manager...\r\nvCSA firstboot: Progress: 72% Starting VMware vSphere Auto Deploy Waiter...\r\nvCSA firstboot: Progress: 75% Starting VMware vSphere Profile-Driven Storage\r\nService...\r\nvCSA firstboot: Progress: 79% Starting VMware Content Library Service...\r\nvCSA firstboot: Progress: 82% Starting VMware vCenter Workflow Manager...\r\nvCSA firstboot: Progress: 89% Starting VMware vService Manager...\r\nvCSA firstboot: Progress: 93% Starting VMware Performance Charts...\r\nvCSA firstboot: Progress: 96% Starting vsphere-client-postinstall...\r\nFirst time configuration succeeded.\r\nvCenter Server Appliance installer finished deploying\r\n&quot;vCenter-Server-Appliance&quot;.\r\nThis appliance is a vCenter Server instance with an embedded Platform Services\r\nController.\r\n    System Name: 172.30.0.97\r\n    Log in as: Administrator@vsphere.local\r\nFinished successfully.\r\n<\/pre>\n<p>You should now be able to long into the vSphere Web Client with <strong><em>Administrator@vsphere.local<\/em><\/strong> as username and the password you specified in the json file<\/p>\n<div id=\"attachment_2225\" style=\"width: 1047px\" class=\"wp-caption aligncenter\"><a data-rokbox href=\"wordpress\/wp-content\/uploads\/2016\/03\/vSphereWebClient.png\"><img decoding=\"async\" aria-describedby=\"caption-attachment-2225\" src=\"wordpress\/wp-content\/uploads\/2016\/03\/vSphereWebClient.png\" alt=\"\" \/><\/a><p id=\"caption-attachment-2225\" class=\"wp-caption-text\">vSphere Web Client<\/p><\/div>\n<p>You can safely ignore the warning about the browser-OS combination.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Up to version 5.5 a vCenter appliance was usually deployed by importing the corresponding ovf template that could be downloaded from the VMware website. That process changed with version 6.0 since there is no longer an ovf template. Instead, VMWare provides and ISO image that contains the necessary data and tools to deploy a vCenter appliance, even directly from the&#8230; <a href=\"https:\/\/possiblelossofprecision.net\/?p=2207\">Read more &raquo;<\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[12],"class_list":["post-2207","post","type-post","status-publish","format-standard","hentry","category-uncategorized","tag-vmware"],"_links":{"self":[{"href":"https:\/\/possiblelossofprecision.net\/index.php?rest_route=\/wp\/v2\/posts\/2207","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/possiblelossofprecision.net\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/possiblelossofprecision.net\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/possiblelossofprecision.net\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/possiblelossofprecision.net\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=2207"}],"version-history":[{"count":19,"href":"https:\/\/possiblelossofprecision.net\/index.php?rest_route=\/wp\/v2\/posts\/2207\/revisions"}],"predecessor-version":[{"id":2231,"href":"https:\/\/possiblelossofprecision.net\/index.php?rest_route=\/wp\/v2\/posts\/2207\/revisions\/2231"}],"wp:attachment":[{"href":"https:\/\/possiblelossofprecision.net\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=2207"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/possiblelossofprecision.net\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=2207"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/possiblelossofprecision.net\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=2207"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}