In the fourth part of ESXi upgrade from version 5.1 to version 5.5, I will cover Auto Deploy upgrade. Upgrade itself isn’t quite different from creating deployment rule with a new version of ESXi.
You have configured vSphere Auto Deploy and you downloaded latest offline bundle. Since I wrote the first post about upgrade methods VMware released a new version of vSphere – 5.5 Update 1. I used ESXi 5.5 Update 1 Offline Bundle from VMware website.
Upgrade using Auto Deploy
For the sake of simplicity, I use Auto Deploy with stateless caching. In case you missed my earlier posts about how to configure Auto Deploy you can find them here:
At the beginning, I suggest checking what kind of deployment rules you now have in use. You can use PowerCLI command Get-DeployCommand to receive a list of all Auto Deploy related commandlets.
- Please check for existing deploy rules by executing Get-DeployRuleSet.
- With my three running ESXi hosts deployed using Auto Deploy I am using ESXi 5.1 Update 2.
- We have to copy new Offline Bundle to our server where Auto Deploy is installed. In my case I copied it to folder E:\SoftwareDepot and I executed PowerCLI command Add-EsxSoftwareDepot E:\SoftwareDepot\update-from-esxi5.5-5.5_update01.zip.
- After we added offline bundle we can check what kind of profile are available. In order to do it execute command Get-EsxImageProfile |Format-Table
- Now what we will do is simply clone existing profile ESXi-5.5.0-20140302001-standard into our new profile with name ESXi 5.5 U1.
Shell1New-EsxImageProfile -CloneProfile "ESXi-5.5.0-20140302001-standard" -Name "ESXi 5.5 U1" -Vendor "wojcieh.net"
- In order to use our brand new profile with Auto Deploy we have to export it.
Shell1Export-EsxImageProfile -ImageProfile "ESXi 5.5 U1" -ExportToBundle -Filepath E:\SoftwareDepot\ESXi_5.5_U1.zip
- My old deploy rule points to ESXi 5.1 U2 image. You can check your active rule using following command Get-DeployRuleSet.
- I deleted old Auto Deploy rule by executing command Remove-DeployRule -DeployRule ESXi5.5-Normal. It just remove it from active rules – if you want to permanently delete rule you have to add -Delete.
- I created new deploy rule.
Shell1New-DeployRule -name "ESXi5.5" -Item "ESXi 5.5 U1", Cluster, AutoDeployStateless -Pattern "ipv4=10.0.0.150-10.0.0.160"
- After executing New-DeployRule command we have fully functional Auto Deploy with a new ESXi image.
- We just need to activate it by executing command Add-DeployRule -DeployRule “ESXi 5.5”.
- There might be a case that your hosts are still booting using old rule. The reason is simple – Auto Deploy use cache to serve data faster. In order to deploy hosts using latest rule execute the following command
Shell1get-cluster Cluster | get-vmhost | Test-DeployRuleSetCompliance
- As you see on the output of command Auto Deploy detected the difference and fixed cache. On screenshot, you see that two out of three hosts are using latest version 5.5 U1.
My experience and skills have been proven by leading vendor certifications like AWS, Alibaba Cloud, VMware, and Microsoft. I contribute to the IT community and I received VMware vExpert 2014 - 2019, vExpert Pro and VMware vExpert NSX 2017 Award.
My blog wojcieh.net - was voted #76 in Top vBlog 2018 contest!
Do what you love, and you’ll never work another day in your life.
Latest posts by Wojciech Marusiak (see all)
- Top vBlog 2018 is there! - 20 November, 2018
- Zentyal – my new Homelab Swiss Army Knife - 10 October, 2018
- Send VMware backups to the cloud – Altaro Offsite Copies to an Azure Cloud Storage - 18 September, 2018