Overview of network QoS policies

Network QoS policies have an ingress and egress component, which define the QoS processing behavior provided for packets that ingress the access-uplink port and egress the access-uplink port, respectively.

The ingress component of the port policy defines how the dot1p bits are mapped to the internal FC and profile state. The FC and profile state define the PHB and the QoS handling through the system. The mapping on each access uplink port defaults to the mappings defined in the default network QoS policy until an explicit policy is defined for the access uplink ports. It also defines the bandwidth-limiting parameters for the traffic mapped to each FC. Traffic mapped to each FC can be limited to configurable bandwidth values using separate meters for unicast traffic and multipoint traffic.

Note:

7210 SAS platforms provide different mechanisms to limit the bandwidth per FC. On 7210 SAS-D and 7210 SAS-Dxp, the user needs to use policers/meters to rate-limit the traffic per FC.

The egress component of the network QoS ip-interface policy type defines the marking values associated with each FC.

Access uplink port egress marking support consists of the following:

Non-default network policy parameters can be modified. The no form of the command reverts to the default values.

Changes made to a policy are applied immediately to all access uplink ports where the policy is applied. For this reason, when a policy requires several changes, Nokia recommends that you copy the policy to a work area policy-id. The work-in-progress copy can be modified, and then the original policy-id can be overwritten using the config qos copy command.

See ‟CLI Usage” in the 7210 SAS-D, Dxp, K 2F1C2T, K 2F6C4T, K 3SFP+ 8C Basic System Configuration Guide for information about the tasks and commands necessary to access the command line interface, and to configure and maintain your devices.