Radius-Based Mirroring Sequence Of Events; Figure 21: Radius-Based Packet Mirroring; Table 54: Setting Up The Radius-Based Packet-Mirroring Environment - Juniper JUNOSE SOFTWARE FOR E SERIES 11.3.X - POLICY MANAGEMENT CONFIGURATION GUIDE 2010-10-04 Configuration Manual

JunosE 11.3.x Policy Management Configuration Guide

RADIUS-Based Mirroring Sequence of Events

236
Account-Session-ID attribute is more efficient because the JunosE Software creates
one secure policy that packet mirroring uses for all links in the MLPPP bundle. If you
use the User-Name attribute, a secure policy is created for the first link, then removed
and re-created for every other link.
Figure 21 on page 236 shows the sequence of events that take place during RADIUS-based
mirroring. The tables after the figure describe the events indicated by the numbers and
letters in the figure. Table 54 on page 236 describes the configuration process; Table 55
on page 237 describes the flow of traffic during a mirroring operation that is initiated when
the user logs in; and Table 56 on page 237 describes the flow of traffic when mirroring a
user who is already logged in.

Figure 21: RADIUS-Based Packet Mirroring

Requesting authority
A
ISP administration
B
2
RADIUS
server
Mirrored user
To create a RADIUS-based packet-mirroring environment, you must complete the
processes listed in Table 54 on page 236.

Table 54: Setting Up the RADIUS-Based Packet-Mirroring Environment

Process Description
A The authorized individual requests packet mirroring of the user's traffic and configures
the analyzer device to receive mirrored traffic.
B The ISP administration configures VSAs in the user's RADIUS record.
C The E Series router administrator configures RADIUS server information and the analyzer
interface connection to the analyzer device.
Table 55 on page 237 indicates the sequence of steps for a packet mirroring operation
that takes place when a user starts a new session.
5 Analyzer device
E Series router
4
Analyzer
C
interface
Mirrored
3
interface
1
Destination
Copyright © 2010, Juniper Networks, Inc.