The 3500XL still participate in the network traffic eventhough it's cofnigured to just monitor the traffic of anothe interface.
When span destination is active, incoming traffic is disabled. The port does not transmit any traffic except that required for the SPAN session. Incoming traffic is never learned or forwarded on a destination port.
If ingress traffic forwarding is enabled for a network security device, the destination port forwards traffic at Layer 2.
In order for the surfcontrol to apply the rules it must participate in the traffic. Therefore enabling "ingress" on the detination port should correct this issue.
Hi everyone, I would like to thank you in advance for any help you can provide a newcomer like myself!
Im studying the 100-105 book by Odom and am currently on the topic of Port security. I purchased a used 2960 and I'm trying to follow a...
While deploying a number of 18xx/2802/3802 model access points (APs), which run AP-COS as their operating platform. It can be observed on some occasions that while many of their access points were able to join the fabric WLC withou...