QoS Policies
7210 SAS D, E, K OS Quality of Service Guide Page 47
• Counters for packets and octets rejected at the queue
• Counters for packets and octets transmitted in-profile
• Counters for packets and octets transmitted out-of-profile
The counters available vary among the 7210 SAS platform. Not all the counters are supported on
all the platforms. Additionally there are restrictions on the number of counters that can be used
simultaneously with a single queue. Some platforms can only count octets or packets and other can
count both packets and octets. Counter (and corresponding accounting record) support available
on each of the platform is listed in the 7210 SAS System Management user guide under the
“Accounting Records/Logs” section.
Service Ingress QoS Policies
Service ingress QoS policies define ingress service forwarding class queues or meters and map
traffic flows to forwarding class.
Service Ingress QoS policies on 7210 SAS-D and 7210 SAS-E
Service ingress QoS policies define ingress service forwarding class meters and map traffic flows
to forwarding class.
On 7210 SAS-D and 7210 SAS-E, when a service ingress QoS policy is created, it always has two
meters defined that cannot be deleted; one for all the unicast traffic and one for all the multipoint
traffic. These meters exist within the definition of the policy. The meters only get instantiated in
hardware when the policy is applied to a SAP. In the case where the service does not have
multipoint traffic, the multipoint meters will not be instantiated.
On 7210 SAS-K, when a service ingress QoS policy is created, it always has one queue defined
that cannot be deleted. The queue is used to queue all the traffic, both the unicast traffic and the
multipoint traffic. These queues exist within the definition of the policy. The queues only get
instantiated in hardware when the policy is applied to a SAP. In the case where the service does not
have multipoint traffic, the multipoint queues will not be instantiated.
In the simplest service ingress QoS policy, all traffic is treated as a single flow and mapped to a
single meter and all flooded traffic is treated with a single multipoint meter.
Pre-requisite for configuring service ingress QoS policy:
• Allocates resources from the ingress internal CAM resource pool for use for service
ingress QoS classification. Additionally, allocate resources to the appropriate
classification match criteria.
To Next Page
Loading...
Need help?
General
