Howdy,
Sorry for the noise but I have run into a little confusion surrounding how NXOS does BFD.
I noticed that BFD wasn't establishing between two switches while there was an iACL attached to an interface and when I checked into the traffic that was getting blocked I noticed this:
Acl: %ACL-6-IPACCESS: list TESTv4 Vlan1061 denied udp 192.168.1.194(49254) -> 192.168.1.194(3785)
Acl: %ACL-6-IPACCESS: list TESTv4 Vlan1061 denied udp 192.168.1.194(49254) -> 192.168.1.194(3785)
Does anyone know why if NXOS is trying to communicate with itself it would try to accomplish this by sending the traffic through the remote device?
I can really easily resolve this by just adding another line to the ACL but I would much rather understand how this traffic is ending up on the wire in the first place.
Thanks,
-Drew
_______________________________________________
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
Sorry for the noise but I have run into a little confusion surrounding how NXOS does BFD.
I noticed that BFD wasn't establishing between two switches while there was an iACL attached to an interface and when I checked into the traffic that was getting blocked I noticed this:
Acl: %ACL-6-IPACCESS: list TESTv4 Vlan1061 denied udp 192.168.1.194(49254) -> 192.168.1.194(3785)
Acl: %ACL-6-IPACCESS: list TESTv4 Vlan1061 denied udp 192.168.1.194(49254) -> 192.168.1.194(3785)
Does anyone know why if NXOS is trying to communicate with itself it would try to accomplish this by sending the traffic through the remote device?
I can really easily resolve this by just adding another line to the ACL but I would much rather understand how this traffic is ending up on the wire in the first place.
Thanks,
-Drew
_______________________________________________
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/