Attribute - Juniper JUNOSE SOFTWARE FOR E SERIES 11.3.X - POLICY MANAGEMENT CONFIGURATION GUIDE 2010-10-04 Configuration Manual
Software for e series broadband services routers policy management configuration guide
Hide thumbs
Also See for JUNOSE SOFTWARE FOR E SERIES 11.3.X - POLICY MANAGEMENT CONFIGURATION GUIDE 2010-10-04:
- Reference manual (284 pages) ,
- Configuration manual (632 pages)
Table of Contents
Advertisement
JunosE 11.3.x Policy Management Configuration Guide
Table 5: Ascend-Data-Filter Fields (continued)
Action or Classifier
Destination port qualifier
Reserved
Marking value
Marking mask
Traffic class
Rate-limit profile
Construction of IPv6 Classifiers from the Hexadecimal Ascend-Data-Filter Attribute
44
Format
1 byte
2 bytes
1 byte
1 byte
1–41 bytes
1–41 bytes
NOTE: To create a rate-limit profile, traffic class, or marking rule, you must
first configure the filter/forward field as forward.
A single RADIUS record can contain two policies—one ingress policy and one egress
policy. Each policy can have a maximum of 512 ascend-data filters. Each ascend data-filter
creates a classifier group and the action associated with the classifier group.
If both the source and destination IP prefixes are 128, the IPv6 classifier is created using
the IPv6 host argument as follows:
IPv6 classifier-list testipv6 source-host 2001:db8:85a3::8a2e:370:7334 destination-host
2001:db8::1428:57ab
Comments
0= no compare
1= less than
2= equal to
3= greater than
4= not equal to
-
Type of Service (ToS)—for IPv4
Differentiated Services Code Point (DSCP)—for IPv6
0= no packet marking
0= no traffic class (required if there is no profile)
First byte specifies the length of the ASCII name of the traffic class
Traffic class must be statically configured
Name can optionally be null terminated, which consumes 1 byte
Although the traffic class name field supports up to 41 bytes, you
can create an Ascend-Data-Filter attribute with the traffic class
name field set to a maximum of 32 bytes only (including null
characters). This restriction occurs because the traffic class group
configuration enables a traffic class name of up to 31 characters
only.
0= no rate limit (required if there is no profile)
First byte specifies the length of the ASCII, followed by the ASCII
name of the profile
Profile must be statically configured
Name can optionally be null terminated, which consumes 1 byte
Copyright © 2010, Juniper Networks, Inc.
Advertisement
Table of Contents
Need help?
Do you have a question about the JUNOSE SOFTWARE FOR E SERIES 11.3.X - POLICY MANAGEMENT CONFIGURATION GUIDE 2010-10-04 and is the answer not in the manual?
Questions and answers