but when i try to configure the port with diagnostic role, the port lost the connection and i can't ping the ip of the sniffer server, but when i changed the role i can ping it, but i can't capture the traffic, the port destination is 21 an the source is 22 because the 22 my ASA is connected directrly to the 22 port. the default traffic is vlan1
This is the normal behavior of the destination port in SPAN session that the usual traffic will be blocked on the dest port while you get the data from the source port. If you put a sniffer on this port (like Ethereal) you can see all the traffic which is sent or received by the source port.
When span is active, incoming traffic is disabled. The port does not transmit any traffic except that required for the SPAN session.
It does not participate in spanning tree while the SPAN session is active.
When it is a destination port, it does not participate in any of the Layer 2 protocols (STP, VTP, CDP, DTP, PagP).
No address learning occurs on the destination port.
one option is to have two NIC cards in your system so that one can be configured as the destination SPAN port and the other can be used for establishing connectivity to it.
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...
I am going to design and build an LAN network under a tunnel underground with long distance between the switches.
I will have 2 Catalyst switches and 8 Industrial IE3000, and they will be connected with fiber.
For now I am planning on use Layer-2 s...