Forwarding class-to-queue ID map on 7210 SAS-Sx/S 1/10GE and 7210 SAS-Sx 10/100GE

There are 8 FCs supported on the device. Each of these FC is mapped to two queues, one used for unicast traffic mapped to the FC and another used for multicast/BUM traffic mapped to the FC. By mapping an FC to different queues, the differential treatment is imparted to various classes of traffic.

In the 7210 SAS-Sx/S 1/10GE and 7210 SAS-Sx 10/100GE devices, there are 16 queues available at the port level for all ports on the device. These 16 queues are created by default per port. Users cannot create or delete the queues or the queue ID. Only the queue parameters can be changed. On 7210 SAS-Sx/S 1/10GE and 7210 SAS-Sx 10/100GE, the queue ID represents one of the 8 scheduling nodes corresponding to 8 FCs. It is not a configurable entity and queue ID 1 to 8 are, by default, used to identify these 8 FC scheduling nodes available on the port. Parameters for these 8 FCs can be configured as part of the access egress QoS policy that is applied on the access ports, and network queue policy that is applied on the network ports and hybrid ports.

The queue IDs 1 to 8 are assigned to each of the 8 FCs. Queue ID 8 is the highest priority scheduling node and queue ID 1 is the lowest priority scheduling node. FCs are correspondingly mapped to these queue IDs according to their priority. The following table describes the system-defined map.