{"id":35079,"date":"2018-10-23T09:00:32","date_gmt":"2018-10-23T07:00:32","guid":{"rendered":"https:\/\/nolabnoparty.com\/?p=35079"},"modified":"2023-07-16T11:30:31","modified_gmt":"2023-07-16T09:30:31","slug":"vsphere-6-7-upgrade-esxi-6-5-to-6-7-pt-3","status":"publish","type":"post","link":"https:\/\/nolabnoparty.com\/en\/vsphere-6-7-upgrade-esxi-6-5-to-6-7-pt-3\/","title":{"rendered":"vSphere 6.7 upgrade ESXi 6.5 to 6.7 - pt.3"},"content":{"rendered":"

\"vsphere-67-upgrade-esxi-01\"<\/p>\n

After upgrading the vCSA, to take benefit of new features<\/strong> provided by vSphere 6.7 you have to upgrade also all ESXi hosts<\/strong> installed in your virtual infrastructure.<\/p>\n

The procedure it's pretty easy and rely on the Update Manager service<\/strong> provided with vSphere 6.7.<\/p>\n

 <\/p>\n

Blog Series<\/h2>\n

vSphere 6.7 install vCSA 6.7 - pt.1<\/a>
\nvSphere 6.7 upgrade vCSA 6.5 to 6.7 - pt.2<\/a>
\nvSphere 6.7 upgrade ESXi 6.5 to 6.7 - pt.3
\nvSphere 6.7 upgrade vSAN 6.6 to 6.7 - pt.4<\/p>\n

 <\/p>\n

Upgrade ESXi 6.5 to 6.7<\/h2>\n

To verify the installed ESXi version<\/strong> in the network, from the vSphere Client go to the\u00a0host's Summary<\/strong> section and check the Hypervisor<\/strong> field.<\/p>\n

\"vsphere-67-upgrade-esxi-02\"<\/p>\n

 <\/p>\n

Create the upgrade baseline<\/h4>\n

A new baseline<\/strong> must be created in the Update Manager service to easily upgrade all ESXi hosts in your network. Click Menu<\/strong> and select Update Manager<\/strong>.<\/p>\n

\"vsphere-67-upgrade-esxi-03\"<\/p>\n

From the Update Manager area, select the ESXi images<\/strong> section and click Import<\/strong>.<\/p>\n

\"vsphere-67-upgrade-esxi-04\"<\/p>\n

Click Browse<\/strong>\u00a0button to select the ESXi 6.7 installer in\u00a0ISO format<\/strong>\u00a0downloaded from VMware website<\/a>.<\/p>\n

\"vsphere-67-upgrade-esxi-05\"<\/p>\n

Selected the correct image version, click Import<\/strong> to import the image in the vCSA.<\/p>\n

\"vsphere-67-upgrade-esxi-06\"<\/p>\n

When the installer has been imported successfully, click New Baseline<\/strong> to create the baseline to apply to the hosts you need to upgrade.<\/p>\n

\"vsphere-67-upgrade-esxi-07\"<\/p>\n

Specify a Name<\/strong> and a Description<\/strong> to better identify the scope of the baseline. Click Next<\/strong>.<\/p>\n

\"vsphere-67-upgrade-esxi-08\"<\/p>\n

Select the previously imported ESXi image<\/strong> and click Next<\/strong>.<\/p>\n

\"vsphere-67-upgrade-esxi-09\"<\/p>\n

Click Finish<\/strong> to create the baseline.<\/p>\n

\"vsphere-67-upgrade-esxi-10\"<\/p>\n

In the Baselines<\/strong> section is now listed the new created baseline .<\/p>\n

\"vsphere-67-upgrade-esxi-11\"<\/p>\n

 <\/p>\n

Attach the baseline<\/h4>\n

Created the baseline needed to upgrade the hosts, you have to attach this baseline to all ESXi you want to upgrade. Select the cluster with the hosts to process and go to Updates<\/strong> section. Click Attach<\/strong>.<\/p>\n

\"vsphere-67-upgrade-esxi-12\"<\/p>\n

Select the correct baseline to attach and click OK<\/strong>.<\/p>\n

\"vsphere-67-upgrade-esxi-13\"<\/p>\n

Click Check Compliance<\/strong> to verify hosts to upgrade.<\/p>\n

\"vsphere-67-upgrade-esxi-14\"<\/p>\n

 <\/p>\n

Remediate hosts<\/h4>\n

Since the host upgrade cannot be staged, click Remediate<\/strong> to proceed with the upgrade.<\/p>\n

\"vsphere-67-upgrade-esxi-15\"<\/p>\n

The installation process begins. Accept the EULA and click OK<\/strong>.<\/p>\n

\"vsphere-67-upgrade-esxi-16\"<\/p>\n

Select the ESXi hosts to upgrade and click OK<\/strong>. You can safely proceed even if you have vSAN cluster<\/strong> configured in place.<\/p>\n

\"vsphere-67-upgrade-esxi-17\"<\/p>\n

The upgrade is being processed.<\/p>\n

\"vsphere-67-upgrade-esxi-18\"<\/p>\n

When the upgrade has completed successfully, all hosts are reported as Compliant<\/strong>.<\/p>\n

\"vsphere-67-upgrade-esxi-19\"<\/p>\n

 <\/p>\n

Troubleshooting<\/h2>\n

After upgrading the first host, the vCSA was unable to reconnect<\/strong> the processed host displaying an error related to the\u00a0Enhanced vMotion Compatibility mode<\/strong>. Not sure why this error, maybe Spectre\/Meltdown CPU microcode fixes somehow may have affected the EVC cluster.<\/p>\n

\"vsphere-67-upgrade-esxi-20\"<\/p>\n

A work around used to continue with upgrade was disabling the VMware EVC<\/strong> feature in the processed cluster and renabling it after connecting all upgraded ESXi hosts.<\/p>\n

\"vsphere-67-upgrade-esxi-21\"<\/p>\n

Disabled the VMware EVC feature, right click the failed host and select Connection > Connect<\/strong>. This time the host was connected successfully to the cluster.<\/p>\n

\"vsphere-67-upgrade-esxi-22\"<\/p>\n

When all upgraded hosts are connected to the cluster, enable the vSphere EVC<\/strong> feature once again.<\/p>\n

\"vsphere-67-upgrade-esxi-23\"<\/p>\n

The ESXi hosts upgrade procedure is now complete. If you have a vSAN cluster configured, the cluster's Summary<\/strong> section reports warnings related to vSAN<\/strong>\u00a0since vSphere 6.7 comes with the new vSAN 6.6 version<\/strong>.<\/p>\n

\"vsphere-67-upgrade-esxi-24\"<\/p>\n

Final step of the overall upgrade procedure consists in the upgrade of the vSAN cluster if configured. Part 4<\/a> will cover vSAN upgrade<\/strong> to finalize the migration to the new version.<\/p>\n

\"signature\"<\/p>\n","protected":false},"excerpt":{"rendered":"

After upgrading the vCSA, to take benefit of new features provided by vSphere 6.7 you have to upgrade also all ESXi hosts installed in your virtual infrastructure. The procedure it's pretty easy and rely on the Update Manager service provided with vSphere 6.7.<\/p>\n","protected":false},"author":3,"featured_media":35314,"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":[580,719,876,1879],"class_list":["post-35079","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-vmware-en","category-vsphere-en","tag-esxi-en","tag-update-manager-en","tag-upgrade-en","tag-vsphere-6-7","has_thumb"],"_links":{"self":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/35079","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=35079"}],"version-history":[{"count":0,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/35079\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media\/35314"}],"wp:attachment":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media?parent=35079"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/categories?post=35079"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/tags?post=35079"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}