Access egress QoS policies on 7210 SAS-T, 7210 SAS-Sx/S 1/10GE, and 7210 SAS-Sx 10/100GE

An access egress policy defines the access port queues, the FC- to-queue mapping, and the marking characteristics for the traffic egressing toward the customer on the access ports. By configuring queue shaping rates, the individual FC traffic can be managed so that each FC traffic is within SLA limits and does not impact the serviceability of other FCs.

The number of queues available per access port on different 7210 SAS platforms is the following:

• On the 7210 SAS-T, there are 8 (eight) queues always available per access port, and all FC traffic is mapped into these separate 8 (eight) queue as per the FC-to-queue-ID map. See Table: Forwarding class to queue-ID map for more information.

• On the 7210 SAS-Sx/S 1/10GE and 7210 SAS-Sx 10/100GE, 16 queues are available per access port, with 8 (eight) queues allocated for unicast traffic and 8 (eight) allocated for multicast traffic. For each of the 8 (eight) FCs, unicast and multicast traffic are mapped to two different queues, for a total of 16 queues across 8 (eight) FCs. See Table: Forwarding class-to-queue ID map for 7210 SAS-Sx/S 1/10GE and 7210 SAS-Sx 10/100GE for more information.

To define a basic access egress QoS policy, the following are required:

• unique service access QoS policy ID

• QoS policy scope of template or exclusive

• see Queue parameters for information about the parameters configured for a queue

• on 7210 SAS-Sx/S 1/10GE and 7210 SAS-Sx 10/100GE, access egress policy allows users to specify a single rate for both multicast and unicast queues, meaning that rates cannot be specified individually for the unicast and multicast queue of an FC. Instead, the rate specified for a queue (for example, queue 8) is distributed equally to the unicast queue and multicast queue associated with the FC. See Schedulers on 7210 SAS-Sx/S 1/10GE and 7210 SAS-Sx 10/100GE for more information.

• remarking (for example, IEEE 802.1p value) based on FC

On the 7210 SAS-T, 7210 SAS-Sx/S 1/10GE, and 7210 SAS-Sx 10/100GE, remarking of dot1p or DSCP or both bits by default is disabled and can be enabled by the remarking command, with options to remark dot1p, dscp, or both present under access-egress context.

The following options are available on different platforms:

• In 7210 SAS-T, 7210 SAS-Sx/S 1/10GE, and 7210 SAS-Sx 10/100GE, network mode, the user is provided with an option to remark dot1p or DSCP or both.

• In 7210 SAS-T access-uplink mode, the user is provided with an option to remark both dot1p bits and IP DSCP bits.

The FC determination per service egress packet is determined at ingress. If the packet ingressed the service on the same router, the service ingress classification rules determine the FC of the packet.

The FC is determined as follows for network mode and access-uplink mode:

• In network mode, if the packet is received over a service transport tunnel on a network port, the FC is typically determined by the MPLS LSP EXP bits.

• For 7210 SAS-T in access-uplink mode, if the packet was received on a access-uplink port, the FC is determined by the dot1p bits in the outer tag of the QinQ encapsulation.

Access egress QoS policy ID 1 is reserved as the default for access ports that do not have another access egress policy explicitly assigned. The following table lists the characteristics of the default policy.