Basic Configurations
Page 244 7210 SAS D, E, K OS Quality of Service Guide
Service Ingress QoS Policy
NOTE: Depending on the platform, either a queue (7210 SAS-K) or a meter (7210 SAS-D/E) is
available to limit the bandwidth per forwarding class on service ingress. The section below talks
about configuration of service ingress policy assuming user is aware of the choices available on
different platforms.
To create an service ingress policy, define the following:
• A policy ID value. The system will not dynamically assign a value.
• Include a description. The description provides a brief overview of policy features.
• For 7210 SAS-E, specify num-qos-classifiers parameter. By default, it is set to 2. The
number of meters/queue allocated is equal to half the number of classifiers specified.
• For 7210 SAS-D, specify the num-qos-classifiers parameter. By default, it is set to 2. The
number of meters/queue allowed is equal to half the number of classifiers specified.
• Specify a default forwarding class for the policy. All packets received on an ingress SAP
using this ingress QoS policy will be classified to the default forwarding class.
• Define forwarding class parameters.
→ Modify the unicast-meter/queue default value to override the default unicast
forwarding type meter mapping for fc fc-name.
→ Modify the multicast-meter/queue default value to override the default multicast
forwarding type meters/queue mapping for fc fc-name.
→ On 7210 SAS-D and E, modify the unknown-meter/queue default value to override
the default unknown unicast forwarding type meter mapping for fc fc-name.
→ On 7210 SAS-D and E, modify the broadcast-meter default value to override the
default broadcast forwarding type meter mapping for fc fc-name.
• On platforms where applicable, specify the appropriate classification criteria - IPv4/IPv6
or MAC criteria or both IP and MAC criteria. You can define IPv4/IPv6, MAC-based and
MAC and IP based SAP ingress policies to select the appropriate ingress meter and
corresponding forwarding class for matched traffic.
• A SAP ingress policy is created with a template scope. The scope can be modified to
exclusive for a special one-time use policy. Otherwise, the template scope enables the
policy to be applied to multiple SAPs.
The following displays an service ingress policy configuration:
A:ALA-7>config>qos>sap-ingress# info
----------------------------------------------
...
sap-ingress 100 create
description "Used on VPN sap"
...
----------------------------------------------