vmotion between vlans - cross vcenter

[billdossett]

Hi,  this is my first time trying vmotioning between vcenters.

So far unsuccessful.

I am using the vmotion tcp stack on my vmotion vmkernel.

I have defined the override gateway to be the gateway on my vmotion network segment.

I can vmkping other hosts on that same network, I can vmkping the gateway on that network - all using the vmotion stack.

when I try to vmkping a host on another vlan/network segment it says unreachable.

The gateway has been configured in the vmkernel tcpip 4 settings

this is esxcfg output for this:

[root@hcidc01inv-p01:~] esxcfg-route -l -N vmotion
VMkernel Routes:
Network          Netmask          Gateway          Interface
10.140.169.0     255.255.255.0    Local Subnet     vmk4

I am not seeing the gateway I configured for the vmotion vmkernel.

I am not seeing the route in esxcli network ip route list

[root@hcidc01inv-p01:~] esxcli network ip route ipv4 list
Network       Netmask        Gateway       Interface  Source
------------  -------------  ------------  ---------  ------
default       0.0.0.0        10.140.168.1  vmk2       MANUAL
10.140.168.0  255.255.255.0  0.0.0.0       vmk2       MANUAL
10.140.170.0  255.255.255.0  0.0.0.0       vmk3       MANUAL
169.254.0.0   255.255.255.0  0.0.0.0       vmk1       MANUAL

at all.

Netops are able to ping between subnets on the switches, nothing restricting that, but when they try to ping a host from another subnet, they get nothing back indicating that the host does indeed not have a route...  is the gateway enough?  do I need to specify a route somewhere...  I have never done this before, so could use some help, thanks!

[basteku73]

Try to configure vmotion on default stack. 

I had a similar problem, hosts were in different sunbets and this didnt work on vmotion stack. On default that was all ok. 

Regards, 

Sebastian

[billdossett]

thanks, you got me to an answer.  I didn't want to delete the vmk and recreate but when I was trying to find a way to change the stack type, I edited the vmotion stack and there was a place to add a route, so added a default route on vmotion stack to the default gw I had put in to override and then it stated working... seems like something isn't quite deploying correctly... anyway, I can now vmkping over vmotion stack to another host that I also added a default route to the vmotion stack.