Egress Network Ip Interface Statistics; Separate Ingress Ipv4 And Ipv6 Statistics; Ingress Pw Shaping Using Spoke-Sdp Forwarding Class-Based Redirection - Alcatel-Lucent 7450 Quality Of Service Manual

When an IP interface associated with a queue group is bound to a port:
If the operation above is successful, then:
When an IP interface associated with a queue group is unbound from a port:

Egress Network IP Interface Statistics

The statistics for network interfaces work differently than statistics on SAPs. Counter sets are
created for each egress IP interface and not per egress queue. When a forwarding class for an
egress IP interface is redirected from the default egress port queue to a queue group queue,
the system continues to use the same counter set.

Separate Ingress IPv4 and IPv6 Statistics

This feature adds support for separate ingress IPv4 and IPv6 statistics on IP interfaces. IES
and VPRN interfaces, and subscriber group interfaces on IES and VPRN, as well as for uRPF.
In previous release, the ingress statistics for IPv4 and IPv6 traffic was combined into a single
set of packet and bytes counters. The existing counters will now only count IPv4 traffic, while
new separate counters are available to IPv6 traffic.
The feature introduces a new CLI command to explicitly enable ingress statistics on IP
interfaces, changing the default to disabled.
Ingress PW Shaping Using Spoke-SDP Forwarding Class-
Quality of Service Guide
• If removing, the queue ID association counter is decremented within each queue
group template based on the queue ID removed from the policy.
• If adding, the queue ID association counter is incremented within each queue group
template based on the queue ID added to the policy.
• If the specified egress queue group does not exist on the port, the port binding will
fail.
• The system increments the association counter for the queue group on the port.
• The system decrements the association counter for the queue group on the unbound
port
Queue Sharing and Redirection
407