Alcatel-Lucent 7950 Quality Of Service Manual page 39

In the simplest service ingress QoS policy, all traffic is treated as a single flow and mapped to a
single queue, and all flooded traffic is treated with a single multipoint queue. The required
elements to define a service ingress QoS policy are:
•
•
•
•
Optional service ingress QoS policy elements include:
•
•
•
To facilitate more forwarding classes, sub-classes are now supported. Each forwarding class can
have one or multiple sub-class associations for SAP ingress classification purposes. Each sub-class
retains the chassis wide behavior defined to the parent class while providing expanded ingress
QoS classification actions.
There can now be up to 64 classes and subclasses combined in a sap-ingress policy. With the extra
56 values, the size of the forwarding class space is more than sufficient to handle the various
combinations of actions.
Forwarding class expansion is accomplished through the explicit definition of sub-forwarding
classes within the SAP ingress QoS policy. The CLI mechanism that creates forwarding class
associations within the SAP ingress policy is also used to create sub-classes. A portion of the sub-
class definition directly ties the sub-class to a parent, chassis wide forwarding class. The sub-class
is only used as a SAP ingress QoS classification tool, the sub-class association is lost once ingress
QoS processing is finished.
7950 XRS Quality of Service Guide
A unique service ingress QoS policy ID.
A QoS policy scope of template or exclusive.
At least one default unicast forwarding class queue. The parameters that can be configured
for a queue are discussed in
At least one multipoint forwarding class queue.
Additional unicast queues up to a total of 32.
Additional multipoint queues up to 31.
QoS policy match criteria to map packets to a forwarding class.
Queue Parameters on page
QoS Policies
30.
Page 39