Guidelines for Configuring CoS Traffic Shaping Attributes for Dynamic Interface Sets and Member Subscriber Sessions
Observe the following guidelines when you apply dynamic CoS traffic-shaping attributes to a dynamic interface set or a dynamic ACI interface set and its member subscriber sessions. For complete information about the Junos OS CoS traffic-shaping predefined dynamic variables and RADIUS tag values used with this feature, see CoS Traffic Shaping Predefined Variables for Dynamic Interface Sets.
This feature is supported only for dynamically configured and instantiated subscriber interfaces.
Do not configure a combination of
$junos-cos-parameter
predefined dynamic variables with RADIUS tag values in the 100s range and$junos-cos-parameter
predefined dynamic variables with tag values not in the 100s range in the same traffic-control profile (TCP). If you do so, the subscriber authentication process fails.Use the
$junos-cos-adjust-minimum
predefined variable (tag 109) only in TCPs for dynamic subscriber interfaces. Using this variable in a TCP for a dynamic interface set or dynamic ACI interface set has no effect.Do not configure the
$junos-cos-excess-rate-high
predefined variable (tag 110) and the$junos-cos-excess-rate
predefined variable (tag 105) in the same TCP.Do not configure the
$junos-cos-excess-rate-low
predefined variable (tag 111) and the$junos-cos-excess-rate
predefined variable (tag 105) in the same TCP.Do not configure the
$junos-cos-byte-adjust-frame
predefined variable (tag 114) and the$junos-cos-byte-adjust
predefined variable (tag 108) in the same TCP.Do not configure the
$junos-cos-byte-adjust-cell
predefined variable (tag 115) and the$junos-cos-byte-adjust
predefined variable (tag 108) in the same TCP.Use the per-priority
$junos-cos-shaping-rate-parameter
predefined variables (tags 116 through 125) only in TCPs for dynamic interface sets or dynamic ACI interface sets. Using these variables in TCPs for a dynamic logical subscriber interface causes the subscriber session to fail.