7. Network QoS policies
This chapter provides information to configure network QoS policies using the command line interface.
7.1. Overview
This section provides an overview of QoS policies in network mode and access up-link mode.
7.1.1. Overview of network QoS policies in network mode
Network QoS policies are available for use with network IP interfaces, network ports and hybrid ports when operating the 7210 SAS in network and standalone mode. The 7210 SAS-T, 7210 SAS-Sx/S 1/10GE, 7210 SAS-Sx 10/100GE, 7210 SAS-Mxp, 7210 SAS-R6, and 7210 SAS-R12 support network and standalone mode of operation.
The following types of QoS mapping decisions are applicable on a network IP interface when operating in network and standalone mode:
- MPLS LSP EXP value mapping to FC (if defined)
- default QoS mapping
- MPLS LSP EXP mapping to profile
The default QoS mapping always exists on an IP interface and every received packet will be mapped to this default if another explicitly defined matching entry does not exist.
The following types of QoS mapping decisions are applicable on a network port when operating in network mode:
- Ethernet dot1P and IP DSCP value mapping (if defined) for use with IP packets
- default QoS mapping
The default QoS mapping always exists on network port and every received packet is mapped to the default if another explicitly defined matching entry does not exist.
7.1.1.1. Overview of network QoS policies in access-uplink mode
Network QoS policies are available for use with access-uplink port when operating the 7210 SAS in access-uplink mode. The 7210 SAS-T supports the access-uplink mode of operation.
The following types of QoS mapping decisions are applicable on an access-uplink port when operating in access-uplink mode:
- option to mark Ethernet dot1p or IP DSCP
- default QoS mapping
The default QoS mapping always exists on an ingress access uplink port and every received packet is mapped to this default if another explicitly defined matching entry does not exist.
The following sections provide more details about the network QoS policies for both network mode and access-uplink mode.
7.2. Network QoS policy in network mode
The network QoS policy consists of an ingress and egress component. For the 7210 SAS-T, 7210 SAS-Sx/S 1/10GE, 7210 SAS-Sx 10/100GE, 7210 SAS-Mxp, 7210 SAS-R6, and 7210 SAS-R12 operating in network mode, there are two types of network QoS policies; network QoS policy of type port and network QoS policy of type ip-interface.
A port type network policy is applied to network and hybrid ports and is used for classification and remarking of IP traffic using DSCP or dot1p values. Either DSCP or dot1p can be used for ingress classification but not both. Both DSCP and dot1p can be configured at egress for remarking.
An ip-interface type network policy is applied to an IP Interface, and is used for classification and remarking of MPLS traffic using EXP values. Note that the FC-to-dot1p marking values configured on the port are also used to mark the dot1p in the VLAN tag, if any, used for MPLS traffic on some 7210 SAS devices.
The ingress component of the port policy type defines how the DSCP or dot1p bits are mapped to internal forwarding class (FC) and profile state. The ingress component of the ip-interface policy type defines how the EXP bits are mapped to the internal FC and profile state. The FC and profile state define the per-hop behavior (PHB) or the QoS treatment through the 7210 SAS. The ingress profile assignments using MPLS-EXP bits are defined using the mpls-lsp-exp-profile-map policy, which defines the mapping between the MPLS LSP EXP bits and the profile (in or out) associated with a packet.
The mapping on each ip-interface or port policy defaults to the mappings defined in the default network QoS policy until an explicit policy is defined for the IP interface or port. 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 and queues for unicast and multipoint traffic. Multipoint is used for IP interfaces for MPLS traffic and for IP multicast traffic received on a network or hybrid port. On both network IP interface ingress and network port ingress, color-aware meters are provisioned by default to use the ingress profile assigned to the packet, if configured.
The total number of QoS resources—that is, ingress classification entries and policers—available for use with IP interfaces is limited. The software allocates these resources to an IP interface on a first-come, first-served basis. The number of resources used per IP interface limits the total number of IP interfaces configured on the system. The total number of IP interfaces allowed is also subject to a system limit.
The egress component of the network QoS ip-interface policy type defines the LSP EXP bits marking values associated with each FC. The egress component of the network QoS port policy type defines the DSCP or dot1p bits marking values associated with each FC.
By default, all ports configured in network mode use the default network policy "1" and all network port IP interfaces use the default network policy "2". Default network policies "1" and "2" cannot be modified or deleted.
New (non-default) network policy parameters can be modified. The no form of this command reverts to the default values.
Changes made to a policy are applied immediately to all network ports, hybrid ports, and IP interfaces 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 until all the changes are made, and then the original policy-id can be overwritten using the config qos copy command.
Refer to the “CLI Usage” chapter in the 7210 SAS-Mxp, R6, R12, S, Sx, T Basic System Configuration Guide for information about the tasks and commands required to access the CLI and to configure and maintain 7210 SAS devices.
7.2.1. Network QoS policy (ip-interface type) behaviour for MPLS LSPs
The following behavior is supported with use of network IP interface QoS policies for LDP, segment routing (SR), and RSVP (with fast reroute (FRR) or penultimate hop popping (PHP)) MPLS LSPs:
- The mpls-lsp-exp-profile-map policy allows you to specify the profile mapping and FC mapping independently. The FC to use is always taken from the network policy using the EXP-to-FC mapping configured in the network policy. The EXP-to-profile mapping defined in the mpls-lsp-exp-profile-map policy associated with the network QoS policy is used. Each IP interface can define a unique network policy for use, and each network policy uses a different MPLS LSP EXP-to-FC mapping. If adequate network classification resources are available, this mapping allows the use of more than 32 distinct network policies.
- MPLS transport tunnels that are set up using LDP and segment routing use a global mpls-lsp-exp-profile-map policy. Although the system assigns a default mpls-lsp-exp-profile-map policy, the user can change the default and specify the global policy to use.
- Use the mpls-lsp-exp-profile-map policy to assign profile values based on the MPLS EXP bits for MPLS packets received over different IP interfaces. This is particularly useful for RSVP LSPs with FRR 1:1 configurations.
- For LDP LSPs or when using the FRR facility, Nokia recommends that a single mpls-lsp-exp-profile-map policy should be used for all IP interfaces. If PHP is enabled, the egress LER receives only VC-labeled packets and the global mpls-lsp-exp-profile-map policy is used for profile mapping. Therefore, when PHP is enabled, a single mpls-lsp-exp-profile-map policy should be used for all IP interfaces to get consistent profile treatment.
- If traffic is received on a transport tunnel set up using RSVP LSP, LDP or SR with an identical EXP bit value, the system provides the same QoS treatment to the MPLS traffic. The FC and meter from the network QoS policy are used for all MPLS traffic received on an IP interface, regardless of whether it is LDP or RSVP LSP. The profile value assigned depends on the configuration. If the user needs similar profile mapping for MPLS traffic received across all transport tunnels, a single mpls-lsp-exp-profile-map must be used for all IP interfaces and for the global mpls-lsp-exp-profile-map.
7.2.2. Basic configurations
A basic network QoS policy must conform to the following:
- Each network QoS policy must have a unique policy ID.
- The network must specify the default action.
- The network must have a QoS policy scope of template or exclusive.
7.2.3. Create a network QoS policy (ip-interface type) for network mode
Configuring and applying QoS policies other than the default policy is optional. A default network policy of the type ip-interface is applied to each IP interface.
To create an network QoS policy of the ip-interface type when operating in network mode, define the following:
- Specify a network policy ID value. The system does not dynamically assign a value.
- Set the network-policy-type parameter to ip-interface.
- Include a description that provides a brief overview of policy features.
- Use egress marking and remarking to specify the egress LSP EXP marking map; otherwise, the default values are applied. The following are defined:
- remarkingThe remark policy-id command specifies the policy, which defines the mapping of the FC-to-packet header priority profile and bits.The remarking command uses the associated policy configured with the remark policy-id command to determine which priority bits to mark on egress.When remarking is enabled, MPLS EXP bits for all MPLS LSR and LER traffic are marked on egress on the specified network IP interface. Remarking is based on the FC-to-LSP EXP bit mapping that is defined in the remark policy and associated under the egress node of the network QoS policy. The EXP marking values used depend on the configured remark policy. If the user does not attach an explicit policy, the default policy is used.When remarking is disabled for MPLS LSR traffic, EXP values received on ingress are not modified on egress. For MPLS LER traffic where the node adds the MPLS encapsulation, MPLS EXP bits are set based on the mapping specified in the policy associated with the IP interface. If the user does not attach an explicit policy, the default policy is used.
- FC criteriaThe FC name represents an egress queue. Specify FC criteria to define the egress characteristics of the queue and the marking criteria of packets flowing through it.
- LSP EXPThe EXP is used for all packets requiring marking that egress on this FC queue that are in or out of profile.
- Specify ingress criteria using the following:
- default actionDefines the default action to take for packets that have undefined bits set. The default action specifies the FC to which these packets are assigned.
- LSP EXPCreates a mapping between the LSP EXP bits of the network ingress MPLS traffic and the FC. Ingress MPLS traffic that matches the specified EXP bits are assigned to the corresponding FC. The user has an option to specify the mapping of the LSP EXP bits to a profile (in or out). Ingress traffic that matches the specified EXP bits is assigned the corresponding profile.
Use the following syntax to create a network QoS policy.
7.2.3.1. Example for network QoS policy of ip-interface type
The following is a sample configuration output of a network ip-interface type QoS policy for the 7210 SAS-Mxp, 7210 SAS-R6, 7210 SAS-R12, 7210 SAS-Sx/S 1/10GE, 7210 SAS-Sx 10/100GE, and 7210 SAS-T.
7.2.4. Configuring network QoS policy (port type) for network mode
To create a network QoS policy of the port type when operating in network mode, define the following:
- Specify a network policy ID value. The system does not dynamically assign a value.
- Set the network-policy-type parameter to port.
- Include a description that provides a brief overview of policy features.
- Modify the egress DSCP and dot1p marking map; otherwise, the default values are applied:
- remarkingWhen enabled, this command remarks all IP packets that egress the specified network port. The remarking is based on the FC-to-DSCP bit mapping defined in the remark policy and associated under the egress node of the network QoS policy for all IP traffic. FC-to-dot1p marking for MPLS packets is not supported; it is supported only for IP packets.
- FC criteriaThe FC name represents an egress queue. Specify FC criteria to define the egress characteristics of the queue and the marking criteria of packets flowing through it.
- DSCP and dot1pSpecify the DSCP and dot1p value to use for IP packets requiring marking that egress on this FC queue that are in or out of profile.
- Specify ingress criteria as either DSCP or dot1p (but not both) to FC mapping for all IP packets. Define the following:
- default actionDefines the default action to take for packets that have undefined DSCP or dot1p bits set. The default action specifies the FC to which these packets are assigned.
- DSCP or dot1pCreates a mapping between the DSCP or dot1p bits of network ingress IP traffic and the FC. Ingress IP traffic that match the specified DSCP or dot1p bits are assigned to the corresponding FC.
The following example shows the command usage to associate a network QoS policy with the network port.
Use the following syntax to create a network QoS policy.
The following is a sample configuration output of a network port type QoS policy on the 7210 SAS-T, 7210 SAS-Sx/S 1/10GE, 7210 SAS-Sx 10/100GE, and 7210 SAS-Mxp.
The following is a sample configuration output of a network port type QoS policy on the 7210 SAS-R6 and 7210 SAS-R12.
7.2.5. Default network policy values available in network mode
The default network policy for IP interfaces is identified as policy-id 2. Default policies cannot be modified or deleted. The following table lists default network policy parameters.
Table 46: Network policy defaults for policy ip-interface type
Field | Default |
description | Default network QoS policy |
scope | template |
ingress | |
default-action | fc be profile out (default action profile out is applicable only for port policies and not for ip-interface policies) |
mpls-lsp-exp-profile | 1 |
egress | |
remarking | no |
fc af: | |
lsp-exp-in-profile | 3 |
lsp-exp-out-profile | 2 |
fc be: | |
lsp-exp-in-profile | 0 |
lsp-exp-out-profile | 0 |
fc ef: | |
lsp-exp-in-profile | 5 |
lsp-exp-out-profile | 5 |
fc h1: | |
lsp-exp-in-profile | 6 |
lsp-exp-out-profile | 6 |
fc h2: | |
lsp-exp-in-profile | 4 |
lsp-exp-out-profile | 4 |
fc h11: | |
lsp-exp-in-profile | 3 |
lsp-exp-out-profile | 2 |
fc h12: | |
lsp-exp-in-profile | 1 |
lsp-exp-out-profile | 1 |
fc nc: | |
lsp-exp-in-profile | 7 |
lsp-exp-out-profile | 7 |
The following table lists default parameters for network QoS policy ip-interface type, LSP EXP-to-FC mapping on ingress. Color-aware policing is supported on network ingress.
Table 47: Default network QoS policy of ip-interface type, LSP EXP-to-FC mapping on Ingress
LSP EXP value | FC ingress | Profile |
0 | be | Out |
1 | l2 | In |
2 | af | Out |
3 | af | In |
4 | h2 | In |
5 | ef | In |
6 | h1 | In |
7 | nc | In |
The default network policy for port is identified as policy-id 1. Default policies cannot be modified or deleted.
The following is a sample configuration output that shows the parameters for the default network port type QoS policy for the 7210 SAS-T, 7210 SAS-Sx/S 1/10GE, 7210 SAS-Sx 10/100GE, 7210 SAS-Mxp, 7210 SAS-R6, and 7210 SAS-R12.
The following is a sample configuration output for the default remark policy used for dot1p and DSCP marking on the 7210 SAS-R6 and 7210 SAS-R12.
7.2.6. Resource allocation for network QoS policy
This section describes the allocation of QoS resources for network QoS policies of the ip-interface and port type.
When an IP interface is created, a default network QoS policy of the ip-interface type is applied. For the default policy, two meters and two classification entries in hardware are allocated.
The resources are allocated to a network policy only when a port is configured for the IP interface. When a network port is configured, a default network QoS policy of the port type is applied.
For every FC in use, the system allocates two classification entries in hardware, provided the FC is configured to use both the unicast meter and multicast meter, or provided the default meter 9 is configured in the policy. If multiple match criteria entries map to the same FC, each of these are allocated two classification entries in hardware; for example, if there are two match-criteria entries that map to FC “af,” a total of four classification entries are allocated in hardware, and if there are four match-criteria entries that map to FC “af,” a total of eight classification entries are allocated in hardware.
For every meter or policer in use, the system allocates one meter in hardware. A meter or policer is considered in use when it is associated with an FC in use.
The number of IP interfaces and network ports allowed is limited by the number of classification resources available in hardware, subject to the system limit on the number of IP interfaces and network or hybrid ports supported by the system.
Calculating the Number of QoS Resources
To calculate the number of QoS resources used by an IP interface, determine the following items:
- number of match-criteria entries used to identify the FC
- number of FCs to use
Only the FCs used by the match-criteria classification entries are considered in the “number of FCs” and are therefore are referred to as “FCs in use”. In network policies of the ip-interface type, a default multipoint meter 9 is created in a policy; for policies of the port type, a default multipoint meter needs to be explicitly configured by the user, if required.
Use the following rules to compute the number of classification entries per FC in use:
- If an FC is in use and is created without explicit meters, use default meter 1 for unicast traffic and default meter 9 (if configured) for all other traffic types (that is, broadcast, multicast, and unknown-unicast). This requires two classification entries in hardware. If default multipoint meter 9 is not configured, the FC uses the unicast meter for all traffic types. In this case, the FC requires a single classification entry in hardware.
- If an FC is in use and is created with an explicit unicast meter, use that meter for unicast traffic and use default meter 9 (if configured) for all other traffic types. This requires two classification entries in hardware. If default multipoint meter 9 is not configured, the FC uses the unicast meter for all traffic types. In this case, the FC requires a single classification entry in hardware.
- If an FC is in use and is created with an explicit unicast meter and explicit multicast meter, use the unicast meter for unicast traffic and a multicast meter for all other kinds of traffic. This requires two classification entries in hardware.
Given the number of match criteria and the number of FCs in use, the following equation calculates the total number of classification entries (TC) per policy:
TC = Σ 2 * E(i)
i = nc, h1, ef, h2, l1, af, l2, be
where:
- E(i) is the number of match-criteria entries that classify packets to FCi. For the 7210 SAS platforms, the maximum number of classification entries per policy can be 64 (including default).
 | Note: In the worst case, only 2 classification entries are used for each FC in a network policy, because only two types of traffic are supported. |
Determining the Number of policers or Meters
Determine the number of policers or meters (TP) to use. A maximum of 16 meters per network policy are available.
The number of TPs used is the number of meters configured in the policy. Among that number, only those meters configured for use with an FC are considered during resource allocation. Meters that are created but not associated with an FC are not counted for resource allocation.
7.2.6.1. Network QoS policies resource usage examples
| Note: In the examples in this section, the profile configuration is not shown. In practice, users must configure the mpls-lsp-exp-profile policy and associate it with the network policy. Association of a profile policy with the network QoS policy does not change the resource calculation methodology shown in the following examples. |
7.2.6.1.1. Example 1
The number of classification entries (TC) used is calculated, as follows:
(2 * 0)nc + (2 * 0)h1 + (2 * 0)ef + (2 * 0)h2 + (2 * 0)l1 + (2 * 0)af + (2 * 0)l2 + (2 * 1)be = 2
The number of meters (TP) used is 2 (meters 1 and 9).
7.2.6.1.2. Example 2
The number of classification entries (TC) used is calculated, as follows:
(2 * 0)nc + (2 * 0)h1 + (2 * 0)ef + (2 * 0)h2 + (2 * 0)l1 + (2 * 1)af + (2 * 0)l2 + (2 * 1)be = 4
The number of meters (TP) user is 4 (meters 1, 2, 9, and 12)
7.2.6.1.3. Example 3
The number of classification entries (TC) used are calculated, as follows:
(2 * 0)nc + (2 * 0)h1 + (2 * 0)ef + (2 * 0)h2 + (2 * 0)l1 + (2 * 1)af + (2 * 0)l2 + (2 * 1)be = 4
The number of meters (TP) user is 2 (meters 2 and 12).
7.2.6.1.4. Example 4
The number of Filter-Entries (TC) used is calculated, as follows:
(2 * 1)nc + (2 * 1)h1 + (2 * 1)ef + (2 * 1)h2 + (2 * 0)l1 + (2 * 2)af + (2 * 1)l2 + (2 * 1)be = 16
The number of meters (TP) used is 2 (meters 1 and 9).
7.2.6.1.5. Example 5
The number of classification entries (TC) used is calculated, as follows:
(2 * 1)nc + (2 * 1)h1 + (2 * 1)ef + (2 * 1)h2 + (2 * 0)l1 + (2 * 2)af + (2 * 1)l2 + (2 * 1)be = 16
The number of meters (TP) used is 2 (meters 1 and 9). Note that meters 2 and 12 are not accounted for because they are not associated with any FC.
7.2.6.1.6. Example 6
The number of classification entries (TC) used is calculated, as follows:
(2 * 1)nc + (2 * 1)h1 + (2 * 1)ef + (2 * 1)h2 + (2 * 0)l1 + (2 * 2)af + (2 * 1)l2 + (2 * 1)be = 16
The number of meters (TP) used is 5 (meters 1, 2, 3, 9, and 12).
7.2.6.1.7. Example 7
The number of classification entries (TC) used is 2.
The number of meters (TP) used is 2.
7.2.6.1.8. Example 8
The number of classification entries (TC) used is calculated, as follows:
(2 * 2)nc + (2 * 0)h1 + (2 * 1)ef + (2 * 0)h2 + (2 * 0)l1 + (2 * 1)af + (2 * 1)l2 + (0 * 0)be = 10
The numbers of meters (TP) used is 6 (meters 2, 3, 4, 7, 8, and 12).
7.3. Network QoS policy in access-uplink mode
The network QoS policy consists of an ingress and egress component. For 7210 SAS-T devices operating in access-uplink mode, network policy is available for use. The ingress component of the policy defines how dot1p bits are mapped to internal forwarding class and profile state (DSCP is not available for use). The forwarding class and profile state define the Per Hop Behavior (PHB) or the QoS treatment 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 rate-limiting parameters for the traffic mapped to each forwarding classes. Traffic mapped to each forwarding class can be rate limited using separate meters for each unicast and multipoint traffic.
The egress component of the network QoS policy provides an option to define either dot1p bits and IP DSCP marking values or both associated with each forwarding class. By default, network QoS policy remarking is always disabled. If the egressing packet originated on an ingress SAP, the egress QoS policy also defines the dot1p bit marking based on the forwarding class and the profile state. The default map of FC-dot1p marking is as shown in default network QoS policy of type 'port', where in the policy-id is equal to 1. All non-default network QoS policies inherits the FC-dot1p map.
Network policy-id 1 exists as the default policy and is applied to access uplink ports.The network policy-id 1 cannot be modified or deleted. It defines the default dot1p-to-FC mapping and default meters for unicast and multipoint meters for the ingress. For the egress, it defines eight forwarding classes and the packet marking criteria.
New (non-default) network policy parameters can be modified. The no form of this command reverts the object to the default values.
Changes made to a policy are applied immediately to all ports where the policy is applied. For this reason, when a policy requires several changes, it is recommended that you copy the policy to a work area policy-id. The work-in-progress copy can be modified until all the changes are made and then the original policy-id can be overwritten with the config qos copy command.
For information about the tasks and commands necessary to access the command line interface and to configure and maintain your devices, refer to CLI Usage chapter in the 7210 SAS-Mxp, R6, R12, S, Sx, T Basic System Configuration Guide.
7.3.1. Basic configurations
A basic network QoS policy must conform to the following:
- Each network QoS policy must have a unique policy ID.
- The network must specify the default-action.
- The network must have a QoS policy scope of template or exclusive.
7.3.2. Configuring network policy for access-uplink mode
To create an network QoS policy when operating in access-uplink mode, define the following:
- A network policy ID value. The system does not dynamically assign a value.
- Include a description. The description provides a brief overview of policy features.
- You can modify egress dot1p and/or IP DSCP marking map. Otherwise, the default values are applied:
- remarkingWhen enabled, this command remarks ALL packets that egress on the specified network port. The remarking is based on the forwarding class to dot1p bit and/or IP DSCP value mapping.
- forwarding class criteriaThe forwarding class name represents an egress queue. Specify forwarding class criteria to define the marking criteria of packets flowing through it.
- DSCP and dot1pThe DSCP and dot1p value to use for all packets requiring marking that egress on this forwarding class queue that are in or out of profile.
- Ingress criteriaSpecifies dot1p to forwarding class mapping for all packets.
- default actionDefines the default action to be taken for packets that have an undefined DSCP or dot1p bits set. The default-action specifies the forwarding class to which such packets are assigned.
- DSCP and dot1pCreates a mapping between the DSCP and dot1p bits of the access uplink port ingress traffic and the forwarding class. Ingress traffic that matches the specified DSCP and dot1p bits will be assigned to the corresponding forwarding class.
The following commands associated a network QoS policy with the access-uplink port.
Use the following syntax to create a network QoS policy for 7210 SAS-T in access uplink mode.
7.3.3. Default network policy values available in access-uplink mode
This following output sample is of a default network port policy on 7210 SAS-T in access-uplink mode.
7.4. DSCP and dot1p marking for CPU self-generated traffic
DSCP and dot1p marking for CPU self-generated traffic is not user-configurable, except on the 7210 SAS-Mxp, 7210 SAS-R6, and 7210 SAS-R12 (see QoS for self-generated (CPU) traffic on network interfaces for the 7210 SAS-Mxp, 7210 SAS-R6, and 7210 SAS-R12). Table 48 lists the default CPU QoS values for DSCP and dot1p marking.
| Note:
|
Table 48: Default CPU QoS values for DSCP and dot1p marking
Protocol | IPv4 | DSCP marking | Dot1p marking | Default FC | DSCP values (decimal) | Dot1p values |
ARP | N/A | N/A | Yes | NC | — | 7 |
BGP | Yes | Yes | Yes | NC | 48 | 7 |
Cflowd | Yes | Yes | Yes | NC | 48 | 7 |
CFM | N/A | N/A | Yes | NC | — | 7 |
DNS | Yes | Yes | Yes | H2 | 34 | 4 |
FTP | Yes | Yes | Yes | H2 | 34 | 4 |
ICMP Req | Yes | Yes | Yes | NC | 0 | 7 |
ICMP Res | Yes | Yes | Yes | NC | 0 | 7 |
ICMP Unreach | Yes | Yes | Yes | NC | 0 | 7 |
IGMP | Yes | Yes | Yes | NC | 48 | 7 |
IS-IS | Yes | No | Yes | NC | — | 7 |
MSDP | Yes | Yes | Yes | NC | 48 | 7 |
NTP | Yes | Yes | Yes | NC | 48 | 7 |
OSPF | Yes | Yes | Yes | NC | 48 | 7 |
PIM (SSM) | Yes | Yes | Yes | NC | 48 | 7 |
PTP | Yes | Yes | Yes | H2 | 48 | 7 |
RADIUS | Yes | Yes | Yes | H2 | 34 | 4 |
RSVP | Yes | Yes | Yes | NC | 48 | 7 |
SCP | Yes | Yes | Yes | H2 | 34 | 4 |
SNMP | Yes | Yes | Yes | H2 | 34 | 4 |
SSH | Yes | Yes | Yes | H2 | 34 | 4 |
STP | N/A | N/A | Yes | NC | — | 7 |
SYSLOG | Yes | Yes | Yes | H2 | 34 | 4 |
TACACS | Yes | Yes | Yes | H2 | 34 | 4 |
TACPLUS | Yes | Yes | Yes | H2 | 34 | 4 |
TELNET | Yes | Yes | Yes | H2 | 34 | 4 |
TFTP | Yes | Yes | Yes | H2 | 34 | 4 |
TLDP | Yes | Yes | Yes | NC | 48 | 7 |
Trace route | Yes | Yes | Yes | NC | 0 | 7 |
7.4.1. QoS for self-generated (CPU) traffic on network interfaces for the 7210 SAS-Mxp, 7210 SAS-R6, and 7210 SAS-R12
Differentiated services code point (DSCP), forwarding class (FC), and IEEE 802.1p values can be specified for use by protocol packets generated by the node. This enables prioritization or deprioritization of supported protocols (as required).
DSCP marking for internally generated control and management traffic should be used for a specified application. This can be configured per routing instance. For example, OSPF packets can carry a different DSCP marking for the base instance than for a VPRN service. ARP and IS-IS are not IP protocols, so only 802.1p values can be configured.
The DSCP value can be set per application. When an application is configured to use a specified DSCP value and an FC, the 802.1p and MPLS EXP bits are marked in accordance with the network (default 802.1p value of 7) or access (default 802.1p value of 0) egress policy as it applies to the logical interface the packet is egressing.
Configuring self-generated QoS is supported in the base router and VPRN service contexts.
The default values for self-generated traffic on network interfaces are the following:
- routing protocols (for example, OSPF and BGP)
- FC - Network Control (NC)
- DSCP value - NC1 (not applicable for ARP and IS-IS)
- 802.1p value - according to the egress QoS policy (7 by default)
- management protocols (for example, SSH and SNMP)
- FC - Network Control (NC)
- DSCP value - AF41
- 802.1p value - according to the egress QoS policy (7 by default)
| Note:
|
7.4.2. Default DSCP mapping table
The following table lists the DSCP mapping between DSCP name and DSCP values (decimal, hexadecimal, and binary) and label.
Table 49: Default DSCP mapping table
DSCP name | DSCP value decimal | DSCP value hexadecimal | DSCP value binary | Label |
Default | 0 | 0x00 | 0b000000 | be |
nc1 | 48 | 0x30 | 0b110000 | h1 |
nc2 | 56 | 0x38 | 0b111000 | nc |
ef | 46 | 0x2e | 0b101110 | ef |
af11 | 10 | 0x0a | 0b001010 | assured |
af12 | 12 | 0x0c | 0b001100 | assured |
af13 | 14 | 0x0e | 0b001110 | assured |
af21 | 18 | 0x12 | 0b010010 | l1 |
af22 | 20 | 0x14 | 0b010100 | l1 |
af23 | 22 | 0x16 | 0b010110 | l1 |
af31 | 26 | 0x1a | 0b011010 | l1 |
af32 | 28 | 0x1c | 0b011100 | l1 |
af33 | 30 | 0x1d | 0b011110 | l1 |
af41 | 34 | 0x22 | 0b100010 | h2 |
af42 | 36 | 0x24 | 0b100100 | h2 |
af43 | 38 | 0x26 | 0b100110 | h2 |
default 1 | 0 |
- The default FC mapping is used for all DSCP names/values for which there is no explicit FC mapping.
Note:
7.5. Service management tasks
This section provides information about service management tasks.
7.5.1. Deleting QoS policies
A network policy is associated by default with IP interfaces and network ports for devices operating in network mode. A network policy is associated by default with access uplink ports for devices in access uplink mode.
You can replace the default policy with a non-default policy, but you cannot remove default policies from the configuration. When you remove a non-default policy, the policy association reverts to the appropriate default network policy.
7.5.2. Remove a policy from the QoS configuration
Use the following syntax to delete a network policy.
7.5.3. Copying and overwriting network policies
You can copy an existing network policy to a new policy ID value or overwrite an existing policy ID. The overwrite option must be specified or an error occurs if the destination policy ID exists.
The following is a sample configuration output.
7.5.4. Editing QoS policies
You can change existing policies, except the default policies, and entries in the CLI. The changes are applied immediately to all network ports or IP interfaces or access uplink ports where the policy is applied. To prevent configuration errors, use the copy command to make a duplicate of the original policy to a work area, make the edits, and then overwrite the original policy.