Quantcast
Channel: VMware Communities: Message List
Viewing all articles
Browse latest Browse all 214147

Re: Nested ESXi 5.1 Duplicate ICMP Response

$
0
0

After changing both pESXi and vESXi vSwitch to default setting, the duplicate ICMP response between pESXi and vESXi be solved.

 

But when I try to ping between vESXi, the duplicate ICMP response occur.

 

vESXi-01

     Name: vSwitch0

     Uplinks x2 which load balancing are setting "port ID" to pESXi vSwitch2-portgroup-MGMT

     Portgroups: MGMT (IP=172.16.10.111)

     Name: vSwitch1

     Uplinks x2 which load balancing are setting "port ID" to pESXi vSwitch2-portgroup-STOR

     Portgroups: STOR (IP=172.16.20.111)

 

vESXi-02

     Name: vSwitch0

     Uplinks x2 which load balancing are setting "port ID" to pESXi vSwitch2-portgroup-MGMT

     Portgroups: MGMT (IP=172.16.10.222)

     Name: vSwitch1

     Uplinks x2 which load balancing are setting "port ID" to pESXi vSwitch2-portgroup-STOR

     Portgroups: STOR (IP=172.16.20.222)


From vESXi-01 to ESXi-02

~ # ping 172.16.10.111

PING 172.16.10.111 (172.16.10.111): 56 data bytes

64 bytes from 172.16.10.111: icmp_seq=0 ttl=64 time=0.403 ms

64 bytes from 172.16.10.111: icmp_seq=1 ttl=64 time=0.435 ms

64 bytes from 172.16.10.111: icmp_seq=2 ttl=64 time=0.461 ms


~ # ping 172.16.20.111

PING 172.16.20.111 (172.16.20.111): 56 data bytes

64 bytes from 172.16.20.111: icmp_seq=0 ttl=64 time=1.047 ms

64 bytes from 172.16.20.111: icmp_seq=0 ttl=64 time=1.141 ms (DUP!)

64 bytes from 172.16.20.111: icmp_seq=0 ttl=64 time=1.165 ms (DUP!)

64 bytes from 172.16.20.111: icmp_seq=0 ttl=64 time=1.186 ms (DUP!)



Viewing all articles
Browse latest Browse all 214147

Trending Articles