This chapter provides information to configure network QoS policies using the CLI.
Network QoS policies have an ingress and egress component, which define the QoS processing behavior to be provided for packets that ingress the access-uplink port and egress the access-uplink port respectively.
The ingress component of the policy defines how the IP DSCP and dot1p values using the DSCP and dot1p classification policies are mapped to internal FC and profile state for the 7210 SAS-K 2F1C2T. The FC 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 bandwidth-limiting parameters for the traffic mapped to each FC. Traffic mapped to each FC can be limited to configurable bandwidth values using separate queues for unicast traffic and multipoint traffic.
7210 SAS platforms provide different mechanisms to limit the bandwidth per FC. On 7210 SAS-K 2F1C2T, users can use the queue with packet buffers and a rate shaper to limit and shape the traffic per FC. Use of queue with shapers typically allows for better TCP traffic behavior in the network.
The egress component of the network QoS policy defines the marking values associated with each FC.
On the 7210 SAS, the user has an option to define the number of queues to use per access-uplink port and map the FC to queues. By default, network QoS policy 1 is used for access-uplink ports, until an explicit policy is associated. The default policy creates eight queues per access-uplink port. The queues are assigned default values for all the parameters defined with the default policy.
Access-uplink port egress marking supports the following.
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 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.
Refer to the CLI usage chapter in the 7210 SAS-D, Dxp, K 2F1C2T, K 2F6C4T, K 3SFP+ 8C Basic System Configuration Guide for information about the tasks and commands required to access the CLI and to configure and maintain 7210 SAS devices.
The queues required for access-uplink port egress are allocated for the egress queue system pool. Queues from the egress queue system pool are allocated for per SAP egress queues and per access-uplink port egress queues.
The dot1p policy and DSCP policy resources used for network qos ingress FC assignment on access-uplink port, is shared with the per SAP ingress classification criteria from the system pool.
A basic network QoS policy must conform to the following:
Configuring and applying QoS policies other than the default policy is optional. A default network policy of the appropriate type is applied to each access uplink port.
To create an network QoS policy, define the following.
Use the following syntax to create a network QoS policy for 7210 SAS-K 2F1C2T.
Use the following syntax to associate a network QoS policy with the access-uplink port.
The following is a sample configuration output that displays uplink port 1/1/1 with network policy 600 applied to the interface.
The default network policy for access-uplink ports is identified as policy-id “1”. Default policies cannot be modified or deleted. The following is sample configuration output that shows the default network policy parameters.
Table 32 and Table 33 list default network policy parameters.
Field | Default |
description | Default network QoS policy. |
scope | template |
ingress | |
default-action | fc be profile out |
egress | |
remarking | No |
fc af: | |
dot1p-in-profile | 3 |
dot1p-out-profile | 2 |
fc be: | |
dot1p-in-profile | 0 |
dot1p-out-profile | 0 |
fc ef: | |
dot1p-in-profile | 5 |
dot1p-out-profile | 5 |
fc h1: | |
dot1p-in-profile | 6 |
dot1p-out-profile | 6 |
fc h2: | |
dot1p-in-profile | 4 |
dot1p-out-profile | 4 |
fc l1: | |
dot1p-in-profile | 3 |
dot1p-out-profile | 2 |
fc l2: | |
dot1p-in-profile | 1 |
dot1p-out-profile | 1 |
fc nc: | |
dot1p-in-profile | 7 |
dot1p-out-profile | 7 |
dot1p 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 network QoS policy has an ingress and egress component, which define the QoS processing behavior for packets that ingress into the network port, hybrid port, and access-uplink port, and egress from the network port, hybrid port, and access-uplink port, respectively.
The ingress component of the policy defines how the IP DSCP and dot1p values using the DSCP and dot1p classification policies are mapped to the internal FC and profile state for the 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C. The FC 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 bandwidth-limiting parameters for the traffic mapped to each FC. Traffic mapped to each FC can be limited to configurable bandwidth values using separate queues for unicast traffic and multipoint traffic.
Note: The 7210 SAS platforms provide different mechanisms to limit the bandwidth per FC. On the 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C, use the queue with packet buffers and a rate shaper to limit and shape the traffic per FC. Use of queues with shapers allows better TCP traffic behavior in the network. |
The egress component of the network QoS policy defines the marking values associated with each FC.
The user has an option to define the number of queues to use per access-uplink port and map the FC to queues. By default, network QoS policy “1” is used for access-uplink ports, until an explicit policy is associated. The default policy creates eight queues per access-uplink port. The queues are assigned default values for all the parameters defined with the default policy.
Access-uplink port egress marking supports 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.
Refer to the CLI usage chapter in the 7210 SAS-D, Dxp, K 2F1C2T, K 2F6C4T, K 3SFP+ 8C Basic System Configuration Guide for information about the tasks and commands required to access the CLI, and to configure and maintain your devices.
The ingress component of the policy defines how the MPLS EXP, IP DSCP, and dot1p values that use classification policies are mapped to internal FC and profile state for 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C. The FC and profile state define the Per Hop Behavior (PHB) or the QoS treatment through the system. The mapping on each network port and hybrid port defaults to the mapping defined in the default network QoS policy, unless an explicit policy is defined for the network ports. The policy 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 queues for unicast traffic and multipoint traffic.
Note: The 7210 SAS platforms provide different mechanisms to limit the bandwidth per FC. On the 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C, use the queue with packet buffers and a rate shaper to limit and shape the traffic per FC. Use of queues with shapers allows better TCP traffic behavior in the network. |
The egress component of the network QoS policy defines the marking values associated with each FC.
The user has an option to define the number of queues to use per network port and hybrid port, and to map the FC to queues. By default, network QoS policy “2” is used for network ports, unless an explicit policy is associated. The default policy creates eight queues per network port or hybrid port. The queues are assigned default values for all the parameters defined with the default policy.
Network port egress marking supports 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.
Refer to the CLI usage chapter in the 7210 SAS-D, Dxp, K 2F1C2T, K 2F6C4T, K 3SFP+ 8C Basic System Configuration Guide for information about the tasks and commands required to access the CLI, and to configure and maintain your devices.
The queues required for network port egress, hybrid port egress, and access-uplink port egress are allocated from the egress queue system pool. Queues from the egress queue system pool are shared among SAP egress queues, access-uplink port egress queues, network port egress queues, and hybrid port egress queues.
The dot1p policy and DSCP policy resources used for network QoS ingress FC assignment on network ports, hybrid ports, and access-uplink ports are shared with the per-SAP ingress classification criteria from the system pool.
The MPLS EXP policy resources used for network QoS ingress FC assignment on network ports and hybrid ports are allocated from the system pool.
A basic network QoS policy must conform to the following:
This section provides information about creating a network QoS policy on 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C.
See Create a Network QoS Policy for Access-Uplink Ports on 7210 SAS-K 2F1C2T for more information.
The default network policy for access-uplink ports is identified as policy-id 1. Default policies cannot be modified or deleted.
The following is a sample configuration output for default network policy ID 1 used for the access-uplink port on the 7210 SAS-K 2F6C4T.
The following is a sample configuration output for default network policy ID 1 used for the access-uplink port on the 7210 SAS-K 3SFP+ 8C.
Configuring and applying QoS policies other than the default policy is optional. A default network policy is applied to each network port or hybrid port.
To create a network QoS policy, define the following.
Use the following syntax to create a network QoS policy for network port on the 7210 SAS-K 2F6C4T or 7210 SAS-K 3SFP+ 8C.
config>qos>network
network network-policy-id [create]
no network network-policy-id
The following commands associate a network QoS policy with the network port on the 7210 SAS-K 2F6C4T or 7210 SAS-K 3SFP+ 8C.
The following is a sample configuration output for network port 1/1/1 with network policy 600 applied to the port.
The default network policy for network ports is identified as policy-id “2”. Default policies cannot be modified or deleted.
The following is a sample configuration output for default network policy ID 2 used for the network port on the 7210 SAS-K 2F6C4T.
The following is a sample configuration output for default network policy ID 2 used for the network port on the 7210 SAS-K 3SFP+ 8C.
The user can configure DSCP marking for CPU-generated traffic on the 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C platforms only. See QoS for CPU Self-Generated Traffic on Network Interfaces for the 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C for more information about QoS for self-generated (CPU) traffic on the 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C. Table 34 lists the default DSCP and dot1p marking values for the 7210 SAS-K 2F1C2T.
Note: Protocols such as BGP, RSVP, TLDP, OSPF, and IS-IS are not supported on 7210 SAS devices configured in access-uplink mode. |
Protocol | IPv4 | DSCP Marking | dot1p Marking | Default FC | DSCP Values | dot1p Values |
SNMP | Yes | Yes | Yes | H2 | 34 | 4 |
NTP | Yes | Yes | Yes | H2 | 48 | 7 |
TELNET | Yes | Yes | Yes | H2 | 34 | 4 |
FTP | Yes | Yes | Yes | H2 | 34 | 4 |
TFTP | Yes | Yes | Yes | H2 | 34 | 4 |
SYSLOG | Yes | Yes | Yes | H2 | 34 | 4 |
TACACS | Yes | Yes | Yes | H2 | 34 | 4 |
RADIUS | Yes | Yes | Yes | H2 | 34 | 4 |
SSH | Yes | Yes | Yes | H2 | 34 | 7 |
ICMP Req | Yes | Yes | Yes | NC | 0 | 7 |
ICMP Res | Yes | Yes | Yes | NC | 0 | 7 |
ICMP Unreach | Yes | Yes | Yes | NC | 0 | 7 |
SCP | NA | NA | Yes | H2 | 34 | 4 |
STP | NA | NA | Yes | NC | - | 7 |
CFM | NA | NA | Yes | NC | - | 7 |
ARP | NA | NA | Yes | NC | - | 7 |
SNMP trap/log | Yes | Yes | Yes | H2 | 34 | 4 |
ICMP ping | Yes | Yes | Yes | NC | 0 | 7 |
Trace route | Yes | Yes | Yes | NC | 0 | 7 |
TACPLUS | Yes | Yes | Yes | H2 | 34 | 4 |
IGMP | Yes | Yes | Yes | NC | 48 | 7 |
PTP | Yes | Yes | Yes | H2 | 48 | 7 |
Table 35 lists the default DSCP and dot1p marking values for the 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C.
Protocol | IPv4 | DSCP Marking | dot1p Marking | Default FC | DSCP Values (Decimal) | dot1p Values |
OSPF | Yes | Yes | Yes | NC | 48 | 7 |
ISIS | Yes | No | Yes | NC | - | 7 |
TLDP | Yes | Yes | Yes | NC | 48 | 7 |
RSVP | Yes | Yes | Yes | NC | 48 | 7 |
SNMP | Yes | Yes | Yes | H2 | 34 | 4 |
NTP | Yes | Yes | Yes | NC | 48 | 7 |
TELNET | Yes | Yes | Yes | H2 | 34 | 4 |
FTP | Yes | Yes | Yes | H2 | 34 | 4 |
TFTP | Yes | Yes | Yes | H2 | 34 | 4 |
SYSLOG | Yes | Yes | Yes | H2 | 34 | 4 |
TACACS | Yes | Yes | Yes | H2 | 34 | 4 |
RADIUS | Yes | Yes | Yes | NC | 48 | 7 |
SSH | 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 |
SCP | Yes | Yes | Yes | H2 | 34 | 4 |
PIM (SSM) | Yes | Yes | Yes | NC | 48 | 7 |
STP | NA | NA | Yes | NC | - | 7 |
CFM | NA | NA | Yes | NC | - | 7 |
ARP | NA | NA | Yes | NC | - | 7 |
Trace route | Yes | Yes | Yes | NC | 0 | 7 |
TACPLUS | Yes | Yes | Yes | H2 | 34 | 4 |
IGMP | Yes | Yes | Yes | NC | 48 | 7 |
DNS | Yes | Yes | Yes | H2 | 34 | 4 |
BGP | Yes | Yes | Yes | NC | 48 | 7 |
PTP (see note 1) | Yes | Yes | Yes | see note 1 | see note 1 | 7 |
Note:
Note: DSCP and dot1p values in Table 35 are applicable when remarking is disabled on the egress service object (for example, access port, SAP, and network port) used to send out the packets. |
DSCP, 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.
DSCP marking for internally-generated control and management traffic should be used for a specified application. The DSCP marking 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 also be set per application. When an application is configured to use a specified DSCP value and 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, because it applies to the logical interface the packet is egressing.
Configuring self-generated QoS traffic is supported in the base router and VPRN service contexts.
Table 34 and Table 35 list the default values for self-generated traffic on network interfaces.
Note:
|
Table 36 lists the DSCP mapping between DSCP names and DSCP values (decimal, hexadecimal, and binary), and labels.
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 | 0b0100010 | h2 |
af42 | 36 | 0x24 | 0b100100 | h2 |
af43 | 38 | 0x26 | 0b100110 | h2 |
default 1 | 0 |
Note:
This section provides information about service management tasks.
A network policy is associated by default with access-uplink ports.
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.
Use the following syntax to delete a network policy.
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.
Use the following syntax to overwrite a network policy.
The following is a sample configuration output.
You can change existing policies, except the default policies, and entries in the CLI. The changes are applied immediately to all 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.