We have a chain of switches configured for vlan 13, let's call them switch1, switch2 and switch3
No, somewhere on this chain the arp requests get lost. I can run tcpdump on these switches. Running just sudo tcpdump -n host 192.168.42.1
shows that switch1 and switch2 get the arp requests but switch3 doesn't.
I'd like to further isolate the problem to see if the problem is switch2 or switch3. Can I tell tcpdump to only listen for outgoing arp requests on one specific interface? I tried with sudo tcpdump -e -i et6
but I don't see the arp requests.
Update:
here's the port config of the three switches. The layout (syntax incoming_port#switch#outgoing_port
):
fw1 - 6#switch1#45 - 45#switch2#51 - fiber - 41#switch3 - fw2
! switch 1: incoming
interface Ethernet6
switchport access vlan 13
spanning-tree portfast
! switch 1: outgoing
interface Ethernet45
channel-group 60 mode active
interface Port-Channel60
switchport trunk allowed vlan 1-3,5-4094
switchport mode trunk
mlag 16
! switch 2: incoming
interface Ethernet45
switchport mode trunk
channel-group 60 mode active
!
interface Port-Channel60
switchport trunk allowed vlan 1-3,5-4094
switchport mode trunk
!
! switch 2: outgoing
interface Ethernet51
mtu 9000
switchport access vlan 8
switchport trunk allowed vlan 2-3,5-14,101-110,112-120
switchport mode trunk
!
! switch 3: incoming
interface Ethernet51
mtu 9000
switchport access vlan 8
switchport trunk allowed vlan 2-3,5-14,101-110,112-120
switchport mode trunk
!
Best Answer
I was able to solve the problem. The issue was indeed on the outgoing port as suggested in the comments above. Whatever it's worth a few findings along the way of solving this problem:
for debugging vlans it's helpful to set up vlan interfaces along the way. In my case the Arista switch supports setting up an endpoint with an ip address like this:
doing this lets you do e.g.
arping 192.168.42.2 -I vlan13
or simplyping 192.168.42.2
(the switch knows that this IP address is configured on vlan 13 and sends the pings over this vlan)