Rotten mud: Change ESXI5.0 management network card and Management IP address, esxi5.0ip

Rotten mud: Change ESXI5.0 management network card and Management IP address, esxi5.0ip

This article was sponsored by Xiuyi linfeng and first launched in the dark world.

The company's servers are basically in the IDC room, in order to make better use of server performance. So there are several servers installed with ESXI5.0 for virtualization.

Note that these servers are currently dual NICs.

Because the ESXI is not installed on your own, it is installed on the IDC and I will be informed of the ESXI management IP address and password. Then, I remotely connect to and manage virtual machines. Therefore, set all the ESXI management IP addresses of these servers to public IP addresses.

This is a waste for the company, because the public IP address would have to be paid. Therefore, we plan to replace this IP address with a private IP address, and save this public IP address for other use. In addition, we plan to replace the current ESXI default Management Network Card vmnic0 with the network card vmnic1.

Because it is an experiment, we should declare it here. The 192 CIDR block represents the public IP address of the production environment. 10 CIDR blocks are the private IP addresses I need to configure and are also the private IP addresses in the production environment.

The network configuration after ESXI5.0 is installed is as follows:

It must be explained againESXI5.0The two NICs are connected directly under the same LAN and switch.

To achieve the above objectives, we need to perform the following steps:

1. Add a standard vSwitch1

2. Add a new ESXI management IP Address

3. Configure the private IP address of the local machine.

4. Use the new management IP address to connect to ESXI

5. Change the ESXI management Nic

1. Add a standard switchVSwitch1

Next, we start to replace the management Nic of ESXI. before changing the management Nic, we need to add a standard switch vSwitch1. As follows:

Click "set"-"network"-"add network", as shown below:

In the pop-up window, select "Virtual Machine" for "connection type", as shown below:

"Network access": select the second network card that is not used. As follows:

Select "connection settings" by default, as shown below:

Then, the final result is as follows:

2. AddESXINew managementIP

After adding the standard vSwitch1, we can add a new management IP address. As follows:

Click "set"-"network"-"add network", as shown below:

Select "VMkernel" for "connection type", as shown below:

For "VMkernel network access", select the newly created standard switch vSwitch1, as shown below:

Select the default value for "VMkernel connection settings", as shown below:

Note This in "VMkernel-IP connection settings". I have configured 10.10.1.5, which is the IP address.

After the IP address is configured, it is as follows:

Click "Next", as shown below:

After the preceding configuration is complete:

3. Configure the local private networkIP

Why do I need to configure the local private network?

As mentioned above, ESXI is a virtual machine virtualized from VMWare on the local machine, and the two NICs of this ESXI virtual machine, the network connection mode is bridging mode. It is equivalent that the ESXI virtual machine is in the same LAN as the local machine.

The local IP address is configured as follows:

The local IP address is 10.10.1.4.

In addition, if the same LAN is not connected to a router (including a layer-3 Switch), it uses a layer-2 switch or a fool switch orHubConnectedPC, As long as there are two or more machines with the same network segment configured in the LANPCCommunication between them can be normal.

Ping the machine now. The new IP address 10.10.1.5 we configured in ESXI is as follows:

We can easily see that the 10.10.1.4 configured on the local machine can communicate with the 10.10.1.5 configured on ESXI normally.

4. Use new managementIPConnectionESXI

Since the local machine can normally communicate with the new ESXI management IP address, we will now connect to ESXI through the Vsphere installed on the local machine. As follows:

We can see that the new management IP address of ESXI is connected to ESXI normally.

Note thatESXIVersion andVsphereIssues between versions,ESXIAndVsphereThe version must be one-to-one. OtherwiseVsphereWhen you log on, you will be prompted to download andESXiVersionVsphere.

V. ChangeESXIManage NICs

After using the new management IP address of ESXi to log on to ESXi, we can change the ESXI management Nic. As follows:

"Configure"-"network" select "Standard switch vSwitch0" and click "properties", as shown below:

Select "Management Network" in "Port", and then select "delete", as shown below:

The final result is as follows:

We can see that the management Nic of ESXI has changed to vmnic1.

In this way, we can change the ESXI Nic and IP address.

Vmware esxi50 implements the underlying architecture. How can we solve the problem of having only one ip address inside the Virtual Machine ip address?

This is definitely not possible. Here is a solution:
1. Set the esxi management address, for example, 192.168.0.x.
2. Set the network card addresses of 2008 and 2000 to 192.168.0.x.
3. Open another virtual machine, make it a virtual router, configure a dual-nic, configure one Nic to 10.30.0.25, And the other Nic to configure the private IP address 192.168.0.x.

4. Configure routes and policies on the vro to allow 2008 and 2000 access to the Intranet and 2008 and 2000 over the Intranet.
This should be acceptable, but I have never actually done so, so I can only provide one idea for your reference.
 
Esxi 50 has several management IP addresses

VSphere Client is required for managing ESXi.
Or you can use ssh for some management in the past. It seems that it is not allowed after 5.0.