vlan 103 is assigned to the correct port group just like any other host. and yes the physical switch port where hosts are connected shares the same exact VLAN configuration.
I tried to run some ping test for my VM ( 10.244.103.181) . VLAN 103 ip range is 10.244.103.1 - 10.244.103.255.
If the VM is on a different host , it will ping the default gateway to the VLAN , it will ping any other subnet too .
IF the VM is migrated to this faulty host , it looses the ping to any other subnets , to the gateway , everything.
for example -
VM for VLAN 103 is residing on a different Host
C:\Users\Administrator>ping 10.244.103.1
Pinging 10.244.103.1 with 32 bytes of data:
Reply from 10.244.103.1: bytes=32 time=1ms TTL=255
Reply from 10.244.103.1: bytes=32 time<1ms TTL=255
Reply from 10.244.103.1: bytes=32 time=5ms TTL=255
Reply from 10.244.103.1: bytes=32 time=1ms TTL=255
Ping statistics for 10.244.103.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 5ms, Average = 1ms
C:\Users\Administrator>ping 10.244.104.1
Pinging 10.244.104.1 with 32 bytes of data:
Reply from 10.244.104.1: bytes=32 time<1ms TTL=255
Reply from 10.244.104.1: bytes=32 time=1ms TTL=255
Reply from 10.244.104.1: bytes=32 time<1ms TTL=255
Reply from 10.244.104.1: bytes=32 time=1ms TTL=255
Ping statistics for 10.244.104.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 1ms, Average = 0ms
C:\Users\Administrator>ping 10.244.104.74
Pinging 10.244.104.74 with 32 bytes of data:
Reply from 10.244.104.74: bytes=32 time<1ms TTL=127
Reply from 10.244.104.74: bytes=32 time<1ms TTL=127
Reply from 10.244.104.74: bytes=32 time<1ms TTL=127
Reply from 10.244.104.74: bytes=32 time<1ms TTL=127
C:\Users\Administrator>tracert 10.244.226.74
Tracing route to 10.244.226.74 over a maximum of 30 hops
1 2 ms <1 ms <1 ms [10.244.103.3]
2 7 ms <1 ms <1 ms [10.244.246.9]
3 <1 ms <1 ms <1 ms [10.244.246.26]
4 <1 ms <1 ms <1 ms 10.244.226.74
VM migrated to host Vsphre-NA2-06
C:\Users\Administrator>ping 10.244.104.1
Pinging 10.244.104.1 with 32 bytes of data:
Reply from 10.244.103.181: Destination host unreachable.
Request timed out.
Reply from 10.244.103.181: Destination host unreachable.
Reply from 10.244.103.181: Destination host unreachable.
Ping statistics for 10.244.104.1:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
C:\Users\Administrator>ping 10.244.103.1
Pinging 10.244.103.1 with 32 bytes of data:
Request timed out.
Reply from 10.244.103.181: Destination host unreachable.
Request timed out.
Reply from 10.244.103.181: Destination host unreachable.
Ping statistics for 10.244.103.1:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
C:\Users\Administrator>tracerT 10.244.103.1
Tracing route to 10.244.103.1 over a maximum of 30 hops
1 VM.XYZ.com [10.244.103.181] reports: Destination host unreachable.
Trace complete.
C:\Users\Administrator>PING 10.244.226.74
Pinging 10.244.226.74 with 32 bytes of data:
Reply from 10.244.103.181: Destination host unreachable.
Reply from 10.244.103.181: Destination host unreachable.
Request timed out.
Reply from 10.244.103.181: Destination host unreachable.
Ping statistics for 10.244.226.74:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
C:\Users\Administrator>TRACERT 10.244.226.74
Tracing route to 10.244.226.74 over a maximum of 30 hops
1 VM.XYZ.com [10.244.103.181] reports: Destination host unreachabLE
- le.
Trace complete.
Restarted the M/G n/w,
Restarted the M/G agents.
Rebooted the machine.
Is there any specific log file i can check here.
