Technical Documentation
New
VSAs for Dynamic IP Interfaces Overview
Table 1 describes the VSAs that apply to dynamic IP interfaces and are supported on a per-user basis from RADIUS. For details, see JunosE Link Layer Configuration Guide.
Table 1: VSAs That Apply to Dynamic IP Interfaces
VSA | Description | Type | Length | Subtype | Subtype Length | Value |
|---|---|---|---|---|---|---|
Ingress-Policy-Name | Specifies the name of the input (ingress) policy | 26 | len | 10 | sublen | string: input-policy-name |
Egress-Policy-Name | Specifies the name of the output (egress) policy | 26 | len | 11 | sublen | string: output-policy-name |
Ingress-Statistics | Indicates whether statistics are collected on input | 26 | 12 | 12 | 6 | integer: 0 – disable, 1 – enable |
Egress-Statistics | Indicates whether statistics are collected on output | 26 | 12 | 13 | 6 | integer: 0 – disable, 1 – enable |
QoS-Profile-Name | Specifies the name of the QoS profile to attach to the interface | 26 | len | 26 | sublen | string: qos-profile-name |
To use the VSAs shown in Table 1:
- Specify the policy, or one or more QoS VSAs in the desired RADIUS user entries.
- Create the ingress or egress policy, or the QoS profile. Policies minimally consist of one or more policy commands and may include classifier control lists and rate limit profiles. See the JunosE Policy Management Configuration Guide for more information about policies and policy routing. See the JunosE Quality of Service Configuration Guide for information about creating QoS profiles.
When a dynamic interface is created according to a profile, the router checks with RADIUS to determine whether an input or output policy or a QoS profile must be applied to the interface. The VSA, if present, provides the name, enabling policy or QoS profile lookup. If found, the policy or QoS profile is applied to the dynamic interface.
The router also determines whether the creation profile specifies any policies to be applied to the interface. Policies specified by the RADIUS VSA supersede any specified by the profile, as described in the following example:
The RADIUS user entry includes an Ingress-Policy-Name VSA that specifies the policy input5. The profile specifies two policies, input7 and output1. In this case, the RADIUS-specified input policy (input5) and the profile-specified output policy (output1) are applied to the dynamic interface.
For information about assigning policies via profiles, see the JunosE Policy Management Configuration Guide. Only attributes assigned by RADIUS appear in RADIUS Acct-Start messages. RADIUS attributes specified by a profile for dynamic interfaces do not appear in RADIUS Acct-Start messages because the profile is not active when the Acct-Start message is generated. These attributes appear in RADIUS Acct-Stop messages for a profile that is active when the session is terminated.
The following section explains traffic shaping for PPP over ATM interfaces:
Traffic Shaping for PPP over ATM Interfaces
The router supports the configuration of traffic shaping parameters for PPP over ATM (PPPoA) via domain-based profiles and RADIUS. In connection with this feature, Table 2 describes VSAs that apply to dynamic IP interfaces and are supported on a per-user basis from RADIUS.
Table 2: Traffic-Shaping VSAs That Apply to Dynamic IP Interfaces
VSA | Description | Type | Length | Subtype | Subtype Length | Value |
|---|---|---|---|---|---|---|
Service-Category | Specifies the type of service | 26 | 12 | 14 | 6 | integer: |
PCR | Specifies the value for the peak cell | 26 | 12 | 15 | 6 | integer |
SCR | Specifies the value for the sustained cell rate (SCR) | 26 | 12 | 16 | 6 | integer |
MBS | Specifies the maximum burst size (MBS) | 26 | 12 | 17 | 6 | integer |
To configure traffic-shaping parameters for PPPoA via domain maps, use the atm command in Domain Map Configuration mode.
