This post is more than 5 years old

3 Posts

24086

July 15th, 2015 03:00

Pair of S4810, cannot ping other switch through VLT link

Hello, my topology is following:

A <-> S4810-1 <======VLTi======> S4810-2 <-> B
              \==VLT-HeartBeat=/

For some reason I'm seeing flakey connectivity with S4810-2's control plane when traffic traverses the VLTi link. For sake of simplicity A,B are configured as access ports to management VLAN:

  • A can ping B
  • A cannot ping S4810-2
  • S4810-1 can ping S4810-2
  • S4810-2 can ping S4810-1
  • S4810-2 cannot ping A
  • B can ping everyone

If I look at tcpdump I can see S4810-2 doing ARP resolves of A but it seems replies aren't reaching S4810-2 at all as shown by

Protocol    Address         Age(min)  Hardware Address    Interface  VLAN             CPU
-----------------------------------------------------------------------------------------
Internet    10.0.50.31            -   00:01:e8:8b:3d:75      -       Vl 50            CP
Internet    10.0.0.1              -   00:01:e8:8b:3d:75   Te 0/1      -               CP
Internet    10.0.0.2             69   00:01:e8:8b:35:02   Te 0/1      -               CP

10.0.0.1,2 are from VLT HB and ...50.31 is the management vlan.

Have I hit a bug or am I doing something wrong? :)

Update: The issue was VLT port-channel mismatch between S4810-1 and A, port-channel was configured to S4810-2 as well and as soon as the mismatch was fixed. The issue got resolved.

3 Posts

July 15th, 2015 07:00

After tcpdumping on the switch I can verify the switch is receiving the ARP replies but is not accepting them for some reason.

UPDATE:
Turns out that there was a mismatch on one of the port-channels of the VLT. As soon as I fixed the mismatch on S4810-2 the switch was able to receive the traffic successfully!

Long story short, in case of any issues, remember to check sh vlt mismatch :)

3 Posts

July 15th, 2015 09:00

Update,

Looks like the S4810-2 had an asymmetry regarding VLANs. As soon as I fixed all mismatches reported by show vlt mismatch the issue disappeared.

No Events found!

Top