The 7210 SAS devices are designed with ingress and egress QoS mechanisms to support multiple services per physical port. The 7210 SAS devices are extensive and flexible capabilities to classify, policy, queue, shape, and mark traffic.
The QoS capabilities supported on different 7210 SAS platforms are different. That is, not all the platforms support all of the capabilities. Please read through the following chapters to know what is available on different 7210 SAS platforms.
In the Nokia service router service model, a service is provisioned on the provider-edge (PE) equipment. Service data is encapsulated and then sent in a service tunnel (for example, QinQ tunnel, dot1q tunnel, IP/MPLS tunnel, and so on) to the far-end Nokia service router where the service data is delivered.
The operational theory of a service tunnel is that the encapsulation of the data between the two Nokia service routers appear as a Layer 2 path to the service data; however, the data is really traversing an QinQ or IP or IP/MPLS core. The tunnel from one edge device to the other edge device is provisioned with an encapsulation, and the services are mapped to the tunnel that most appropriately supports the service needs.
The 7210 SAS supports the following FCs, internally named: Network-Control, High-1, Expedited, High-2, Low-1, Assured, Low-2, and Best-Effort. See FCs for more information about FCs.
The 7210 SAS supports the use of different types of QoS policies to handle the specific QoS needs at each point in the service delivery model within the device. QoS policies are defined in a global context in the 7210 SAS and only take effect when the policy is applied to an entity.
QoS policies are uniquely identified with a policy ID number or name. Typically, Policy ID 1 or Policy ID ‟default” is reserved for the default policy, however, there are a few instances where the default QoS policy uses a different ID. The default QoS policy is used if no policy is explicitly applied.
The QoS policies supported on the 7210 SAS can be divided into the following main types:
policies that are used for classification, defining metering and queuing attributes and defining marking behavior
slope policies that define default buffer allocations and weighted random early detection (WRED) slope definitions
port scheduler policies, SAP-ingress and egress policies, or network and network-queue policies that determine how queues are scheduled