{"id":35084,"date":"2018-10-16T09:00:05","date_gmt":"2018-10-16T07:00:05","guid":{"rendered":"https:\/\/nolabnoparty.com\/?p=35084"},"modified":"2023-07-16T11:30:31","modified_gmt":"2023-07-16T09:30:31","slug":"vsphere-6-7-upgrade-vcsa-6-5-to-6-7-pt-2","status":"publish","type":"post","link":"https:\/\/nolabnoparty.com\/en\/vsphere-6-7-upgrade-vcsa-6-5-to-6-7-pt-2\/","title":{"rendered":"vSphere 6.7 upgrade vCSA 6.5 to 6.7 - pt.2"},"content":{"rendered":"<p><img decoding=\"async\" class=\"aligncenter wp-image-35242 size-full\" title=\"vsphere-67-upgrade-vcsa-01\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/10\/vsphere-67-upgrade-vcsa-01.jpg\" alt=\"vsphere-67-upgrade-vcsa-01\" width=\"602\" height=\"202\" \/><\/p>\n<p>If your vSphere environment is running version 6.0 or above, you can easily migrate the vCenter Server to version 6.7 with the <strong>migration tool<\/strong> provided with vSphere 6.7.<\/p>\n<p>Compared to a\u00a0<a href=\"https:\/\/nolabnoparty.com\/en\/vsphere-6-7-install-vcsa-6-7-pt-1\/\">fresh vCSA installation<\/a>, the upgrade is the preferred method to use for\u00a0<strong>complex environments<\/strong>\u00a0or where\u00a0<strong>time consuming settings<\/strong>\u00a0have been configured in the original vCenter Server. Currently the direct vCSA upgrade to version 6.7 is\u00a0<strong>supported from vCSA 6.0 or 6.5 U1<\/strong>\u00a0but it was already announced the upcoming vCSA 6.7 U1 update release will support the upgrade also from <a href=\"https:\/\/nolabnoparty.com\/en\/vmware-vsphere-6-5-update-2-available\/\">version 6.5 U2<\/a>.<!--more--><\/p>\n<p>Although the upgrade process doesn't delete the original vCSA, before proceeding with the upgrade make sure you have a <strong>working backup available<\/strong> to restore the original vCSA in case of problems.<\/p>\n<p>&nbsp;<\/p>\n<h2>Blog Series<\/h2>\n<p><a href=\"https:\/\/nolabnoparty.com\/en\/vsphere-6-7-install-vcsa-6-7-pt-1\/\">vSphere 6.7 install vCSA 6.7 - pt.1<\/a><br \/>\nvSphere 6.7 upgrade vCSA 6.5 to 6.7 - pt.2<br \/>\n<a href=\"https:\/\/nolabnoparty.com\/en\/vsphere-6-7-upgrade-esxi-6-5-to-6-7-pt-3\/\">vSphere 6.7 upgrade ESXi 6.5 to 6.7 - pt.3<\/a><br \/>\n<a href=\"https:\/\/nolabnoparty.com\/en\/vsphere-6-7-upgrade-vsan-6-6-to-6-7-pt-4\/\">vSphere 6.7 upgrade vSAN 6.6 to 6.7 - pt.4<\/a><\/p>\n<p>&nbsp;<\/p>\n<h2>Pre-requisites<\/h2>\n<p>Before proceeding with the upgrade, the vSphere DRS feature in the source vCSA must be <strong>disabled or set to manual<\/strong> to avoid issue with the vCSA during the upgrade procedure.<\/p>\n<p>From the vSphere Web Client, right click the cluster and select <strong>Settings<\/strong>. Access the <strong>vSphere DRS<\/strong> section under <strong>Services<\/strong> and set <strong>DRS Automation<\/strong> to\u00a0<strong>Manual<\/strong> then click <strong>OK<\/strong> to confirm.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-35244 size-large\" title=\"vsphere-67-upgrade-vcsa-02\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/10\/vsphere-67-upgrade-vcsa-02-600x358.jpg\" alt=\"vsphere-67-upgrade-vcsa-02\" width=\"600\" height=\"358\" \/><\/p>\n<p>When the vSphere DRS has been set to Manual you are <strong>ready to begin<\/strong> the upgrade procedure.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-35246 size-large\" title=\"vsphere-67-upgrade-vcsa-03\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/10\/vsphere-67-upgrade-vcsa-03-600x195.jpg\" alt=\"vsphere-67-upgrade-vcsa-03\" width=\"600\" height=\"195\" \/><\/p>\n<p>&nbsp;<\/p>\n<h2>Upgrade the vCSA<\/h2>\n<p>The upgrade to version 6.7 is a two stage process:<\/p>\n<ul>\n<li><strong>Stage 1<\/strong> - Deployment of the new appliance<\/li>\n<li><strong>Stage 2<\/strong> - Configuration of the vCSA<\/li>\n<\/ul>\n<h4>Stage 1 - Deploy the appliance<\/h4>\n<p>Mount the ISO file downloaded from <a href=\"https:\/\/my.vmware.com\/web\/vmware\/downloads\" target=\"_blank\" rel=\"noopener\">VMware website<\/a> and run the installer from the supported OSs (Windows, Linux, MacOS) by double clicking the <em>installer.exe<\/em> file.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-35248 size-large\" title=\"vsphere-67-upgrade-vcsa-04\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/10\/vsphere-67-upgrade-vcsa-04-600x345.jpg\" alt=\"vsphere-67-upgrade-vcsa-04\" width=\"600\" height=\"345\" \/><\/p>\n<p>From the Deploy appliance wizard, click <strong>Upgrade<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-35250 size-large\" title=\"vsphere-67-upgrade-vcsa-05\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/10\/vsphere-67-upgrade-vcsa-05-600x413.jpg\" alt=\"vsphere-67-upgrade-vcsa-05\" width=\"600\" height=\"413\" \/><\/p>\n<p>Click <strong>Next<\/strong> to begin the procedure.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-35252 size-large\" title=\"vsphere-67-upgrade-vcsa-06\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/10\/vsphere-67-upgrade-vcsa-06-600x413.jpg\" alt=\"vsphere-67-upgrade-vcsa-06\" width=\"600\" height=\"413\" \/><\/p>\n<p>Accept the EULA then click <strong>Next<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-35254 size-large\" title=\"vsphere-67-upgrade-vcsa-07\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/10\/vsphere-67-upgrade-vcsa-07-600x413.jpg\" alt=\"vsphere-67-upgrade-vcsa-07\" width=\"600\" height=\"413\" \/><\/p>\n<p>Enter the source <strong>Appliance FQDN or IP Address<\/strong>\u00a0then click <strong>Connect to source<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-35256 size-large\" title=\"vsphere-67-upgrade-vcsa-08\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/10\/vsphere-67-upgrade-vcsa-08-600x286.jpg\" alt=\"vsphere-67-upgrade-vcsa-08\" width=\"600\" height=\"286\" \/><\/p>\n<p>Specify the <strong>SSO User name<\/strong>, <strong>SSO password<\/strong> and the <strong>Appliance (OS) root password<\/strong>. Enter also the <strong>ESXi host<\/strong> where the source vCSA resides. Click <strong>Next<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-35258 size-large\" title=\"vsphere-67-upgrade-vcsa-09\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/10\/vsphere-67-upgrade-vcsa-09-600x408.jpg\" alt=\"vsphere-67-upgrade-vcsa-09\" width=\"600\" height=\"408\" \/><\/p>\n<p>Click <strong>Yes<\/strong> to accept the certificate.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-35260 size-full\" title=\"vsphere-67-upgrade-vcsa-10\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/10\/vsphere-67-upgrade-vcsa-10.jpg\" alt=\"vsphere-67-upgrade-vcsa-10\" width=\"578\" height=\"494\" \/><\/p>\n<p>Specify the target ESXi host where to deploy the new appliance and enter the credentials. Click <strong>Next<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-35263 size-large\" title=\"vsphere-67-upgrade-vcsa-11\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/10\/vsphere-67-upgrade-vcsa-11-600x408.jpg\" alt=\"vsphere-67-upgrade-vcsa-11\" width=\"600\" height=\"408\" \/><\/p>\n<p>Click <strong>Yes<\/strong> to accept the certificate from the specified host.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-35265 size-full\" title=\"vsphere-67-upgrade-vcsa-12\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/10\/vsphere-67-upgrade-vcsa-12.jpg\" alt=\"vsphere-67-upgrade-vcsa-12\" width=\"578\" height=\"374\" \/><\/p>\n<p>Enter the <strong>VM name<\/strong> and the <strong>root password<\/strong>. Click <strong>Next<\/strong> to continue.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-35267 size-large\" title=\"vsphere-67-upgrade-vcsa-13\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/10\/vsphere-67-upgrade-vcsa-13-600x408.jpg\" alt=\"vsphere-67-upgrade-vcsa-13\" width=\"600\" height=\"408\" \/><\/p>\n<p>Based on your environment, specify the <strong>Deployment size<\/strong> and <strong>Storage size<\/strong> then click <strong>Next<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-35269 size-large\" title=\"vsphere-67-upgrade-vcsa-14\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/10\/vsphere-67-upgrade-vcsa-14-600x408.jpg\" alt=\"vsphere-67-upgrade-vcsa-14\" width=\"600\" height=\"408\" \/><\/p>\n<p>Select the datastore to use and click <strong>Next<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-35271 size-large\" title=\"vsphere-67-upgrade-vcsa-15\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/10\/vsphere-67-upgrade-vcsa-15-600x408.jpg\" alt=\"vsphere-67-upgrade-vcsa-15\" width=\"600\" height=\"408\" \/><\/p>\n<p>Configure the required network parameters. The <strong>Temporary IP address<\/strong> is used only during the deployment process, production IP address will be the <strong>same as the source appliance<\/strong>. Click <strong>Next<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-35273 size-large\" title=\"vsphere-67-upgrade-vcsa-16\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/10\/vsphere-67-upgrade-vcsa-16-600x408.jpg\" alt=\"vsphere-67-upgrade-vcsa-16\" width=\"600\" height=\"408\" \/><\/p>\n<p>Click <strong>Finish<\/strong> to begin the deployment.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-35275 size-large\" title=\"vsphere-67-upgrade-vcsa-17\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/10\/vsphere-67-upgrade-vcsa-17-600x408.jpg\" alt=\"vsphere-67-upgrade-vcsa-17\" width=\"600\" height=\"408\" \/><\/p>\n<p>The deployment of the new appliance is being performed.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-35277 size-large\" title=\"vsphere-67-upgrade-vcsa-18\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/10\/vsphere-67-upgrade-vcsa-18-600x149.jpg\" alt=\"vsphere-67-upgrade-vcsa-18\" width=\"600\" height=\"149\" \/><\/p>\n<p>When the deployment has been completed successfully, click <strong>Continue<\/strong> to proceed with Stage 2. At this point you could stop the upgrade procedure and <strong>resume it later<\/strong>\u00a0accessing the <strong>vCSA Management interface<\/strong> at the address <span style=\"color: #0000ff;\">https:\/\/IP_temp_address:5480<\/span>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-35281 size-large\" title=\"vsphere-67-upgrade-vcsa-19\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/10\/vsphere-67-upgrade-vcsa-19-600x219.jpg\" alt=\"vsphere-67-upgrade-vcsa-19\" width=\"600\" height=\"219\" \/><\/p>\n<p>Take a <strong>snapshot of the new vCSA<\/strong> to resume the deployment from this point in case Stage 2 fails for some reasons.<\/p>\n<p>&nbsp;<\/p>\n<h4>Stage 2 - Configuration of the vCSA<\/h4>\n<p>Completed Stage 1, click <strong>Next<\/strong> to begin Stage 2 of the deployment procedure.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-35283 size-large\" title=\"vsphere-67-upgrade-vcsa-20\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/10\/vsphere-67-upgrade-vcsa-20-600x414.jpg\" alt=\"vsphere-67-upgrade-vcsa-20\" width=\"600\" height=\"414\" \/><\/p>\n<p>Enter the required parameters to connect to source vCenter and click <strong>Next<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-35285 size-large\" title=\"vsphere-67-upgrade-vcsa-21\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/10\/vsphere-67-upgrade-vcsa-21-600x414.jpg\" alt=\"vsphere-67-upgrade-vcsa-21\" width=\"600\" height=\"414\" \/><\/p>\n<p>Before migrating the configuration from the source vCenter Server, a <strong>pre-upgrade check<\/strong> is performed by the installer.<\/p>\n<p>You may receive warnings about the following:<\/p>\n<ul>\n<li>The cluster where the source vCenter Server is located must have the vSphere DRS feature <strong>not set to Fully Automated<\/strong><\/li>\n<li><strong>Baselines not compatible<\/strong> with Update Manager 6.7 won't be copied<\/li>\n<li>Warnings about vCenter Server extensions that cannot be migrated<\/li>\n<li>If the source appliance has multiple NICs configured, only the network information related to\u00a0<strong>Eth0 will be preserved<\/strong><\/li>\n<\/ul>\n<p>Fix the detected\u00a0issues that may prevent the upgrade (in the worse case you need to redeploy the vCSA). Click <strong>Close<\/strong> to proceed.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-35287 size-large\" title=\"vsphere-67-upgrade-vcsa-22\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/10\/vsphere-67-upgrade-vcsa-22-600x386.jpg\" alt=\"vsphere-67-upgrade-vcsa-22\" width=\"600\" height=\"386\" \/><\/p>\n<p>Select the data to be migrated and click <strong>Next<\/strong>. Available data migration options are the following:<\/p>\n<ul>\n<li>Configuration<\/li>\n<li>Configuration + historical data (events and tasks)<\/li>\n<li>Configuration + historical data (events, tasks and performance metrics)<\/li>\n<\/ul>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-35289 size-large\" title=\"vsphere-67-upgrade-vcsa-23\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/10\/vsphere-67-upgrade-vcsa-23-600x414.jpg\" alt=\"vsphere-67-upgrade-vcsa-23\" width=\"600\" height=\"414\" \/><\/p>\n<p>Optionally you can select the\u00a0<strong>Join the VMware's CEIP<\/strong> option. Click <strong>Next<\/strong>\u00a0to begin data migration.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-35291 size-large\" title=\"vsphere-67-upgrade-vcsa-24\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/10\/vsphere-67-upgrade-vcsa-24-600x414.jpg\" alt=\"vsphere-67-upgrade-vcsa-24\" width=\"600\" height=\"414\" \/><\/p>\n<p>Click <strong>OK<\/strong> to proceed with the upgrade.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-35293 size-full\" title=\"vsphere-67-upgrade-vcsa-25\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/10\/vsphere-67-upgrade-vcsa-25.jpg\" alt=\"vsphere-67-upgrade-vcsa-25\" width=\"522\" height=\"302\" \/><\/p>\n<p>In step 1 <strong>data are copied<\/strong> from the source vCenter Server.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-35295 size-large\" title=\"vsphere-67-upgrade-vcsa-26\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/10\/vsphere-67-upgrade-vcsa-26-600x355.jpg\" alt=\"vsphere-67-upgrade-vcsa-26\" width=\"600\" height=\"355\" \/><\/p>\n<p>During step 2 target vCSA is being <strong>configured and services are started<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-35297 size-large\" title=\"vsphere-67-upgrade-vcsa-27\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/10\/vsphere-67-upgrade-vcsa-27-600x355.jpg\" alt=\"vsphere-67-upgrade-vcsa-27\" width=\"600\" height=\"355\" \/><\/p>\n<p>Final step <strong>import copied data<\/strong> to the new vCSA.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-35299 size-large\" title=\"vsphere-67-upgrade-vcsa-28\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/10\/vsphere-67-upgrade-vcsa-28-600x355.jpg\" alt=\"vsphere-67-upgrade-vcsa-28\" width=\"600\" height=\"355\" \/><\/p>\n<p>Some messages are displayed to inform you about <strong>changes you should do in your environment<\/strong> after the deployment. Click <strong>Close<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-35301 size-large\" title=\"vsphere-67-upgrade-vcsa-29\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/10\/vsphere-67-upgrade-vcsa-29-600x386.jpg\" alt=\"vsphere-67-upgrade-vcsa-29\" width=\"600\" height=\"386\" \/><\/p>\n<p>When the upgrade has completed successfully, click <strong>Close<\/strong> to exit the wizard. The new vCSA is now reachable at the <strong>same DNS name or IP address<\/strong> of the source vCenter Server.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-35303 size-large\" title=\"vsphere-67-upgrade-vcsa-30\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/10\/vsphere-67-upgrade-vcsa-30-600x355.jpg\" alt=\"vsphere-67-upgrade-vcsa-30\" width=\"600\" height=\"355\" \/><\/p>\n<p>After logging to the new vCSA (the HTML5 client works more much better now and provides most of available features) you can notice the <strong>old vCenter Server still available<\/strong> and in a<strong> powered off\u00a0state<\/strong>\u00a0and of course the just deployed vCSA. The <strong>IP address didn't change<\/strong> and it is the same as the source vCenter Server.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-35305 size-large\" title=\"vsphere-67-upgrade-vcsa-31\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/10\/vsphere-67-upgrade-vcsa-31-600x399.jpg\" alt=\"vsphere-67-upgrade-vcsa-31\" width=\"600\" height=\"399\" \/><\/p>\n<p>The <strong>vSphere DRS<\/strong> feature in the cluster can be re-configured to <strong>Fully Automated<\/strong>, if you use this configuration.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-35307 size-large\" title=\"vsphere-67-upgrade-vcsa-32\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/10\/vsphere-67-upgrade-vcsa-32-600x396.jpg\" alt=\"vsphere-67-upgrade-vcsa-32\" width=\"600\" height=\"396\" \/><\/p>\n<p>The vCSA is now running the new version 6.7. To <strong>take benefit of new features<\/strong>\u00a0available in vSphere 6.7, next step to perform is the upgrade of the ESXi hosts present in the infrastructure. <a href=\"https:\/\/nolabnoparty.com\/en\/vsphere-6-7-upgrade-esxi-6-5-to-6-7-pt-3\/\">Part 3<\/a> will cover the <strong>ESXi hosts upgrade<\/strong> using VUM.<\/p>\n<p><img decoding=\"async\" title=\"signature\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/images\/firma.jpg\" alt=\"signature\" \/><\/p>\n","protected":false},"excerpt":{"rendered":"<p>If your vSphere environment is running version 6.0 or above, you can easily migrate the vCenter Server to version 6.7 with the migration tool provided with vSphere 6.7. Compared to a\u00a0fresh vCSA installation, the upgrade is the preferred method to use for\u00a0complex environments\u00a0or where\u00a0time consuming settings\u00a0have been configured in the original vCenter Server. Currently the direct vCSA upgrade to version 6.7 is\u00a0supported from vCSA 6.0 or 6.5 U1\u00a0but it was already announced the upcoming vCSA 6.7 U1 update release will support the upgrade also from version 6.5 U2.<\/p>\n","protected":false},"author":3,"featured_media":35242,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"rop_custom_images_group":[],"rop_custom_messages_group":[],"rop_publish_now":"initial","rop_publish_now_accounts":{"linkedin_93tdZWzMZc_93tdZWzMZc":"","facebook_2879994398731222_17841400390232720":"","twitter_113568041_113568041":"","mastodon_115463926174894442_115463926174894442":""},"rop_publish_now_history":[],"rop_publish_now_status":"pending","footnotes":""},"categories":[903,2701],"tags":[876,1551,1879],"class_list":["post-35084","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-vmware-en","category-vsphere-en","tag-upgrade-en","tag-vcsa","tag-vsphere-6-7","has_thumb"],"_links":{"self":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/35084","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/comments?post=35084"}],"version-history":[{"count":0,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/35084\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media\/35242"}],"wp:attachment":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media?parent=35084"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/categories?post=35084"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/tags?post=35084"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}