Overview
Use this procedure to configure a global session for mirroring buffer drop packets to an ERSPAN destination.
Perform these steps on the router to configure a global session for mirroring buffer drop packets for SPAN to file destination:
Procedure
| 1. | Configure the tunnel mode. Example:
|
|
| 2. | Configure the tunnel source. Example:
|
|
| 3. | Configure the tunnel destination. Example:
|
|
| 4. | Configure a traffic mirroring session. Example:
|
|
| 5. | Associate a destination interface with the traffic mirroring session. Example:
|
|
| 6. | Configure the TM buffer drop session and save the changes. Example:
|
|
| 7. | Configure a policer on the ingress interface and send the traffic at a line rate faster than the policer. The router drops the packets with the reason PACKET_GOT_DROPPED_DUE_TO_EXACT_METER (displayed as TM_EXACT_METER_DROP). Example:
|
|
| 8. | Configure a regular SPAN to file on the ingress interface and send the traffic at 100% line rate. The router drops the packets with the reason PACKET_GOT_DROPPED_DUE_TO_STATISTICAL_METER (Displayed as: TM_STATISTICAL_METER_DROP). |
|
| 9. | Verify the buffer drop packets are mirrored using the show monitor-session status command. Example:
The Packets Accepted counter of the statistical meter dropped packets and exact meter dropped packets in show controllers npu stats traps-all should match the SPAN drop counter in show spp node-counters within an acceptable range. This is because the statistics displayed are not updated in real-time; they refresh every 30 seconds from the hardware. |