Managing Packet Mirroring; Avoiding Conflicts Between Multiple Packet Mirroring Configurations - Juniper JUNOSE SOFTWARE FOR E SERIES 11.3.X - POLICY MANAGEMENT CONFIGURATION GUIDE 2010-10-04 Configuration Manual

CHAPTER 13

Managing Packet Mirroring

Avoiding Conflicts Between Multiple Packet Mirroring Configurations

Copyright © 2010, Juniper Networks, Inc.
Packet mirroring enables you to send a copy of a packet to an external host for analysis.
Packet mirroring has many uses, including traffic debugging and troubleshooting user
networking problems.
This chapter contains the following topics:
Avoiding Conflicts Between Multiple Packet Mirroring Configurations on page 241
Understanding the Prepended Header During a Packet Mirroring Session on page 243
Resolving and Tracking the Analyzer Device's Address on page 246
Using Multiple Triggers for CLI-Based Packet Mirroring on page 247
Optimizing Packet Mirroring Performance on page 248
Logging Packet Mirroring Information on page 249
Using SNMP Secure Packet Mirroring Traps on page 250
Configuring SNMP Secure Packet Mirroring Traps on page 253
Capturing SNMP Secure Audit Logs on page 254
The JunosE Software gives you a great deal of flexibility in creating your packet mirroring
environment by supporting both the CLI-based and the RADIUS-based configuration
methods. However, a conflict might occur when you use both methods. For example, a
given subscriber might be targeted by both a CLI-based configuration and a RADIUS-based
configuration. The rival configurations might use the same trigger to identify the subscriber,
or they might use different triggers.
The configuration method that is applied to the subscriber depends on several variables:
the trigger, when the packet mirroring configuration is created, and when the subscriber
logs in. The following considerations apply to multiple packet mirroring configurations.
CLI-based and RADIUS CoA (RADIUS-initiated mirroring) configurations identify
targeted subscribers according to the following configured criteria in the order given:
Account session ID
1.
Calling station ID
2.
IP address associated with the virtual router where the subscriber logs in
3.
241