• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 7644
  • Last Modified:

vMotion default gateway problem with multiple VLANs?

I'm trying to get vMotion up and running. Here is my config:

Two ESX hosts. 6 pNICs each. One reserved for vMotion, each.

Two VLANs:
VLAN 48 - iSCSI Network - 172.16.48.0, 255.255.255.240
VLAN 200 - vMotion - 172.16.200.0, 255.255.255.248

When I click on the Host and click Configuration tab, I click Networking and then "Add Networking."

When I select VMkernel (for vMotion) the Network Access page comes up. I assign a new vswitch and NIC. I'm now at the Connection Settings and here is where I run into the issue (i think.)

I name the Network Label (I'm matching this name on both hosts) ... I tag the "Use this port group for vMotion" checkbox. I assign the IP and SM and the "VMkernel Default Gateway" is already assigned but grayed out. The DG is the gateway for VLAN 48 .... not VLAN 200.

If I leave the Gateway as 172.16.48.1, I cannot ping the vMotion NIC/IP once I complete the wizard...but if I click the edit box and change the VMkernel Def Gateway to 172.16.200.1, I believe I will lose connectivity to the Service Console/Host machine. (On my last config, when I changed this setting to 200.1, my config got hosed and I had to re-format and re-install. I'd prefer not to do this :D )

In all documentation/best practice reading that I've done, it states that the vMotion network should be on a separate network/VLAN from the VM Network or iSCSI network. How can this be achieved if I can only assign one VMkernel default gateway?? (I have another VMkernel port created and assigned for the iSCSI network...)

What am I doing wrong? I can provide more information as necessary. Please help!
0
sjknits
Asked:
sjknits
1 Solution
 
kumarnirmalCommented:
Your vMotion vSwitch should have its IP in 172.16.200.X Subnet and not in 172.16.48.X Subnet the reason being the NIC which would be used for iSCSI Datastore access should be able to locate the vMotion subnet and vice-versa.

This is the reason why one of the Ports in the Physical Switches connected to each other would be configured as a Trunk Link

For more info about Trunk Links, check this URL - http://www.firewall.cx/vlans-links.php
0
 
65tdCommented:
Is there a NIC for the service console and the virual machine network?

One can test the vmkernal connection by using vmkping if the ESX host has a service console.
See:

http://kb.vmware.com/selfservice/viewContent.do?externalId=1003728&sliceId=1

http://download3.vmware.com/vmworld/2006/tac9689-b.pdf
0
 
sjknitsAuthor Commented:
Well it looks like this is resolved. Called VMware support.

It appeared that when I created the vMotion kernel port, I named the port and set a value of "200" for the VLAN ID. This apparently confused the system. The moment I took that value out, my vMotion nics began to respond. I'm guessing because we're doing port-based VLANs from our Foundry Networks switching equipment, that we didn't need to do any configuration on the ESX itself.

Also, as far as the "DNS and Routing" is considered, I entered the VLAN 48 gateway IP for both the Service Console and VMKernel and all seems well.
0

Featured Post

Veeam Disaster Recovery in Microsoft Azure

Veeam PN for Microsoft Azure is a FREE solution designed to simplify and automate the setup of a DR site in Microsoft Azure using lightweight software-defined networking. It reduces the complexity of VPN deployments and is designed for businesses of ALL sizes.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now