Quality of Service Guide QoS and QoS Policies
Edition: 01 3HE 11014 AAAC TQZZA 127
• network (for ingress and egress and ring)
− IP interface type policy for network ingress and egress
− ring type policy for Ethernet bridging domain on a ring adapter card
• network queue (for ingress and egress)
• slope
• ATM traffic descriptor profile
• fabric profile
• shaper
Service ingress QoS policies are applied to the customer-facing Service Access
Points (SAPs) and map traffic to forwarding class queues on ingress. The mapping
of traffic to queues can be based on combinations of customer QoS marking (dot1p
bits and DSCP values). The number of forwarding class queues for ingress traffic
and the queue characteristics are defined within the policy. There can be up to eight
ingress forwarding class queues in the policy, one for each forwarding class.
Within a service ingress QoS policy, up to three queues per forwarding class can be
used for multipoint traffic for multipoint services. Multipoint traffic consists of
broadcast, multicast, and unknown (BMU) traffic types. For VPLS, four types of
forwarding are supported (which are not to be confused with forwarding classes):
unicast, broadcast, multicast, and unknown. The BMU types are flooded to all
destinations within the service, while the unicast forwarding type is handled in a
point-to-point fashion within the service.
Service ingress QoS policies on the 7705 SAR permits flexible arrangement of these
queues. For example, more than one FC can be mapped to a single queue, both
unicast and multipoint (BMU) traffic can be mapped to a single queue, or unicast and
BMU traffic can be mapped to separate queues. Therefore, customers are not limited
to the default configurations that are described in this guide.
Service egress QoS policies are applied to egress SAPs and provide the
configurations needed to map forwarding classes to service egress queues. Each
service can have up to eight queues configured, since a service may require multiple
forwarding classes. A service egress QoS policy also defines how to re-mark dot1p
bits and DSCP values of the customer traffic in native format based on the forwarding
class of the customer traffic.
Note: The terms access ingress/egress and service ingress/egress are interchangeable.
The previous sections used the term access, and the sections that follow use the term
service.
To Next Page
Loading...
