Table of Contents
Advertisement
JUNOSe 11.1.x Policy Management Configuration Guide
In lower-numbered releases, the formats of the input and output classifier list names
and policy list names were as follows:
where:
In this release, the formats of the input and output classifier list names and policy
list names are modified to support IPv6 subscribers. The following is the new format
of the input and output classifier list and policy list:
where:
Related Topics
50
Using RADIUS to Create and Apply Policies Overview
If the Type 1 action is used and the Indirection action field is set to 00 in the
Ascend-Data-Filter attribute, one primary output policy is created and applied
on the egress IPv4 interface.
If the Type 3 action is used and the Indirection action field is set to 00 in the
Ascend-Data-Filter attribute, one primary output policy is created and applied
on the egress IPv6 interface.
Ascend-Data-Filter attributes for both IPv4 and IPv6 interfaces are stored on the
RADIUS server and the appropriate policies are created and applied to the
corresponding interfaces when they come up, depending on the type of
subscribers.
clin_<InterfaceId>_<filterNum>
clout_<InterfaceId>_<filterNum>
plin_<InterfaceId>
plout_<InterfaceId>
clin Classifier list included in an input policy list
clout Classifier list included in an output policy list
plin Policy list applied to the ingress interface
plout Policy list applied to the egress interface
InterfaceId A unique identifier for the interface to which the policy is applied
filterNum A value that denotes the sequence of Ascend-Data-Filter attribute
configured on the RADIUS server
clin_<AuthId>_<filterNum>
clout_<AuthId>_<filterNum>
plin_<ip/ipv6>_<AuthId>
plout_<ip/ipv6>_<AuthId>
AuthId A unique identifier that is used during the authentication of the client
with the RADIUS server
ip/ipv6 Type of protocol used based on the Type action field
Examples: Using the Ascend-Data-Filter Attribute for IPv4 Subscribers on page 51
Advertisement
Table of Contents
