In a switched network, traffic is sent only to the port where the destination device is connected.
This means that other ports do not see that traffic. As a result, you cannot simply plug in a laptop and expect to see what is happening on another interface.This is where SPAN becomes useful.
Why Local SPAN Is Needed
Local SPAN allows you to copy traffic from one interface to another so it can be analyzed by a traffic collector.
Imagine this scenario:
PC1 is communicating with another device in the network. When its packet arrives on interface G0/0 of SW1, the switch forwards it normally to its destination.

Figure 1 – Local SPAN mirroring
If SPAN is configured, the switch creates a copy of that traffic and sends it to the configured SPAN destination interface.
The original traffic continues to its intended destination without interruption.
Figure 2 – SPAN source and destination
This allows you to see exactly what is being transmitted and analyze the traffic using a traffic collector.
As its name indicates, Local SPAN operates on a single switch.
When you configure Local SPAN, you must define two elements:SPAN source interface – the traffic you want to monitor
SPAN destination interface – where the mirrored traffic is sent
By default, both incoming (RX) and outgoing (TX) traffic are mirrored.
Answer the question below
Local SPAN operates on how many switches?
Now that you understand why Local SPAN is needed, let’s configure it step by step.
Local SPAN configuration is simple.
You need to define:The SPAN source
The SPAN destination

Figure 3 - Local SPAN Configuration
The SPAN source identifies the interface, VLAN, or port-channel whose traffic you want to monitor.
In this example, we will monitor interface G0/0 only.Specify the SPAN Source
To configure the SPAN source, you must create a monitor session.
We will use session number 1.SW1# conf t Enter configuration commands, one per line. End with CNTL/Z. SW1(config)# monitor session 1 source interface g0/0Here, you are telling the switch:
Monitor interface G0/0
Capture both incoming (RX) and outgoing (TX) traffic (default behavior)
Remember: by default, Local SPAN mirrors both RX and TX traffic.
Specify the SPAN Destination
Now that the source is defined, you must specify where the mirrored traffic will be sent.
We use the same monitor session (session 1) and configure the destination interface.In this example, the traffic collector is connected to G0/1.
SW1(config)# monitor session 1 destination interface g0/1 SW1(config)# exitAt this point:
G0/0 is the SPAN source
G0/1 is the SPAN destination
Traffic from G0/0 is mirrored to G0/1
Now let’s verify the configuration.
Answer the question below
What number identifies the SPAN session in this configuration?
To verify your Local SPAN configuration, use the following command:
SW1# show monitor session local Session 1 --------- Type : Local Session Source Ports : Both : Gi0/0 Destination Ports : Gi0/1 Encapsulation : NativeLet’s interpret this output together:
Type : Local Session
This confirms that the session is a Local SPAN session.Both : Gi0/0
This means that both incoming (RX) and outgoing (TX) traffic are being mirrored on interface G0/0.Destination Ports : Gi0/1
This confirms that the mirrored traffic is being sent to interface G0/1, where the traffic collector is connected.
If you see these values, your Local SPAN configuration is working as expected.
Important Consideration
Because traffic is duplicated, the destination port may become congested if the source traffic volume is too high.
For example, if you mirror traffic from a high-speed interface to a lower-speed destination port, packet loss may occur on the SPAN destination. Always verify that the destination interface capacity is sufficient for the mirrored traffic.
Answer the question below
What confirms that both RX and TX traffic are being mirrored?
Answer the question below
PC1 sends 600 Mbps and receives 700 Mbps on G0/0: how many Mbps won't fit on the 1 Gbps G0/1?