Hi
I have a strange behaviour of a stack of powerconnect 8132F.
Here it is
I have two esx connected to the stack and there s a virtual machine on the cluster of esx machine.
The esx are connected on both member of the stack with nic teaming.
The stack of 8132F are connected to the core network through a portchannel to a stack of 8164F
The ip of the virtual machine is 172.16.0.8
the mac address is 0050.56AA.437D
the 8132F and the 8164F have an ip configured on the same vlan than the virtual machine.
on the 8164F when i ping the virtual machine it doesn't work
on the 8132F when i ping the wirtual machine it works
but
when i look on the mac adress in the 8132F i got :
show mac address-table address 0050.56AA.437D
Aging time is 300 Sec
Vlan Mac Address Type Port
-------- --------------------- ----------- ---------------------
512 0050.56AA.437D Dynamic Po1
Po1 is the port channel between the 8132F and 8164F.
obviously the virtual machine can't respond to the ping as it s attached to the 8132F
but when i ping the wirtual machine from the 8132F i got
Reply From 172.16.0.8: icmp_seq = 0. time= 6515 usec.
Reply From 172.16.0.8: icmp_seq = 1. time= 1092 usec.
Reply From 172.16.0.8: icmp_seq = 2. time= 1027 usec.
Reply From 172.16.0.8: icmp_seq = 3. time= 929 usec.
it works even if the first answer is a bit more longer and the mac adress is on the good port
show mac address-table address 0050.56AA.437D
Aging time is 300 Sec
Vlan Mac Address Type Port
-------- --------------------- ----------- ---------------------
512 0050.56AA.437D Dynamic Te1/0/1
The mac address is on the good port. but as soon as i ping from the 8164F or from any other machine
is the core network the mac adress goes to po1. and the ping not succeed.
If i reboot it solved apparently the problem but after some days it comes again.
it s not always the same virtual machine who has the problem.
Has someone already seen that kind of problem?