VMWare Esxi NAT-based management port forwarding

The previous article on WMware Esxi describes the case of sharing an IP with a soft route between multiple virtual machines (VMWare Esxi + Sea Spider configuration Nat shared IP Internet) with two IPs, one for virtual machine access and one for management Network. However, in the case of only one public IP, this IP can only be used for external network request and management. It is not difficult to do so, using soft routing to manage the port to be used to forward it.

Continue with the article "Configure NAT sharing Internet", this experiment continues the relevant operation in this example.

Purpose: a public network IP (172.16.12.141 in this case), 2 virtual devices and management network share the IP

System Environment: VMWare Esxi 5.5

Software Environment: Sea spider soft route (V8), VMWare VSphere Client 5.5, operating system mirroring

Detailed steps:

1. Original network topology

Review the previous example of the final network topology:

Where vsphere uses 172.16.12.140 to log on.

2. Create a management port group

In "Configuration"-"network", the upper-right corner "add Network"-"Vmkenel", Next, select "VSwitch1", Next, tick "Use this port group to manage Traffic" (Network label can be renamed as needed), next, you need to fill in the IP address. Here the IP address is a soft route in the network segment (the management port is connected to the LAN port of the soft route), select manually enter the fixed IP. This example sets such as:

Note The default gateway is a 172 segment by default, and a soft-routed gateway (192.168.0.1) is changed.

3. Soft-Routed port forwarding

Log in to the Web-side Administration Web page of the Sea spider via one of the virtual machines, and in firewall-port mapping, start the port mapping and forward the extranet 902 and 443 ports to the 902 and 443 ports of 192.168.0.200:

The Esxi5.5 uses 902 as a vsphere management port and 443 is the port for the HTTPS home page.

3. Change the management IP

To this end, ESXi's management IP is still 172.16.12.140, to use the new management port, the original IP will be changed to a new (in the soft route for 192.168.0.200).

Now delete the VSwitch0 in the Management network, directly click on the VSwitch0 to the left to remove it. After you've identified the removal, vsphere will get stuck, because 140 of this management IP has been removed, the current connection is not valid, and you can close vsphere directly.

From VMware workstation into the underlying management of ESXi, into the management network configuration, you can see that the current management IP has become 192.168.0.200, and network adapters does not specify any physical adapter. Now fill in the default gateway (192.168.0.1) from the IP configuration and exit to "Restart Management Network".

Open vsphere, and you can log in by 172.16.12.141. Final network topology:

4. Analysis

Vsphere uses 902 as the management port, using 443 ports as the SSL home page, to share an IP with other virtual machines, only need to forward these two ports, the remaining ports are left for other virtual machines to use. On the server, if the virtual machine needs to use SSL, you can leave the 443 port to the management IP instead of the virtual machine. In fact, only need to forward 902,vsphere to be able to use normally.

VMWare Esxi NAT-based management port forwarding