When you encounter any issue with traffic mirroring, begin
troubleshooting by checking the output of the
show monitor-session
status command. This command displays the recorded state of all
sessions and source interfaces:
# show monitor-session status
Monitor-session 5
rx destination interface tunnel-ip5
tx destination is not specified
================================================================================
Source Interface Dir Status
--------------------- ---- ----------------------------------------------------
Te0/0/0/23 (port) Rx Operational
In the preceding example, the line marked as
<Session
status>
can indicate one of these configuration errors:
Session Status
|
Explanation
|
Session is not configured globally
|
The session does not exist in global configuration. Review the show run command output and ensure that a session with a correct name has been configured.
|
Destination interface <intf> (<down-state>)
|
The destination interface is not in Up state in the Interface Manager. You can verify the state using the show interfaces command. Check the configuration to determine what might be keeping the interface from coming up (for example, a sub-interface
needs to have an appropriate encapsulation configured).
|
The <Source interface status> can report these messages:
Source Interface Status
|
Explanation
|
Operational
|
Everything appears to be working correctly in traffic mirroring PI. Please follow up with the platform teams in the first
instance, if mirroring is not operating as expected.
|
Not operational (Session is not configured globally)
|
The session does not exist in global configuration. Check the show run command output to ensure that a session with the right name has been configured.
|
Not operational (destination not known)
|
The session exists, but it either does not have a destination interface specified, or the destination interface named for
the session does not exist. For example, if the destination is a sub-interface that has not been created.
|
Not operational (source same as destination)
|
The session exists, but the destination and source are the same interface, so traffic mirroring does not work.
|
Not operational (destination not active)
|
The destination interface or pseudowire is not in the Up state. See the corresponding Session status error messages for suggested resolution.
|
Not operational (source state <down-state>)
|
The source interface is not in the Up state. You can verify the state using the show interfaces command. Check the configuration to see what might be keeping the interface from coming up (for example, a sub-interface
needs to have an appropriate encapsulation configured).
|
Error: see detailed output for explanation
|
Traffic mirroring has encountered an error. Run the show monitor-session status detail command to display more information.
|
The show monitor-session status detail command displays full details of the configuration parameters and any errors encountered. For example:
RP/0/RP0/CPU0:router show
monitor-session status detail
Monitor-session sess1
Destination interface is not configured
Source Interfaces
-----------------
TenGigE0/0/0/1
Direction: Both
ACL match: Disabled
Portion: Full packet
Status: Not operational (destination interface not known)
TenGigE0/0/0/2
Direction: Both
ACL match: Disabled
Portion: First 100 bytes
Status: Not operational (destination interface not known). Error: 'Viking SPAN PD' detected the 'warning' condition 'PRM connection
creation failure'.
Monitor-session foo
Destination next-hop TenGigE 0/0/0/0
Source Interfaces
-----------------
TenGigE 0/0/0/1.100:
Direction: Both
Status: Operating
TenGigE 0/0/0/2.200:
Direction: Tx
Status: Error: <blah>
Monitor session bar
No destination configured
Source Interfaces
-----------------
TenGigE 0/0/0/3.100:
Direction: Rx
Status: Not operational(no destination)
Here are additional trace and debug commands:
RP/0/RP0/CPU0:router# show monitor-session platform trace ?
all Turn on all the trace
errors Display errors
events Display interesting events
RP/0/RP0/CPU0:router# show monitor-session trace ?
process Filter debug by process
#
RP/0/RP0/CPU0:router# debug monitor-session process all
RP/0/RP0/CPU0:router# debug monitor-session process ea
RP/0/RP0/CPU0:router# debug monitor-session process ma
RP/0/RP0/CPU0:router# show monitor-session process mgr
detail Display detailed output
errors Display only attachments which have errors
internal Display internal monitor-session information
| Output Modifiers
RP/0/RP0/CPU0:router# show monitor-session status
RP/0/RP0/CPU0:router# show monitor-session status errors
RP/0/RP0/CPU0:router# show monitor-session status internal