Juniper POLICY MANAGEMENT - CONFIGURATION GUIDE V11.1.X Configuration Manual page 259

The following considerations apply to trigger rules:
Related Topics
Configuring the Analyzer Device
The analyzer device must be configured to receive the mirrored traffic from the E
Series router's analyzer interface. You can use the default keyword with the interface
command to configure an interface as the virtual router's default analyzer interface;
it is then used when an analyzer interface is not explicitly specified in the ip mirror
command. You cannot configure multiaccess interfaces, such as IP over Ethernet,
as default analyzer interfaces.
You can configure any type of IP interface on the E Series router as an analyzer
interface, except for special interfaces such as SRP interfaces, null interfaces, and
loopback interfaces. An interface cannot be both an analyzer interface and a mirrored
interface at the same time. A single analyzer interface can serve multiple mirrored
sessions.
The receive side of an analyzer interface is disabled; all traffic attempting to access
the router through an analyzer interface is dropped. Analyzer interfaces drop all
nonmirrored traffic.
You can configure IP or GRE analyzer interfaces to enable traffic to flow between
tunnel endpoints that are local to the router. The tunnel can be located on a shared
tunnel server port or line module. For a complete list of the line modules and I/O
modules available for ERX14xx models, ERX7xx models, and the ERX310 Broadband
Services Router, see ERX Module Guide. For more information about line modules
and IOAs available with the E120 and E320 Broadband Services Routers, see E120
and E320 Module Guide.
Policies are not supported on analyzer interfaces. When you configure an analyzer
interface, existing policies are disabled, and no new policies are accepted.
Configuring the E Series Router
To configure the router to support CLI-based packet mirroring:
A new trigger rule is not applied to matching connected subscribers if any of the
subscribers is mirrored by another rule.
CLI-initiated mirroring per account session ID creates a rule that continues to
exist after the subscriber logs out.
RADIUS CoA messages affect only currently connected subscribers; they do not
create persistent rules.
Example: Configuring CLI-Based Interface-Specific Mirroring on page 234
Example: Configuring CLI-Based User-Specific Mirroring on page 235
Chapter 11: Configuring CLI-Based Packet Mirroring
Configuring the Analyzer Device
233