Configuring Traffic Mirroring
Characteristics of the Destination Port
Each session must have a destination port that receives a copy of the traffic from the source ports.
A destination port has these characteristics:
• A destination port must reside on the same router as the source port for local traffic mirroring. For remote
• A destination port for local mirroring can be any Ethernet physical port, EFP, and GRE tunnel interface,
• A destination port can be a trunk (main) interface or a subinterface.
• At any one time, a destination port can participate in only one traffic mirroring session. A destination
• A destination port cannot also be a source port.
Figure 11: Network Analysis on a Cisco NCS 5500 Series Router With Traffic Mirroring
Note
1. Source traffic mirroring ports (can be ingress or egress traffic ports).
2. Destination traffic mirroring port.
Traffic Mirroring Configuration Examples
This section contains examples of how to configure traffic mirroring:
Traffic Mirroring with Physical Interfaces (Local): Example
This example shows a basic configuration for traffic mirroring with physical interfaces.
RP/0/RP0/CPU0:router# configure
mirroring the destination is always a GRE tunnel.
but not a bundle interface. It can be a Layer 2 or Layer 3 transport interface.
port in one traffic mirroring session cannot be a destination port for a second traffic mirroring session.
In other words, no two monitor sessions can have the same destination port.
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release 6.1.x
Characteristics of the Destination Port
133