Network Ip Interface Forwarding Class-Based Redirection; Egress Network Forwarding Class Redirection Association Rules - Alcatel-Lucent 7450 Quality Of Service Manual

This means that it is not possible to perform accounting within a queue group based on the
source SAPs feeding packets to the queue. That is, the statistics associated with the SAP will
not include packets redirected to a queue group queue.
If the user enables the packet-byte-offset {add bytes | subtract bytes} option under the
ingress queue-group policer, the byte counters of that policer will reflect the adjusted packet
size.
The set of statistics per queue are eligible for collection in a similar manner to SAP queues.
The collect-stats command enables or disables statistics collection in to a billing file based
on the accounting policy applied to the queue group.

Network IP Interface Forwarding Class-Based Redirection

Forwarding class redirection for a network IP interface is defined in a four step process.
Egress Network Forwarding Class Redirection
Association Rules
The association rules work differently for network egress IP interfaces than they do for access
SAPs. Since the network QoS policy does not directly reference the queue group names, the
system is unable to check for queue group template existence or queue ID existence when the
forwarding class queue redirection is defined. Configuration verification can only be checked
at the time the network QoS policy is applied to a network IP interface.
Quality of Service Guide
1. Create an ingress or egress queue group template with the appropriate queues or
policers.
2. Apply an instance of an ingress queue-group template created in step 1 (containing
only policers) to the FP ingress network configuration context of card X. In addition,
or alternatively, apply an instance of an egress queue-group template created in step
1 to the network egress configuration context of port Y.
3. Configure the network QoS policy used on the IP interface to redirect ingress traffic
to a policer ID (defined in the ingress queue-group template created in step 1) on the
basis of forwarding-class and forwarding-type (unicast vs. multicast). In addition, or
alternatively, configure the network QoS policy to redirect egress traffic to a queue
ID and/or a policer ID based on forwarding-class.
4. Apply the network QoS policy to the network IP interface and at the same time
specify the ingress and/or egress queue-group instances associated with the interface.
Queue Sharing and Redirection
405