Qos Policies - Alcatel-Lucent 7950 Quality Of Service Manual

QoS Policies

unknown. Multicast, broadcast, and unknown 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 egress QoS policies are applied to SAPs and map forwarding classes to service egress
queues for a service. Up to 8 queues per service can be defined for the 8 forwarding classes. A
service egress QoS policy also defines how to remark the forwarding class to IEEE 802.1p bits in
the customer traffic.
Network QoS policies are applied to IP interfaces. On ingress, the policy applied to an IP interface
maps incoming DSCP and EXP values to forwarding class and profile state for the traffic received
from the core network. On egress, the policy maps forwarding class and profile state to DSCP and
EXP values for traffic to be transmitted into the core network.
Network queue policies are applied on egress to network ports and on ingress to MDAs. The
policies define the forwarding class queue characteristics for these entities.
Service ingress, service egress, and network QoS policies are defined with a scope of either
template or exclusive. Template policies can be applied to multiple SAPs or IP interfaces whereas
exclusive policies can only be applied to a single entity.
One service ingress QoS policy and one service egress QoS policy can be applied to a specific
SAP. One network QoS policy can be applied to a specific IP interface. A network QoS policy
defines both ingress and egress behavior.
If no QoS policy is explicitly applied to a SAP or IP interface, a default QoS policy is applied.
Page 22 7950 XRS Quality of Service Guide