Juniper JUNOSE SOFTWARE FOR E SERIES 11.3.X - POLICY MANAGEMENT CONFIGURATION GUIDE 2010-10-04 Configuration Manual page 70

JunosE 11.3.x Policy Management Configuration Guide
Related
Documentation
46
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.
In lower-numbered releases, the formats of the input and output classifier list names
and policy list names were as follows:
clin_<InterfaceId>_<filterNum>
clout_<InterfaceId>_<filterNum>
plin_<InterfaceId>
plout_<InterfaceId>
where:
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
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:
clin_<AuthId>_<filterNum>
clout_<AuthId>_<filterNum>
plin_<ip/ipv6>_<AuthId>
plout_<ip/ipv6>_<AuthId>
where:
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 47
Examples: Using the Ascend-Data-Filter Attribute for IPv6 Subscribers on page 52
Copyright © 2010, Juniper Networks, Inc.