What should I pay attention to when using VMware ESX vmotion (Virtual Machine environment) (physical machine environment )?

First, I would like to say that the vmotion function cannot be implemented because your deployment of your environment meets all the conditions.

The following describes the precautions for setting up two environments:

(1) virtual machine environment (this environment hardly requires much network knowledge, but do not experiment with private IP addresses)

(1) We must have vmware workstation, the underlying hardware tool for the virtual computer.

(2) Configure low-level Virtual Hardware for ESX on VMWare Workstation. Refer to many installation methods on the Internet, but remember to virtualize two NICs.

(3) install two ESX instances on VMWare Workstation. Note that you must ping both IP addresses on the same gateway and subnet mask to specify different static IP addresses for ESX instances, after the installation, a problem may occur, similar to NUMA. You only need to search the error message on Google to solve the problem. The problem is modified after the vsphere client connects to ESX.

(3) After the installation, we will remove the two ESX shut instances and use vmware workstation to allocate a shared hard disk to the two ESX instances. There are many settings for creating shared disks on the two ESX instances, you can search for them online. If they are not set properly, errors may occur.

(4) use the vsphere client to connect to the vcenter host and configure vmotion in it. we can configure-Network-and then add vkernel to configure the private IP address. You need to add the private IP address to the gateway during configuration. remember, the vkernel names of the two ESX servers should be the same, and then be assigned to the Second Nic. After configuration, we can use the vmkping command to check whether the private IP addresses of pingesx instances are accessible.

(5) the configuration file of the virtual machine used to test vmotion should be stored in the shared disk.

(6) Now we can implement vmotion through vcenter.

To sum up the difficulties in vmotion configuration testing in this environment: the network problem becomes simpler, but shared storage brings us a lot of problems, as well as configuration and ESX installation problems. however, our environment can be set up to solve these two problems. (In fact, these two problems are relatively large), but the hardware cost for testing vmotion is low, there is no physical environment to choose from.

 

(2) physical machine environment (this environment tests your network knowledge and storage knowledge)

(1) There are two ESX physical hosts (remember to set the bios, otherwise vmotion cannot be achieved), with one NIC with two ports or two single port NICs, A shared iSCSI or SAN storage.

(2) During the ESX installation process, you must specify different static IP addresses, the same gateway, and the same subnet mask. Both IP addresses must be pinged.

(3) There is a vcenter host and vsphere client.

(4) If you are using your own vro, you can use a private IP address. If you are in the company's internal network segment and want to use unused private IP addresses, make sure that your network Department activates a private IP address to access the external private network (two different switches I mentioned, do not activate the same one). Otherwise, vmotion cannot be implemented, you can configure-Network-and then add vkernel to configure the private IP address. You need to add the private IP address to the gateway during configuration. remember, the vkernel names of the two ESX servers should be the same, and then be assigned to the Second Nic. After configuration, we can use the vmkping command to check whether the private IP addresses of pingesx instances are accessible.

(5) the configuration file of the virtual machine used to test vmotion should be stored in the shared iSCSI or SAN storage. (For iSCSI or SAN storage, you can contact the company or use the openfiler tool to virtualize an iSCSI for use. I have tried it and can use it. For details, visit the official website of this tool)

(6) Now we can implement vmotion through vcenter.

To sum up the difficulties of vmotion configuration in this test environment: Because iSCSI or SAN storage is used, you must first know how to get and use it, and then go to the network, assuming that the two ESX hosts are not connected to the same vswitch, what should we do? The two problems have been solved, and there is almost no obstacle.

ThisArticleIt depends on the knowledge of VMware, Linux, and storage.