Assign 2nd Network to Host

[AlexD1979]

Hello,

In my ESXi 4. I have at the moment one vSwitch with 192.168.100.1-254 Network on it and 16 vHosts, VM Network and Management Network on it. Now I have to assign a 2nd IP and NIC to a vHost, with a different Network IP. (192.168.200.1). Will be the host per default accessable through this IP only add a 2nd NIC and IP the the vHost or have I todo something else on the Network Configuration. It is a IVM xSeries Server with two physically NICs, but only one is connected at the moment.

Greetings

Alexander Diedler

[J1mbo]

Create new vSwitch, assign physical NIC and connect to appropriate physical network.

Power down VM, add new vNIC, selecting the appropriate network, power on VM.

Within VM OS, configure the new NIC as required.

Be sure to assign a default gateway to only ONE NIC.

Please award points to any useful answer.

[a2alpha]

Do you want it to be accessible through both IPs.

If so, In the Configuration -- Networking

Create a new vSwitch, add you second uplink, create a VMkernel management Port Group with the IP in the new range and select the tick box for use this for management traffic. Then it will be accessible through both.

Hope this helps,

Dan

[AlexD1979]

Hello a2alpha,

Yes, it is a Win XP VM, with 2 NICs and two IP addresses, that have to be accessed from inside and outside. One NIC, this is the interal NIc with the 192.168.100.x IP, and one NIC, that is the "external" IP 192.168.200.x, which is a VPN Translated Network from the customer, because the customer has already the same network on his side (192.168.100.x). So I want to give them access through the VPN to this on the 2nd NIC with the 200.x Range.

There is no risk, that i make my Server unaccessable, if I miss-configure in network settings?

Greetings

Alexander

[a2alpha]

Sorry, I just seem to be getting confused between the host and vm and what is where. Think I have it now though!

If your second physical network port on you esx host is plugged in to the other network (200), does the customer need access to your host?

If not and it is just the virtual machine he needs access to then you don't need to create a vmkernel port group on the second vSwitch just create a vm network on it. Then make sure your virtual machine has to vNics attached. The select one in the vswitch0 vmnetwork port group (100) and one in the vmnetwork portgroup on vSwitch1 (200).

Even in the way I said to set up a new management port group in my previous post, or this one, I can't see your actuall esx host becoming inaccessible.

Dan