Configuring The Src Client; Table 9: Radius Attributes Specifying Lag Interface; Table 10: Src Client And Cops Terminology; Monitoring And Troubleshooting Remote Access - Juniper JUNOSE SOFTWARE FOR E SERIES 11.3.X - BROADBAND ACCESS CONFIGURATION GUIDE 2010-10-12 Configuration Manual

JunosE 11.3.x Broadband Access Configuration Guide
Related
Documentation

Configuring the SRC Client

92
asterix uses the following values for RADIUS attributes in RADIUS authentication and
accounting messages:

Table 9: RADIUS Attributes Specifying LAG Interface

Field Name
Acct-Session-Id
Nas-Port-Type
Nas-Port
Nas-Port-Id
Calling-Station-Id
Chapter 2, Monitoring and Troubleshooting Remote Access
Chapter 3, Configuring RADIUS Attributes
Configuring AAA Authentication for DHCP Local Server Standalone Mode on page 483
show subscribers
The JunosE Software has an embedded client that interacts with the Juniper Networks
SRC software, enabling the SRC software to manage the router's policy and QoS
configuration.
The connection between the router and the SRC software uses the Common Open Policy
Service (COPS) protocol and is fully compliant with the COPS usage for policy provisioning
(COPS-PR) specification. The router's SRC client functions as the COPS client, or policy
enforcement point (PEP). The SRC software functions as the COPS server, or policy
decision point (PDP).
Table 10 on page 92 provides common terms used in the COPS environment.

Table 10: SRC Client and COPS Terminology

Term Description
COPS Common Open Policy Service; query-and-response protocol used to exchange policy
information between a policy server and its clients.
COPS-PR COPS usage for policy provisioning; the PEP requests policy provisioning when the
operational state of interface and DHCP addresses changes.
PDP Policy decision point; the COPS server. which makes policy decisions for itself and
for clients that request decisions. The SRC software is the PDP.
Field Description
erx lag lag1.1:1-10:0001048620
15
2148532268
lag lag1.1:1-10
#asterix#lag1#10
Copyright © 2010, Juniper Networks, Inc.