The 7210 SAS devices are designed with ingress and egress QoS mechanisms to support multiple services for each physical port. The 7210 SAS devices provide extensive and flexible capabilities to classify, police, queue, shape, and mark traffic.
Not all QoS capabilities are supported on all 7210 SAS platforms. The following chapters describe what is supported 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 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 behave like a Layer 2 path to the service data; however, the data is really traversing an IP or IP/MPLS core. The tunnel from one edge device to the other edge device is provisioned with 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 Forwarding classes for more information about the 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, which is used if no policy is explicitly applied. There are a few instances where the default QoS policy uses a different ID.
The QoS policies supported on the 7210 SAS can be divided into the following main types:
QoS policies that are used for classification, defining metering and queuing attributes, and defining marking behavior.
Slope policies that are used to define default buffer allocations and weighted random early detection (WRED) slope definitions.
Port scheduler policies, SAP ingress and egress policies, and network and network-queue policies that determine how queues are scheduled.