Network QoS policies

This chapter provides information to configure network QoS policies using the command line interface.

Overview

This section provides an overview of QoS policies in network mode and access up-link mode.

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.

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.

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.

See 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.

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.

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.

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:

    • remarking

      The 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 criteria

      The 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 EXP

      The 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 action

      Defines 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 EXP

      Creates 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.

config>router
    interface interface-name
        qos network-policy-id

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.

*7210 SAS>config>qos>network# info 
----------------------------------------------
            ingress
                meter 1 create
                exit
                meter 3 create
                exit
                meter 5 multipoint create
                exit
                meter 9 multipoint create
                exit
                fc "ef" create
                    meter 3
                    multicast-meter 5
                exit
                lsp-exp 0 fc be
                lsp-exp 1 fc l2
                lsp-exp 2 fc af
                lsp-exp 3 fc af
                lsp-exp 4 fc h2
                lsp-exp 5 fc ef
            exit
            egress
                remarking             
                remark 200
            exit
----------------------------------------------

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:

    • remarking

      When 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 criteria

      The 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 dot1p

      Specify 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 action

      Defines 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 dot1p

      Creates 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.

network port (in network mode)
config> port
    ethernet
        network
            qos network-policy-id

Use the following syntax to create a network QoS policy.

config>qos# 
    network policy-id [network-policy-type network-policy-type]
        description description-string
scope {exclusive|template}
        egress
            remarking
            remark <policy-id>
        ingress
            default-action fc {fc-name} profile {in|out}
            lsp-exp lsp-exp-value fc fc-name profile {in | out}
            fc {fc-name}
                meter {meter-id}
                multicast-meter {id}
            meter meter-id [multipoint]
                adaptation-rule cir {closest | max | min} pir {closest | max | min}
                cbs {size-in-kbits}
                mbs {size-in-kbits}
                mode {trtcm | srtcm}
                rate cir cir-rate-in-kbps [pir pir-rate-in-kbps]
            mpls-lsp-exp-profile policy-id

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.

*A:dut-d>config>qos>network# info detail
----------------------------------------------
            description "Default network-port QoS policy."
            scope template
            ingress
                default-action fc be profile out
                meter 1 create
                    mode trtcm1
                    adaptation-rule cir closest pir closest
                    rate cir 0 pir max
                    mbs default kbits
                    cbs default kbits
                exit
                dscp be fc be profile out
                dscp ef fc ef profile in
                dscp cs1 fc l2 profile in
                dscp nc1 fc h1 profile in
                dscp nc2 fc nc profile in
                dscp af11 fc af profile in
                dscp af12 fc af profile out
                dscp af41 fc h2 profile in
            exit
            egress
                no remarking
                fc af
                    dscp-in-profile af11
                    dscp-out-profile af12
                    no dot1p
                    dot1p-in-profile 3
                    dot1p-out-profile 2
                    no de-mark
                exit
                fc be
                    dscp-in-profile be
                    dscp-out-profile be
                    no dot1p
                    dot1p-in-profile 0
                    dot1p-out-profile 0
                    no de-mark
                exit
                fc ef

The following is a sample configuration output of a network port type QoS policy on the 7210 SAS-R6 and 7210 SAS-R12.

A:Dut-B>config>qos>network# info detail
----------------------------------------------
            description "Default network-port QoS policy."
            scope template
            ingress
                default-action fc be profile out
                meter 1 create
                    mode trtcm1
                    adaptation-rule cir closest pir closest
                    rate cir 0 pir max
                    mbs default kbits
                    cbs default kbits
                exit
                dscp be fc be profile out
                dscp ef fc ef profile in
                dscp cs1 fc l2 profile in
                dscp nc1 fc h1 profile in
                dscp nc2 fc nc profile in
                dscp af11 fc af profile in
                dscp af12 fc af profile out
                dscp af41 fc h2 profile in
            exit
            egress
                no remarking
                remark 1
            exit
----------------------------------------------
A:Dut-B>config>qos>network#

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 1. 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 2. 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.


*A:Dut-A>config>qos>network# info detail
----------------------------------------------
            description "Default network-port QoS policy."
            scope template
            ingress
                default-action fc be profile out
                meter 1 create
                    mode trtcm1
                    adaptation-rule cir closest pir closest
                    rate cir 0 pir max
                    mbs default kbits
                    cbs default kbits
                exit
                dscp be fc be profile out
                dscp ef fc ef profile in
                dscp cs1 fc l2 profile in
                dscp nc1 fc h1 profile in
                dscp nc2 fc nc profile in
                dscp af11 fc af profile in
                dscp af12 fc af profile out
                dscp af41 fc h2 profile in
            exit
            egress
                no remarking
                remark 1
            exit
----------------------------------------------
*A:Dut-A>config>qos>network#

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.

fc af
                    dscp-in-profile af11
                    dscp-out-profile af12
                    no lsp-exp-in-profile
                    no lsp-exp-out-profile
                    no dot1p-lsp-exp-in-profile
                    no dot1p-lsp-exp-out-profile
                    dot1p-in-profile 3
                    dot1p-out-profile 2
                exit
                fc be
 [no] de-mark
                    [no] dot1p 
                    dscp-in-profile be
                    dscp-out-profile be
                    no lsp-exp-in-profile
                    no lsp-exp-out-profile
                    no dot1p-lsp-exp-in-profile
                    no dot1p-lsp-exp-out-profile
                    dot1p-in-profile 0
                    dot1p-out-profile 0
                exit
                fc ef                 
                    dscp-in-profile ef
                    dscp-out-profile ef
                    no lsp-exp-in-profile
                    no lsp-exp-out-profile
                    no dot1p-lsp-exp-in-profile
                    no dot1p-lsp-exp-out-profile
                    dot1p-in-profile 5
                    dot1p-out-profile 5
                exit
                fc h1
                    dscp-in-profile nc1
                    dscp-out-profile nc1
                    no lsp-exp-in-profile
                    no lsp-exp-out-profile
                    no dot1p-lsp-exp-in-profile
                    no dot1p-lsp-exp-out-profile
                    dot1p-in-profile 6
                    dot1p-out-profile 6
                exit
                fc h2
                    dscp-in-profile af41
                    dscp-out-profile af41
                    no lsp-exp-in-profile
                    no lsp-exp-out-profile
                    no dot1p-lsp-exp-in-profile
                    no dot1p-lsp-exp-out-profile
                    dot1p-in-profile 4
                    dot1p-out-profile 4
                exit
                fc l1
                    dscp-in-profile af21
                    dscp-out-profile af22
                    no lsp-exp-in-profile
                    no lsp-exp-out-profile
                    no dot1p-lsp-exp-in-profile
                    no dot1p-lsp-exp-out-profile
                    dot1p-in-profile 3
                    dot1p-out-profile 2
                exit
                fc l2
                    dscp-in-profile cs1
                    dscp-out-profile cs1
                    no lsp-exp-in-profile
                    no lsp-exp-out-profile
                    no dot1p-lsp-exp-in-profile
                    no dot1p-lsp-exp-out-profile
                    dot1p-in-profile 1
                    dot1p-out-profile 1
                exit
                fc nc
                    dscp-in-profile nc2
                    dscp-out-profile nc2
                    no lsp-exp-in-profile
                    no lsp-exp-out-profile
                    no dot1p-lsp-exp-in-profile
                    no dot1p-lsp-exp-out-profile
                    dot1p-in-profile 7
                    dot1p-out-profile 7
                exit

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.

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.

Example 1
network 1 network-policy-type ip-interface create
     description ‟network-policy-1”
            ingress
                default-action fc be 
                meter 1 create
                exit
                meter 9 multipoint create
                exit
            exit
     egress
                fc af
                exit
                fc be
                exit
                fc ef
                exit
                fc h1
                exit
                fc h2
                exit
                fc l1
                exit
                fc l2
                exit
                fc nc
                exit
            exit

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).

Example 2
network 2 network-policy-type ip-interface create
     description ‟network-policy-2”
            ingress
                default-action fc be 
                meter 1 create
                exit
                meter 2 create
                exit
                meter 9 multipoint create
                exit
                meter 12 multipoint create
                exit
                fc "af" create
                    meter 2
                    multicast-meter 12
                exit
                lsp-exp 2 fc af 
            exit
            egress
                fc af
                exit
                fc be
                exit
                fc ef
                exit
                fc h1
                exit
                fc h2
                exit
                fc l1
                exit
                fc l2
                exit
                fc nc
                exit
            exit
      exit

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)

Example 3
network 3 network-policy-type ip-interface create
     description ‟network-policy-3”
            ingress
                default-action fc be 
                meter 1 create
                exit
                meter 2 create
                exit
                meter 9 multipoint create
                exit
                meter 12 multipoint create
                exit
                fc "af" create
                    meter 2
                    multicast-meter 12
                exit
                fc "be" create
                    meter 2
                    multicast-meter 12
                exit
                lsp-exp 2 fc af 
            exit
            egress
                fc af
                exit
                fc be
                exit
                fc ef
                exit
                fc h1
                exit
                fc h2
                exit
                fc l1
                exit
                fc l2
                exit
                fc nc
                exit
            exit
exit

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).

Example 4
network 4 network-policy-type ip-interface create
     description ‟network-policy-4”
            ingress
                default-action fc be 
                meter 1 create
                exit
                meter 9 multipoint create
                exit
                lsp-exp 1 fc l2 
                lsp-exp 2 fc af 
                lsp-exp 3 fc af 
                lsp-exp 4 fc h2 
                lsp-exp 5 fc ef 
                lsp-exp 6 fc h1 
                lsp-exp 7 fc nc 
            exit
            egress
                fc af
                exit
                fc be
                exit
                fc ef
                exit
                fc h1
                exit
                fc h2
                exit
                fc l1
                exit
                fc l2
                exit
                fc nc
                exit
            exit
exit

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).

Example 5
network 5 network-policy-type ip-interface create
     description ‟network-policy-5”
            ingress
                default-action fc be 
                meter 1 create
                exit
                meter 2 create
                exit
                meter 9 multipoint create
                exit
                meter 12 multipoint create
                exit
                fc "af" create
                exit
                fc "be" create
                exit
                fc "ef" create
                exit
                fc "h1" create
                exit
                fc "h2" create
                exit
                fc "l2" create
                exit
                fc "nc" create
                exit
                lsp-exp 1 fc l2 
                lsp-exp 2 fc af 
                lsp-exp 3 fc af 
                lsp-exp 4 fc h2 
                lsp-exp 5 fc ef 
                lsp-exp 6 fc h1 
                lsp-exp 7 fc nc 
            exit
            egress
                fc af
                exit
                fc be
                exit
                fc ef
                exit
                fc h1
                exit
                fc h2
                exit
                fc l1
                exit
                fc l2
                exit
                fc nc
                exit
            exit

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.

Example 6
network 6 network-policy-type ip-interface create
     description ‟network-policy-6”

            ingress
                default-action fc be 
                meter 1 create
                exit
                meter 2 create
                exit
                meter 3 create
                exit
                meter 9 multipoint create
                exit
                meter 12 multipoint create
                exit
                fc "af" create
                    meter 2
                    multicast-meter 12
                exit
                fc "be" create
                exit
                fc "ef" create
                exit
                fc "h1" create
                    meter 3
                exit
                fc "h2" create
                exit
                fc "l2" create
                exit
                fc "nc" create
                    meter 3
                exit
                lsp-exp 1 fc l2 
                lsp-exp 2 fc af 
                lsp-exp 3 fc af 
                lsp-exp 4 fc h2 
                lsp-exp 5 fc ef 
                lsp-exp 6 fc h1 
                lsp-exp 7 fc nc 
            exit
            egress
                fc af
                exit
                fc be
                exit
                fc ef
                exit
                fc h1
                exit
                fc h2
                exit
                fc l1
                exit
                fc l2
                exit
                fc nc
                exit
            exit
exit

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).

Example 7
network 2 network-policy-type ip-interface create
            description "Default network QoS policy."
            scope template
            ingress
                default-action fc be 
                meter 1 create
                    mode trtcm 
                    adaptation-rule cir closest pir closest
                    rate cir 0 pir max
                    mbs default
                    cbs default
                exit
                meter 9 multipoint create
                    mode trtcm 
                    adaptation-rule cir closest pir closest
                    rate cir 0 pir max
                    mbs default
                    cbs default
                exit
                lsp-exp 0 fc be 
                lsp-exp 1 fc l2 
                lsp-exp 2 fc af 
                lsp-exp 3 fc af 
                lsp-exp 4 fc h2 
                lsp-exp 5 fc ef 
                lsp-exp 6 fc h1 
                lsp-exp 7 fc nc 
            exit
            egress
                no remarking 
                fc af
                    lsp-exp-in-profile 3
                    lsp-exp-out-profile 2
                exit
                fc be
                    lsp-exp-in-profile 0
                    lsp-exp-out-profile 0
                exit
                fc ef
                    lsp-exp-in-profile 5
                    lsp-exp-out-profile 5
                exit
                fc h1
                    lsp-exp-in-profile 6
                    lsp-exp-out-profile 6
                exit                  
                fc h2
                    lsp-exp-in-profile 4
                    lsp-exp-out-profile 4
                exit
                fc l1
                    lsp-exp-in-profile 3
                    lsp-exp-out-profile 2
                exit
                fc l2
                    lsp-exp-in-profile 1
                    lsp-exp-out-profile 1
                exit
                fc nc
                    lsp-exp-in-profile 7
                    lsp-exp-out-profile 7
                exit
            exit
exit

The number of classification entries (TC) used is 2.

The number of meters (TP) used is 2.

Example 8
network 8 network-policy-type ip-interface create
description ‟network-policy-8”
            ingress
                default-action fc nc 
                meter 1 create
                exit
                meter 2 create
                exit
                meter 3 create
                exit
                meter 4 create
                exit
                meter 5 create
                exit
                meter 7 multipoint create
                exit
                meter 8 multipoint create
                exit
                meter 9 multipoint create
                exit
                meter 12 multipoint create
                exit
                fc "af" create
                    meter 2           
                    multicast-meter 12
                exit
                fc "ef" create
                    meter 4
                    multicast-meter 8
                exit
                fc "h2" create
                exit
                fc "l2" create
                    meter 3
                    multicast-meter 7
                exit
                fc "nc" create
                    meter 4
                    multicast-meter 8
                exit
                lsp-exp 1 fc l2 
                lsp-exp 3 fc af 
                lsp-exp 5 fc ef 
                lsp-exp 7 fc nc 
            exit
            egress
                fc af
                exit
                fc be
                exit
                fc ef
                exit
                fc h1
                exit
                fc h2
                exit
                fc l1
                exit
                fc l2
                exit
                fc nc
                exit
            exit
exit

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).

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, see the "CLI Usage" chapter in the 7210  SAS-Mxp, R6, R12, S, Sx, T Basic System Configuration Guide.

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.

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:

    • remarking

      When 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 criteria

      The forwarding class name represents an egress queue. Specify forwarding class criteria to define the marking criteria of packets flowing through it.

    • DSCP and dot1p

      The 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 criteria

    Specifies dot1p to forwarding class mapping for all packets.

    • default action

      Defines 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 dot1p

      Creates 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.

config>port
    ethernet
        access
            uplink
                qos network-policy-id

Use the following syntax to create a network QoS policy for 7210 SAS-T in access uplink mode.

A:MTU>config>qos>network# info detail
----------------------------------------------
            description "Default network-port QoS policy."
            scope template
            ingress
                default-action fc be profile out
                meter 1 create
                    mode trtcm1
                    adaptation-rule cir closest pir closest
                    rate cir 0 pir max
                    mbs default kbits
                    cbs default kbits
                exit
                meter 9 multipoint create
                    mode trtcm1
                    adaptation-rule cir closest pir closest
                    rate cir 0 pir max
                    mbs default kbits
                    cbs default kbits
                exit
                dot1p 0 fc be profile out
                dot1p 1 fc l2 profile in
                dot1p 2 fc af profile out
                dot1p 3 fc af profile in
                dot1p 4 fc h2 profile in
                dot1p 5 fc ef profile in
                dot1p 6 fc h1 profile in
                dot1p 7 fc nc profile in
            exit
            egress
                no remarking
                fc af
                    dscp-in-profile af11
                    dscp-out-profile af12
                    no dot1p
                    dot1p-in-profile 3
                    dot1p-out-profile 2
                    no de-mark
                exit
                fc be
                    dscp-in-profile be
                    dscp-out-profile be
                    no dot1p
                    dot1p-in-profile 0
                    dot1p-out-profile 0
                    no de-mark
                exit
                fc ef
                    dscp-in-profile ef
                    dscp-out-profile ef
                    no dot1p
                    dot1p-in-profile 5
A:MTU>config>qos>network#

Default network policy values available in access-uplink mode

The following sample output is of a default network port policy on 7210 SAS-T in access-uplink mode.

*7210SAST>config>qos>network# info detail
----------------------------------------------
            description "Default network-port QoS policy."
            scope template
            ingress
                default-action fc be profile out
                meter 1 create
                    mode trtcm1
                    adaptation-rule cir closest pir closest
                    rate cir 0 pir max
                    mbs default kbits
                    cbs default kbits
                exit
                meter 9 multipoint create
                    mode trtcm1
                    adaptation-rule cir closest pir closest
                    rate cir 0 pir max
                    mbs default kbits
                    cbs default kbits
                exit
                dot1p 0 fc be profile out
                dot1p 1 fc l2 profile in
                dot1p 2 fc af profile out
                dot1p 3 fc af profile in
                dot1p 4 fc h2 profile in
                dot1p 5 fc ef profile in
                dot1p 6 fc h1 profile in
                dot1p 7 fc nc profile in
            exit
            egress
                no remarking
                fc af
                    dscp-in-profile af11
                    dscp-out-profile af12
                    no dot1p
                    dot1p-in-profile 3
                    dot1p-out-profile 2
                    no de-mark
                exit
                fc be
                    dscp-in-profile be
                    dscp-out-profile be
                    no dot1p
                    dot1p-in-profile 0
                    dot1p-out-profile 0
                    no de-mark
                exit
                fc ef
                    dscp-in-profile ef
                    dscp-out-profile ef
                    no dot1p
                    dot1p-in-profile 5
                    dot1p-out-profile 5
                    no de-mark
                exit
                fc h1
                    dscp-in-profile nc1
                    dscp-out-profile nc1
                    no dot1p
                    dot1p-in-profile 6
                    dot1p-out-profile 6
                    no de-mark
                exit
                fc h2
                    dscp-in-profile af41
                    dscp-out-profile af41
                    no dot1p
                    dot1p-in-profile 4
                    dot1p-out-profile 4
                    no de-mark
                exit
                fc l1
                    dscp-in-profile af21
                    dscp-out-profile af22
                    no dot1p
                    dot1p-in-profile 3
                    dot1p-out-profile 2
                    no de-mark
                exit
                fc l2
                    dscp-in-profile cs1
                    dscp-out-profile cs1
                    no dot1p
                    dot1p-in-profile 1
                    dot1p-out-profile 1
                    no de-mark
                exit
                fc nc
                    dscp-in-profile nc2
                    dscp-out-profile nc2
                    no dot1p
                    dot1p-in-profile 7
                    dot1p-out-profile 7
                    no de-mark
                exit
            exit
----------------------------------------------

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). Default CPU QoS values for DSCP and dot1p marking lists the default CPU QoS values for DSCP and dot1p marking.

Note:
  • Protocols such as BGP, RSVP, TLDP, OSPF, and IS-IS are not supported on 7210 SAS platforms operating in access-uplink mode.

  • For PTP messages, based on the message type (event or non-event), the DSCP value used is either 0x30 (h1) or 0x38 (nc), and the dot1p value is always 7.

  • DSCP and dot1p values in the table are applicable when remarking is disabled at the port level.

Table 3. 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

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:
  • ICMP echo requests (type 8) and ICMPv6 echo requests (type 128) initiated from the router use the DSCP value that is specified in the sgt-qos command. The FC value is NC by default, or the value that is specified in the ping command parameter fc fc-name.

  • Configurable values for BFD are not supported.

  • On access SAP egress and access port egress, when remarking is not enabled, the dot1p value for all IP packets generated by the node is set to zero. To enable dot1p marking, remarking must be enabled.

Default DSCP mapping table

The following table lists the DSCP mapping between DSCP name and DSCP values (decimal, hexadecimal, and binary) and label.

Table 4. 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

Service management tasks

This section provides information about service management tasks.

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.

Remove a policy from the QoS configuration

Use the following syntax to delete a network policy.

config>qos# no network network-policy-id

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.

config>qos# copy network source-policy-id dest-policy-id [overwrite]

The following is a sample configuration output.

A:ALA-12>config>qos# info detail
---------------------------------------------
...
        network 1 create
            description "Default network QoS policy."
            scope template
            ingress
                default-action fc be profile out
...
        network 600 create
            description "Default network QoS policy."
            scope template
            ingress
                default-action fc be profile out
...
        network 700 create
            description "Default network QoS policy."
            scope template
            ingress
                default-action fc be profile out
...
---------------------------------------------
A:ALA-12>config>qos# 

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.

Network QoS policy command reference

Command hierarchies

Configuration commands (7210 SAS-T, 7210 SAS-Sx/S 1/10GE, and 7210 SAS-Sx 10/100GE configured in network mode)

config
    - qos
        - [no] network network-policy-id [create]
        - [no] network network-policy-id [create] [network-policy-type {ip-interface | port}] 
            - description description-string 
            - no description
            - scope {exclusive | template}
            - no scope
            - egress
                - no remark
                - remark policy-id
                - remarking 
                - no remarking
            - ingress
                - default-action fc fc-name profile {in | out | use-dei}
                - dot1p dot1p-priority fc fc-name profile {in | out | use-dei}
                - no dot1p dot1p-priority
                - [no] fc fc-name [create]
                    - meter meter-id
                    - no meter
                    - multicast-meter meter-id
                    - no multicast-meter
                - dscp dscp-name fc fc-name profile {in | out}
                - no dscp dscp-name
                - lsp-exp lsp-exp-value fc fc-name
                - no lsp-exp lsp-exp-value
                - meter meter-id [multipoint] [create]
                - no meter meter-id
                    - adaptation-rule [cir adaptation-rule] [pir adaptation-rule]
                    - no adaptation-rule
                    - cbs size [kbits | bytes | kbytes] 
                    - no cbs
                    - mbs size [kbits | bytes | kbytes] 
                    - no mbs
                    - mode mode
                    - no mode
                    - rate cir-rate-in-kbps [pir pir-rate-in-kbps]
                    - no rate
                - [no] mpls-lsp-exp-profile policy-id

Configuration commands (7210 SAS-Mxp, 7210 SAS-R6, and 7210 SAS-R12)

config
    - qos
        - [no] network network-policy-id [create] [network-policy-type {ip-interface | port}] 
            - description description-string 
            - no description
            - egress
                - remark policy-id
                - no remark
                - remarking 
                - no remarking
            - ingress
                - default-action fc fc-name profile {in | out | use-dei}
                - dot1p dot1p-priority fc fc-name profile {in | out | use-dei}
                - no dot1p dot1p-priority
                - [no] fc fc-name [create]
                    - meter meter-id
                    - no meter
                    - multicast-meter meter-id
                    - no multicast-meter
                - dscp dscp-name fc fc-name profile {in | out}
                - no dscp dscp-name
                - lsp-exp lsp-exp-value fc fc-name 
                - no lsp-exp lsp-exp-value
                - mpls-lsp-exp-profile policy-id
                - no mpls-lsp-exp-profile
                - meter meter-id [multipoint] [create]
                - no meter meter-id
                    - adaptation-rule [cir adaptation-rule] [pir adaptation-rule]
                    - no adaptation-rule
                    - cbs size [kbits | bytes | kbytes] 
                    - no cbs
                    - mbs size [kbits | bytes | kbytes] 
                    - no mbs
                    - mode mode
                    - no mode
                    - rate cir-rate-in-kbps [pir pir-rate-in-kbps]
                    - no rate
            - scope {exclusive | template}
            - no scope

Configuration commands (access-uplink mode)

config
    - qos
        - [no] network network-policy-id [network-policy-type] {ip-interface | port} (only type port is supported) 
            - description description-string
            - no description
            - no scope {exclusive | template}
            - egress
                - [no] fc fc-name
                    - [no] de-mark [force de-value]
                    - dot1p dot1p-priority
                    - no dot1p
                    - dscp-in-profile dscp-name
                    - no dscp-in-profile
                    - dscp-out-profile dscp-name
                    - no dscp-out-profile
                    - dot1p-in-profile dot1p-priority
                    - no dot1p-in-profile
                    - dot1p-out-profile dot1p-priority
                    - no dot1p-out-profile
                - [no] remarking {use-dot1p | use-dscp | all}
            - ingress
                - default-action fc fc-name profile {in | out | use-dei}
                - dot1p dot1p-priority fc fc-name profile {in | out | use-dei}
                - no dot1p dot1p-priority
                - [no] fc fc-name [create]
                    - meter meter-id
                    - no meter
                    - multicast-meter meter-id
                    - no multicast-meter
                - meter meter-id [multipoint] [create]
                - no meter meter-id
                    - adaptation-rule [cir adaptation-rule] [pir adaptation-rule]
                    - no adaptation-rule
                    - cbs size-in-kbits
                    - no cbs
                    - mbs size-in-kbits
                    - no mbs
                    - mode {trtcm1 | trtcml2 | srtcm}
                    - no mode
                    - rate cir-rate-in-kbps [pir pir-rate-in-kbps]
                    - no rate

Self-generated traffic commands (7210 SAS-Mxp, 7210 SAS-R6, and 7210 SAS-R12)

config
    - router
        - sgt-qos
            - application dscp-app-name dscp {dscp-value | dscp-name}
            - application dot1p-app-name dot1p dot1p-priority
            - no application {dscp-app-name | dot1p-app-name}
            - dscp dscp-name fc fc-name
            - no dscp dscp-name
    - service
        - vprn
            - sgt-qos               (See Note below) 
                - application dscp-app-name dscp {dscp-value | dscp-name}
                - application dot1p-app-name dot1p dot1p-priority
                - no application {dscp-app-name | dot1p-app-name}
                - dscp dscp-name fc fc-name
                - no dscp dscp-name
Note:

For descriptions of the config service vprn sgt-qos commands, refer to the VPRN Service Configuration Commands section in the 7210 SAS-Mxp, S, Sx, T Services Guide and the 7210 SAS-R6, R12 Services Guide.

Operational commands (network mode or access-uplink mode)

config
    - qos
        - copy network src-pol dst-pol [overwrite]

Show commands (network mode or access-uplink mode)

show
    - qos
        - network policy-id [detail]
        - network [network-policy-id] association
        - network [network-policy-id] [detail]
        - mpls-lsp-exp-profile-map [policy-id] [detail] (available only in Network Mode)

Show commands (7210 SAS-Mxp, 7210 SAS-R6, and 7210 SAS-R12)

show
    - qos
        - dscp-table [value dscp-value]
show
    - router [router-instance]
    - router service-name service-name 
        - sgt-qos
            - application [app-name] [dscp | dot1p] 
            - dscp-map [dscp-name]

Command descriptions

Configuration commands

Generic commands
description
Syntax

description description-string

no description

Context

config>qos>network

config>qos>mpls-lsp-exp-profile-map

Platforms

Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode

Description

This command creates a text description stored in the configuration file for a configuration context.

The description command associates a text string with a configuration context to help identify the context in the configuration file.

The no form of this command removes any description string from the context.

Parameters
description-string

Specifies a text string describing the entity. Allowed values are any string up to 80 characters composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes.

Network QoS policy commands

network
Syntax

network network-policy-id [create] [network-policy-type {ip-interface | port}]

no network network-policy-id

Context

config>qos

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command creates or edits a QoS network policy. The network policy defines the treatment packets receive as they ingress and egress the network port and network IP interface in network mode of operation.

The QoS network policy consists of an ingress and egress component. The ingress component of the policy defines how packet header priority bits are mapped to internal forwarding class and profile state. The forwarding class and profile state define the Per Hop Behavior (PHB) or the QoS treatment through the 7210 SAS. The mapping on each network interface defaults to the mappings defined in the default network QoS policy until an explicit policy is defined for the network interface. 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 unicast and multipoint traffic.

The egress component of the network QoS policy defines forwarding class and profile state to packet header priority bit values for traffic to be transmitted into the core network. If the egressing packet originated on an ingress SAP, the parameter is always enabled for the network port. The egress QoS policy also defines the dot1p bit marking based on the forwarding class and the profile state.

In network mode, network policy ID 2 exists as the default policy that is applied to all IP interface by default. The network policy ID 2 cannot be modified or deleted. It defines the default LSP EXP-to-FC mapping and default meters for unicast traffic and optional multipoint meters for BUM traffic on the ingress MPLS packets. For the egress, it defines eight forwarding classes which define LSP EXP values and the packet marking behavior.

In network mode, Network policy-id 1 exists as the default policy that is applied to all network ports by default. This default policy cannot be modified or deleted. It defined the default DSCP-to-FC mapping and default unicast meters for ingress IP traffic. For the egress, if defines the forwarding class to dot1p and DSCP values and the packet marking criteria.

In network mode, If a new network policy is created (for instance, policy ID 3), only the default action, default meters for unicast and multipoint traffic and egress forwarding class parameters are identical to the default policy. A new network policy does not contain the default LSP EXP-to-FC mapping for network QoS policy of type ip-interface or the DSCP-to-FC mapping (for network QoS policy of type port). The default network policy can be copied (use the copy command) to create a new network policy that includes the default ingress LSP EXP or DSCP to FC mapping (as appropriate). You can modify parameters or use the no modifier to remove an object from the configuration.

Any changes made to an existing policy, using any of the sub-commands, will be applied immediately to all network ports where this policy is applied. For this reason, when many changes are required on a policy, Nokia highly recommends that the policy be copied to a work area policy ID. That work-in-progress policy can be modified until complete and then written over the original policy ID. Use the config qos copy command to maintain policies in this manner.

The no form of this command deletes the network policy. A policy cannot be deleted until it is removed from all entities where it is applied. The default network policy policy-id 1 cannot be deleted.

Default

system default network policy 1

Parameters
network-policy-id

Specifies the policy on the interface or port.

Values

1 to 65535

network-policy-type

Specifies the type of the policy. This parameter defines where this network policy can be applied.

Values

ip-interface — Specifies only EXP-based classification rules and marking values. It can only be associated with an IP interface. It can be used only when the device is operating in network mode.

port — Specifies only DSCP and dot1p classification rules and marking values. It can only be associated with a network port or hybrid port.

mpls-lsp-exp-profile-map
Syntax

mpls-lsp-exp-profile-map policy-id [create]

no mpls-lsp-exp-profile-map

Context

config>qos

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command creates a new mpls-lsp-exp-profile-map policy. The policy specifies the profile to assign to the packet based on the MPLS LSP EXP bits value matched in the MPLS packet received on a network IP interface.

The assigned profile is available for use by the meter or policer associated with FC in the network policy attached to this IP interface.

The policy is associated with network policy attached to a network IP interface.

Default

1 (default mpls-lsp-exp-profile-map policy ‟1”)

Parameters
policy-id

Specifies the policy ID on the 7210 SAS.

Values

1 to 65535

create

Keyword to create a policy.

lsp-exp
Syntax

lsp-exp lsp-exp-value

no lsp-exp

Context

config>qos> mpls-lsp-exp-profile-map

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command creates a mapping between the LSP EXP bits of the network ingress traffic and the profile.

Ingress traffic that matches the specified LSP EXP bits will be assigned the corresponding profile.

Multiple commands can be entered to define the association of some or all eight LSP EXP bit values to the profile. For undefined values, packets are assigned the profile value out.

The no form of this command removes the association of the LSP EXP bit value to the profile value. The default profile value out then applies to that LSP EXP bit pattern.

Parameters
lsp-exp-value

Specifies a 3-bit LSP EXP bit value, expressed as a decimal integer.

Values

0 to 7

use-global-mpls-lsp-exp-profile
Syntax

use-global-mpls-lsp-exp-profile policy-id

no use-global-mpls-lsp-exp-profile

Context

config>qos

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command associates the mpls-lsp-exp-profile-map policy for use with LDP LSPs. When color-aware metering is in use for the IP interface, the policy specified here provides the profile to assign to the MPLS packets received on any of the network IP interface in use in the system. The MPLS EXP bits in the received packet are matched for assigning the profile.

On system boot-up, the policy ID is set to the default policy ID 1. The user can modify it to use the policy of their choice.

For LDP LSP traffic and segment routing (SR), the system always uses the global mpls-lsp-exp-profile-map policy. For RSVP LSP traffic, system uses the mpls-lsp-exp-profile-map policy associated with the network policy. For consistent QoS treatment, Nokia highly recommends using a single mpls-lsp-exp-profile-map policy for all network policies when the FRR facility or a mix of LDP, SR, and RSVP is in use, or when the PHP is enabled.

The no form of this command reverts the policy to the default.

Default

1

Parameters
policy-id

Specifies the mpls-lsp-exp-profile-map policy to use.

Values

1 to 65535

mpls-lsp-exp-profile
Syntax

mpls-lsp-exp-profile policy-id [create]

no mpls-lsp-exp-profile

Context

config>qos>network>ingress

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command specifies the mpls-lsp-exp-profile-map policy to use for assigning profile values for packets received on this IP interface.

Note:

For LDP LSP traffic, the system uses the global mpls-lsp-exp-profile-map policy. For RSVP LSP traffic, the system uses the mpls-lsp-exp-profile-map policy that is associated with the network policy. For consistent QoS treatment, Nokia highly recommends using a single mpls-lsp-exp-profile-map policy for all the network policies when FRR facility is in use.

The no form of this command removes the policy.

Parameters
policy-id

Specifies the policy.

Values

1 to 65535

create

Keyword to create a policy.

Network QoS policy commands (7210 SAS-T in access-uplink mode)

network
Syntax

[no] network network-policy-id [create] [network-policy-type]

Context

config>qos

Platforms

7210 SAS-T (access-uplink mode)

Description

This command creates or edits a QoS network policy. The network policy defines the treatment packets receive as they ingress and egress the access-uplink port. Only network-policy-type port is supported in access-uplink mode.

The QoS network policy consists of an ingress and egress component. The ingress component of the policy defines how dot1p bits are mapped to internal forwarding class and profile state. The forwarding class and profile state define the Per Hop Behavior (PHB) or the QoS treatment through the 7210 SAS. 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 port. 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 uni-cast and multipoint traffic.

The egress component of the network QoS policy defines the queuing parameters associated with each forwarding class. There are eight queues per port on the egress. Each of the forwarding classes is associated with a queue on each access-uplink port. This queue gets all the parameters defined within the default network QoS policy 1 until an explicit policy is defined for the network interface access-uplink port. If the egressing packet originated on an ingress SAP, the parameter is always enabled for the access-uplink port, the egress QoS policy also defines the dot1p bit marking based on the forwarding class and the profile state.

The network policy ID 1 cannot be modified or deleted. It defines the default dot1p-to-FC mapping and default meters for unicast traffic and optional multipoint meters for the ingress. For the egress, it defines eight forwarding classes which represent individual queues and the packet marking criteria.

If a new network policy is created (for instance, policy ID 2), only the default action and default meters for unicast and multipoint traffic and egress forwarding class parameters are identical to the default policy. A new network policy does not contain the default dot1p-to-FC mapping for network QoS policy of type port. The default network policy can be copied using the copy command to create a new network policy that includes the default ingress dot1p or DSCP to FC mapping (as appropriate).

You can modify parameters or use the no modifier to remove an object from the configuration.

Any changes made to an existing policy, using any of the sub-commands, will be applied immediately to all access-uplink ports where this policy is applied. For this reason, when many changes are required on a policy, it is highly recommended that the policy be copied to a work area policy ID. That work-in-progress policy can be modified until complete and then written over the original policy ID. Use the config qos copy command to maintain policies in this manner.

The no form of this command deletes the network policy. A policy cannot be deleted until it is removed from all entities where it is applied. The default network policy ID1 cannot be deleted.

Default

System Default Network Policy 1

Parameters
network-policy-id

Specifies the policy on the 7210 SAS.

Values

1 to 65535

network-policy-type

Specifies the type of network policy. This parameter defines where this network policy can be applied. In the access-uplink mode, only port type must be used and attached to an access-uplink port.

Values

ip-interface — Specifies only EXP-based classification rules and marking values. It can only be associated with an IP interface. It can be used only when the device is operating in network mode.

port — Specifies only DSCP and dot1p classification rules and marking values. It can only be associated with a network port or hybrid port.

Network ingress QoS policy commands

fc
Syntax

fc fc-name [create]

no fc fc-name

Context

config>qos>network>ingress

config>qos>network>egress

Platforms

Supported on all 7210 SAS platforms as described in this document

Description
Note:

The config>qos>network>egress context is only supported on the 7210 SAS-T (access-uplink mode).

This command creates a class instance of the forwarding class. After the fc-name is created, classification actions can be applied and it can be used in match classification criteria.

The no form of this command removes all the explicit meter mappings for fc-name forwarding types. The meter mappings revert to the default meters for fc-name.

Default

Undefined forwarding classes default to the configured parameters in the default policy policy-id 1.

Parameters
fc-name

Specifies a case-sensitive, system-defined forwarding class name for which policy entries will be created.

Values

be, l2, af, l1, h2, ef, h1, nc

create

Creates the forwarding class. The create keyword requirement can be enabled or disabled in the environment>create context.

ingress
Syntax

ingress

Context

config>qos>network policy-id

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in the access-uplink mode

Description

This command creates or edits policy entries that specify the lsp-exp-value to forwarding class mapping for all MPLS packets.

When pre-marked packets ingress on a network port, the QoS treatment through the 7210 SAS-based on the mapping defined under the current node.

default-action
Syntax

default-action fc fc-name [profile {in | out | use-dei}]

Context

config>qos>network>ingress

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in the access-uplink mode

Description

This command defines or edits the default action to be taken for packets that have an undefined LSP EXP (only when devices is operating in network mode) or dot1p bits (for 7210 SAS-T in access-uplink mode) bits set. The default-action command specifies the forwarding class to which such packets are assigned.

Multiple default-action commands will overwrite each previous default-action command.

Default

default-action fc be profile out

Parameters
fc fc-name

Specifies the forwarding class name. All packets with LSP EXP (only when devices is operating in network mode) or dot1p bits (for 7210 SAS-T in access-uplink mode) that are not defined will be placed in this forwarding class.

Values

be, l2, af, l1, h2, ef, h1, nc

profile {in | out | use-dei}

Specifies that all packets assigned to this forwarding class are considered in or out of profile based on this command. A value must be specified when the profile keyword is used in the command. If the profile is not assigned to a forwarding class, the packets of that FC are treated as out-of-profile packets.

Values

in — Defines the packet profile as in-profile.

out — Defines the packet profile as out-of-profile

use-dei — Specifies that DEI is used to determine the initial profile of the packet

dot1p
Syntax

dot1p dot1p-priority fc fc-name profile {in | out | use-dei}

no dot1p

Context

config>qos>network>ingress

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in the access-uplink mode

Description

This command explicitly sets the forwarding class or enqueuing priorityand profile of the packet when a packet has the dot1p-priority specified. Adding a dot1p rule on the policy forces packets that match the dot1p-priority specified to be assigned to the forwarding class and enqueuing priority and profile of the packet based on the parameters included in the dot1p rule.

The dot1p-priority is derived from the most significant three bits in the IEEE 802.1 q or IEEE 802.1p header. The three dot1p bits define eight Class-of-Service (CoS) values commonly used to map packets to per-hop QoS behavior.

The no form of this command removes the explicit dot1p classification rule from the policy. Removing the rule on the policy immediately removes the rule from all ingress SAP ports using the policy.

Parameters
dot1p-priority

Specifies the unique IEEE 802.1p value that will match the dot1p rule. If the command is executed multiple times with the same dot1p-priority value, the previous forwarding class is completely overridden by the new parameters.

A maximum of eight dot1p rules are allowed on a single policy.

Values

0 to 7

fc fc-name

Specifies a predefined forwarding classes in the system. Specifying the fc-name is optional. When a packet matches the rule, the forwarding class is only overridden when the fc fc-name parameter is defined on the rule. If the packet matches and the forwarding class is not explicitly defined in the rule, the forwarding class is inherited based on previous rule matches.

Values

be, l2, af, l1, h2, ef, h1, nc

profile {in | out | use-dei}

Specifies that all packets that are assigned to this forwarding class will be considered in-profile or out-of-profile based on this command or to use the default. In case of congestion, the in-profile packets are preferentially queued over the out-of-profile packets.

Values

in — Defines the packet profile as in-profile.

out — Defines the packet profile as out-of-profile.

use-dei — Specifies that DEI is used to determine the initial profile of the packet

meter
Syntax

meter meter-id [multipoint] [create]

no meter meter-id

Context

config>qos>network>ingress

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in the access-uplink mode

Description

This command configures an ingress Network QoS policy meter. The meter command allows the creation of multipoint meters. Only multipoint meters can receive ingress packets that need to be sent to multiple destinations

Multipoint meters are for traffic bound to multiple destinations. Within non-multipoint services, such as Epipe services, all traffic is considered unicast because of the nature of the service type. Multicast and broadcast-destined traffic in an Epipe service will not be mapped to a multipoint service meter.

The no form of this command removes the meter-id from the Network ingress QoS policy and from any existing ports using the policy. If any forwarding class forwarding types are mapped to the meter, they revert to their default meters. When a meter is removed, any pending accounting information for each port meter created due to the definition of the meter in the policy is discarded.

Default

meter 1 (for unicast traffic)

meter 9 multipoint (for all other traffic, other than unicast traffic)

Parameters
meter-id

Specifies the meter within the policy. The value 9 is reserved for the default multipoint meter.

Values

1 to 16 (For network policy of type ip-interface)

1 to 8 (For network policy of type port)

multipoint

Specifies that this meter-id is for multipoint forwarded traffic only. This meter-id can only be explicitly mapped to the forwarding class multicast, broadcast, or unknown unicast ingress traffic. If you attempt to map forwarding class unicast traffic to a multipoint queue, an error is generated and no changes are made to the current unicast traffic queue mapping.

The meter must be created as multipoint. The multipoint designator cannot be defined after the meter is created. If an attempt is made to modify the command to include the multipoint keyword, an error is generated and the command will not execute.

The multipoint keyword can be entered in the command line on a pre-existing multipoint meter to edit meter-id parameters.

meter
Syntax

meter meter-id

no meter

Context

config>qos>network>ingress>fc

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in the access-uplink mode

Description

This command overrides the default unicast forwarding type meter mapping for fc fc-name. The specified meter-id must exist within the policy as a non-multipoint meter before the mapping can be made. After the forwarding class mapping is executed, all unicast traffic on a port using this policy is forwarded using the meter-id.

The no form of this command sets the unicast (point-to-point) meter-id back to the default meter for the forwarding class (meter 1).

Default

meter 1

Parameters
meter-id

Specifies the meter. The specified parameter must be an existing, non-multipoint meter defined in the config>qos>network>ingress context.

Values

1 to 16

multicast-meter
Syntax

multicast-meter meter-id

no multicast-meter

Context

config>qos>network>ingress>fc

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command overrides the default multicast forwarding type meter mapping for fc fc-name. The specified meter-id must exist within the policy as a multipoint meter before the mapping can be made. After the forwarding class mapping is executed, all multicast traffic on a port using this policy is forwarded using the meter-id.

This command can be used with a network policy of type ip-interface, and on a network port when multicast is enabled.

The no form of this command reverts the multicast forwarding type meter-id to the default meter for the forwarding class.

Default

9

Parameters
meter-id

Specifies the multicast meter. The specified parameter must be an existing, multipoint meter defined in the config>qos>network>ingress context.

Values

1 to 16

dscp
Syntax

dscp dscp-name fc fc-name profile {in | out}

no dscp

Context

config>qos>network policy-id>ingress

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command creates a mapping between the DiffServ Code Point (DSCP) of the network ingress traffic and the forwarding class.

Ingress traffic that matches the specified DSCP will be assigned to the corresponding forwarding class. Multiple commands can be entered to define the association of some or all 64 DiffServ code points to the forwarding class. For undefined code points, packets are assigned to the forwarding class specified under the default-action command.

The no form of this command removes the DSCP-to-FC association. The default-action then applies to that code point value.

Parameters
dscp-name

Specifies the name of the DiffServ code point to be associated with the forwarding class. DiffServ code point can only be specified by its name and only an existing DiffServ code point can be specified. The software provides names for the well known code points.

Default DSCP names to DSCP value mapping table shows the available system-defined names. The system-defined names must be referenced as all lowercase exactly as listed in the first column in Default DSCP names to DSCP value mapping table and Default class selector code points to DSCP value mapping table below.

Additional names to code point value associations can be added using the dscp-name dscp-name dscp-value command.

The actual mapping is being done on the dscp-value, not the dscp-name that references the dscp-value. If a second dscp-name that references the same dscp-value is mapped within the policy, an error will occur. The second name will not be accepted until the first name is removed.

Table 5. Default DSCP names to DSCP value mapping table
DSCP name DSCP value decimal DSCP value hexadecimal DSCP value binary

nc1

48

0x30

0b110000

nc2

56

0x38

0b111000

ef

46

0x2e

0b101110

af41

34

0x22

0b100010

af42

36

0x24

0b100100

af43

38

0x26

0b100110

af31

26

0x1a

0b011010

af32

28

0x1c

0b011100

af33

30

0x1d

0b011110

af21

18

0x12

0b010010

af22

20

0x14

0b010100

af23

22

0x16

0b010110

af11

10

0x0a

0b001010

af12

12

0x0c

0b001100

af13

14

0x0e

0b001110

default

0

0x00

0b000000

Table 6. Default class selector code points to DSCP value mapping table
DSCP name DSCP value decimal DSCP value hexadecimal DSCP value binary

cs7

56

0x38

0b111000

cs6

48

0X30

0b110000

cs5

40

0x28

0b101000

cs4

32

0x20

0b100000

cs3

24

0x18

0b011000

cs2

16

0x10

0b010000

cs1

08

0x8

0b001000

fc fc-name

Specifies the fc-name with which the code point will be associated.

Values

be, l2, af, l1, h2, ef, h1, nc

profile {in | out}

Keyword to indicate whether the DiffServ code point value is the in-profile or out-of-profile value. For every DSCP value defined, the profile must be indicated. If a DSCP value is not mapped, the default-action forwarding class and profile state will be used for that value.

Note:
  • DSCP values mapping to forwarding classes Expedited (ef), High-1 (h1) and Network-Control (nc) can only be set to in-profile.

  • DSCP values mapping to forwarding class be can only be set to out-of-profile.

Values

in — Defines the packet profile as in-profile.

out — Defines the packet profile to be out-of-profile.

lsp-exp
Syntax

lsp-exp lsp-exp-value fc fc-name

no lsp-exp lsp-exp-value

Context

config>qos>network policy-id>ingress

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command creates a mapping between the LSP EXP bits of the network ingress traffic and the forwarding class.

Ingress traffic that matches the specified LSP EXP bits will be assigned to the corresponding forwarding class. Multiple commands can be entered to define the association of some or all eight LSP EXP bit values to the forwarding class. For undefined values, packets are assigned to the forwarding class specified under the default-action command.

The no form of this command removes the association of the LSP EXP bit value to the forwarding class. The default-action then applies to that LSP EXP bit pattern.

Parameters
lsp-exp-value

Specifies the LSP EXP values to be associated with the forwarding class.

Values

0 to 7 (decimal representation of three EXP bit field)

fc fc-name

Specifies the fc-name that the EXP bit pattern will be associated with.

Values

be, l2, af, l1, h2, ef, h1, nc

adaptation-rule
Syntax

adaptation-rule [cir adaptation-rule] [pir adaptation-rule]

no adaptation-rule

Context

config>qos>network>ingress>meter

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in the access-uplink mode

Description

This command defines the method used by the system to derive the operational CIRs and PIRs when the meter is provisioned in hardware. For the cir and pir parameters, the system attempts to find the best operational rate depending on the defined constraint.

Note:

The adaptation rule configured for the rate influences the step-size used for the burst. See Adaptation rule for meters for information.

The no form of this command removes any explicitly defined constraints used to derive the operational CIR and PIR created by the application of the policy. When a specific adaptation-rule is removed, the default constraints for cir and pir apply.

Default

adaptation-rule cir closest pir closest

Parameters
cir adaptation-rule

Specifies the adaptation rule and defines the constraints enforced to adapt the CIR defined using the meter meter-id rate command. The cir parameter requires a qualifier that defines the constraint used to derive the operational CIR for the meter. When the cir command is not specified, the default constraint applies. The max (maximum), min (minimum), and closest qualifiers are mutually exclusive.

See Supported hardware rates and burst step sizes for CIR and PIR values on the 7210 SAS-Mxp, 7210 SAS-R6, 7210 SAS-R12, 7210 SAS-Sx/S 1/10GE, and 7210 SAS-T and Supported hardware rates and burst step sizes for CIR and PIR values on the 7210 SAS-Sx 10/100GE for more information about supported hardware step-size rates.

Default

closest

Values

max — Specifies that the operational CIR value is equal to or less than the specified rate, taking into account the hardware step size. The hardware step size varies based on the rate and the platform.

min — Specifies that the operational CIR value is equal to or greater than the specified rate, taking into account the hardware step size. The hardware step size varies based on the rate and the platform.

closest — Specifies that the operational CIR value is equal to the closest specified rate, taking into account the hardware step size. The hardware step size varies based on the rate and the platform.

pir adaptation-rule

Specifies the adaptation rule and defines the constraints enforced to adapt the PIR defined using the meter meter-id rate command. The pir parameter requires a qualifier that defines the constraint used to derive the operational PIR for the meter. When the rate command is not specified, the default constraint applies. The max (maximum), min (minimum), and closest qualifiers are mutually exclusive.

See Supported hardware rates and burst step sizes for CIR and PIR values on the 7210 SAS-Mxp, 7210 SAS-R6, 7210 SAS-R12, 7210 SAS-Sx/S 1/10GE, and 7210 SAS-T and Supported hardware rates and burst step sizes for CIR and PIR values on the 7210 SAS-Sx 10/100GE for information about supported hardware step-size rates.

Default

closest

Values

max — Specifies that the operational PIR value is less than or equal to the specified rate, taking into account the hardware step size. The hardware step size varies based on the rate and the platform.

min — Specifies that the operational PIR value is equal to or greater than the specified rate, taking into account the hardware step size. The hardware step size varies based on the rate and the platform.

closest — Specifies that the operational CIR value is equal to the closest specified rate, taking into account the hardware step size. The hardware step size varies based on the rate and the platform.

cbs
Syntax

cbs size [kbits | bytes | kbytes]

no cbs

Context

config>qos>network>ingress>meter

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

Description

This command overrides the default CBS for the meter. The committed burst size parameter specifies the maximum burst size that can be transmitted by the source while still complying with the CIR. If the transmitted burst is lower than the CBS value, the packets are marked as in-profile by the meter to indicate that the traffic is complying with meter-configured parameters.

Note:

The adaptation rule configured for the rate influences the step-size used for the burst. See Adaptation rule for meters for information.

The no form of this command reverts the CBS to the default value.

Default

32 kbits

Parameters
size

Specifies the number of kilobits or kilobytes or bytes reserved for the meter. For example, if a value of 100 kbits is desired, then enter the value 100. The bucket size is rounded off to the next highest 4096 bytes boundary.

Values

kbits — 4 to 2146959, default

bytes — 512 to 274810752

kbytes — 1 to 268369

[kbits | bytes | kbytes]

Specifies the unit of measure for the size of the CBS.

mbs
Syntax

mbs size [kbits | bytes | kbytes]

no mbs

Context

config>qos>network>ingress>meter

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

Description

This command overrides the default MBS for the meter. The maximum burst size parameter specifies the maximum burst size that can be transmitted by the source while still complying with the CIR. If the transmitted burst is lower than the MBS value, the packets are marked as in-profile by the meter to indicate that the traffic is complying with meter-configured parameters.

Note:

The adaptation rule configured for the rate influences the step-size used for the burst. See Adaptation rule for meters for information.

The no form of this command reverts the MBS to the default value.

Default

512 kbits

Parameters
size

Specifies the number of kilobits or kilobytes or bytes reserved for the meter. For example, if a value of 100 kbits is desired, then enter the value 100. The bucket size is rounded off to the next highest 4096 bytes boundary.

Values

kbits — 4 to 2146959, default

bytes — 512 to 274810752

kbytes — 1 to 268369

[kbits | bytes | kbytes]

Specifies the unit of measure for the size of the MBS.

mode
Syntax

mode mode

no mode

Context

config>qos>network>ingress>meter

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

Description

This command defines the mode of the meter. The mode can be configured as Two Rate Three Color Marker (trTCM) or Single Rate Three Color Marker (srTCM). The mode command can be executed at any time.

The no form of this command reverts to the default value.

Default

trtcm

Parameters
trtcm1

Keyword to meter the packet stream and mark the packets green, yellow, or red. A packet is marked red if it exceeds the PIR. Otherwise, it is marked yellow or green depending on whether it exceeds or does not exceed the CIR. The trTCM1 is useful for ingress policing of a service, where a peak rate needs to be enforced separately from a committed rate.

srtcm

Keyword to meter a packet stream and mark its packets green, yellow, or red. Marking is based on a CIR and two associated burst sizes, a CBS and an MBS. A packet is marked green if it does not exceed the CBS, yellow if it exceeds the CBS but not the CIR, and red otherwise. The srTCM is useful for ingress policing of a service, where only the length, not the peak rate, of the burst determines service eligibility.

rate
Syntax

rate cir cir-rate-in-kbps [pir pir-rate-in-kbps]

no rate

Context

config>qos>network>ingress>meter

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

Description

This command defines the administrative PIR and CIR parameters for the meter.

The rate command can be executed at any time, altering the PIR and CIR for all meters created through the association of the Network QoS policy with the meter-id.

The no form of this command reverts all meter instances created with this meter-id to the default PIR (max) and CIR (0) parameters.

Note:

The value of rates are represented as 1000 kilobits per second and bursts are represented as 1024 kilobits per second.

Default

rate 0 pir max

Parameters
cir cir-rate-in-kbps

Specifies the administrative CIR, in kilobits, for the meter. The cir parameter overrides the default administrative CIR used by the meter. When the rate command has not been executed or the cir parameter is not explicitly specified, the default CIR (0) is assumed.

Fractional values are not allowed and must be given as a positive integer.

The actual CIR is dependent on the meter’s adaptation-rule parameters and the hardware.

Values

0 to 20000000, max

pir pir-rate-in-kbps

Specifies the administrative PIR, in kilobits, for the meter. When this command is executed, a valid PIR setting must be explicitly defined. When the rate command has not been executed, the default PIR of max is assumed. When the rate command is executed, a PIR setting is optional.

The max default specifies the amount of bandwidth in kilobits per second (thousand bits per second). The max value is mutually exclusive to the pir-rate value.

Fractional values are not allowed and must be given as a positive integer.

The actual PIR is dependent on the meter’s adaptation-rule parameters and the hardware.

Note:

If the meter mode is configured as trtcm2, the system configures the policer EIR rate, based on the value of the PIR rate configured by the user.

Values

0 to 20000000, max

Network egress QoS policy commands

egress
Syntax

egress

Context

config>qos>network policy-id

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

Description

This command creates or edits egress policy entries that specify the forwarding class map to be instantiated when this policy is applied to the network IP interface, or access-uplink port

The forwarding class and profile state mapping to appropriate marking values for all packets are defined in this context.

In network mode of operation, the system supports use of forwarding class mapping to EXP bits for IP interface, forwarding class mapping to DSCP and dot1p bits for network ports. In access-uplink mode of operation it allows the user to specify the FC mapping to dot1p bits for access-uplink ports.

fc
Syntax

[no] fc fc-name

Context

config>qos>network>egress

Platforms

7210 SAS-T (access-uplink mode)

Description

This command specifies the forwarding class name. The forwarding class name represents an egress queue. The fc fc-name represents a CLI parent node that contains sub-commands or parameters describing the marking criteria of packets flowing through it. The fc command overrides the default parameters for that forwarding class to the values defined in the network default policy. Appropriate default parameters are picked up based on whether the network-policy-type is port or ip-interface.

The no form of this command removes the forwarding class LSP EXP/dot1p/DSCP map associated with this fc, as appropriate. The forwarding class reverts to the defined parameters in the default network policy. If the fc-name is removed from the network policy that forwarding class reverts to the factory defaults.

Default

Undefined forwarding classes default to the configured parameters in the default network policy policy-id 1.

Parameters
fc-name

Specifies a case-sensitive, system-defined forwarding class name for which policy entries will be created.

Values

be, l2, af, l1, h2, ef, h1, nc

de-mark
Syntax

[no] de-mark [force de-value]

Context

config>qos>network>egress>fc

Platforms

7210 SAS-T (access-uplink mode)

Description

This command explicitly defines the marking of the DEI bit for fc fc-name according to the in and out of profile status of the packet (fc-name may be used to identify the dot1p-value).

If no de-value is present, the default values are used for the marking of the DEI bit, as defined in the IEEE 802.1ad-2005 standard. For example 0 for in-profile packets, 1 for out-of-profile ones.

If the de-value is specifically mentioned in the command line it means this value is to be used for all the packets of this forwarding class regardless of their in/out of profile status.

Parameters
de-value

Specifies the DEI value to use for this forwarding class.

Values

0 or 1

dot1p
Syntax

[no] dot1p dot1p-value

Context

config>qos>network>egress>fc

Platforms

7210 SAS-T access-uplink mode

Description

This command explicitly defines the egress IEEE 802.1P (dot1p) bits marking for fc-name. When the marking is set, all packets of fc-name that have either an IEEE 802.1Q or IEEE 802.1P encapsulation use the explicitly defined dot1p-value. If the egress packets for fc-name are not IEEE 802.1Q or IEEE 802.1P encapsulated, the dot1p command has no effect.

DEI marking can be enabled using the de-mark command along with this command for the command to take effect. When de-mark command is configured along with this command, then the DEI bit is marked in the packet to indicate the profile of the packet. The DEI bit is marked to 0 to indicate in-profile/green packet and 1 to indicate out-of-profile/yellow packet. If the force de-value parameter is specified then the DEI bit is set to specified value for all packets.

If the no form of this command is executed then software will use the dot1p-in-profile and dot1p-out-profile if configured, else it will use default values.

Note:

The following rules are applied to determine the dot1p values when both the dot1p command, and the dot1p-in-profile and dot1p-out-profile commands are specified:

  • If de-mark is not configured, dot1p [in | out]-profile values are considered. Even if dot1p value is configured it is ignored and if dot1p [in | out]-profile value is not configured, default values are considered for that FC.

  • If de-mark is configured and the dot1p value is configured, it is considered. If the dot1p [in | out]-profile value is configured, it is considered. In this case, the dot1p value takes precedence over the dot1p [in | out]-profile.

Default

no dot1p

Parameters
dot1p-value

Specifies the 802.1p value to set for in-profile frames in this forwarding class.

Values

0 to 7

dot1p-in-profile
Syntax

dot1p-in-profile dot1p-priority

no dot1p-in-profile

Context

config>qos>network>egress>fc

Platforms

7210 SAS-T access-uplink mode

Description

The command adds the capability to mark on an egress the in and out of profile status through a certain dot1p combination, similarly with the DEI options. It may be used when the internal in and out of profile status needs to be communicated to an adjacent network/customer device that does not support the DEI bit.

This command explicitly defines the egress IEEE 802.1P (dot1p) bits marking for fc-name. When the marking is set, all packets with in-profile status (or green color) of fc-name that have either an IEEE 802.1Q or IEEE 802.1P encapsulation use the explicitly defined dot1p-value. If the egress packets for fc-name are not IEEE 802.1Q or IEEE 802.1P encapsulated, the dot1p command has no effect.

If DEI marking is enabled using the de-mark command and the command dot1p dot1p-value is used to configure the dot1p value, then this command has no effect. In other words, enabling DEI marking has precedence over this command and the system ignores this command.

When this command is used the DEI Bit is left unchanged by the egress processing if a tag exists. If a new tag is added, the related DEI bit is set to 0.

The no form of this command sets the IEEE 802.1P or IEEE 802.1Q priority bits to 0.

Note:

The following rules are applied to determine the dot1p values when both the dot1p command and the dot1p-in-profile and dot1p-out-profile commands are specified:

  1. If de-mark is not configured, dot1p [in|out]-profile values are considered. Even if dot1p command value is configured, it is ignored, and if the dot1p [in|out]-profile value is not configured, default values are considered for that FC.

  2. If de-mark is configured and if the dot1p command value is configured, it is considered. Otherwise, if the dot1p [in|out]-profile value is configured, it is considered. In this case, the dot1p command value has the precedence over the dot1p [in|out]-profile.

  3. If marking is enabled and both the dot1p command value and the dot1-[in|out]-profile commands are not specified, the default values are used.

Default

0

Parameters
dot1p-priority

Specifies the 802.1p value to set for in-profile frames in this forwarding class.

Values

0 to 7

dot1p-out-profile
Syntax

dot1p-out-profile dot1p-priority

no dot1p-out-profile

Context

config>qos>network>egress>fc

Platforms

7210 SAS-T access-uplink mode

Description

The command adds the capability to mark on an egress the in and out of profile status via a certain dot1p combination, similarly with the DEI options. It may be used when the internal in and out of profile status needs to be communicated to an adjacent network/customer device that does not support the DEI bit.

This command explicitly defines the egress IEEE 802.1P (dot1p) bits marking for fc-name. When the marking is set, all packets with out-of-profile status (or yellow color) of fc-name that have either an IEEE 802.1Q or IEEE 802.1P encapsulation use the explicitly defined dot1p-value. If the egress packets for fc-name are not IEEE 802.1Q or IEEE 802.1P encapsulated, the dot1p command has no effect.

If DEI marking is enabled using the de-mark command and the dot1p-value is configured, then this command has no effect. In other words, enabling DEI marking has precedence over this command and the system ignores this command.

When this command is used the DEI Bit is left unchanged by the egress processing if a tag exists. If a new tag is added, the related DEI bit is set to 0.

The no form of this command reverts the IEEE 802.1P or IEEE 802.1Q priority bits to the default.

Note:

The following rules are applied to determine the dot1p values to when both the dot1p command and dot1p-in-profile and dot1p-out-profile commands are specified:

  1. If de-mark is not configured, the dot1p [in|out]-profile values are considered. Even if the dot1p command value is configured, it is ignored, and if the dot1p [in|out]-profile value is not configured, default values are considered for that FC.

  2. If de-mark is configured and if the dot1p command value is configured, it is considered. Otherwise, if the dot1p [in|out]-profile value is configured, it is considered. In this case, the dot1p command value, has the precedence over the dot1p [in|out]-profile value.

  3. If marking is enabled and the dot1p command value and the dot1p-[in|out]-profile command are not specified, the default values are used.

Default

0

Parameters
dot1p-priority

Specifies the 802.1p value to set for in-profile frames in this forwarding class.

Values

0 to 7

dscp-in-profile
Syntax

dscp-in-profile dscp-name

no dscp-in-profile

Context

config>qos>network >egress>fc

Platforms

7210 SAS-T (access-uplink mode)

Description

This command specifies the in-profile DSCP name for the forwarding class.

When multiple DSCP names are associated with the forwarding class at network egress, the last name entered will overwrite the previous value.

The no form of this command reverts to the factory default in-profile dscp-name value for policy-id 1.

Parameters
dscp-name

Specifies a system- or user-defined, case-sensitive dscp-name.

dscp-out-profile
Syntax

dscp-out-profile dscp-name

no dscp-out-profile

Context

config>qos>network>egress>fc

Platforms

7210 SAS-T (access-uplink mode)

Description

This command specifies the out-of-profile DSCP name for the forwarding class.

When multiple DSCP names are associated with the forwarding class at network egress, the last name entered will overwrite the previous value.

The no form of this command reverts to the factory default out-of-profile dscp-name value for policy-id 1.

Parameters
dscp-name

Specifies a system- or user-defined, case-sensitive dscp-name.

remarking
Syntax

remarking {use-dot1p | use-dscp | all}

no remarking

Context

config>qos>network>egress

Platforms

7210 SAS-T(access-uplink mode)

Description

This command enables the system to remark egress packets sent out of access-uplink ports. The user can specify if dot1p or dscp or both dot1p and dscp to be used for marking the packets sent out of the port.

When 7210 is operated in access-uplink mode, marking support is available as given below.

  • On access-uplink port egress, the behavior is as follows:

    • If the use-dot1p keyword is configured in the access-egress policy, then the dot1p bits are marked in the packet header for all traffic sent out of all SAPs configured on that access-uplink port.

    • If the use-dscp keyword is configured in the access-egress policy, then the IP DSCP bits are marked in the packet header for IPv4 traffic sent out of all SAPs configured on that access port.

      Note:

      DSCP marking also marks the IPv4 packets associated with SAPs configured in an Layer 2 VPN service. If this is not required, to avoid this it is recommended to use only dot1p marking on access-uplink ports.

    • If the all keyword is configured is configured in the access-egress policy, then the dot1p bits are marked in the packet header for all traffic (Layer 2 and IPv4) sent out of all SAPs and the IP DSCP bits are marked in the packet header for all IPv4 traffic sent out of all SAPs configured on that access port.

      Note:
      • DSCP marking also marks the packets associated with SAPs configured in an Layer 2 VPN service. If this is not required, to avoid this it is recommended to use only dot1p marking on access-uplink ports.

      • If remarking is enabled in access-egress policy, by default use-dot1p is used. If no marking values are specified, the default FC-to-dot1p marking values are used.

The no form of this command disables remarking.

Default

no remarking

remark
Syntax

remark policy-id

no remark

Context

config>qos>network>egress

Platforms

7210 SAS-T (network mode), 7210 SAS-Sx 1/10GE: standalone and standalone-VC, 7210 SAS-Sx 10/100GE, 7210 SAS-Mxp, 7210 SAS-R6, and 7210 SAS-R12

Description

This command specifies the remarking policy ID to use for marking packets on network port and network IP interface egress.

The remarking policy ID must be associated with the appropriate network QoS policy associated with the network port and or network IP interface and remarking must be enabled in the network QoS policy to enable marking of packets sent out of network port and or network IP interface egress. Remarking policy of type dot1p, dscp, and dot1p-dscp is allowed to be used when the remark policy is associated with network QoS policy of type port. Remarking policy of type lsp-exp and dot1p-lsp-exp-shared is allowed to be used when the remark policy is associated with network QoS policy of type ip-interface. Summary of remark policy and attachment points for 7210 SAS-T, 7210 SAS-Sx/S 1/10GE, and 7210 SAS-Sx 10/100GE (network mode) and Summary of remark policy and attachment points for 7210 SAS-Mxp, 7210 SAS-R6, and 7210 SAS-R12 describe the remark policies, their attachment points supported on the node, and their uses.

The no form of this command removes the explicit association of the remark policy and associates the default remark policy. For example, if remarking is enabled and the no remark command is configured, the default remark policy is used to mark packets sent out. If no remark policy is executed and remarking is disabled, then packets are not remarked at all.

Parameters
policy-id

Specifies the remark policy ID.

Values

1 to 65535

remarking
Syntax

[no] remarking

Context

config>qos>network>egress

Platforms

7210 SAS-T (network mode), 7210 SAS-Sx 1/10GE: standalone and standalone-VC, 7210 SAS-Sx 10/100GE, 7210 SAS-Mxp, 7210 SAS-R6, and 7210 SAS-R12

Description

This command enables the system to remark egress packets sent out of network ports and hybrid ports.

When remarking is enabled, the remark policy configured in the QoS policy context is used to determine the FC to QoS bit mapping. For example, when remarking is enabled in the network QoS policy, the remark policy associated with network QoS policy is used to determine the FC-to-EXP mapping to use for marking packets sent out of access ports.

See Remark policies for the remark policy that can be used to configure FC to priority bit markings in different QoS policies associated with different service entities. For more information, see Summary of remark policy and attachment points for 7210 SAS-T, 7210 SAS-Sx/S 1/10GE, and 7210 SAS-Sx 10/100GE (network mode) and Summary of remark policy and attachment points for 7210 SAS-Mxp, 7210 SAS-R6, and 7210 SAS-R12.

The no form of this command disables remarking. When remarking is disabled for MPLS LSR traffic, EXP values received at ingress are not modified at 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.

Default

no remarking

scope
Syntax

scope {exclusive | template}

no scope

Context

config>qos>network policy-id

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

Description

This command configures the network policy scope as exclusive or template.

The no form of this command reverts the scope of the policy to the default.

Default

template

Parameters
exclusive

Specifies that the policy can only be applied to one interface. If a policy with an exclusive scope is assigned to a second interface an error message is generated. If the policy is removed from the exclusive interface, it will become available for assignment to another exclusive interface. The system default policies cannot be put into the exclusive scope. An error will be generated if scope exclusive is executed in any policies with a policy ID equal to 1.

template

Specifies that the policy can be applied to multiple interfaces on the router.

Default QoS policies are configured with template scopes. An error is generated if you try to modify the template scope parameter to exclusive scope on default policies.

Self-generated traffic commands (7210 SAS-Mxp, 7210 SAS-R6, and 7210 SAS-R12)

sgt-qos
Syntax

sgt-qos

Context

config>router

Platforms

7210 SAS-Mxp, 7210 SAS-R6, and 7210 SAS-R12

Description

Commands in this context configure DSCP/dot1p re-marking for select self-generated traffic.

application
Syntax

application dscp-app-name dscp {dscp-value | dscp-name}

application dot1p-app-name dot1p dot1p-priority

no application {dscp-app-name | dot1p-app-name}

Context

config>router>sgt-qos

Platforms

7210 SAS-Mxp, 7210 SAS-R6, and 7210 SAS-R12

Description

This command configures DSCP/dot1p re-marking for self-generated application traffic. When an application is configured using this command, then the specified DSCP name/value is used for all packets generated by this application within the router instance it is configured. The instances can be base router or VPRN service.

Using the value configured in this command does the following.

  • Sets the DSCP bits in the IP packet.

  • Maps to the FC.

  • Based on this FC, the egress QoS policy sets the Ethernet 802.1p and MPLS EXP bits. This includes ARP and IS-IS packets that, because of their nature, do not carry DSCP bits.

  • The DSCP value in the egress IP header will be as configured in this command.

Only one DSCP name/value can be configured per application. If multiple entries are configured then the subsequent entry overrides the previously configured entry.

The no form of this command reverts to the default value.

Parameters
dscp-app-name

Specifies the DSCP application name.

Values

The following values apply to the base router instance:

bgp, dns, ftp, icmp, igmp, ldp, ndis, ntp, ospf, pim, ptp, radius, rip, rsvp, snmp, snmp-notification, ssh, syslog, tacplus, telnet, tftp, traceroute, vrrp, arp, isis

dscp-value

Specifies a value when this packet egresses the respective egress policy should provide the mapping for the DSCP value to either LSP-EXP bits or IEEE 802.1p (dot1p) bits as appropriate, otherwise the default mapping applies.

Values

0 to 63

dscp-name

Specifies the DSCP name.

Values

none, be, ef, cp1, cp2, cp3, cp4, cp5, cp6, cp7, cp9, cs1, cs2, cs3, cs4, cs5, nc1, nc2, af11, af12, af13, af21, af22, af23, af31, af32, af33, af41, af42, af43, cp11, cp13, cp15, cp17, cp19, cp21, cp23, cp25, cp27, cp29, cp31, cp33, cp35, cp37, cp39, cp41, cp42, cp43, cp44, cp45, cp47, cp49, cp50, cp51, cp52, cp53, cp54, cp55, cp57, cp58, cp59, cp60, cp61, cp62, cp63

dot1p-priority

Specifies the dot1p priority.

Values

none, or 0 to 7

dot1p-app-name

Specifies the dot1p application name.

Values

arp, isis

dscp
Syntax

dscp dscp-name fc fc-name

no dscp dscp-name

Context

config>router>sgt-qos

Platforms

7210 SAS-Mxp, 7210 SAS-R6, and 7210 SAS-R12

Description

This command creates a mapping between the DiffServ Code Point (DSCP) of the self-generated traffic and the forwarding class.

Self-generated traffic for configured applications that matches the specified DSCP will be assigned to the corresponding forwarding class. Multiple commands can be entered to define the association of some or all 64 DSCPs to a forwarding class.

All DSCP names that define a DSCP value must be explicitly defined.

The no form of this command removes the DSCP-to-forwarding class association.

Parameters
dscp-name

Specifies the name of the DSCP to be associated with the forwarding class. A DiffServ code point can only be specified by its name and only an existing DiffServ code point can be specified. The software provides names for the well known code points.

Values

be, ef, cp1, cp2, cp3, cp4, cp5, cp6, cp7, cp9, cs1, cs2, cs3, cs4, cs5, nc1, nc2, af11, af12, af13, af21, af22, af23, af31, af32, af33, af41, af42, af43, cp11, cp13, cp15, cp17, cp19, cp21, cp23, cp25, cp27, cp29, cp31, cp33, cp35, cp37, cp39, cp41, cp42, cp43, cp44, cp45, cp47, cp49, cp50, cp51, cp52, cp53, cp54, cp55, cp57, cp58, cp59, cp60, cp61, cp62, cp63

fc fc-name

Specifies the forwarding class name. Applications and protocols that are configured under the dscp command will use the configured IP DSCP value.

Values

be, l2, af, l1, h2, ef, h1, nc

Operational commands

copy
Syntax

copy network src-pol dst-pol [overwrite]

Context

config>qos

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

Description

This command copies existing QoS policy entries for a QoS policy-id to another QoS policy-id. It also allows bulk modifications to an existing policy with the use of the overwrite keyword.

Parameters
network src-pol dst-pol

Specifies the source policy that the copy command will copy and the destination policy to which the command will duplicate the policy to a new or different policy ID. This parameter indicates that the source and destination policies are network policy IDs.

Values

1 to 65535

overwrite

Keyword to replace the existing destination policy. Everything in the existing destination policy will be overwritten with the contents of the source policy. If overwrite is not specified, an error will occur if the destination policy ID exists.

Example:
    SR>config>qos# copy network 1 427
    MINOR: CLI Destination "427" exists use {overwrite}.
    SR>config>qos# copy network 1 427 overwrite

Show commands

network
Syntax

network [policy-id] [detail]

Context

show>qos

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

Description

This command displays network policy information.

Parameters
policy-id

Displays information for the specific policy ID.

Values

1 to 65535

Default

all network policies

detail

Displays information about ingress and egress EXP bit mappings and network policy interface associations (for devices operating in network mode).

detail

Displays information about ingress and egress dot1p bit mappings and network policy interface associations (for 7210 SAS-T in access-uplink mode).

Output

The following outputs are examples of QoS network policy information, and the associated tables describe the output fields:

Sample output
A:qos1# show qos network 
=========================================================================
Network Policies
=========================================================================
Policy-Id            Remark LerUseDscp Description                             
-------------------------------------------------------------------------
1                    False  False      Default network-port QoS policy.        
2                    False  False      Default network QoS policy.             
=========================================================================
A:qos1# 
*A:ALA# show qos network 1 detail 
===============================================================================
QoS Network Policy
===============================================================================
Network Policy (1)
-------------------------------------------------------------------------------
Policy-id      : 1                            Remark       : False             
Forward Class  : be                           Profile      : Out               
Attach Mode    : l2                           Config Mode  : l2+mpls           
Scope          : Template                     Policy Type  : port              
Accounting     : packet-based                                                  
Description    : Default network-port QoS policy.
-------------------------------------------------------------------------------
DSCP                                    Forwarding Class                Profile
-------------------------------------------------------------------------------
be                                      be                              Out    
ef                                      ef                              In     
cs1                                     l2                              In     
nc1                                     h1                              In     
nc2                                     nc                              In     
af11                                    af                              In     
af12                                    af                              Out    
af41                                    h2                              In 
-------------------------------------------------------------------------------
Dot1p Bit Map                         Forwarding Class                Profile
-------------------------------------------------------------------------------
No Matching Entries
-------------------------------------------------------------------------------
Meter Mode   CIR Admin   CIR Rule   PIR Admin   PIR Rule    CBS       MBS
-------------------------------------------------------------------------------
1     TrTcm_CA  0         closest       max       closest   32 KBytes 128 KBytes
-------------------------------------------------------------------------------
FC                  UCastM         MCastM         
-------------------------------------------------------------------------------
No FC-Map Entries Found.
-------------------------------------------------------------------------------
Egress Forwarding Class Queuing
-------------------------------------------------------------------------------
FC Value       : 0                            FC Name      : be                
- DSCP Mapping                        
Out-of-Profile : be                           In-Profile   : be                
 
- Dot1p Mapping
Out-of-Profile : 0                            In-Profile   : 0                 
 
FC Value       : 1                            FC Name      : l2                
- DSCP Mapping
Out-of-Profile : cs1                          In-Profile   : cs1               
 
- Dot1p Mapping
Out-of-Profile : 1                            In-Profile   : 1                 
 
FC Value       : 2                            FC Name      : af                
- DSCP Mapping
Out-of-Profile : af12                         In-Profile   : af11              
 
- Dot1p Mapping
Out-of-Profile : 2                            In-Profile   : 3                 
 
FC Value       : 3                            FC Name      : l1                
- DSCP Mapping
Out-of-Profile : af22                         In-Profile   : af21              
 
- Dot1p Mapping                       
Out-of-Profile : 2                            In-Profile   : 3                 
 
FC Value       : 4                            FC Name      : h2                
- DSCP Mapping
Out-of-Profile : af41                         In-Profile   : af41              
 
- Dot1p Mapping
Out-of-Profile : 4                            In-Profile   : 4                 
 
FC Value       : 5                            FC Name      : ef                
- DSCP Mapping
Out-of-Profile : ef                           In-Profile   : ef                
 
- Dot1p Mapping
Out-of-Profile : 5                            In-Profile   : 5                 
 
FC Value       : 6                            FC Name      : h1                
- DSCP Mapping
Out-of-Profile : nc1                          In-Profile   : nc1               
 
- Dot1p Mapping
Out-of-Profile : 6                            In-Profile   : 6                 
 
FC Value       : 7                            FC Name      : nc                
- DSCP Mapping
Out-of-Profile : nc2                          In-Profile   : nc2               
 
- Dot1p Mapping
Out-of-Profile : 7                            In-Profile   : 7 
-------------------------------------------------------------------------------
Interface Association
-------------------------------------------------------------------------------
No Interface Association Found.
-------------------------------------------------------------------------------
Port Attachments
-------------------------------------------------------------------------------
Port-id : 1/1/1                                                                
Port-id : 1/1/2                                                                
Port-id : 1/1/3                                                                
Port-id : 1/1/4                                                                
Port-id : 1/1/5                                                                
Port-id : 1/1/6                                                                
Port-id : 1/1/7                                                                
Port-id : 1/1/8                                                                
Port-id : 1/1/9                                                                
Port-id : 1/1/10                                                               
Port-id : 1/1/11                                                               
Port-id : 1/1/12                                                               
Port-id : 1/1/13                                                               
Port-id : 1/1/14                                                               
Port-id : 1/1/16                                                               
Port-id : 1/1/17                                                               
Port-id : 1/1/18                                                               
Port-id : 1/1/20                                                               
Port-id : 1/1/21                                                               
Port-id : 1/1/22                                                               
Port-id : 1/1/23                                                               
Port-id : 1/1/24                                                               
===============================================================================
*A:ALA#


*A:ALA# show qos network 2 detail 
===============================================================================
QoS Network Policy
===============================================================================
Network Policy (2)
-------------------------------------------------------------------------------
Policy-id      : 2                            Remark       : False             
Forward Class  : be                           Profile      : Out               
Attach Mode    : mpls                         Config Mode  : mpls              
Scope          : Template                     Policy Type  : IpInterface       
Accounting     : packet-based                                                  
Profile Policy : 1
Global Prof  : 1
Description    : Default network QoS policy.
 
-------------------------------------------------------------------------------
LSP EXP Bit Map                         Forwarding Class                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     
-------------------------------------------------------------------------------
Meter Mode   CIR Admin   CIR Rule   PIR Admin   PIR Rule    CBS       MBS
-------------------------------------------------------------------------------
1     TrTcm_CA  0         closest       max       closest   32 KBytes 128 KBytes
9     TrTcm_CA  0         closest       max       closest   32 KBytes 128 KBytes
-------------------------------------------------------------------------------
FC                  UCastM         MCastM         
-------------------------------------------------------------------------------
No FC-Map Entries Found.
-------------------------------------------------------------------------------
Egress Forwarding Class Queuing
-------------------------------------------------------------------------------
FC Value       : 0                            FC Name      : be                
- LSP EXP Bit Mapping
Out-of-Profile : 0                            In-Profile   : 0                 
 
FC Value       : 1                            FC Name      : l2                
- LSP EXP Bit Mapping
Out-of-Profile : 1                            In-Profile   : 1                 
                                      
FC Value       : 2                            FC Name      : af                
- LSP EXP Bit Mapping
Out-of-Profile : 2                            In-Profile   : 3                 
 
FC Value       : 3                            FC Name      : l1                
- LSP EXP Bit Mapping
Out-of-Profile : 2                            In-Profile   : 3                 
 
FC Value       : 4                            FC Name      : h2                
- LSP EXP Bit Mapping
Out-of-Profile : 4                            In-Profile   : 4                 
 
FC Value       : 5                            FC Name      : ef                
- LSP EXP Bit Mapping
Out-of-Profile : 5                            In-Profile   : 5                 
 
FC Value       : 6                            FC Name      : h1                
- LSP EXP Bit Mapping
Out-of-Profile : 6                            In-Profile   : 6                 
 
FC Value       : 7                            FC Name      : nc                
- LSP EXP Bit Mapping
Out-of-Profile : 7                            In-Profile   : 7 
-------------------------------------------------------------------------------
Interface Association
-------------------------------------------------------------------------------
Interface      : system
IP Addr.       : n/a                          Port Id      : system            
Interface      : in-band-management
IP Addr.       : 10.135.25.189/24             Port Id      : 1/1/23 
-------------------------------------------------------------------------------
Port Attachments
-------------------------------------------------------------------------------
No Matching Entries
===============================================================================
*A:ALA#


For SAS-MXP:
*A:qos1# show qos network 1001 detail 
===============================================================================
QoS Network Policy
===============================================================================
-------------------------------------------------------------------------------
Network Policy (1001)
-------------------------------------------------------------------------------
Policy-id      : 1001                         Remark       : False             
Forward Class  : be                           Profile      : In                
Attach Mode    : mpls                         Config Mode  : mpls              
Scope          : Template                     Policy Type  : IpInterface       
Accounting     : packet-based                                                  
Description    : ip-interface-type
-------------------------------------------------------------------------------
LSP EXP Bit Map                         Forwarding Class                Profile
-------------------------------------------------------------------------------
0                                       be                              Out    
1                                       l2                              Out    
2                                       af                              In     
3                                       l1                              Out    
4                                       h2                              In     
5                                       ef                              Out    
6                                       h1                              Out    
7                                       nc                              In     
-------------------------------------------------------------------------------
Meter Mode   CIR Admin   CIR Rule   PIR Admin   PIR Rule    CBS Admin MBS Admin
             CIR Oper               PIR Oper                CBS Oper  MBS Oper
-------------------------------------------------------------------------------
1     TrTcm_CA  4000      closest       8000      closest   def       def    
                4000                    8000                def       500    
2     TrTcm_CA  4000      closest       7000      closest   16384     16384  
                4000                    7000                16000     16000  
3     TrTcm_CA  4000      closest       7000      closest   def       def    
                4000                    7000                def       500    
4     TrTcm_CA  4000      closest       7000      closest   def       def    
                4000                    7000                def       500    
5     TrTcm_CA  4000      closest       7000      closest   def       def    
                4000                    7000                def       500    
6     TrTcm_CA  4000      closest       7000      closest   def       def    
                4000                    7000                def       500    
7     TrTcm_CA  4000      closest       7000      closest   def       def    
                4000                    7000                def       500    
8     TrTcm_CA  7000      closest       7000      closest   def       def    
                7000                    7000                def       500    
9     TrTcm_CA  4000      closest       7000      closest   def       def    
                4000                    7000                def       500    
10    TrTcm_CA  4000      closest       7000      closest   def       def    
                4000                    7000                def       500    
11    TrTcm_CA  4000      closest       7000      closest   def       def    
                4000                    7000                def       500    
12    TrTcm_CA  4000      closest       7000      closest   def       def    
                4000                    7000                def       500 
-------------------------------------------------------------------------------
FC                  UCastM         MCastM         
-------------------------------------------------------------------------------
l2                  2              def           
af                  3              def           
l1                  4              def           
h2                  5              12            
ef                  6              11            
h1                  7              10            
nc                  8              9 
-------------------------------------------------------------------------------
Egress Forwarding Class Queuing
-------------------------------------------------------------------------------
FC Value       : 0                            FC Name      : be                
- LSP EXP Bit Mapping
Out-of-Profile : 0                            In-Profile   : 0                 
 
FC Value       : 1                            FC Name      : l2                
- LSP EXP Bit Mapping
Out-of-Profile : 1 
...
===============================================================================
*A:qos1# 
Table 7. Output fields: QoS network policy
Label Description

Policy-Id

The ID that uniquely identifies the policy

Remark

True — Remarking is enabled for all packets that egress this router where the network policy is applied

The remarking is based on the forwarding class to EXP bit mapping defined under the egress node of the network QoS policy.

Description

A text string that helps identify the policy’s context in the configuration file

Forward Class/ FC Name

Specifies the forwarding class name

Profile

Out— Specifies the EXP marking for the packets which are out-of-profile, egressing on this queue

Specifies the EXP marking for the packets which are out-of-profile, egressing on this queue.

In — Specifies the EXP marking for the packets which are in-of-profile, egressing on this queue

Specifies the EXP markings for in-profile packets egressing this queue

Accounting

Packet-based — Specifies that the meters associated with this policy do not account for packet framing overheads (such as Ethernet the Inter Frame Gap (IFG) and the preamble), while accounting for the bandwidth to be used by this flow

Frame-based — Specifies that the meters associated with this policy account for the packet framing overheads (such as for Ethernet the IFG and preamble), while accounting the bandwidth to be used by the flow

Profile policy

Displays the profile policy ID

Global Prof

Displays the global profile policy ID for LDP packets

EXP Bit Mapping:

Out-of-Profile

Displays the EXP value used for out-of-profile traffic

In-Profile

Displays the EXP value used for in-profile traffic

Interface

Displays the interface name

IP Addr

Displays the interface IP address

Port-Id

Specifies the physical port identifier that associates the interface

Sample output (policy ID 1) for the 7210 SAS-R6 and 7210 SAS-R12
*A:SAS>config>qos>network# show qos network 1 detail 

===============================================================================
QoS Network Policy
===============================================================================
-------------------------------------------------------------------------------
Network Policy (1)
-------------------------------------------------------------------------------
Policy-id      : 1                            
Egr Remark     : False                        Egr Rem Plcy : N/A
Forward Class  : be                           Profile      : Out
Scope          : Template                     Policy Type  : port
Accounting     : packet-based                 
Description    : Default network-port QoS policy.
 
-------------------------------------------------------------------------------
Dot1p Bit Map                         Forwarding Class                Profile
-------------------------------------------------------------------------------
No Matching Entries
 
-------------------------------------------------------------------------------
Meter Mode     CIR Admin CIR Rule   PIR Admin   PIR Rule    CBS Admin MBS Admin
               CIR Oper             PIR Oper                CBS Oper  MBS Oper
-------------------------------------------------------------------------------
1     TrTcm1_CA   0         closest       max       closest   def       def    
                  0                       max                 def       def    
 
 
-------------------------------------------------------------------------------
FC              UCastM         MCastM         
-------------------------------------------------------------------------------
No FC-Map Entries Found.
 
 
-------------------------------------------------------------------------------
Port Attachments
-------------------------------------------------------------------------------
Port-id : 1/1/10                                                               
Port-id : 1/1/11                                                               
Port-id : 1/1/12                                                               
Port-id : 1/1/13                                                               
Port-id : 1/1/20                                                               
Port-id : 1/1/21                                                               
Port-id : 1/1/22                                                               
Port-id : 1/1/23                                                               
Port-id : 1/1/24                                                               
Port-id : 1/1/25                                                               
Port-id : 1/1/26                                                               
Port-id : lag-3                                                                
Port-id : lag-5                                                                
===============================================================================
*A:SAS>config>qos>network# 

Sample output (policy ID 2) for the 7210 SAS-R6 and 7210 SAS-R12
*A:SAS>config>qos>network# show qos network 2 detail 

===============================================================================
QoS Network Policy
===============================================================================
-------------------------------------------------------------------------------
Network Policy (2)
-------------------------------------------------------------------------------
Policy-id      : 2                            
Egr Remark     : False                        Egr Rem Plcy : N/A
Forward Class  : be                           Profile      : Out
Scope          : Template                     Policy Type  : IpInterface
Accounting     : packet-based                 
Profile Policy : 1
Local FC       : Disabled                     Global Prof  : 1
Description    : Default network QoS policy.
 
-------------------------------------------------------------------------------
Dot1p Bit Map                         Forwarding Class                Profile
-------------------------------------------------------------------------------
No Matching Entries
 
-------------------------------------------------------------------------------
Meter Mode     CIR Admin CIR Rule   PIR Admin   PIR Rule    CBS Admin MBS Admin
               CIR Oper             PIR Oper                CBS Oper  MBS Oper
-------------------------------------------------------------------------------
1     TrTcm1_CA   0         closest       max       closest   7 KBytes 10 KBytes 
                  0                       max 
9     TrTcm1_CA   0         closest       max       closest   11 KBytes 14 KBytes 

 
-------------------------------------------------------------------------------
FC              UCastM         MCastM         
-------------------------------------------------------------------------------
No FC-Map Entries Found.
 
 
-------------------------------------------------------------------------------
Interface Association
-------------------------------------------------------------------------------
Interface      : system
IP Addr.       : 180.10.10.10/32              Port Id      : system
Interface      : in-band-management
IP Addr.       : 10.135.25.183/24             Port Id      : 1/1/24
Interface      : management
IP Addr.       : 10.135.25.183/24             Port Id      : A/1
===============================================================================
*A:SAS>config>qos>network#



*A:qos1# show qos network 1001 detail 
===============================================================================
QoS Network Policy
===============================================================================
-------------------------------------------------------------------------------
Network Policy (1001)
-------------------------------------------------------------------------------
Policy-id      : 1001                         Remark       : False             
Forward Class  : be                           Profile      : In                
Attach Mode    : mpls                         Config Mode  : mpls              
Scope          : Template                     Policy Type  : IpInterface       
Accounting     : packet-based                                                  
Description    : ip-interface-type
-------------------------------------------------------------------------------
LSP EXP Bit Map                         Forwarding Class                Profile
-------------------------------------------------------------------------------
0                                       be                              Out    
1                                       l2                              Out    
2                                       af                              In     
3                                       l1                              Out    
4                                       h2                              In     
5                                       ef                              Out    
6                                       h1                              Out    
7                                       nc                              In     
-------------------------------------------------------------------------------
Meter Mode   CIR Admin   CIR Rule   PIR Admin   PIR Rule    CBS Admin MBS Admin
             CIR Oper               PIR Oper                CBS Oper  MBS Oper
-------------------------------------------------------------------------------
1     TrTcm_CA  4000      closest       8000      closest   def       def    
                4000                    8000                def       500    
2     TrTcm_CA  4000      closest       7000      closest   16384     16384  
                4000                    7000                16000     16000  
3     TrTcm_CA  4000      closest       7000      closest   def       def    
                4000                    7000                def       500    
4     TrTcm_CA  4000      closest       7000      closest   def       def    
                4000                    7000                def       500    
5     TrTcm_CA  4000      closest       7000      closest   def       def    
                4000                    7000                def       500    
6     TrTcm_CA  4000      closest       7000      closest   def       def    
                4000                    7000                def       500    
7     TrTcm_CA  4000      closest       7000      closest   def       def    
                4000                    7000                def       500    
8     TrTcm_CA  7000      closest       7000      closest   def       def    
                7000                    7000                def       500    
9     TrTcm_CA  4000      closest       7000      closest   def       def    
                4000                    7000                def       500    
10    TrTcm_CA  4000      closest       7000      closest   def       def    
                4000                    7000                def       500    
11    TrTcm_CA  4000      closest       7000      closest   def       def    
                4000                    7000                def       500    
12    TrTcm_CA  4000      closest       7000      closest   def       def    
                4000                    7000                def       500 
-------------------------------------------------------------------------------
FC                  UCastM         MCastM         
-------------------------------------------------------------------------------
l2                  2              def           
af                  3              def           
l1                  4              def           
h2                  5              12            
ef                  6              11            
h1                  7              10            
nc                  8              9 
-------------------------------------------------------------------------------
Egress Forwarding Class Queuing
-------------------------------------------------------------------------------
FC Value       : 0                            FC Name      : be                
- LSP EXP Bit Mapping
Out-of-Profile : 0                            In-Profile   : 0                 
 
FC Value       : 1                            FC Name      : l2                
- LSP EXP Bit Mapping
Out-of-Profile : 1 
...
===============================================================================
*A:qos1# 

Table 8. Output fields: network QoS policyfor the 7210 SAS-R6 and 7210 SAS-R12
Label Description

Policy-Id

Displays the ID that uniquely identifies the policy

Remark

True — Remarking is enabled for all packets that egress this router where the network policy is applied. The remarking is based on the FC to bit mapping defined under the egress node of the network QoS policy.

Description

Displays a text string that helps identify the policy context in the configuration file

Forward Class/FC Name

Specifies the FC name

Profile

Out — Specifies the EXP marking for the packets that are out-of-profile, egressing on this queue

In — Specifies the EXP marking for the packets that are in-of-profile, egressing on this queue

Accounting

Packet-based — Specifies that the meters associated with this policy do not account for packet framing overheads (such as Ethernet the Inter Frame Gap (IFG) and the preamble), while accounting for the bandwidth to be used by this flow

Frame-based — Specifies that the meters associated with this policy account for the packet framing overheads (such as for Ethernet the IFG and preamble), while accounting for the bandwidth used by the flow

Profile policy

Displays the profile policy ID

Global Prof

Displays the global profile policy ID for LDP packets

Bit Mapping:

Out-of-Profile

Displays the value used for out-of-profile traffic

In-Profile

Displays the value used for in-profile traffic

Interface

Displays the interface name

IP Addr

Displays the interface IP address

Port-Id

Specifies the physical port identifier that associates the interface

mpls-lsp-exp-profile-map
Syntax

mpls-lsp-exp-profile-map [policy-id] [detail]

Context

show>qos

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command displays profile policy information.

Parameters
policy-id

Displays information for the specific policy ID.

Values

1 to 65535

detail

Displays detailed policy information.

Output

The following output is an example of MPLS LSP EXP profile mapping information, and Output fields: QoS MPLS LSP EXP profile map describes the output fields.

Sample output
*A:7210-SAS>show>qos# mpls-lsp-exp-profile-map 1

===============================================================================
QoS MPLS LSP EXP Profile Maps
===============================================================================
-------------------------------------------------------------------------------
Profile Map-id     : 1
Description        : Default MPLS LSP EXP Profile Map policy

-------------------------------------------------------------------------------
Exp       Profile
-------------------------------------------------------------------------------
0         Out
1         In
2         Out
3         In
4         In
5         In
6         In
7         In
===============================================================================
*A:7210SAS>show>qos# mpls-lsp-exp-profile-map 1 detail

===============================================================================
QoS MPLS LSP EXP Profile Maps
===============================================================================
-------------------------------------------------------------------------------
Profile Map-id     : 1
Description        : Default MPLS LSP EXP Profile Map policy

-------------------------------------------------------------------------------
Exp       Profile
-------------------------------------------------------------------------------
0         Out
1         In
2         Out
3         In
4         In
5         In
6         In
7         In

-------------------------------------------------------------------------------
Network Policy Associations
-------------------------------------------------------------------------------
Network Policy Id             : 2
-------------------------------------------------------------------------------
===============================================================================
*A:7210-SAS>show>qos#
Table 9. Output fields: QoS MPLS LSP EXP profile map
Label Description

Profile Map-id

Displays the profile Map ID

Description

A text string that helps identify the policy’s context in the configuration file

Exp

Displays the EXP. value

Profile

Specifies the marking of the packets as in-profile or out-of-profile

Network Policy Id

Displays the Network policy ID with which the mpls-lsp-exp-profile is associated

Show commands (7210 SAS-Mxp, 7210 SAS-R6, and 7210 SAS-R12)

dscp-table
Syntax

dscp-table [value dscp-value]

Context

show>qos

Platforms

7210 SAS-Mxp, 7210 SAS-R6, and 7210 SAS-R12

Description

This command displays DSCP name and DSCP value mappings.

Parameters
value dscp-value

Specifies the DSCP value for which to display information.

Values

0 to 63

Default

all values

Output

The following output is an example of DSCP value information, and Output fields: QoS network DSCP describes the output fields.

Sample output
A:ALA-48# show qos dscp-table
===========================================================
DSCP Mapping
===========================================================
DSCP Name      DSCP Value     TOS (bin)      TOS (hex)
-----------------------------------------------------------
be             0              0000 0000      00
cp1            1              0000 0100      04
cp2            2              0000 1000      08
cp3            3              0000 1100      0C
cp4            4              0001 0000      10
cp5            5              0001 0100      14
cp6            6              0001 1000      18
cp7            7              0001 1100      1C
cs1            8              0010 0000      20
cp9            9              0010 0100      24
af11           10             0010 1000      28
cp11           11             0010 1100      2C
af12           12             0011 0000      30
cp13           13             0011 0100      34
af13           14             0011 1000      38
cp15           15             0011 1100      3C
cs2            16             0100 0000      40
cp17           17             0100 0100      44
af21           18             0100 1000      48
cp19           19             0100 1100      4C
af22           20             0101 0000      50
cp21           21             0101 0100      54
af23           22             0101 1000      58
cp23           23             0101 1100      5C
cs3            24             0110 0000      60
cp25           25             0110 0100      64
af31           26             0110 1000      68
cp27           27             0110 1100      6C
af32           28             0111 0000      70
cp29           29             0111 0100      74
af33           30             0111 1000      78
cp31           31             0111 1100      7C
cs4            32             1000 0000      80
cp33           33             1000 0100      84
af41           34             1000 1000      88
cp35           35             1000 1100      8C
af42           36             1001 0000      90
cp37           37             1001 0100      94
af43           38             1001 1000      98
cp39           39             1001 1100      9C
cs5            40             1010 0000      A0
cp41           41             1010 0100      A4
cp42           42             1010 1000      A8
cp43           43             1010 1100      AC
cp44           44             1011 0000      B0
cp45           45             1011 0100      B4
ef             46             1011 1000      B8
cp47           47             1011 1100      BC
nc1            48             1100 0000      C0
cp49           49             1100 0100      C4
cp50           50             1100 1000      C8
cp51           51             1100 1100      CC
cp52           52             1101 0000      D0
cp53           53             1101 0100      D4
cp54           54             1101 1000      D8
cp55           55             1101 1100      DC
nc2            56             1110 0000      E0
cp57           57             1110 0100      E4
cp58           58             1110 1000      E8
cp59           59             1110 1100      EC
cp60           60             1111 0000      F0
cp61           61             1111 0100      F4
cp62           62             1111 1000      F8
cp63           63             1111 1100      FC
===========================================================
A:ALA-48#


A:ALA-48# show qos dscp-table value 46
===========================================================
DSCP Mapping
===========================================================
DSCP Name      DSCP Value     TOS (bin)      TOS (hex)
-----------------------------------------------------------
ef             46             1011 1000      B8
===========================================================
A:ALA-48#
Table 10. Output fields: QoS network DSCP
Label Description

DSCP Name

Displays the name of the DiffServ code point to be associated with the forwarding class

DSCP Value

Displays the DSCP values range between 0 and 63

TOS (bin)

Displays the type of service in binary format

TOS (hex)

Displays the type of service in hexadecimal format

router
Syntax

router [router-instance]

router service-name service-name

Context

show

Platforms

7210 SAS-Mxp, 7210 SAS-R6, and 7210 SAS-R12

Description

This command displays router information.

Parameters
router-instance

Specifies the router name or service ID

Values

router-name — Base

service-id — 1 to 2147483647

Default

Base

service-name

Specifies the service name, up to a 64 characters.

sgt-qos
Syntax

sgt-qos

Context

show>router

Platforms

7210 SAS-Mxp, 7210 SAS-R6, and 7210 SAS-R12

Description

This command displays QoS information about self-generated traffic. In the output, the value ‟none” indicates that the default value is used; it does not indicated that there is no value set. Default DSCP mapping table lists the application defaults.

application
Syntax

application [app-name] [dscp | dot1p]

Context

show>router>sgt-qos

Platforms

7210 SAS-Mxp, 7210 SAS-R6, and 7210 SAS-R12

Description

This command displays application QoS settings.

Parameters
app-name

Specifies the application.

Values

The following values apply to the base router instance:

bgp, dns, ftp, icmp, igmp, ldp, ndis, ntp, ospf, pim, ptp, radius, rip, rsvp, snmp, snmp-notification, ssh, syslog, tacplus, telnet, tftp, traceroute, vrrp, arp, isis

The following values apply to a VPRN service instance:

bgp, icmp, igmp, ndis, ospf, pim, ssh, telnet, traceroute, vrrp, arp

Note:
  • The value ‟ptp” in the context of SGT QoS is defined as Precision Timing Protocol and is an application. The PTP application name is also used in areas such as event-control and logging. Precision Timing Protocol is defined in IEEE 1588-2008.

  • The value ‟ptp” in the context of IP filters is defined as Performance Transparency Protocol. IP protocols can be used as IP filter match criteria; the match is made on the 8-bit protocol field in the IP header.

dscp

Displays all DSCP applications.

dot1p

Displays all dot1p applications.

Output

The following outputs show an example of application QoS information for the base router and for a VPRN service instance, and Output fields: SGT-QoS application describes the output fields.

Sample output (router)
*A:SAS-DUTA# show router sgt-qos application 
===============================================================================
DSCP Application Values
===============================================================================
Application         DSCP Value                    Default DSCP Value
-------------------------------------------------------------------------------
bgp                 none                          none
dns                 none                          none
ftp                 none                          none
icmp                none                          none
igmp                none                          none
ldp                 none                          none
ndis                none                          none
ntp                 none                          none
ospf                none                          none
pim                 none                          none
ptp                 none                          none
radius              none                          none
rip                 none                          none
rsvp                none                          none
snmp                none                          none
snmp-notification   none                          none
ssh                 none                          none
syslog              none                          none
tacplus             none                          none
telnet              none                          none
tftp                none                          none
traceroute          none                          none
vrrp                none                          none
===============================================================================
===============================================================================
Dot1p Application Values
===============================================================================
Application         Dot1p Value                   Default Dot1p Value
-------------------------------------------------------------------------------
arp                 none                          none
isis                none                          none
===============================================================================
*A:SAS-DUTA# 
*A:SAS-DUTA# show router sgt-qos application arp 
===============================================================================
Dot1p Application Values
===============================================================================
Application         Dot1p Value                   Default Dot1p Value
-------------------------------------------------------------------------------
arp                 none                          none
===============================================================================
*A:SAS-DUTA# 
Sample output (VPRN service instance)
=======================
*A:SAS-DUTA# show router 1 sgt-qos application  
===============================================================================
DSCP Application Values
===============================================================================
Application         DSCP Value                    Default DSCP Value
-------------------------------------------------------------------------------
bgp                 none                          none
icmp                cp17                          none
igmp                none                          none
ndis                none                          none
ospf                none                          none
pim                 none                          none
ssh                 none                          none
telnet              none                          none
traceroute          none                          none
vrrp                none                          none
===============================================================================
===============================================================================
Dot1p Application Values
===============================================================================
Application         Dot1p Value                   Default Dot1p Value
-------------------------------------------------------------------------------
arp                 none                          none
isis                none                          none
===============================================================================
*A:SAS-DUTA#    
*A:SAS-DUTA>config>service# \show router 1 sgt-qos application  arp 
===============================================================================
Dot1p Application Values
===============================================================================
Application         Dot1p Value                   Default Dot1p Value
-------------------------------------------------------------------------------
arp                 none                          none
===============================================================================
*A:SAS-DUTA# 
Table 11. Output fields: SGT-QoS application
Label Description

Application

The DSCP or dot1p application

DSCP Value

The DSCP name or value assigned to the application; if you assign a value to the application (0 to 63), the DSCP name that maps to the value is displayed

Default DSCP Value

The default DSCP value

Dot1p Value

The dot1p priority assigned to the application (applies only to ARP and IS-IS)

Default Dot1p Value

The default dot1p value

dscp-map
Syntax

dscp-map [dscp-name]

Context

show>router>sgt-qos

Platforms

7210 SAS-Mxp, 7210 SAS-R6, and 7210 SAS-R12

Description

This command displays DSCP-to-FC mappings.

Parameters
dscp-name

Specifies the DSCP name.

Values

be, ef, cp1, cp2, cp3, cp4, cp5, cp6, cp7, cp9, cs1, cs2, cs3, cs4, cs5, nc1, nc2, af11, af12, af13, af21, af22, af23, af31, af32, af33, af41, af42, af43, cp11, cp13, cp15, cp17, cp19, cp21, cp23, cp25, cp27, cp29, cp31, cp33, cp35, cp37, cp39, cp41, cp42, cp43, cp44, cp45, cp47, cp49, cp50, cp51, cp52, cp53, cp54, cp55, cp57, cp58, cp59, cp60, cp61, cp62, cp63

Output

The following outputs show examples of DSCP-to-FC mapping information for a base router and a VPRN service instance, and Output fields: SGT-QoS DSCP-to-FC mapping describes the output fields.

Sample output (router)
*A:SAS-DUTA# show router sgt-qos dscp-map 
===============================================================================
DSCP to FC Mappings
===============================================================================
DSCP Value          FC Value            Default FC Value
-------------------------------------------------------------------------------
be                  nc                  nc
cp1                 be                  be
cp2                 be                  be
cp3                 be                  be
cp4                 be                  be
cp5                 be                  be
cp6                 be                  be
cp7                 be                  be
cs1                 be                  be
cp9                 be                  be
af11                af                  af
cp11                be                  be
af12                af                  af
cp13                be                  be
af13                af                  af
cp15                be                  be
cs2                 be                  be
cp17                be                  be
af21                l1                  l1
cp19                be                  be
af22                l1                  l1
cp21                be                  be
af23                l1                  l1
cp23                be                  be
cs3                 be                  be
cp25                be                  be
af31                l1                  l1
cp27                be                  be
af32                l1                  l1
cp29                be                  be
af33                h2                  l1
cp31                be                  be
cs4                 be                  be
cp33                be                  be
af41                nc                  nc
cp35                be                  be
af42                h2                  h2
cp37                be                  be
af43                h2                  h2
cp39                be                  be
cs5                 be                  be
cp41                be                  be
cp42                be                  be
cp43                be                  be
cp44                be                  be
cp45                be                  be
ef                  ef                  ef
cp47                be                  be
nc1                 nc                  nc
cp49                be                  be
cp50                h2                  h2
cp51                be                  be
cp52                be                  be
cp53                be                  be
cp54                be                  be
cp55                be                  be
nc2                 nc                  nc
cp57                be                  be
cp58                be                  be
cp59                be                  be
cp60                be                  be
cp61                be                  be
cp62                be                  be
cp63                be                  be
===============================================================================
*A:SAS-DUTA# 
Sample output (VPRN service instance)
*A:SAS-DUTA# show router 1 sgt-qos dscp-map 
===============================================================================
DSCP to FC Mappings
===============================================================================
DSCP Value          FC Value            Default FC Value
-------------------------------------------------------------------------------
be                  nc                  nc
cp1                 be                  be
cp2                 be                  be
cp3                 be                  be
cp4                 be                  be
cp5                 be                  be
cp6                 be                  be
cp7                 be                  be
cs1                 be                  be
cp9                 be                  be
af11                af                  af
cp11                be                  be
af12                af                  af
cp13                be                  be
af13                af                  af
cp15                be                  be
cs2                 be                  be
cp17                ef                  be
af21                l1                  l1
cp19                be                  be
af22                l1                  l1
cp21                be                  be
af23                l1                  l1
cp23                be                  be
cs3                 be                  be
cp25                be                  be
af31                l1                  l1
cp27                be                  be
af32                l1                  l1
cp29                be                  be
af33                l1                  l1
cp31                be                  be
cs4                 be                  be
cp33                be                  be
af41                nc                  nc
cp35                be                  be
af42                h2                  h2
cp37                be                  be
af43                h2                  h2
cp39                be                  be
cs5                 be                  be
cp41                be                  be
cp42                be                  be
cp43                be                  be
cp44                be                  be
cp45                be                  be
ef                  ef                  ef
cp47                be                  be
nc1                 nc                  nc
cp49                be                  be
cp50                h2                  h2
cp51                be                  be
cp52                be                  be
cp53                be                  be
cp54                be                  be
cp55                be                  be
nc2                 nc                  nc
cp57                be                  be
cp58                be                  be
cp59                be                  be
cp60                be                  be
cp61                be                  be
cp62                be                  be
cp63                be                  be
===============================================================================
*A:SAS-DUTA# 
Table 12. Output fields: SGT-QoS DSCP-to-FC mapping
Label Description

DSCP Value

Displays the DSCP values (displayed as names) of the self-generated traffic

FC Value

Displays the FC value mapped to each DSCP value

Default FC Value

Displays the default FC value

1 The default FC mapping is used for all DSCP names/values for which there is no explicit FC mapping.