This section provides a list of configuration guidelines for access SAP egress policies.
This section applies to SAPs configured on access ports and hybrid ports.
The configuration guidelines for access SAP egress policies are the following:
On the 7210 SAS-K 2F1C2T and 7210 SAS-K 2F6C4T, hardware queues are allocated in groups of two, and on the 7210 SAS-K 3SFP+ 8C, hardware queues are allocated in groups of four; these grouped queues are reserved for use by the SAP even if the user specifies an odd value. The 7210 SAS-K 2F1C2T and 7210 SAS-K 2F6C4T support two, four, six, or eight queues per SAP. The 7210 SAS-K 3SFP+ 8C supports four or eight queues per SAP.
FC-to-queue map can be defined; this allows the user to assign the packets classified into a particular FC to any one of the queues configured for the SAP.
Both unicast traffic and BUM traffic share a single queue per FC. In other words, unlike service ingress policy, it is not possible to assign different queues for BUM traffic and unicast traffic.
The queue parameters such as queue shaper rate (CIR/PIR), CBS and MBS, queue priority and weight can be defined. The assigned priority and weight is used to determine the priority and weight of the queue in both the CIR and PIR scheduling loop.
WRED slopes (per queue) can be configured: high-slope and low-slope. Depending on the queue mode and the profile assigned to the packet on SAP ingress classification, one of the configured WRED slopes is used to evaluate if a buffer can be allocated to the packet. In-profile packets use the high-slope and out-of-profile packets use the low-slope.
SP scheduling and WFQ scheduling for SAP ingress queues are supported.