Background introduction
An enterprise's original 8 ESXi host formed a cluster, Version of 5.1U2, this year, a new batch of new servers planned to install 5.5U3, and then migrate some of the virtual machine to 5.5U3, the other part of the original 5.1U2, observe a period of time to determine that no problem, and then gradually migrate the remaining virtual machines, eventually the old server down, and require the virtual machine without interruption to complete the replacement, Environmental structure
650) this.width=650; "src=" Http://s2.51cto.com/wyfs02/M01/8D/5A/wKiom1iZHlmiFhjqAACtckCtBns408.png "title=" 1.png " Style= "Float:none;" alt= "Wkiom1izhlmifhjqaactckctbns408.png"/>
Solution Ideas
After careful review of the old environment, it was found that only ESXi and vcenter were used in the old environment, and Vcenter worked in workgroup mode without adding an additional identity source, and the virtual switch was a standard Virtual switch (VSS) and did not use a similar view, Vsan and Distributed Virtual Switch (VDS) have a high degree of integration with vcenter components, the new and old two clusters using the same shared storage, Then plan to re-create a VCENTER5.5U3 on the new server, and then use VCENTER5.5U3 to install the newly purchased server ESXI5.5U3 after adding, directly use VCENTER5.5U3 to Rob Vcenter5.1u2 managed ESXI5.1U2 host, and then The virtual machine running location on it is migrated to the new esxi5.5 host. If there is more than one resource pool on an ESXi host in an older environment, it is recommended that you upgrade it as standard
Implementation steps
1. Select Join host on vcenter5.5, add 172.16.10.11 Host, at this time he will ask you this operation makes 172.16.10.11 ESXi host and vcenter5.1 lose connection whether continue, click Yes
650) this.width=650; "src=" Http://s2.51cto.com/wyfs02/M02/8D/57/wKioL1iZHlqS3jlpAABnI0cEC1A039.png "title=" 2.png " Style= "Float:none;" alt= "Wkiol1izhlqs3jlpaabni0cec1a039.png"/>
2. The 172.16.10.31 virtual machine running on the 172.16.10.11 host added to the vcenter5.5 process will not be affected by vcenter changes
650) this.width=650; "src=" Http://s2.51cto.com/wyfs02/M00/8D/5A/wKiom1iZHlrxstzAAABgwWKjJpc765.png "title=" 3.png " Style= "Float:none;" alt= "Wkiom1izhlrxstzaaabgwwkjjpc765.png"/>
3. When the 172.16.10.11 is added, the host is displayed as unresponsive in vcenter5.1, and the host can be removed from vcenter5.1
650) this.width=650; "src=" Http://s2.51cto.com/wyfs02/M00/8D/57/wKioL1iZHluz8ialAAB_EcEr038326.png "title=" 4.png " Style= "Float:none;" alt= "Wkiol1izhluz8ialaab_ecer038326.png"/>
4. In vcenter5.5, you can see that the 172.16.10.11 Host has been successfully added and the virtual machine on it is still functioning properly
650) this.width=650; "src=" Http://s5.51cto.com/wyfs02/M01/8D/5A/wKiom1iZHlzC58n0AAEkLDU-Abg685.png "title=" 5.png " Style= "Float:none;" alt= "Wkiom1izhlzc58n0aaekldu-abg685.png"/>
5. Open the 172.16.10.11 host Configuration interface, the release ESXi version and configuration are consistent with the switch vcenter before
650) this.width=650; "src=" Http://s1.51cto.com/wyfs02/M01/8D/57/wKioL1iZHl2h6MyAAACxZG0-Tzw685.png "title=" 6.png " Style= "Float:none;" alt= "Wkiol1izhl2h6myaaacxzg0-tzw685.png"/>
6. Use the migration option to migrate the virtual machine run location from esxi5.1 to esxi5.5 (it is important to note that the virtual machine port group names on the source and destination hosts of the virtual machine migration are consistent or the migration fails)
650) this.width=650; "src=" Http://s1.51cto.com/wyfs02/M01/8D/57/wKioL1iZHl3TyAeoAACXW90xq2Y447.png "title=" 7.png " Style= "Float:none;" alt= "Wkiol1izhl3tyaeoaacxw90xq2y447.png"/>
Additional Information
Another use scenario for this approach is to create a new version of vcenter in the environment when an older environment requires a version upgrade, and then use the new version of Vcenter to rob an ESXi host managed by the old version of vcenter before using Updata Management upgrade VMware Tools for the robbed ESXi host and virtual machine
This article from "Rabbit-like rabbit sen Broken" blog, please be sure to keep this source http://arkling.blog.51cto.com/2844506/1895477
Production environment VMware Environment Smooth Upgrade