Network QoS policies

This chapter provides information to configure network QoS policies using the CLI.

Overview of network QoS policies

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

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

Note:

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

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

Access uplink port egress marking support consists of the following:

  • For packets sent out of a access-uplink port, the network QoS policy defines the marking values (for example, IEEE 802.1p bits, and so on) to use based on the FC and the profile state.

  • The default map of FC to marking values (for example, 802.1p bits) is as shown in the default network QoS policy, policy id 1.

  • All non-default network QoS policies inherit the default map and can be modified by the user.

  • On 7210 SAS-D and 7210 SAS-Dxp, remarking can be enabled or disabled on access uplink ports. An option is provided to map FC to dot1p and DEI bits and IP DSCP values.

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

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

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

Resource allocation for network QoS policy

This section describes the allocation of QoS resources for network QoS policies. When the port mode is changed to access-uplink, a default network QoS policy is applied. For the default policy, two meters and eighteen classification entries in hardware are allocated.

Note:

The number of resources used per network QoS policy determines the number of access-uplink ports that can be configured. If more resources are used, fewer access-uplink ports can be used, and the other way around.

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

To calculate the number of QoS resources used by an access-uplink port, 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 for the ‟number of FCs” and are therefore are referred to as ‟FCs in use”. Also, in network policies of the type ip-interface, the default multipoint meter 9 is created in a policy; whereas, for policy of type ‟port”, the 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 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, use the following equation to calculate the total number of classification entries per policy (for example TC):

  • 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 7210 SAS platforms, the maximum number of classification entries per policy can be 64 (including default).

  • 2 is the number of classification entries that are required by FCi.

Note:

In the worst case, only 2 classification entries are used per FC in a network policy, because only two traffic types are supported.

Determine number of policers or meters to use (for example TP). A maximum of 16 meters per network policy are available.

Only those meters that are associated with FCs need to be considered for number of meters; only FCs in use are considered.

Network QoS policies resource usage examples

This section provides usage examples for network QoS policies.

Example 1
network 1 create
     description ‟default QoS policy”
            ingress
                default-action fc be profile out
                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 = 18

The number of meters (TP) used is 2 (meter 1 and 9).

Example 2
network 2 create
     description ‟network-policy-2”

            ingress
                default-action fc be profile out
                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
                dot1p 2 fc af profile out
            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) used is 4 (meters 1,2,9,12).

Example 3
network 3 create
     description ‟network-policy-3”
            ingress
                default-action fc be profile out
                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
                dot1p 2 fc af profile out
            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) used is 2 (meters 2 and 12).

Example 4
network 4 create
     description ‟network-policy-4”
            ingress
                default-action fc be profile out
                meter 1 create
                exit
                meter 9 multipoint create
                exit
                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
                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 create
     description ‟network-policy-5”
            ingress
                default-action fc be profile out
                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
                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
                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 create
     description ‟network-policy-6”

            ingress
                default-action fc be profile out
                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
                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
                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 create
            description "network-policy 2"
            scope template
            ingress
                default-action fc be profile out
                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
                network-policy 2 0 fc be profile out
                network-policy 2 1 fc l2 profile in
                network-policy 2 2 fc af profile out
                network-policy 2 3 fc af profile in
                network-policy 2 4 fc h2 profile in
                network-policy 2 5 fc ef profile in
                network-policy 2 6 fc h1 profile in
                network-policy 2 7 fc nc profile in
            exit
            egress
                no remarking 

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

The number of meters (TP) used is 2.

Example 8
network 8 create
description ‟network-policy-8”
            ingress
                default-action fc nc profile in
                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
                dot1p 1 fc l2 profile in
                dot1p 3 fc af profile in
                dot1p 5 fc ef profile in
                dot1p 7 fc nc profile in
            exit
            egress

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

Basic configuration

A basic network QoS policy must:

  • have a unique policy ID

  • specify the default-action

  • have a QoS policy scope of template or exclusive

  • depending on the 7210 SAS platform, have at least one default unicast FC meter/queue

  • depending on the 7210 SAS platform, have at least one multipoint FC meter/queue

Create a network QoS policy

Configuring and applying QoS policies other than the default policy is optional. A default network policy of the appropriate type is applied to each uplink port.

To create an network QoS policy, define the following:

  • Specify a network policy ID value. The system does not dynamically assign a value.

  • Include a description that provides a brief overview of policy features.

  • Use egress marking and remarking to specify the egress FC to marking value (for example, IEEE 802.1p) map. Otherwise, the default values are applied:

    • remarking

      If enabled, this command remarks ALL packets that egress on the specified access uplink port. The remarking is based on the FC to marking values mapping defined under the egress node of the network QoS policy. Remarking can be enabled or disabled.

    • FC criteria

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

    • marking value

      The marking (for example, IEEE 802.1p) value is used for all packets requiring marking that egress on this FC queue that are in-profile or out-of-profile.

  • Specify ingress criteria using the following:

    • default action

      Defines the default action to be taken for packets that have an undefined dot1p bit set. The default-action specifies the FC to which such packets are assigned.

    • dot1p

      This specifies the dot1p to FC mapping for all packets. Ingress traffic that matches the specified criteria are assigned to the corresponding FC.

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
             
             fc {be|l2|af|l1|h2|ef|h1|nc} 
                 dot1p-in-profile dot1p-priority
                 dot1p-out-profile dot1p-priority
             default-action fc {fc-name} profile {in|out}
             dot1p dot1p-priority 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]

The following commands associate a network QoS policy with the access-uplink port.

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

The following is a sample configuration output for uplink port 1/1/1 with network policy 600 applied to the interface.

A:ALA-7>config# info
#--------------------------------------------------
echo "Port Configuration"
#--------------------------------------------------
    port 1/1/1
        shutdown
        description "port 1/1/1"
        ethernet
            mode access uplink
            access
                uplink
                    qos 600
                exit
            exit
        exit
    exit
...
#--------------------------------------------------
A:ALA-7>config#

Default network policy values

The default network policy access uplink port is identified as policy-id ‟1”. Default policies cannot be modified or deleted. The following table lists default network policy parameters.

Table 1. Default network policy 1

Field

Default

description

Default network QoS policy

Ingress

default-action

fc be profile out

meter

1

mode

trtcm1

adaptation-rule

cir closest

pir closest

rate

cir 0

pir max

mbs

default kbits

cbs

default kbits

DSCP marking for CPU-generated traffic

DSCP marking for CPU-generated traffic is not configurable by the user. The following table lists the default values.

Note:

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

Table 2. DSCP and dot1p marking

Protocol

IPv4

DSCP marking

dot1p marking

Default FC

DSCP values

dot1p values

ARP

NA

NA

Yes

NC

-

7

CFM

NA

NA

Yes

NC

-

7

FTP

Yes

Yes

Yes

H2

34

4

ICMP ping

Yes

Yes

Yes

NC

0

7

ICMP Req

Yes

Yes

Yes

NC

0

7

ICMP Res

Yes

Yes

Yes

NC

0

7

ICMP Unreach

Yes

Yes

Yes

NC

0

7

IGMP

Yes

Yes

Yes

NC

48

7

NTP

Yes

Yes

Yes

NC

48

7

PTP 1

Yes

Yes

Yes

See1

See1

7

RADIUS

Yes

Yes

Yes

H2

34

4

SCP

Yes

Yes

Yes

H2

34

4

SNMP

Yes

Yes

Yes

H2

34

4

SNMP trap/log

Yes

Yes

Yes

H2

34

4

SSH

Yes

Yes

Yes

H2

34

4

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

Trace route

Yes

Yes

Yes

NC

0

7

1 Based on the type of the PTP message, that is, PTP event messages (for example, Sync message) and PTP non-event messages (for example, Announce, Follow-up), the DSCP value used is either 0x30 (h1) or 0x38 (nc), and the dot1p value is always 7.

Default DSCP mapping table

The following table lists default DSCP mapping values.

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

default1

0

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

Service management tasks

This section provides information about service management tasks.

Deleting QoS policies

A network policy is associated by default with access uplink ports.

You can replace the default policy with a non-default policy, but you cannot remove default policies from the configuration. When you remove a non-default policy, the policy association reverts to the appropriate default network policy.

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.

Use the following syntax to overwrite a network policy.

 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 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 for 7210 SAS-D and 7210 SAS-Dxp

    - config
        - qos
            - [no] network network-policy-id [create]
                - description description-string 
                - no description
                - egress
                    - [no] fc fc-name 
                        - [no] de-mark [force de-value]
                        - dot1p dot1p-priority
                        - no dot1p
                        - dot1p-in-profile dot1p-priority
                        - no dot1p-in-profile
                        - dot1p-out-profile dot1p-priority
                        - no dot1p-out-profile
                        - dscp-in-profile dscp-name
                        - no dscp-in-profile
                        - dscp-out-profile dscp-name
                        - no dscp-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}
                    - 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 [kbits | bytes | kbytes] 
                        - no cbs
                        - mbs size [kbits | bytes | kbytes] 
                        - no mbs
                        - mode {trtcm1 | trtcm2 | srtcm}
                        - no mode
                        - rate cir-rate-in-kbps [pir pir-rate-in-kbps]
                        - no rate
                - scope {exclusive | template}
                - no scope

Operational commands

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

Show commands

    - show
        - qos
            - network policy-id [detail]
            - network [network-policy-id] association
            - network [network-policy-id] [detail]

Command descriptions

Configuration commands

Generic commands

description
Syntax

description description-string

no description

Context

config>qos>network

Platforms

Supported on all 7210 SAS platforms as described in this document

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.

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

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 that the source and destination policies are network policy IDs. 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.

Values

1 to 65535

overwrite

Specifies that everything in the existing destination policy is overwritten with the contents of the source policy. If overwrite is not specified, an error occurs if the destination policy ID exists.

remarking
Syntax

[no] remarking {use-dot1p | use-dscp | all}

Context

config>qos>network>egress

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command remarks egress packets sent out of access ports and access-uplink ports. Remarking can be enabled or disabled. On access port and access-uplink port egress, the behavior is as follows.

If remarking is enabled without specifying one of the options, by default 'use-dot1p' is used for access-egress and ‟all” is used for network-egress (that is, access-uplink port egress).

The no form of this command disables remarking.

Default

no remarking

Parameters
use-dot1p

Specifies that the dot1p bits are marked in the packet header for all IEEE 802.1q and IEEE 802.1p encapsulated traffic sent out of the access port.

use-dscp

Specifies that the IP DSCP bits are marked in the packet header for IPv4 traffic sent out of the access port.

all

Specifies that the dot1p bits are marked in the packet header for all IEEE 802.1q and IEEE 802.1p encapsulated traffic, and in addition the IP DSCP bits are marked in the packet header for all IPv4 traffic sent out the access port.

scope
Syntax

scope {exclusive | template}

no scope

Context

config>qos>network

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

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

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

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, the policy becomes available for assignment to another exclusive interface.

The system default policies cannot be put into the exclusive scope. An error is generated if scope exclusive is executed in any policies with a policy-id equal to 1.

template

Specifies that the scope of a policy is defined as template, 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 scope template parameter to scope exclusive on default policies.

Network QoS policy commands

network
Syntax

network network-policy-id [create]

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 access uplink 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 dot1p 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 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 FC. Traffic mapped to each FC can be rate limited using separate meters for unicast and multipoint traffic.

The egress component of the network QoS policy defines the FC and profile to packet header priority bits (for example: dot1p bits).

The network policy 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 BUM traffic on the, ingress. For the egress, it defines eight FCs which represent individual queues and the packet marking behavior.

If a new network policy is created (for instance, policy 2), only the default action and egress FC parameters are identical to the default policy. A new network policy does not contain the default dot1p to FC mapping for network QoS policy. The default network policy can be copied (use the copy command) to create a new network policy that includes the default ingress dot1p to FC mapping (as appropriate). You can modify parameters or use the no modifier to remove an object from the configuration.

Changes made to an existing policy, using any of the sub-commands, are applied immediately to all access uplink 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. 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 1 cannot be deleted.

Default

system default network policy 1

Parameters
network-policy-id

Specifies the policy on the 7210 SAS.

Values

1 to 65535

create

Specifies that a QoS network policy is created.

Network ingress QoS policy commands

fc
Syntax

[no] fc fc-name [create]

Context

config>qos>network>ingress

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command creates a class instance of the FC. After the fc-name is created, classification actions can be applied, which can be used in match classification criteria. By default, undefined FCs use the parameters configured in the default policy policy-id 1.

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.

Parameters
fc-name

Specifies the case-sensitive, system-defined FC name for which policy entries will be created.

Values

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

create

Specifies that the FC is created. The create keyword requirement can be enabled in the environment>create context.

ingress
Syntax

ingress

Context

config>qos>network

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

Commands in this context create or edit policy entries that specify the dot1p to FC mapping for all packets.

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

default-action
Syntax

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

Context

config>qos>network>ingress

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command configures the default action taken for packets that have undefined dot1p bits set. The default-action command specifies the FC 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 FC name. All packets with dot1p or dot1p bits that are not defined are placed in this FC.

Values

be | l2 | af | l1 | h2 | e | h1 | nc

profile {in | out}

Specifies an in or out of profile for all packets assigned to this FC. A value of 'in' defines the packet profile as 'in-profile' and a value of 'out' defines the packet profile to be 'out-of-profile.

fc
Syntax

[no] fc fc-name [create]

Context

config>qos>network>ingress

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command creates a class instance of the FC. After the fc-name is created, classification actions can be applied and it can be used in match classification criteria. By default, undefined FCs use the parameters configured in the default network policy policy-id 1.

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.

Parameters
fc-name

Specifies the case-sensitive system-defined FC name for which policy entries are created.

Values

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

create

Specifies that the FC is created. The create keyword requirement can be enabled in the environment>create context.

dot1p
Syntax

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

no dot1p dot1p-priority

Context

config>qos>network>ingress

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command explicitly sets the FC or enqueuing priority and 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 FC 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.1Q or IEEE 802.1P header. The three dot1p bits define 8 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 from 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 FC is 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 value that must be one of the predefined FCs in the system. Specifying the fc-name is optional. When a packet matches the rule, the FC is only overridden when the fc fc-name parameter is defined on the rule. If the packet matches and the FC is not explicitly defined in the rule, the FC is inherited based on previous rule matches.

Values

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

profile {in|out}

Specifies an in or out of profile for all packets assigned to this FC. A value of 'in' defines the packet profile as 'in-profile' and a value of 'out' defines the packet profile to be 'out-of-profile.

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

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 FC forwarding types are mapped to the meter, they revert to their default meters. When a meter is removed, any pending accounting information is discarded for each port meter created because of the definition of the meter in the policy is discarded.

Default

meter 1 (for unicast traffic)

meter 9 multipoint (for traffic other than unicast traffic)

Parameters
meter-id

Specifies the meter-id that uniquely identifies the meter within the policy. This is a required parameter each time the meter command is executed.

Values

1 to 12

multipoint

Specifies that this meter-id is for multipoint forwarded traffic only. This meter-id can only be explicitly mapped to the FC multicast, broadcast, or unknown unicast ingress traffic. If you attempt to map FC 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 does not execute.

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

create

Keyword to create the ingress network QoS policy meter.

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

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 FC mapping is executed, all unicast traffic on a port using this policy is forwarded using the meter-id.

The no form of this command reverts the unicast (point-to-point) meter ID back to the default meter for the FC.

Default

meter 1

Parameters
meter-id

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

Values

1 to 12

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 FC mapping is executed, all multicast traffic on a port using this policy is forwarded using the meter ID.

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

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

2 to 12

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

Description

This command defines the method used by the system to derive the operational CIR and PIR rates 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.

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 rate and cir 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 rate defined using the meter meter-id rate command. The cir parameter requires a qualifier that defines the constraint used to derive the operational CIR rate for the meter. When the pir command is not specified, the default constraint applies. The max (maximum), min (minimum), and closest qualifiers are mutually exclusive.

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. When max is defined, the operational CIR is the next multiple of 8 kbps (for 7210 SAS-D) equal to or less than the specified rate. For 7210 SAS-Dxp, see Adaptation rule for meters on 7210 SAS-Dxp devices for information about calculating the next multiple equal to or less than the specified rate.

min — Specifies that the operational CIR value is equal to or greater than the specified rate, taking into account the hardware step size. When min is defined, the operational CIR is the next multiple of 8 kbps (for 7210 SAS-D) equal to or greater than the specified rate. For 7210 SAS-Dxp, see Adaptation rule for meters on 7210 SAS-Dxp devices for information about calculating the next multiple equal to or greater than the specified rate.

closest — Specifies that the operational CIR value is equal to the closest specified rate, taking into account the hardware step size. When closest is defined, the operational CIR is the next multiple of 8 kbps (for 7210 SAS-D) closest to the specified rate. For 7210 SAS-Dxp, see Adaptation rule for meters on 7210 SAS-Dxp devices for information about calculating the next multiple closest to the specified rate.

pir adaptation-rule

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

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. When max is defined, the operational PIR is the next multiple of 8 kbps (for 7210 SAS-D) equal to or less than the specified rate. For 7210 SAS-Dxp, see Adaptation rule for meters on 7210 SAS-Dxp devices for information about calculating the next multiple equal to or less than the specified rate.

min — Specifies that the operational PIR value is equal to or greater than the specified rate, taking into account the hardware step size. When min is defined, the operational PIR is the next multiple of 8 kbps (for 7210 SAS-D) equal to or greater than the specified rate. For 7210 SAS-Dxp, see Adaptation rule for meters on 7210 SAS-Dxp devices for information about calculating the next multiple equal to or greater than the specified rate.

closest — Specifies that the operational PIR value is equal to the closest specified rate, taking into account the hardware step size. When closest is defined, the operational PIR is the next multiple of 8 kbps (for 7210 SAS-D) closest to the specified rate. For 7210 SAS-Dxp, see Adaptation rule for meters on 7210 SAS-Dxp devices for information about calculating the next multiple closest to the specified rate.

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

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 size to the default value.

Default

32 kbits

Parameters
size

Specifies the size parameter is an integer expression of the number of kilobits, kilobytes, or bytes reserved for the meter; for example, if a value of 100 kb is needed, then enter the value 100. The bucket size is rounded to the next highest 4096 bytes boundary.

Values

kbits — 4 to 16384, default (7210 SAS-D)

4 to 2146959, default (7210 SAS-Dxp)

bytes — 512 to 2097152, default (7210 SAS-D)

512 to 274810752, default (7210 SAS-Dxp)

kbytes — 1 to 2048, default (7210 SAS-D)

1 to 268369, default (7210 SAS-Dxp)

kbits

Specifies that the value is in kilobits.

bytes

Specifies that the value is in kilobytes.

kbytes

Specifies that the value is in bytes.

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

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 size to the default value.

Default

128 kbits

Parameters
size

Specifies the size parameter is an integer expression of the number of kilobits reserved for the meter; for example, if a value of 100 kb is needed, then enter the value 100. The bucket size is rounded off to the next highest 4096 bytes boundary.

Values

kbits — 4 to 16384, default (7210 SAS-D)

4 to 2146959, default (7210 SAS-Dxp)

bytes — 512 to 2097152, default (7210 SAS-D)

512 to 274810752, default (7210 SAS-Dxp)

kbytes — 1 to 2048, default (7210 SAS-D)

1 to 268369, default (7210 SAS-Dxp)

kbits

Specifies that the value is in kilobits.

bytes

Specifies that the value is in kilobytes.

kbytes

Specifies that the value is in bytes.

mode
Syntax

mode {trtcm1|srtcm}

no mode

Context

config>qos>network>ingress>meter

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command defines the mode of the meter. The mode can be configured as Two Rate Three Color Marker (trTCM1) 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

trtcm1

Parameters
trtcm1

Specifies the policing algorithm defined in RFC2698 and meters the packet stream and marks its 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 example, for ingress policing of a service, where a peak rate needs to be enforced separately from a committed rate. Two token buckets are used, the CBS bucket and the MBS bucket. Tokens are added to the buckets based on the CIR and PIR rates. The algorithm deducts tokens from both the CBS and the MBS buckets to determine a profile for the packet.

srtcm

Specifies that the mode is configured as a srTCM and meters a packet stream and marks the 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 does exceed the CBS but not the cir and red otherwise. The srTCM is useful, for example, 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

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 rates for all meters created through the association of the network QoS policy with the meter-id. 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.

Note:

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

The no form of this command reverts all meter instances created with this meter-id to the default.

Default

rate 0 pir max

Parameters
cir cir-rate-in-kbps

Specifies that the default administrative CIR used by the meter will be overridden. 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 values must be a positive integer.

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

Values

0 to 20000000, max (7210 SAS-Dxp)

0 to 4000000, max (7210 SAS-D)

pir pir-rate-in-kbps

Specifies the administrative PIR rate, 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.

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

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

Values

0 to 20000000, max (7210 SAS-Dxp)

0 to 4000000, max (7210 SAS-D)

Network egress QoS policy commands

egress
Syntax

egress

Context

config>qos>network

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command creates or edits egress policy entries that specify the FC to marking values map to be instantiated when this policy is applied to the access-uplink port.

The FC and profile state mapping to marking values (for example: IEEE 802.1p bits, etc.) bits mapping for all packets are defined in this context.

fc
Syntax

[no] fc fc-name

Context

config>qos>network>egress

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command specifies the FC name. The FC name represents an egress queue. The fc fc-name represents a CLI parent node that contains subcommands or parameters describing the marking criteria of packets flowing through it. The fc command overrides the default parameters for that FC to the values defined in the network default policy.

The no form of this command removes the FC to marking value association. The FC reverts to the mapping defined in the default network policy.

Default

undefined FCs default to the configured parameters in the default network policy (policy ID 1)

Parameters
fc-name

Specifies the case-sensitive, system-defined FC name for which policy entries will be created.

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>queue

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

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

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 rate and cir apply. See Supported hardware rates and CIR and PIR values for egress queues on the 7210 SAS-D and Supported hardware rates and CIR and PIR values for egress queues on the 7210 SAS-Dxp for information about supported hardware step-size rates for 7210 SAS-D and 7210 SAS-Dxp.

Default

adaptation-rule cir closest pir closest

Parameters
cir adaptation-rule

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

Default

closest

Values

max — Specifies that the operational CIR 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 CIR value is greater 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.

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 when adapting the PIR rate defined using the queue queue-id rate command. The pir parameter requires a qualifier that defines the constraint used when deriving the operational PIR rate for the queue. When the pir command is not specified, the default constraint applies. The max (maximum), min (minimum), and closest qualifiers are mutually exclusive. See Supported hardware rates and CIR and PIR values for egress queues on the 7210 SAS-D and Supported hardware rates and CIR and PIR values for egress queues on the 7210 SAS-Dxp for information about supported hardware step-size rates for 7210 SAS-D and 7210 SAS-Dxp.

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

closest — Specifies that the operational PIR 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.

slope-policy
Syntax

[no] slope-policy name

Context

config>qos>network>queue

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command overrides the default slope policy configuration for the queue. The specified slope policy name must exist as a current slope policy name. If the slope policy does not exist, the slope-policy command fails. If a slope policy is currently associated with a queue, the slope policy cannot be removed from the system.

The slope policy contains the ring and non-ring high and low WRED slope definitions that will be used by the queue. The non-ring slopes are used by the traffic received on access SAP ingress and sent out of access SAP egress queues. The ring slopes are used by the traffic received on access-uplink port ingress and sent out of access-uplink port egress queues.

If the slope-policy command is not executed or the no slope policy command is executed, the default slope policy is associated with the queue.

The no form of the command reverts the default slope policy to the queue.

Parameters
name

Specifies an existing slope policy name. If the slope policy name does not exist, the slope-policy command fails.

Values

32 chars maximum

queue
Syntax

queue queue-id create

no queue

Context

config>qos>network

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command creates the context to modify queue parameters associated with a particular queue.

The no form of this command deletes the queue.

Parameters
queue-id

Specifies the ID of the queue.

Values

1 to 8

create

Specifies that a network queue policy will be created.

rate
Syntax

rate [cir cir-percent] [pir pir-percent]

no rate

Context

config>qos>network>queue

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command defines the administrative Peak Information Rate (PIR) and the administrative Committed Information Rate (CIR) parameters for the queue. The PIR defines the maximum rate that the queue can transmit packets through the port. Defining a PIR does not necessarily guarantee that the queue can transmit at the intended rate. The actual rate sustained by the queue can be limited by oversubscription factors or available egress bandwidth. The CIR defines the rate at which the system prioritizes the queue over other queues competing for the same bandwidth.

The rate command can be executed at anytime, altering the PIR and CIR rates for all queues created on the access ports.

The no form of the command reverts all queues created with the queue-id by association with the QoS policy to the default PIR and CIR parameters.

Parameters
cir cir-percent

Specifies the percentage of the guaranteed rate allowed for the queue. When the rate command is executed, a valid CIR setting must be explicitly defined. When the rate command has not been executed, the default CIR of 0 is assumed. Fractional values are not allowed and must be specified as a positive integer.

The actual CIR rate is dependent on the queue’s adaptation-rule parameters and the actual hardware where the queue is provisioned.

Values

0 to 100

Default

0

pir pir-percent

Specifies the percentage of the maximum rate allowed for the queue. When the rate command is executed, the PIR setting is optional. When the rate command has not been executed, or the PIR parameter is not explicitly specified, the default PIR of 100 is assumed. Fractional values are not allowed and must be specified as a positive integer.

Values

1 to 100 %

Default

100

Network egress QoS policy forwarding class commands

dot1p-in-profile
Syntax

dot1p-in-profile dot1p-priority

no dot1p-in-profile

Context

config>qos>network>egress>fc

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

The command enables the context to mark on an egress the in and out of profile status through a specific dot1p combination (similar to DEI option). 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-namethat 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, this command has no effect.

The no form of the command reverts to the default in-profile dot1p-priority setting for policy-id 1.

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-value, the previous FC and enqueuing priority is completely overridden by the new parameters or defined to be inherited when a FC or enqueuing priority parameter is missing. A maximum of eight dot1p rules are allowed on a single policy.

Values

0 to 7

dot1p-out-profile
Syntax

dot1p-out-profile dot1p-priority

no dot1p-out-profile

Context

config>qos>network>egress>fc

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

The command enables the context to mark on an egress the in and out of profile status via a specific dot1p combination (similar to DEI option). 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-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, this command has no effect.

The no form of this command reverts to the default out-profile dot1p-priority setting for policy-id 1.

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-value, the previous FC and enqueuing priority is completely overridden by the new parameters or defined to be inherited when a FC or enqueuing priority parameter is missing. A maximum of eight dot1p rules are allowed on a single policy.

Values

0 to 7

dscp-in-profile
Syntax

dscp-in-profile dscp-name

no dscp-in-profile

Context

config>qos>network>egress>fc

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command specifies the in-profile DSCP name for the FC. When marking is set, the corresponding DSCP value is used to mark all IP packets with in-profile status, on the egress of this FC queue.

When multiple DSCP names are associated with the FC 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 setting for policy-id 1.

Parameters
dscp-name

Specifies a system-defined or a 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

Supported on all 7210 SAS platforms as described in this document

Description

This command specifies the out-of-profile DSCP name for the FC. When marking is set, the corresponding DSCP value is used to mark all IP packets with out-of-profile status, on the egress of this FC queue.

When multiple DSCP names are associated with the FC 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 setting for policy-id 1.

Parameters
dscp-name

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

Show commands

network
Syntax

network [policy-id] [detail]

Context

show>qos

Platforms

Supported on all 7210 SAS platforms as described in this document

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 dot1p bit mappings and network policy interface associations.

Output

The following outputs are examples of network policy information, and Output fields: QoS network displays the output fields:

Sample output for 7210 SAS-D
*A:SN12345678# show qos network 1        
===============================================================================
QoS Network Policy
===============================================================================
-------------------------------------------------------------------------------
Network Policy (1)
-------------------------------------------------------------------------------
Policy-id      : 1                            Remark       : True              
Forward Class  : be                           Profile      : Out               
Attach Mode    : l2                           Config Mode  : l2                
Scope          : Template                                                      
Description    : Default network QoS policy.
-------------------------------------------------------------------------------
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.
-------------------------------------------------------------------------------
Port Attachments
-------------------------------------------------------------------------------
Port-id : 1/1/24 
===============================================================================
*A:SN12345678# 


*A:dut-g# show qos network 1 detail 
===============================================================================
QoS Network Policy
===============================================================================
-------------------------------------------------------------------------------
Network Policy (1)
-------------------------------------------------------------------------------
Policy-id      : 1                            Remark       : True              
Forward Class  : be                           Profile      : Out               
Attach Mode    : l2                           Config Mode  : l2                
Scope          : Template                                                      
Description    : Default network QoS policy.
-------------------------------------------------------------------------------
Meter Mode   CIR Admin   CIR Rule   PIR Admin   PIR Rule    CBS       MBS
-------------------------------------------------------------------------------
1     TrTcm_CA  0         closest       max       closest   32        128    
9     TrTcm_CA  0         closest       max       closest   32        128    
 
-------------------------------------------------------------------------------
FC                  UCastM         MCastM         
-------------------------------------------------------------------------------
No FC-Map Entries Found.
-------------------------------------------------------------------------------
Dot1p 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     
 
-------------------------------------------------------------------------------
Egress Forwarding Class Queuing
-------------------------------------------------------------------------------
FC Value       : 0                            FC Name      : be                
- Dot1p Mapping
Out-of-Profile : 0                            In-Profile   : 0                 
 
FC Value       : 1                            FC Name      : l2                
- Dot1p Mapping
Out-of-Profile : 1                            In-Profile   : 1                 
 
FC Value       : 2                            FC Name      : af                
- Dot1p Mapping
Out-of-Profile : 2                            In-Profile   : 3                 
 
FC Value       : 3                            FC Name      : l1                
- Dot1p Mapping
Out-of-Profile : 2                            In-Profile   : 3                 
 
FC Value       : 4                            FC Name      : h2                
- Dot1p Mapping
Out-of-Profile : 4                            In-Profile   : 4                 
 
FC Value       : 5                            FC Name      : ef                
- Dot1p Mapping
Out-of-Profile : 5                            In-Profile   : 5                 
 
FC Value       : 6                            FC Name      : h1                
- Dot1p Mapping
Out-of-Profile : 6                            In-Profile   : 6                 
 
FC Value       : 7                            FC Name      : nc                
- Dot1p Mapping
Out-of-Profile : 7                            In-Profile   : 7                 
-------------------------------------------------------------------------------
Port Attachments
-------------------------------------------------------------------------------
Port-id : 1/1/24                                                               
===============================================================================
*A:dut-g# 
Sample output for 7210 SAS-D (detail)

*A:K-SASD>config>qos# show qos network 
Policy-id  Remark     LerUseDscp     Description
-------------------------------------------------------------------------------
1          False  False      Default network QoS policy.
19         True   False      Description for Network Policy id # 19
100        True   False      
200        True   False      
300        True   False      
-------------------------------------------------------------------------------

*A:K-SASD>config>qos# show qos network 1 detail 

===============================================================================
QoS Network Policy
===============================================================================
-------------------------------------------------------------------------------
Network Policy (1)
-------------------------------------------------------------------------------
Policy-id      : 1                            
Egr Remark     : False                        
Forward Class  : be                           Profile      : Out
Scope          : Template                     Policy Type  : port
Accounting     : packet-based                 
Description    : Default network QoS policy.

-------------------------------------------------------------------------------
DSCP (Egress)                           Forwarding Class                Profile
-------------------------------------------------------------------------------
No Matching Entries

 
-------------------------------------------------------------------------------
Prec (Egress)                           Forwarding Class                Profile
-------------------------------------------------------------------------------
No Matching Entries

 
-------------------------------------------------------------------------------
Dot1p 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 Admin MBS Admin
               CIR Oper             PIR Oper                CBS Oper  MBS Oper
-------------------------------------------------------------------------------
1     TrTcm1_CA   0         closest       max       closest   def       def
                  0                       max                 def       def
9     TrTcm1_CA   0         closest       max       closest   def       def
                  0                       max                 def       def
                                      
-------------------------------------------------------------------------------
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

-------------------------------------------------------------------------------

-------------------------------------------------------------------------------
Port Attachments                      
-------------------------------------------------------------------------------
Port-id : 1/1/10

===============================================================================

Table 4. Output fields: QoS network

Label

Description

Policy-Id

Displays the ID that uniquely identifies the policy.

Remark

True — Remarking is enabled.

False — Remarking is disabled.

Description

Displays a text string that helps identify the policy’s 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.Specifies the dot1p marking for the packets which 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.Specifies the dot1p 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

dot1p Bit Mapping:

Out-of-Profile

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

In-Profile

Displays the dot1p value used for in-profile traffic

Port Attachment

Port-Id

Specifies the physical port identifier that associates the interface