CCNA 200-301

CCNP Enterprise

CCNP Security

CCIE Enterprise Lab

CCIE Security Lab

CCNP Service Provider

CCNP Data Center

CCNP Collaboration

CCIE DC Lab

Verifying whether a Switched Port Analyzer (SPAN) session is active—and confirming which interfaces are acting as traffic sources or capture destinations—is a routine requirement during network troubleshooting, security auditing, and packet analysis. Because a SPAN destination port behaves differently from standard switching ports, checking its configuration only through basic interface counters can easily lead to misinterpretation. This guide provides the exact command-line workflows to inspect, compare, configure, and troubleshoot SPAN sessions across Cisco switches.

CLI Commands to Check Active SPAN Sessions on Cisco Switches

Use the following Cisco IOS and IOS-XE privileged EXEC commands to inspect active port mirroring sessions, verify physical port states, and extract the underlying configuration lines.

! 1. Display all configured SPAN and RSPAN sessions on the switch
Switch# show monitor session all

! 2. Inspect a specific SPAN session by session ID (1 to 66)
Switch# show monitor session 1

! 3. Filter by session type (local or remote)
Switch# show monitor session local
Switch# show monitor session remote

! 4. Check physical port status to identify ports in the "monitoring" state
Switch# show interfaces status | include monitoring

! 5. Inspect detailed operational state of a specific SPAN destination port
Switch# show interfaces GigabitEthernet1/0/48

! 6. View exact SPAN configuration statements in the running configuration
Switch# show running-config | include monitor session

Output Template and Field Interpretation

When you run show monitor session 1, the switch returns a structured status block similar to the template below:

Session 1
---------
Type                   : Local Session
Source Ports           : 
    Both               : Gi1/0/1-2
    Rx Only            : Gi1/0/3
    Tx Only            : None
Source VLANs           : 
    Both               : 10,20
Destination Ports      : Gi1/0/48
    Encapsulation      : Native
          Ingress      : Disabled
  • Type: Indicates whether the session is a Local Session, Remote Source Session, Remote Destination Session, or ERSPAN Source/Destination Session.
  • Source Ports / Source VLANs: Lists the monitored interfaces or VLANs broken down by capture direction (Rx Only for ingress, Tx Only for egress, or Both).
  • Destination Ports: Identifies the physical switch port connected to your packet capture appliance or analyzer (such as Wireshark or an IDS sensor).
  • Encapsulation: Shows Native (VLAN tags stripped on egress) or Replicate (original 802.1Q VLAN tags preserved).
  • Ingress: Displays Disabled by default, ensuring the analyzer cannot inject traffic back into the switch through the destination port.

Checking SPAN Ports on Cisco Nexus (NX-OS) vs. Catalyst (IOS/IOS-XE)

While the commands above apply directly to enterprise Catalyst switches running Cisco IOS or IOS-XE, data center Cisco Nexus switches running NX-OS use a modular configuration structure and report session health differently. Follow this progression to verify SPAN sessions across both operating systems.

Step 1: Check the High-Level Session Summary

On Catalyst IOS/IOS-XE, show monitor session all immediately outputs the full configuration details of every session. On Nexus NX-OS, start by running the shorter show monitor command to view a tabular summary of all sessions, including their administrative state and failure reasons:

Nexus9K# show monitor
Session  State        Reason                  Description
-------  -----------  ----------------------  --------------------------------
1        up           The session is up       Production_Firewall_Capture
2        down         Session admin shut      Temp_Debug_Session

Unlike Catalyst switches—where a session becomes active as soon as both a source and destination are defined—NX-OS creates monitor sessions in an administratively shut state by default.

Step 2: Inspect Detailed Session Parameters

To view the source and destination mappings on NX-OS, run show monitor session <id> or show monitor session all. Compare the output fields with Catalyst IOS-XE:
* Catalyst IOS/IOS-XE reports port direction under Rx Only, Tx Only, and Both headings without an explicit session health line.
* Nexus NX-OS explicitly lists State: up (The session is up) or a specific hardware/configuration error reason at the top of the output, followed by RxConfigured, TxConfigured, and BothConfigured interface lists.

Step 3: Verify Encapsulated Remote SPAN (ERSPAN) Sessions

When checking Layer 3 routed SPAN sessions across platforms:
* On Catalyst IOS-XE, run show monitor session all. Look for Type: ERSPAN Source Session, along with the ERSPAN ID, Destination IP, and Origin IP fields at the bottom of the block.
* On Nexus NX-OS, run show monitor session erspan-source (or show monitor session <id>) to verify the erspan-id, vrf, destination-ip, and GRE tunnel operational status.

Step 4: Audit the Running Configuration Syntax

Because Catalyst and Nexus switches store SPAN settings differently in NVRAM, use platform-specific filters to audit the configuration:
* Catalyst (Flat Global Statements): Run show running-config | include monitor session to pull all single-line global declarations.
* Nexus (Hierarchical Sub-Mode): Run show running-config monitor to display the nested configuration blocks (monitor session 1, source interface ..., destination interface ..., no shut) alongside the required switchport monitor command under the destination interface stanza.

How to Configure, Modify, or Remove a Cisco SPAN Session

Once you have inspected the existing sessions on your switch and confirmed which session numbers and ports are available, you can create a new session, update active sources, or clean up stale sessions.

Step 1: Define the SPAN Source Port or VLAN

Enter global configuration mode and specify the session number, the source interface (or VLAN), and the traffic direction (rx, tx, or both). If you omit the direction keyword, Cisco IOS defaults to both.

Switch# configure terminal
! Mirror both ingress and egress traffic from a physical interface
Switch(config)# monitor session 1 source interface GigabitEthernet1/0/1 both

! Or mirror only ingress traffic across an entire VLAN to prevent duplicate packets
Switch(config)# monitor session 1 source vlan 10 rx

Step 2: Define the SPAN Destination Port

Assign the physical port where your packet analyzer or security sensor is connected. If your source port is an 802.1Q trunk and you need to inspect VLAN tags in your capture tool, include the encapsulation replicate option.

! Standard destination port configuration
Switch(config)# monitor session 1 destination interface GigabitEthernet1/0/48

! Destination port configuration preserving 802.1Q VLAN tags
Switch(config)# monitor session 1 destination interface GigabitEthernet1/0/48 encapsulation replicate

(Note: On Cisco Nexus NX-OS, you must first configure switchport monitor directly under interface Ethernet1/48, and then run no shut inside the monitor session 1 configuration sub-mode.)

Step 3: Add or Remove Individual Sources in an Existing Session

You do not need to delete an entire session to change what is being monitored. Adding a new source statement appends that port to the active session. Prefixing a specific source statement with no removes only that interface while leaving the rest of the session intact.

! Append an additional source port to Session 1
Switch(config)# monitor session 1 source interface GigabitEthernet1/0/5 rx

! Remove only GigabitEthernet1/0/2 from Session 1 without disrupting Gi1/0/1 or Gi1/0/5
Switch(config)# no monitor session 1 source interface GigabitEthernet1/0/2

Step 4: Delete a SPAN Session Completely

When packet capture is finished, remove the session in global configuration mode to release hardware resources and return the destination interface to normal Layer 2 switching operation.

! Delete a single SPAN session
Switch(config)# no monitor session 1

! Or clear all configured SPAN sessions on the switch
Switch(config)# no monitor session all
Switch(config)# end
Switch# write memory

Troubleshooting Common Cisco SPAN Port Issues

Even when show monitor session all shows a valid configuration, physical state alerts or hardware limitations can prevent traffic from reaching your packet capture tool. Below are solutions to the most common problems discovered when checking a SPAN port.

Why does my SPAN destination port show “up, line protocol is down (monitoring)”?

When you check a SPAN destination port on a Catalyst switch using show interfaces, seeing GigabitEthernet1/0/48 is up, line protocol is down (monitoring) is normal behavior, not a link failure. The switch places the line protocol into the down (monitoring) state to disable spanning tree (STP), CDP, ARP, and MAC address learning on that port, preventing network loops and blocking outbound management frames from polluting your packet capture.

If your analyzer still captures zero packets while the port is in this state:
1. Confirm the physical link state is up (not administratively down or notconnect).
2. Verify that the capture NIC on your server or laptop is running in promiscuous mode.
3. Check the source port counters (show interfaces <source-port>) to verify that traffic is actively traversing the monitored interface.
4. On Nexus NX-OS, ensure the session state is not down (Session admin shut) by entering no shut under the monitor session.

How do I check for SPAN port packet drops caused by bandwidth oversubscription?

When you mirror multiple active ports (for example, four 1 Gbps ports monitored in both directions, generating up to 8 Gbps of aggregate traffic) onto a single 1 Gbps destination port, the destination buffer will quickly saturate and drop mirrored frames. Cisco switches prioritize production traffic and silently drop excess SPAN frames when a destination port is oversubscribed.

To verify if your SPAN destination port is dropping packets, check its outbound queue and interface drop counters:

Switch# show interfaces GigabitEthernet1/0/48 | include output drops|Output queue|packets output
  Input queue: 0/2000/0/0 (size/max/drops/flushes); Total output drops: 148920

On Catalyst 9000 Series switches running IOS-XE, you can also inspect ASIC-level queue drops with show platform hardware fed switch active qos queue stats interface GigabitEthernet1/0/48. To stop oversubscription drops, restrict monitoring to rx only, apply a VLAN filter (monitor session 1 filter vlan 10,20), or use a higher-speed interface as the destination port.

Why is my SPAN capture missing 802.1Q VLAN tags?

By default, a Cisco SPAN destination port operates in Native encapsulation mode, which strips all 802.1Q trunk tags before transmitting mirrored frames out of the destination interface. As shown in the configuration steps earlier, you must append encapsulation replicate to the destination interface command to preserve VLAN headers. If show monitor session all already shows Encapsulation : Replicate and tags are still missing in Wireshark, check your host operating system’s network adapter settings—many Windows and Linux NIC drivers strip 802.1Q headers in hardware unless VLAN tag preservation is enabled in the driver properties.

Why am I seeing duplicate packets in my packet capture?

Duplicate frames typically occur when monitoring an entire VLAN or multiple ports in the same VLAN using the both direction. When Host A (on Port 1) sends a frame to Host B (on Port 2) within the same switch and VLAN, the SPAN engine copies the frame once as it enters Port 1 (rx) and a second time as it exits Port 2 (tx). Reconfigure the session to capture only ingress traffic (rx) on the source VLAN or source ports so each frame is mirrored only once.

Local SPAN vs. RSPAN vs. ERSPAN vs. Network TAPs

When planning packet visibility across an enterprise or data center network, understanding hardware session limits and architectural trade-offs helps determine whether a native Cisco SPAN mode is sufficient or if a dedicated hardware network TAP is required.

Comparison CriteriaLocal SPANRemote SPAN (RSPAN)Encapsulated Remote SPAN (ERSPAN)Hardware Network TAP
Traffic Scope & TransportSource and destination ports reside on the same physical switch (or switch stack).Mirrors traffic across multiple Layer 2 switches using a dedicated RSPAN VLAN over 802.1Q trunks.Mirrors traffic across Layer 3 IP networks by encapsulating frames inside GRE tunnels.Physical Layer 1 device inserted inline on a copper or fiber link.
Typical Cisco Session LimitsCatalyst 2960/3560: 2 active source sessions.
Catalyst 9300/9500: Up to 66 configured, max 8 active source sessions.
Nexus 9000: Up to 32 configured, 4–18 active bidirectional (ASIC-dependent).
Shares the same active hardware source session limits as Local SPAN on the source switch; adds Layer 2 trunk bandwidth overhead.Shares hardware source session limits; supported on Catalyst 6500/9000, ASR, and Nexus platforms (not available on entry-level Layer 2 switches).Unlimited switch sessions; constrained only by the number of physical links tapped and packet broker ports.
Oversubscription & Packet Drop RiskHigh risk during microbursts when aggregating multiple ports; drops mirrored packets first.High risk; competes with trunk link utilization and requires flood-forwarding inside the RSPAN VLAN.Moderate to high risk; adds GRE/IP header overhead (requires MTU planning) and consumes router/switch CPU or ASIC resources.Zero packet drops; copies 100% of full-duplex wire-speed traffic in real time.
Layer 1 & Corrupted Frame VisibilityDrops physical layer errors, runt frames, and bad FCS/CRC packets at the ingress ASIC before mirroring.Drops corrupted Layer 1/Layer 2 frames at ingress prior to RSPAN VLAN tagging.Drops corrupted frames at ingress prior to GRE encapsulation.Passes malformed frames, CRC errors, and physical layer anomalies directly to the analyzer (passive TAPs).
802.1Q Tag PreservationPreserved only when encapsulation replicate is explicitly configured.Overwrites original VLAN tag with the RSPAN VLAN ID.Preserves original 802.1Q tag inside the encapsulated GRE payload.Exact bit-for-bit duplicate of all Layer 2 headers and tags.
Deployment Cost & ImpactZero hardware cost; configured instantaneously via CLI with no link downtime.Zero hardware cost; requires VLAN pruning and STP configuration across intermediate trunks.Zero hardware cost; requires IP reachability and MTU adjustments across routed paths.Requires capital expenditure per link and a brief maintenance window to cable inline.

Cisco Official Documentation and Command Reference Resources

Switched Port Analyzer (SPAN) implementation details, ASIC buffer allocations, and maximum concurrent session limits vary by switch family and software train. Refer to the following official Cisco documentation manuals and command references for platform-specific specifications:

  • Cisco Catalyst 9000 Series (Cisco IOS-XE):
  • Manual Title: Network Management Configuration Guide, Cisco IOS XE [Release] (Catalyst 9200 / 9300 / 9400 / 9500 / 9600 Switches)
  • Section: Configuring SPAN and RSPAN and Configuring ERSPAN
  • Scope: Defines platform-specific active session limits per Unified Access Data Plane (UADP) or Silicon One ASIC, Port-Channel source/destination support, and FNF (Flexible NetFlow) interaction rules.
  • Cisco Classic Catalyst 2960-X / 3650 / 3850 Series (Cisco IOS / IOS-XE):
  • Manual Title: Catalyst [Model] Switch Software Configuration Guide – Configuring SPAN and RSPAN
  • Scope: Details cross-stack SPAN behavior (StackWise), ingress forwarding parameters (ingress encapsulation), and VLAN filter restrictions.
  • Cisco IOS Master Command Reference:
  • Manual Title: Cisco IOS Interface and Hardware Component Command Reference / Network Management Command Reference
  • Key Commands Documented: monitor session source, monitor session destination, monitor session filter vlan, and show monitor.
  • Cisco Nexus 9000 and 7000 Series (Cisco NX-OS):
  • Manual Title: Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release [Version]
  • Section: Configuring SPAN, Configuring ERSPAN, and SPAN-on-Drop / Cloud Scale ASIC Guidelines
  • Command Reference: Cisco Nexus 9000 Series NX-OS System Management Command Reference (covers monitor session, switchport monitor, erspan-id, and show monitor session).

Conclusion

Checking a SPAN port on a Cisco switch begins with show monitor session all on Catalyst IOS/IOS-XE or show monitor on Nexus NX-OS to verify source directions, destination bindings, and encapsulation modes. Pairing session output with interface status checks (show interfaces status) and outbound drop counters ensures that your destination port is not only in the expected monitoring state, but also delivering complete, unthrottled packet captures to your analysis tools.

Please follow and like us:
Last modified: November 18, 2026

Author

Comments

Write a Reply or Comment

Your email address will not be published.