Overview of QoS policies on 7210 SAS-R6 and 7210 SAS-R12

7210 SAS-R6 and 7210 SAS-R12 QoS policies are applied on service ingress, service egress, access port egress, network port ingress and egress, and network IP interface ingress. These policies allow users to configure the following:

classification rules to map traffic to FCs
FC association with meters and meter parameters used for policing (rate-limiting)
queuing parameters for shaping, scheduling, and buffer allocation
QoS marking and interpretation

The 7210 SAS-R6 IMM-b, 7210 SAS-R12 IMM-b, 7210 SAS-R6 IMM-c, and 7210 SAS-R12 IMM-c support the following types of QoS policies:

service ingress policies for access SAP ingress

Service ingress QoS policies are applied to customer-facing SAPs. Traffic that enters through the SAP is classified to map to an FC. FCs are associated with meters or policers on ingress. Mapping traffic meters can be based on combinations of customer QoS marking (IEEE 802.1p bits), IP criteria, and MAC criteria. The policy defines the number of FC meters for unicast traffic and other meter characteristics (such as CIR, PIR, and so on). Each FC can be associated with different unicast parameters.

A service ingress QoS policy also defines up to three meters per FC for multipoint traffic for use with multipoint services. The system supports the configuration of up to 32 meters per service ingress QoS policy. In the case of VPLS, four forwarding types (not to be confused with forward classes) are supported: unicast, multicast, broadcast, and unknown. Multicast, broadcast, and unknown types are flooded to all destinations within the service, while the unicast forwarding type is handled in a point-to-point fashion within the service.

Service ingress QoS policies are supported on the 7210 SAS-R6 IMM-b, 7210 SAS-R12 IMM-b, 7210 SAS-R6 IMM-c, and 7210 SAS-R12 IMM-c.
service egress policies for access SAP egress

Service egress QoS policies are applied to SAPs and map FCs to service egress queues for a service. The system allocates a maximum of eight queues per SAP for the eight FCs; this is not user configurable. All traffic types (unicast and BUM) share the same service egress queue. A service egress QoS policy defines the FC queue characteristics and how the FC to priority bits in the packet header are remarked (for example, IEEE 802.1p bits in the Ethernet VLAN tag) in the customer traffic.

On the 7210 SAS-R6 and 7210 SAS-R12, the user has a per-node or per-chassis option of configuring the SAP-based or access port-based egress queuing mode. The SAP-based egress queuing mode (port-scheduler-mode command disabled) uses a service egress QoS policy with the capability to use eight egress queues per SAP. The access port-based egress queuing mode (port-scheduler-mode command enabled) uses an access egress policy with the capability to use eight egress queues for all SAPs configured on the access port.

A service egress QoS policy or access egress policy also defines how to remark the FC-to-IEEE 802.1p bits in the customer traffic.

Service egress policies are supported only on 7210 SAS-R6 IMM-b and 7210 SAS-R12 IMM-b. 7210 SAS-R6 IMM-c and 7210 SAS-R12 IMM-c support only the port-based egress queuing mode and use access egress policies to configure the access port egress queues.
access egress policies for access port egress

An access egress policy is applied to all SAPs on the physical port (and not the logical port (SAP)) for SAP-egress policies. It applies to all the SAPs on the port. Access egress policies provide different capabilities based on the egress queuing mode applied to the node. In SAP-based egress queuing mode, an access egress policy defines the remarking of the FC-to-packet header bits. For example, IEEE 802.1p bits in the Layer 2 VLAN header.

In port-based egress queuing mode, the access egress policy, in addition to remarking, is used to define the queuing and scheduling behavior for the port-based egress queues. Access egress QoS policies are applied to ports and map forwarding classes (FCs) to port egress queues. The system allocates a maximum of eight queues per port for the eight FCs. The allocation is not user-configurable. All traffic types, (unicast and BUM traffic types) share the same queue on port egress.

An access egress QoS policy defines the FC queue characteristics and the remarking of the FC to priority bits in the packet header (for example, IEEE 802.1p bits in the Ethernet VLAN tag) in the customer traffic.

Access egress policies are supported on the 7210 SAS-R6 IMM-b, 7210 SAS-R12 IMM-b, 7210 SAS-R6 IMM-c, and 7210 SAS-R12 IMM-c. On IMM-b cards, when SAP-based egress queuing is configured, an access egress policy is used to configure marking. When port-based egress queuing is configured, an access egress policy is used to define port egress queue shaping and scheduling parameters, and configure marking.
access ingress policies for access port ingress

An access ingress policy is applied to the physical port instead of the SAP; the policy applies to all SAPs configured on the specific access port. At ingress, the access ingress QoS policy uses dot1p, DEI with dot1p, or IP DSCP values to assign an FC and profile to traffic, which facilitates the classification of traffic received on the access port. The FC is associated with meters at ingress. An access ingress QoS policy allows the user to define up to one meter per FC for unicast traffic, and up to one meter per FC for multipoint traffic (broadcast, multicast, and unknown-unicast) for multipoint services. The system supports up to 16 meters per access ingress QoS policy.

This policy is supported on the 7210 SAS-R6 IMM-b, 7210 SAS-R12 IMM-b, 7210 SAS-R6 IMM-c, and 7210 SAS-R12 IMM-c.

Note:
Access ingress policies are available only when the node is operating in sap-scale mode high. See the 7210 SAS-Mxp, S, Sx, T Services Guide and 7210 SAS-Mxp, R6, R12, S, Sx, T Basic System Configuration Guide for more information about this command.
network policies for network port and hybrid port ingress and egress, and network IP interface ingress

For devices configured to operate in network mode, two types of network QoS policies are supported: one that is applied to a network IP interface and the other to a network port. On ingress, the policy applied to an IP interface maps incoming MPLS LSP EXP values to FC and profile state for traffic received from the core network. On egress, the network policy maps FC and profile state to MPLS LSP EXP values for traffic transmitted into the core network. The network policy applied to a network port maps incoming IP packets, DSCP, or dot1p values to the FC and the profile state for the traffic received from the core network. On egress, the network policy maps FC and profile state to DSCP or dot1p values for IP traffic transmitted into the core network.

These network policies are supported on the 7210 SAS-R6 IMM-b, 7210 SAS-R12 IMM-b, 7210 SAS-R6 IMM-c, and 7210 SAS-R12 IMM-c.
network queue policies for network port and hybrid port, egress

Network queue policies are applied on egress to network ports when operating in network mode. The policies define the FC queue characteristics for these entities. The FCs are mapped to the queues. The FC-to-queue mapping is static and not configurable. The number of queues is not user-configurable and the software allocates eight queues at the port level.

These network queue policies are supported on the 7210 SAS-R6 IMM-b, 7210 SAS-R12 IMM-b, 7210 SAS-R6 IMM-c, and 7210 SAS-R12 IMM-c.
remark policies for service egress, access port egress, network port and hybrid port egress, and network IP interface egress marking

Remark policies are applied to access ports/SAPs, network ports/IP interfaces, and hybrid ports/SAPs/IP interfaces to configure the marking values for different forwarding classes and profiles.These policies enable marking of packet header QoS fields for packets that are forwarded out of the port, SAP, or IP interface. See Remark policies for more information.
queue management policies for buffer allocation and slope configuration on service egress and network port egress

Queue management policies are applied to service egress, access port egress, network port egress, and hybrid port egress to configure CBS and MBS parameters for the egress queues and the WRED slope parameters for the queues.

This policy is supported on the 7210 SAS-R6 IMM-b, 7210 SAS-R12 IMM-b, 7210 SAS-R6 IMM-c, and 7210 SAS-R12 IMM-c. On the 7210 SAS-R6 IMM-c and 7210 SAS-R12 IMM-c, the CBS and MBS parameters are system-defined and not user-configurable. The values configured in the queue management policy for CBS and MBS parameters are ignored and only the WRED slope parameters are used.

Service ingress, access ingress, service egress, access egress, and network QoS policies are defined with a scope of either template or exclusive. Template policies can be applied to multiple entities (such as SAPs and ports); exclusive policies can only be applied to a single entity.

One service ingress and one service egress QoS policy can be applied to a specific SAP access egress policy, which can then be applied to an access port. One network QoS policy can be applied to a specific IP interface or network port based on the type of network QoS policy. A network QoS policy defines both ingress and egress behavior. One network queue policy can be applied to the network port.

If no QoS policy is explicitly applied to a SAP, port, or interface, a default QoS policy is applied.

The 7210 SAS-R6 and 7210 SAS-R12 can operate in either the low SAP scale mode or high SAP scale mode. In low SAP scale mode, SAP and service scaling is limited by the amount of CAM resources available for the SAP ingress policy (both classification and meters). In the high SAP scale mode, SAP and service scaling are significantly higher compared to the low SAP scale mode and use access port ingress policies. The use of network port policies remains unchanged when the system is operating in high SAP scale mode; however, the high SAP scale mode assumes that the user requires Layer 2 uplinks, and uses access port ingress and egress policies on those uplinks.

SAPs configured on ports operating in hybrid mode cannot be configured to use access ingress QoS policies. Therefore, the access-ingress-qos port-mode option is not supported for ports configured in hybrid mode.

The following QoS policies are supported on access ports and SAPs in the low SAP scale mode:

service ingress policy for SAP ingress classification and metering using the following:
- CAM-based classification and metering
- table-based classification and CAM-based metering
service egress policy for SAP egress queuing, shaping, and scheduling with an egress policy for marking only
access egress policy for access port egress queuing, shaping, scheduling, and marking (this policy is mutually exclusive with the use of service egress policies)

The following QoS policies are supported on access ports and SAPs in the high SAP scale mode:

the choice of an access port ingress policy on access service delivery ports or per-SAP ingress policies; Nokia recommends using an access port ingress policy for higher SAP scaling
access egress policy for port egress queuing, shaping, scheduling, and marking (this policy is mutually exclusive with the use of service egress policies)

The following table describes the major functions performed by QoS policies for 7210 SAS-R6 and 7210 SAS-R12.

Table: QoS policy types and descriptions for 7210 SAS-R6 and 7210 SAS-R12
Policy type	Applied at	Description	Section
Service ingress	Access SAP ingress	defines up to 32 FC meters and meter parameters for traffic classification defines match criteria to map flows to the meters based on any one of the criteria (IP or MAC, or both IP and MAC) optionally, can map the priority bits (DSCP) to FC and profile using table-based classification supported on the 7210 SAS-R6 IMM-b, 7210 SAS-R12 IMM-b, 7210 SAS-R6 IMM-c, and 7210 SAS-R12 IMM-c	Service ingress QoS policies
Service egress	SAP egress	available only in SAP-based egress queuing mode defines up to eight FC queues Maps FCs to queues defines queue parameters for the queues defines FC-to-remarking values defines CIR levels and PIR weights that determine how the queue is prioritized by the scheduler supported on the 7210 SAS-R6 IMM-b and 7210 SAS-R12 IMM-b	Service egress QoS policies on 7210 SAS-Mxp, 7210 SAS-R6, and 7210 SAS-R12
Access Ingress	Access Port	defines dot1p and IP DSCP classification criteria to use defines up to 16 meters per access ingress QoS policy supported on 7210 SAS-R6 IMM-b, 7210 SAS-R12 IMM-b, 7210 SAS-R6 IMM-c, and 7210 SAS-R12 IMM-c	Access ingress QoS policies
Access egress	Access port	In port-based egress queuing mode, the access egress QoS policy supports the following: defines up to eight FC queues maps FCs to queues defines queue parameters for the queues defines FC-to-remarking values defines queue priorities that determine how the queue is prioritized by the scheduler supported on both IMM-b and IMM-c cards In SAP-based egress queuing mode, access egress is used to configure the FC-to-remarking map values	Access egress QoS policies on 7210 SAS-R6 and 7210 SAS-R12
Network (type = ip-interface)	Network IP interface	used for classification and marking of MPLS packets on ingress, defines MPLS LSP-EXP-to-FC mapping, and defines up to 16 FC meters on egress, defines FC-to-MPLS LSP-EXP marking supported the 7210 SAS-R6 IMM-b, 7210 SAS-R12 IMM-b, 7210 SAS-R6 IMM-c, and 7210 SAS-R12 IMM-c	Network QoS policy ‟ip-interface” type
Egress rate	Access and network port	configures the maximum bandwidth available for traffic sent out of a specified port supported on the 7210 SAS-R6 IMM-b, 7210 SAS-R12 IMM-b, 7210 SAS-R6 IMM-c, and 7210 SAS-R12 IMM-c	Egress port rate limiting
Network (type = port)	Network and hybrid ports	used for classification and marking of IP packets on ingress, defines DSCP or dot1p-to-FC mapping, and up to 16 FC meters on egress, defines FC-to-DSCP or dot1p marking, or both supported on the 7210 SAS-R6 IMM-b, 7210 SAS-R12 IMM-b, 7210 SAS-R6 IMM-c, and 7210 SAS-R12 IMM-c	Network QoS policy ‟port” type
Network queue	Network and hybrid ports	defines FC mappings to network queues and queue characteristics for the queues supported on the 7210 SAS-R6 IMM-b, 7210 SAS-R12 IMM-b, 7210 SAS-R6 IMM-c, and 7210 SAS-R12 IMM-c	Network queue policies in network mode
Queue management policies	Queues at service ingress, service egress, and network egress	defines the CBS and MBS parameters for the queues enables or disables the high-slope and low-slope parameters for the queues supported on the 7210 SAS-R6 IMM-b, 7210 SAS-R12 IMM-b, 7210 SAS-R6 IMM-c, and 7210 SAS-R12 IMM-c; on the 7210 SAS-R6 IMM-c and 7210 SAS-R12 IMM-c, only WRED slope parameters are used	Queue management policies for 7210 SAS-Mxp, 7210 SAS-R6, and 7210 SAS-R12
Remark	SAP egress, network egress (port and IP interface)	defines the FC-to-remarking values supported on the 7210 SAS-R6 IMM-b, 7210 SAS-R12 IMM-b, 7210 SAS-R6 IMM-c, and 7210 SAS-R12 IMM-c	Remark policies on 7210 SAS-Mxp, 7210 SAS-R6, 7210 SAS-R12, 7210 SAS-S 1/10GE, 7210 SAS-Sx 10/100GE, and 7210 SAS-T (network mode)