EasyManua.ls Logo

Juniper E Series

Juniper E Series
212 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
JUNOSe 7.2.x Policy Management Configuration Guide
68 ! Applying Policy Lists to Interfaces and Profiles
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.
Destination port qualifier 1 byte 0 = no compare
1 = less than
2 = equal to
3 = greater than
4 = not equal to
Reserved 2 bytes –
Marking value 1 byte –
Marking mask 1 byte 0 = no packet marking
Traffic class 1–41 bytes
! 0 = no traffic class (required if there is no
profile)
! First byte specifies the length of the ASCII string,
followed by the ASCII name of the traffic class
! Traffic class must be statically configured
! Name can optionally be null terminated, which
consumes 1 byte
Rate-limit profile 1–41 bytes
! 0 = no rate limit (required if there is no profile)
! First byte specifies the length of the ASCII string,
followed by the ASCII name of the profile
! Profile must be statically configured
! Name can optionally be null terminated, which
consumes 1 byte
Table 6: Ascend-Data-Filter Policy Format (continued)
Action or Classifier Format Comments
NOTE: To create a rate-limit profile, traffic class, or marking rule, you must first
configure the filter/forward field as forward.

Table of Contents

Other manuals for Juniper E Series

Related product manuals