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

Last week, while taking stock and sorting out the server information, I found that a temporary server (POS inspection system) that was launched last year was still running on the PC. It seems that the company is not going to replace the server, to prevent accidents plan to migrate to the VMware virtual machine. There are not many resources available in the existing vSphere environment, so we intend to replace the A8 server replaced the year before last (the OA system has been replaced, but the original data should be retained for more than 3 years for query. Hardware resource utilization is less than half) reinstall the vSphere environment, and then migrate the POS system to the A8 server. Implementation steps:

First, P2V migrates A8 system to vCenter6.5 (upgrade is not recommended for ESXI host 5.5 IBM x3650M2 compatibility issues). The migration process is relatively smooth. File-level data migration is used because of the need to modify the configuration. In the case of a large number of files, the speed is slow.

Second, stop the original A8 system, plug the encrypted dog into the ESXI host, edit the virtual machine settings, add Host USB Device devices, and select the identified encryption dog. Start the migrated virtual machine and install vmware tools.

3. The A8 service cannot be started after restart. After inspection, it is found that the encryption dog is bound to the MAC address of the network card, and the MAC address is not modified during the migration, resulting in an error in loading the encryption dog times after the MAC address is changed.

Modify the virtual machine MAC address to the original physical machine MAC address, the solution:

1. Shut down the vm virtual machine and remove the virtual machine from the inventory

2. Enable the SSH service of the ESXI host, log in to the ESXI host using Putty, and enter the virtual machine directory, as follows:

# cd / vmfs/volumes/DatastoreName/VMFolderName

3. Back up the original vmname.vmx file and modify the .vmx file

# cp vmname.vmx vmname.vmx.old

# vi vmname.vmx modifies or adds the following:

EthernetN.checkMACAddress = "false"

EthernetN.addressType = "static"

EthernetN.Address = "XX:XX:XX:XX:XX:XX"

Where XX:XX:XX:XX:XX:XX is the new MAC address of the virtual machine. Change N in ethernetN to the network adapter value. For example:

Network Adapter 1-> ethernet0

Network Adapter 2-> ethernet1

Note:

When you modify the MAC address, you can also modify the network connection in the edit virtual machine settings, specify the MAC address as manual, and enter a new MAC address to save it. As shown below:

However, after the modification is completed, an error will be reported when starting the virtual machine: Invalid Ethernet address

At this point, you need to check whether ethernetN.checkMACAddress = "false" is set and whether the virtual network card type (Adapter Type) is "vmxnet3". If it is the E1000 type, you can delete and re-add the network card and select the network card type as "VMXNET 3". Otherwise, the above error will be reported even if the .vmx file is modified.

At first, the problem of the type of network card was not noticed, and the test could not be booted several times.

4. Find the virtual machine vmx file in the storage and register the virtual machine

5. Start the virtual machine.

Reference: failed to power on virtual machine after migrating to VMware vCenter Server 5.x with error: invalid MAC address specified (2102096)

Fourth, reinstall the original A8 server as ESXI6.0 (Dell R710 compatibility up to 6.0), and join vCenter6.5. Migrate the A8 system online to the original server.

Fifth, P2V migrates the POS system to the original A8 server and eliminates the PC.

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.