Ingress Per Sap Statistics With Ingress Queue Groups - Alcatel-Lucent 7450 Quality Of Service Manual

If the packet does not have an IP header, DSCP or IP-precedence based matching is not
performed.
The IP precedence and DSCP based re-classification are only supported on a PW used in an
IES or VPRN spoke-interface. The CLI blocks the application of a network QoS policy with
the egress re-classification commands to a network IP interface or to a spoke-SDP part of L2
service. Conversely, the CLI does not allow the user to add the egress re-classification
commands to a network QoS policy if it is being used by a network IP interface or a L2 spoke-
SDP.
In addition, the egress re-classification commands only take effect if the redirection of the
spoke-SDP to use an egress port queue-group succeeds; for example, the following CLI
commands succeed:
config>service>vprn>interface>spoke-sdp>egress>qos network-policy-id port-redirect-
group queue-group-name instance instance-id
config>service>ies>interface>spoke-sdp>egress>qos network-policy-id port-redirect-
group queue-group-name instance instance-id
Reclassification will however occur regardless of whether the queue group instance exists or
not on a given egress network port. When the redirection command fails in CLI, the PW uses
the network QoS policy assigned to the network IP interface. Since the network QoS policy
applied to a network IP interface does not support re-classification, the PW packets do not
undergo re-classification.

Ingress Per SAP Statistics with Ingress Queue Groups

A new statistic displaying the number of valid ingress packets received on a SAP, or
subscribers on that SAP, is shown below in the sap-stats output. This is available for SAPs
in all services. This is particularly useful to display SAP level traffic statistics when
forwarding classes in a SAP ingress policy have been redirected to an ingress queue group.
In the example below, traffic is received on an ingress FP policer with a packet-byte-offset of
subtract 10. It can be seen that the ingress queueing stats and offered forwarding engine
stats are all zero as the traffic is using the FP ingress policer. The Received Valid statistic is
non-zero and matches that seen on the ingress FP queue group, with the difference being that
the packet-byte-offset is applied to the queue group policer octets but not the Received
Valid octets.
The value in the Received Valid field may not instantaneously match the sum of the offered
stats (even in the case where all traffic is using the SAP queues) when traffic is being
forwarded, however, once the traffic has stopped the Received Valid will equal the sum of
the offered stats.
Quality of Service Guide
Queue Sharing and Redirection
415