These are the limitations of Switched Port Analyzer (SPAN) and Remote SPAN (RSPAN) on the Cisco Catalyst 2950, 3550, 3560 and 3750 swtiches:
The Cisco Catalyst 2950 switches can only have one SPAN session active at a time. The Cisco Catalyst 2950 switches can monitor only source ports, not VLANs.
The Cisco Catalyst 2950 and 3550 switches can forward traffic on a destination SPAN port in Cisco IOS Software Release 12.1(13)EA1 and later.
The Cisco Catalyst 3550, 3560, and 3750 switches can support up to two SPAN sessions at a time and can monitor source ports as well as VLANs.
The Cisco Catalyst 2970, 3560, and 3750 switches do not require configuration of a reflector port when a ReRSPAN session is configured.
The Cisco Catalyst 3750 switches support session configuration with source and destination ports that reside on any of the switch stack members.
Use a network analyzer in order to monitor interfaces.
You cannot mix source VLANs and filter VLANs within a SPAN session. You can have source VLANs or filter VLANs, but not both at the same time.
EtherChannel interfaces can be SPAN source interfaces; they cannot be SPAN destination interfaces.
When you specify source interfaces and do not specify a traffic type, for example, Tx, Rx, or both. "both" is used by default.
If you specify multiple SPAN source interfaces, the interfaces can belong to different VLANs.
You cannot have two SPAN sessions that use the same destination port. The destination port cannot be a source port; a source port cannot be a destination port.
You can configure a maximum of two source sessions and 64 RSPAN destination sessions on each switch stack. A source session is either a local SPAN session or an RSPAN source session.
If a 10-Gigabit Ethernet module port is configured as a SPAN or RSPAN destination port, its link rate decreases.
Enter the nomonitor sessionnumber command with no other parameters in order to clear the SPAN session number.
The no monitor command clears all SPAN sessions.
You cannot configure a SPAN destination interface in order to receive ingress traffic.
SPAN destinations never participate in any spanning tree instance. SPAN includes BPDUs in the monitored traffic, so any bridge protocol data units (BPDUs) seen on the SPAN destination are from the SPAN source.
Note: Unlike the 2900XL and 3500XL Series switches, the Cisco Catalyst 2940, 2950, 2955, 2970, 3550, 3560 and 3750 Series switches support SPAN on source port traffic in the receive direction only (Rx SPAN or ingress SPAN), in the transmit direction only (Tx SPAN or egress SPAN), or both.
Hello,I am working with ASR-920-12CZ's and am in the process of updating the IOS in dozens of 920's. Recently I have ran into a batch where the USB MEM port is not recognizing my memory stick and have to resort to updating the IOS over tftp. That wo...
I currently have a route-map in that goes through an access list and if you match the ACL the next-hop is something different then the gateway of last resort. If I want something to go the default route, I just deny the ip on the ACL. No...
I'm currently using PI 3.9 Patch 1, to send an interactive command to all my switches (9300 & 3850) but it fails every time. I usually have less issues when I perform "install remove inactive" on all my switches before upgrading them with prime. I was...
Hey forums, so I have a situationI used to be able to SSH connect from my Catalyst to my Nexus, doing like a nested SSH situationAfter I updated the Nexus to the version 8.4.2, when I attempt to access the Nexus, it closes my Catalyst SSH sessionI am sure...