Guidelines for Configuring CoS for Subscriber Access
When configuring CoS for subscriber access, consider the
following guidelines:
In the current release, you configure the traffic scheduling
and shaping parameters in a traffic-control profile within the dynamic
profile. You can configure the scheduler map and schedulers in a dynamic
profile or in the [edit class-of-service] hierarchy. You
must statically configure the remaining CoS parameters, such as hierarchical
scheduling, classifiers, drop profiles, and forwarding classes, in
the [edit class-of-service] hierarchy.
You must enable hierarchical scheduling in the static
CLI for the interface referenced in the dynamic profile. If not, the
dynamic profile fails.
You can configure only one traffic-control-profile under
a dynamic profile.
You must define the output-traffic-control-profile that
binds the traffic-control profile to the interface within the same
dynamic profile as the interface.
We recommend that you provide different names for the
schedulers defined in dynamic profiles that are used for access and
services. For example, if there are two dynamic profiles, voice-profile
and video-profile, provide unique names for the schedulers defined
under those profiles.
You must use a service dynamic profile with a different profile
name for each RADIUS CoA request over the same logical interface.