Good day! All,
I know we are away behind on our ESXi upgrade still around 5.1 u2. We recently added new G8 HP Blades to our ESXi infrastructure and started with ESXi upgrade from 5.0 to 5.1 U2.
As all these are HP Blades we downloaded a custom ESXi image for HP and re-mediated all the blades for firmware using Update Manager.
We did all this like 3 months ago, as this was small site with about 60 VM's on 4 ESXi blades we never had any performance issue and for some reason we never identified that this site had DRS issue and VM's are not migrating until one day we started to do some VMTools upgrade on the Virtual Machines.
Started to browse on the internet for the error and we found across this article which kind of closely matched to our issue.. So we logged a case, VMware was involved and after going through the logs they confirmed the same..
Now we identified the issue so getting down time was big challenge and VMWARE clearly stated that we need to shutdown all the VM's , upgrade AMS or disabled AMS on the ESXi host to fix the DRS issue.
So getting downtime all business was a daunting task so we checked all the VM's and picked a ESXi host with least number of Virtual Machines running on it... So we took the risk asked the business to give down time for 6 Servers and keeping fingers crossed started to work on the issue.
After Uninstalling and re-installing the updated AMS component to our Surprise guess what VMmotion started to work on that ESXi host.. and this just proved VMWARE wrong :)
I know writing this article would be too late may be someone would have tried something like this or most of them have already upgrade to latest ESXi upgrades.. but still if someone out there who still on 5.1 U2 this article would kind of help them in planning properly and not go shutting down all the VM's.
After the upgrade we started to move VM's across to this ESXi host and started to do the same on other ESXi host one by one and end of the day we achieved this will very minimal downtime.
So this just proves that we should always have a development environment but let me guess ESXi development environment will business spend , leave it for your guys to thing :)
Have a good day!!!!
I know we are away behind on our ESXi upgrade still around 5.1 u2. We recently added new G8 HP Blades to our ESXi infrastructure and started with ESXi upgrade from 5.0 to 5.1 U2.
As all these are HP Blades we downloaded a custom ESXi image for HP and re-mediated all the blades for firmware using Update Manager.
We did all this like 3 months ago, as this was small site with about 60 VM's on 4 ESXi blades we never had any performance issue and for some reason we never identified that this site had DRS issue and VM's are not migrating until one day we started to do some VMTools upgrade on the Virtual Machines.
Started to browse on the internet for the error and we found across this article which kind of closely matched to our issue.. So we logged a case, VMware was involved and after going through the logs they confirmed the same..
Now we identified the issue so getting down time was big challenge and VMWARE clearly stated that we need to shutdown all the VM's , upgrade AMS or disabled AMS on the ESXi host to fix the DRS issue.
So getting downtime all business was a daunting task so we checked all the VM's and picked a ESXi host with least number of Virtual Machines running on it... So we took the risk asked the business to give down time for 6 Servers and keeping fingers crossed started to work on the issue.
After Uninstalling and re-installing the updated AMS component to our Surprise guess what VMmotion started to work on that ESXi host.. and this just proved VMWARE wrong :)
I know writing this article would be too late may be someone would have tried something like this or most of them have already upgrade to latest ESXi upgrades.. but still if someone out there who still on 5.1 U2 this article would kind of help them in planning properly and not go shutting down all the VM's.
After the upgrade we started to move VM's across to this ESXi host and started to do the same on other ESXi host one by one and end of the day we achieved this will very minimal downtime.
So this just proves that we should always have a development environment but let me guess ESXi development environment will business spend , leave it for your guys to thing :)
Have a good day!!!!
No comments:
Post a Comment