{"id":13502,"date":"2015-08-05T10:00:00","date_gmt":"2015-08-05T08:00:00","guid":{"rendered":"http:\/\/nolabnoparty.com\/?p=13502"},"modified":"2023-07-16T11:25:00","modified_gmt":"2023-07-16T09:25:00","slug":"vmware-esxi-5-5-upgrade-to-6-0-with-cli","status":"publish","type":"post","link":"https:\/\/nolabnoparty.com\/en\/vmware-esxi-5-5-upgrade-to-6-0-with-cli\/","title":{"rendered":"VMware ESXi 5.5 upgrade to 6.0 with CLI"},"content":{"rendered":"

\"esxi55upg60cli01\"<\/p>\n

When the vSphere Update Manager is not available, the ESXi 5.5 upgrade to 6.0 can be performed using the CLI commands.<\/p>\n

If you work with a single host or VUM is not available to perform the \"easy way\" upgrade, esxcli commands<\/strong> allow the administrators to upgrade the hypervisor directly from the command line using the ESXi Offline Bundle<\/strong>\u00a0image.<\/p>\n

<\/p>\n

From VMware website download<\/a> the ESXi 6.0.0b Offline Bundle<\/strong> file.<\/p>\n

\"esxi55upg60cli02\"<\/p>\n

 <\/p>\n

Upload image to the datastore<\/h2>\n

To allow the upgrade, you need to upload the Offline Bundle file to a datastore reachable by the ESXi.<\/p>\n

Open the vSphere Client and go to the Summary<\/strong> tab, right click the datastore to use and select Browse Datastore<\/strong> option. Note the current ESXi version 5.5.0, 2718055<\/strong>.<\/p>\n

\"esxi55upg60cli03\"<\/p>\n

Click the Upload icon<\/strong> and select Upload File<\/strong> option.<\/p>\n

\"esxi55upg60cli04\"<\/p>\n

Select the Offline Bundle image and click Open<\/strong>.<\/p>\n

\"esxi55upg60cli05\"<\/p>\n

Click Yes<\/strong> to proceed.<\/p>\n

\"esxi55upg60cli06\"<\/p>\n

The file is being uploaded to the datastore.<\/p>\n

\"esxi55upg60cli07\"<\/p>\n

When the upload is complete, close the Datastore Browser<\/strong>.<\/p>\n

\"esxi55upg60cli08\"<\/p>\n

Shutdown the active virtual machines and put the host in Maintenance Mode<\/strong>. Right click the host and select Enter Maintenance Mode<\/strong> option.<\/p>\n

\"esxi55upg60cli09\"<\/p>\n

The host is now in Maintenance Mode<\/strong>.<\/p>\n

\"esxi55upg60cli10\"<\/p>\n

 <\/p>\n

Upgrade the host<\/h2>\n

To perform the upgrade, the software profile update<\/strong> command is used to updates existing VIBs with the corresponding VIBs from the specified profile but does not affect other VIBs installed<\/strong> on the target server.<\/p>\n

Connect the ESXi via SSH<\/strong> (SSH must be enabled) and set the firewall rules for httpClient<\/strong> running the command:<\/p>\n

~ # esxcli network firewall ruleset set -e true -r httpClient<\/span><\/p>\n

\"esxi55upg60cli11\"<\/p>\n

The correct update version is required to execute the command.\u00a0List the available ESXi 6.0 updates<\/strong>\u00a0(you need the latest that ends in \"standard\") running the command:<\/p>\n

~ # esxcli software sources profile list -d https:\/\/hostupdate.vmware.com\/software\/VUM\/PRODUCTION\/main\/vmw-depot-index.xml | grep ESXi-6<\/span><\/p>\n

\"esxi55upg60cli12\"<\/p>\n

Identified the correct version<\/strong> (in the example ESXi-6.0.0-20150704001-standard<\/em>), run the command:<\/p>\n

esxcli software profile update -d <path>\/<volume_name>\/<image_name> -p <profile_name><\/p><\/blockquote>\n

Pay attention to run the software profile update<\/strong> command because software profile install<\/strong> overwrites drivers that the ESXi host needs.<\/p>\n

~ # esxcli software profile update -d \/vmfs\/volumes\/ts421_lun06_raid5\/<\/span>ESXi600-201507001-OfflineBundle.zip -p ESXi-6.0.0-20150704001-standard<\/span><\/p>\n

\"esxi55upg60cli13\"<\/p>\n

Reboot<\/strong> the host to complete the upgrade.<\/p>\n

\"esxi55upg60cli14\"<\/p>\n

When the ESXi has rebooted, right click the host\u00a0and select Exit Maintenance Mode<\/strong>.<\/p>\n

\"esxi55upg60cli15\"<\/p>\n

 <\/p>\n

Fix NICs not detected<\/h2>\n

The ESXi has been upgraded to version 6.0.0-2809209<\/strong> but in the example the datastores are not connected to the host.<\/p>\n

\"esxi55upg60cli16\"<\/p>\n

Checking the Network configuration<\/strong>, the iSCSI VMKernel port doesn't have any NIC attached. The adapter hasn't been detected during the upgrade because the NIC installed in the host is a Realtek 8168<\/strong> no longer supported.<\/p>\n

\"esxi55upg60cli17\"<\/p>\n

 <\/p>\n

Install missing drivers<\/h4>\n

To fix the problem, Andreas Peetz<\/a> made a procedure to inject the drivers directly into the host.<\/p>\n

Run the following command to set the acceptance<\/strong> of the host to \u201ccommunity supported\u201d<\/p>\n

~ # esxcli software acceptance set --level=CommunitySupported<\/span><\/p>\n

\"esxi55upg60cli18\"<\/p>\n

Install the missing driver<\/strong> by running the command:<\/p>\n

~ # esxcli software vib install -d https:\/\/vibsdepot.v-front.de -n net55-r8168<\/span><\/p>\n

\"esxi55upg60cli19\"<\/p>\n

Reboot<\/strong> the host.<\/p>\n

\"esxi55upg60cli20\"<\/p>\n

After reboot, the host is able to detect the missing NIC<\/strong>.<\/p>\n

\"esxi55upg60cli21\"<\/p>\n

With the working NIC, the datastores connections<\/strong>\u00a0are restored successfully.<\/p>\n

\"esxi55upg60cli22\"<\/p>\n

The ESXi upgrade is now complete. Previous configuration is retained<\/strong> and the hypervisor is fully functional.<\/p>\n

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

When the vSphere Update Manager is not available, the ESXi 5.5 upgrade to 6.0 can be performed using the CLI commands. If you work with a single host or VUM is not available to perform the \"easy way\" upgrade, esxcli commands allow the administrators to upgrade the hypervisor directly from the command line using the ESXi Offline Bundle\u00a0image.<\/p>\n","protected":false},"author":3,"featured_media":13480,"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":[271,580,876],"class_list":["post-13502","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-vmware-en","category-vsphere-en","tag-cli","tag-esxi-en","tag-upgrade-en","has_thumb"],"_links":{"self":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/13502","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=13502"}],"version-history":[{"count":0,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/13502\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media\/13480"}],"wp:attachment":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media?parent=13502"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/categories?post=13502"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/tags?post=13502"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}