Shulou(Shulou.com)06/01 Report--

Practical university data center vsphere6.0 upgrade 6.5, re-planning the network.

On June 19th, vsphere was redeployed according to the above plan. Due to the need to replan the network, vcenter was changed from windows to vcsa, so my plan was basically pushed back, and the whole deployment was smooth, but encountered some minor troubles and wasted a lot of time.

The whole upgrade process lasted 2 days, except that the service of the two virtual machines was interrupted for a long time due to the connection of the usb encryption dog (which can also be avoided). In addition, there will be a few minutes of business interruption when the network address is switched after the upgrade.

Problems encountered:

First, if the HP BL460C GEN9 blade reinstalls the vsphere6.5, there will be the problem of not finding the HBA card. Compared with the vsphere6.5 of another data center, it is found that the driver and the driver version are all right, but the HBA card cannot be found in the storage setter.

I am actually aware of this problem, but I installed it with a new version of HPE custom image, so I got stuck and upgraded 4 BL460C directly, but all failed, so I had no choice but to reinstall vsphere6.0. After seeing the HBA card, I upgraded to vsphere6.5 again, and I did it on the afternoon of the 19th.

Second, HP DL580 GEN7 I directly upgraded to 6.5on the basis of vsphere6.0, no problem, and then use update manage to patch when the system crashed. Then re-install vsphere6.5 when vcenter can not connect to vsphere, read the compatibility guide my server is too old to upgrade to vsphere6.0 U3, there is no way to redo 6.0.

To sum up, be sure to read the compatibility guide and release notes before upgrading in the future.

VMware compatibility Guid

Https://www.vmware.com/resources/compatibility/search.php

VMware vSphere 6.5 release Notes

Http://pubs.vmware.com/Release_Notes/cn/vsphere/65/vsphere-esxi-vcenter-server-65-release-notes.html#compatibility

=

Upgrade step correction:

1. Do a good job of VCSA6.5 first, connect several hosts upgraded to vsphere6.5, and configure standard switches and distributed switches.

2. The vsphere6.0 host modifies the newly planned IP address (it can also be modified after upgrading 6.5), the VCSA6.5 is connected to the vsphere6.0 host, and the vmotion network is configured in the standard switch.

3. Migrate the virtual machine to the vsphere6.5 host.

4. Upgrade 6. 0 to 6. 5 with update manager, which is very convenient and there will be no problem with the upgrade.

Harvest

First, I do the upgrade during the day, the whole process of business is not interrupted, I guess it may be caused by the following reasons.

1. The network of the virtual machine is empty when the vsphere6.0 is connected to the vcsa6.5, because the vsphere has not yet been configured with a distributed switch, and the network of the virtual machine may go through the VMKernel management network.

2, my management network and production network IP address are under the same vlan, from the sub address, so at this time even if the management network, the service industry will not be interrupted.

3. Select the target network when the vmotion is migrated, and switch to the new distributed switch after the migration. Since the addresses are all under the same vlan, the business will not be interrupted.

Second, be sure to make good use of update manager upgrades, there is no need to redo vsphere under ilo.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.