Service ingress QoS policies

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

Overview of service ingress policy

There is one default service ingress policy. The default policy allocates a single queue and maps all traffic to the ‟be” (best-effort) FC. The default policies can be copied and modified but they cannot be deleted. The default policies are identified as policy ID 1. The default policies are applied to the appropriate interface, by default. For example, the default SAP-ingress policy is applied to access ingress SAPs. You must explicitly associate other QoS policies. For information about the tasks and commands necessary to access the command line interface and to configure and maintain your 7210 SAS devices, see the ‟CLI Usage” chapter in the 7210 SAS-D, Dxp, K 2F1C2T, K 2F6C4T, K 3SFP+ 8C Basic System Configuration Guide.

In a service ingress QoS policy, a user can define up to eight queues or 16 policers/meters per policy, with up to two queues or two meters per FC.

For VPLS, the following types of forwarding are supported:

  • unicast

  • multicast

  • broadcast

  • unknown

Multicast, broadcast, and unknown types are flooded to all destinations within the service while the unicast forwarding type is handled in a point-to-point manner within the service. All these traffic types use the same queue or meter (in other words, a separate queue or meter for multicast, broadcast, and unknown unicast traffic types cannot be defined).

Unicast and multipoint traffic can be defined to use the same queue or meter or different queues or meter per FC. In other words, eight queues and 16 policers are shared by unicast and multicast traffic types and if a user allocates a dedicated multicast queue for BUM traffic, the number of queues available for unicast traffic reduces. Similarly, up to 16 meters can be shared by unicast and multicast traffic types.

Configuration guidelines for SAP-ingress policy

The configuration guidelines for SAP ingress policies are the following:

  • The option is available to configure a smaller number of ingress queues or ingress policers per SAP.

  • On the 7210 SAS-K 2F1C2T and 7210 SAS-K 2F6C4T, hardware queues are allocated in groups of two, and on the 7210 SAS-K 3SFP+ 8C, hardware queues are allocated in groups of four; these grouped queues are reserved for use by the SAP even if the user specifies an odd value. The 7210 SAS-K 2F1C2T and 7210 SAS-K 2F6C4T support two, four, six, or eight queues per SAP. The 7210 SAS-K 3SFP+ 8C supports four or eight queues per SAP.

  • FC-to-queue map can be defined; this allows the user to assign the packets classified into a particular FC to any one of the queues configured for the SAP.

  • The option is available to use up to two queues per FC, with one queue for unicast traffic and one queue for BUM traffic, with a maximum of eight queues per access SAP. This option can be used with multipoint services for example, VPLS service. BUM traffic shares a single queue per FC; therefore it is not possible to use individual queue for each of broadcast, unknown-unicast, and multicast traffic. It is possible to define the same queue for unicast and BUM traffic. For example, users can assign two queues per FC, such that unicast traffic uses one of the queues and the BUM traffic uses the other queue. This allows users to have four FCs per SAP with two queues per FC; or the user can have seven FCs per SAP with one queue per FC and the eighth queue being shared by BUM traffic of all the FCs; or a mix and match is allowed. If a multicast queue is not assigned to an FC explicitly, it uses queue 1 (the default queue of the policy).

  • The queue parameters such as queue shaper rate (CIR/PIR), CBS and MBS, queue priority, and weight can be defined. The assigned priority and weight are used to determine the priority and weight of the queue in both the CIR and PIR scheduling loop.

  • Allow configuration of WRED slopes (per queue) – high-slope and low-slope. Depending on the queue mode and the profile assigned to the packet on SAP ingress classification, one of the configured WRED slopes is used to evaluate if a buffer can be allocated to the packet. In-profile packets use the high-slope and out-of-profile packets use the low-slope.

  • Supports Strict priority (SP) scheduling and Weighted-Fair Queuing (WFQ) scheduling for SAP ingress queues. For more information about service ingress scheduling, see the Schedulers.

  • The option is available to use up to two policers per FC, with one policer for unicast traffic and one for BUM traffic, with a maximum of up to 16 policers per access SAP. This option can be used with multipoint services for example, VPLS service. BUM traffic shares a single meter per FC; therefore it is not possible to use individual meter for each of broadcast, unknown-unicast, and multicast traffic. It is possible to define the same meter for unicast and BUM traffic. For example, users can assign two meters per FC, such that unicast traffic uses one meter and the BUM traffic uses the other meter. This allows users to have eight FCs per SAP with two meters per FC, or users can have eight FCs per SAP with one meter per FC and the eighth meter being shared by BUM traffic of all the FCs; or a mix and match is allowed. If a multicast meter is not assigned to an FC explicitly, it uses queue 1 (the default queue of the policy).

  • The option is available to use a queue or a meter per FC, with up to two queues per FC or two meters per FC or a queue and a meter per FC for a maximum of up to eight queues per access SAP and 16 meters/policers per access SAP. It is allowed to configure queue for unicast traffic and meter for BUM traffic or the other way around. This option can be used with multipoint services for example, VPLS service. BUM traffic shares a single meter or queue per FC; therefore it is not possible to use individual meter or an individual queue for each of broadcast, unknown-unicast, and multicast traffic. If a multicast meter is not assigned to an FC explicitly, it uses queue 1 (the default queue of the policy).

  • The meter parameters such as meter rate (CIR/PIR), CBS and MBS, and meter mode (srTCM, trTCM) can be defined.

  • If both IP criteria and MAC criteria are configured in SAP ingress QoS classification then they need resources from two different slices. In other words, the MAC and IP criteria entries cannot be located in the same slice. If resources are not found in two different slices, then the association of the policy fails.

Resource allocation for service ingress QoS classification policy

The available global pool of ingress internal CAM hardware resources can be allocated as per user needs for use with different features such as SAP ingress QoS policy, ingress ACLs, and so on. SAP ingress QoS can be allocated classification for use from this pool. Resources can be allocated for SAP ingress QoS policy classification IPv4, IPv6, and MAC match criteria, based on the operator needs. Users can modify the resources allocated to scale the number of entries available per match criteria or scale the number of SAPs. The resources from the global ingress internal CAM pool are allocated in slices with a fixed number of entries.

The number of slices to be allotted for a SAP ingress QoS policy is specified using the config system resource-profile ingress-internal-tcam qos-sap-ingress-resource CLI command.

The user can specify a limit for the amount of resources required for SAP ingress QoS policies and also has the option to limit the amount of resources used per match criteria supported for SAP ingress QoS policies. A specific slice can be used for MAC criteria, IP criteria, and IPv6 criteria.

Before associating SAP-ingress policy match criteria with a SAP, resources must be allocated. Until resources are allocated for use, attempts to associate a policy with a SAP fail. When the user allocates resources for use by SAP ingress QoS policies using the config system resource-profile ingress-internal-tcam qos-sap-ingress-resource CLI command, the system allocates resources in slices of 510 entries (192 entries for the 7210 SAS-K 3SFP+ 8C).

The above resources set the maximum limit on the resources available for use by all SAP ingress policies in use simultaneously on the system. The software manages the resource slices allocated to the SAP ingress QoS policy pool and allocates the entries in the slices when a SAP ingress QoS policy is associated with a SAP. The software allocates the resources required by a SAP from the slices depending on whether the SAP-ingress policy uses IP criteria, IPv6 criteria, or MAC criteria, and the number of entries configured in the SAP-ingress policy.

When the user allocates slices of resources using the config system resource-profile ingress-internal-tcam qos-sap-ingress-resource CLI command, the resources are used only for classification entries configured under IPv4 criteria or MAC criteria.

If the user needs to use IPv6 criteria, resources must be allocated using the config system resource-profile ingress-internal-tcam qos-sap-ingress-resource mac-ipv4-ipv6-128-match-enable CLI command. The resources allocated using this command are used for classification entries configured under IPv6 criteria, IPv4 criteria, or MAC criteria. Each IPv6, IPv4, or MAC classification entry consumes two resources from this pool, reducing the number of classification entries that can be accommodated in a single slice to 256 (96 entries for the 7210 SAS-K 3SFP+ 8C.) The user can choose to allocate all the slices allocated for SAP ingress QoS classification for IPv6 criteria or allocate only a portion of it.

The tools dump system-resources CLI command displays the current usage and availability of the resources. One or more entries per slice are reserved for system use.

Resource allocation for SAP ingress meters

The FC ingress meter and SAP ingress aggregate meter allocate resources for the common meter resource pool. A single FC ingress meter requires one entry from the pool when the policy is associated with the SAP and a single SAP ingress aggregate meter uses a single entry from the pool when the command to enable SAP aggregate meter functionality is executed under the context of the SAP. An increase in FC ingress meter reduces the number of meters available for SAP ingress aggregate meter. The reverse is also true.

The tools dump system-resources CLI command can be used to display the current utilization of the ingress meter resource pool.

Default SAP-ingress policy

The default policy 1 maps all traffic to default FC ‟be” and maps FC ‟be” to queue 1. Queue 1 is configured with CIR 0 and PIR max.

Configuration output of a default SAP-ingress policy
A:SAH01-071>config>qos>sap-ingress# info detail 
----------------------------------------------
            policy-name "default"
            description "Default SAP ingress QoS policy."
            no ip-mac-match
            scope template
            queue 1 create
                adaptation-rule cir closest pir closest
                rate cir 0 pir max
                slope-policy "default"
                mbs 60
                cbs 10
                priority 1
                weight 1
            exit
            fc "af" create
                queue 1
                multicast-queue 1
                no use-dei
            exit
            fc "be" create
                queue 1
                multicast-queue 1
                no use-dei            
            exit
            fc "ef" create
                queue 1
                multicast-queue 1
                no use-dei
            exit
            fc "h1" create
                queue 1
                multicast-queue 1
                no use-dei
            exit
            fc "h2" create
                queue 1
                multicast-queue 1
                no use-dei
            exit
            fc "l1" create
                queue 1
                multicast-queue 1
                no use-dei
            exit
            fc "l2" create
                queue 1               
                multicast-queue 1
                no use-dei
            exit
            fc "nc" create
                queue 1
                multicast-queue 1
                no use-dei
            exit
            default-fc "be"
            no dot1p-classification
            no dscp-classification

The following table lists the SAP-ingress policy defaults.

Table 1. SAP-ingress policy defaults

Field

Default

description

‟Default SAP-ingress QoS policy.”

scope

template

queue

1

adaptation-rule

cir closest pir closest

rate

pir = max, cir= 0

cbs

10KBytes - default

mbs

60KBytes - default

priority

1

weight

1

default-fc

be

Use of index file by SAP QoS ingress policy

The 7210 SAS uses an index file to store the map that indicates the QoS resource allocation to the SAPs. This file is used to ensure that all the SAPs that were created successfully before a reboot can be recreated during a reboot. Without an index file, it is possible that all the SAPs that were configured successfully may fail on a reboot after saving the configuration file. The index file is stored in the flash. During a reboot, if the file is found, the system allocates resources as per the stored map. If the file is not found, the system implements a best-fit algorithm and tries to allocate resources for all the SAPs on a first-come-first-served basis. When the index file is not present it is possible that the saved configuration did not execute successfully after the reboot.

Note:

The following restrictions apply:

  • There is no guarantee that resources will be allocated to all SAPs.

  • The index file used for QoS maps is different from the one used for storing interface indexes.

Basic configurations

A basic service ingress QoS policy must conform to the following:

  • have a unique service ingress QoS policy ID

  • have a QoS policy scope of template or exclusive

  • have at least one default unicast FC queue

  • (optionally) use multipoint FC queue

  • (optionally) use unicast meter and BUM traffic

Configuring and applying QoS policies is optional. If no QoS policy is explicitly applied to a SAP, a default QoS policy is applied.

Service ingress QoS policies

To create a service ingress policy, perform the following.

  1. Define a policy ID value.
    The system does not dynamically assign a value.
  2. Define a description that provides a brief overview of policy features.
  3. Specify a default FC for the policy.

    All packets received on an ingress SAP using this ingress QoS policy are classified to the default FC.

  4. Define FC parameters by performing the following.
    • Modify the unicast/queue default value to override the default unicast forwarding type queue mapping for fc fc-name.

    • Modify the multicast or queue default value to override the default multicast forwarding type queue mapping for fc fc-name.

    • Associate a meter for fc fc-name, if required, for both unicast and BUM traffic types.

  5. Specify the following classification criteria - IPv4/IPv6 or MAC criteria or both IP and MAC criteria.

    You can define IPv4/IPv6, MAC-based and MAC and IP based SAP ingress policies to select the appropriate ingress meter and corresponding FC for matched traffic.

  6. Create a SAP-ingress policy using a template scope.

    The scope can be modified to exclusive for a special one-time use policy. Otherwise, the template scope enables the policy to be applied to multiple SAPs.

    The following is a sample service ingress policy configuration output.

    A:ALA-7>config>qos>sap-ingress# info
    ----------------------------------------------
    ...
            sap-ingress 100 create
                description "Used on VPN sap"
    ...
    ----------------------------------------------
    A:ALA-7>config>qos>sap-ingress#

Service ingress QoS queues

To create service ingress queue parameters, perform the following.

  1. Define a new queue ID value.

    The system does not dynamically assign a value.

  2. Configure queue parameters. Rate, slope-policy, CBS, MBS, priority, and weight.

    The following is a sample ingress queue configuration output.

    A:ALA-7>config>qos# info
    echo "QoS Policy Configuration"
    #--------------------------------------------------
            sap-ingress 1 create
                policy-name "default"
                description "Default SAP ingress QoS policy."
                no ip-mac-match
                scope template
                queue 1 create
                  adaptation-rule cir closest pir closest
                  rate cir 0 pir max
                  slope-policy "default"
                  mbs 60
                  cbs 10
                  priority 1
                  weight 1
                exit
    .........
    #------------------------------------------
    A:ALA-7>config>qos#

Service ingress QoS meters

The following are sample service ingress QoS meters.

A:ALA-7>config>qos#
echo "QoS Policy Configuration"
#--------------------------------------------------
sap-ingress 1 create
policy-name "test"
description "SAP ingress QoS policy."
no ip-mac-match
scope template
meter 1 create
adaptation-rule cir closest pir closest
rate cir 0 pir max
mbs 60
cbs 10
exit
.........
#------------------------------------------
A:ALA-7>config>qos#

SAP ingress FC configuration

The following is a sample SAP ingress FC configuration output with unicast queues and multicast queues.

*A:dut-i>config>qos>sap-ingress$ info
----------------------------------------------
....
queue 1 create
exit
queue 2 create
rate cir 1000 pir 2000
exit
fc "af" create
queue 1
multicast-queue 2
exit
fc "nc" create
queue 2
multicast-queue 1
exit
.....
----------------------------------------------
config>qos>sap-ingress$ info

The following is a sample SAP ingress FC configuration output with a mix of unicast queues and meters, and a mix of multicast queues and meters.

*A:dut-i>config>qos>sap-ingress$ info
----------------------------------------------
....
queue 1 create
exit
queue 2 create
rate cir 1000 pir 2000
exit
meter 1 create
rate cir 10000 pir 10000
exit
meter 2 create
rate cir 1000 pir 2000
exit
fc "h2" create
meter 1
multicast-meter 2
exit
fc "nc" create
meter1
multicast-meter 2
exit
fc "af" create
queue 1
multicast-queue 2
exit
fc "be" create
queue 2
multicast-queue 1
exit
.....
----------------------------------------------
config>qos>sap-ingress$ info

Service ingress dot1p and IP DSCP criteria

The following is a sample configuration output of dot1p classification policy and IP DSCP classification policy used for ingress classification and its association with SAP-ingress policy.

A:ALA-7>config>qos>dot1p-classification# info
#-------------------------------------------------------------
.....
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
......

#--------------------------------------------------

A:ALA-7>config>qos>sap-ingress# info
#--------------------------------------------------
......

dot1p-classification  1

.......
#--------------------------------------------------
A:ALA-7>

Service ingress IP match criteria

When specifying SAP ingress match criteria, only one match criteria type can be configured in the SAP ingress QoS policy.

Ingress IP criteria configuration output

A:ALA-7>config>qos# info
...
#------------------------------------------
echo "QoS Policy Configuration"
#------------------------------------------
...
             sap-ingress 100 create
...
             ip-criteria
             entry 10 create
             description "Entry 10-FC-AF"
             match dscp af12
             exit
             action fc af
             exit
             entry 20 create
             description "Entry 20-FC-BE"
             match dscp be
             exit
             no action
             exit
             exit
exit
..
#------------------------------------------
A:ALA-7>config>qos#

Service ingress MAC match criteria

To configure service ingress policy MAC criteria, perform the following:

  1. Define a new entry ID value.

    Entries must be explicitly created; the system does not dynamically assign entries or a value.

  2. Associate the FC with a specific MAC criteria entry ID.
  3. Define a description.

    The description provides a brief overview of policy features.

    The following is a sample ingress MAC criteria configuration output.

    A:ALA-7>config>qos# info
    ...
    #------------------------------------------
    echo "QoS Policy Configuration"
    #------------------------------------------
    ...
            sap-ingress 101 create
    ...
                mac-criteria
                    entry 10 create
                        description "Entry10"
                        match
                            dst-mac 04-67-ff-00-00-01 ff-ff-ff-ff-ff-ff
                            dot1p 7 7
                        exit
                        action fc be
                    exit
                exit
            exit
    #------------------------------------------
    A:ALA-7>config>qos# 
    

Applying service ingress policies

SAP ingress QoS policies are supported only on access SAPs.

Epipe service

The following sample configuration output shows an Epipe service configuration with SAP-ingress policy 100 applied to the SAP.

A:ALA-7>config>service# info
----------------------------------------------
        epipe 6 customer 6 vpn 6 create
            description "Epipe service to west coast"
            sap 1/1/10:10 create
                exit
                ingress
                    qos 100
                exit
            exit
        exit
----------------------------------------------
A:ALA-7>config>service#

VPLS

The following sample configuration output shows a VPLS service configuration with SAP-ingress policy 100.

A:ALA-7>config>service# info
----------------------------------------------
        vpls 700 customer 7 vpn 700 create
            description "test"
            stp
                shutdown
            exit
            sap 1/1/9:10 create
                ingress
                    qos 100
                exit
            exit
        exit
----------------------------------------------
A:ALA-7>config>service#

IES

The following sample configuration output shows an IES service configuration.

A:ALA-7>config>service# info
----------------------------------------------
...
ies 1 customer 1 create
 interface "to-c1" create
  address 10.1.0.1/24
   sap 1/1/10:100 create
    ingress
     qos 100
    exit
   exit
  exit
  no shutdown
 exit
...
----------------------------------------------

Service management tasks

This section describes service management tasks.

Deleting QoS policies

Every service SAP is associated, by default, with the appropriate ingress policy (policy-id 1). You can replace the default policy with a customer-configured policy, but you cannot entirely remove the policy from the SAP configuration. When you remove a non-default service ingress policy, the association reverts to the default policy-id 1.

A QoS policy cannot be deleted until it is removed from all SAPs where it is applied.

A:ALA-7>config>qos# no sap-ingress 100
MINOR: CLI SAP ingress policy "100" cannot be removed because it is in use.
A:ALA-7>config>qos#

Removing a QoS policy from service SAPs

The following Epipe service output sample shows that the SAP service ingress reverts to policy-id 1 when the non-default policies are removed from the configuration.

A:ALA-104>config>service>epipe# info detail
----------------------------------------------
description "Distributed Epipe service to west coast"
                no tod-suite
                dot1ag
                exit
                ingress
                    qos 1 
                    no filter
                exit
                egress
                    no filter
                exit
                no collect-stats
                no accounting-policy
                no shutdown           
----------------------------------------------
A:ALA-7>config>service>epipe#

Copying and overwriting QoS policies

You can copy an existing service ingress policy, rename it with 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 {sap-ingress} source-policy-id dest-policy-id [overwrite]
*A:ALU-7210>config>qos# info
#--------------------------------------------------
echo "QoS Policy Configuration"
#--------------------------------------------------
        sap-ingress 100 create
            description "Used on VPN sap"
            meter 1 create
            exit
            meter 2 multipoint create
            exit
            meter 10 create
                rate cir 11000
            exit
            meter 11 multipoint create
            exit
        exit
        sap-ingress 101 create
            description "Used on VPN sap"
            meter 1 create
            exit
            meter 2 multipoint create
            exit
            meter 10 create
                rate cir 11000
            exit
            meter 11 multipoint create
            exit
        exit
        sap-ingress 200 create
            description "Used on VPN sap"
            meter 1 create
            exit
            meter 2 multipoint create

Removing a policy from the QoS configuration

Use the following syntax to remove a policy from the QoS configuration.

config>qos# no sap-ingress policy-id
config>qos# no sap-ingress 100

Editing QoS policies

You can change existing QoS policies and entries. The changes are applied immediately to all services where this policy is applied. To prevent configuration errors, copy the policy to a work area, make the edits, and then overwrite the original policy.

Service SAP QoS policy command reference

Command hierarchies

Service ingress QoS policy commands

    - config 
        - qos
            - [no] sap-ingress policy-id [create]
                - default-fc fc [profile {in |out | use-dei}] 
                - no default-fc
                - description description-string
                - no description
                - dot1p-classification policy-id
                - no dot1p-classification
                - dscp-classification policy-id
                - no dscp-classification
                - [no] fc fc-name [create]
                    - multicast-meter meter-id
                    - no multicast-meter
                    - no meter 
                    - meter meter-id 
                    - multicast-queue queue-id
                    - no multicast-queue
                    - no queue 
                    - queue queue-id 
                    - no use-dei
                    - use-dei
                - [no] ip-criteria 
                    - [no] entry entry-id [create]
                        - action [fc fc-name] [profile {in | out | use-dei}] 
                        - no action
                        - description description-string
                        - no description
                        - match [protocol protocol-id]
                        - no match
                            - dscp dscp-name
                            - no dscp
                            - dst-ip {ip-address/mask | ip-address netmask} 
                            - no dst-ip
                            - dst-port fc {eq} dst-port-number
                            - no dst-port
                            - fragment {true | false}
                            - no fragment
                            - src-ip {ip-address/mask | ip-address netmask} 
                            - no src-ip
                            - src-port {eq} src-port-number
                            - no src-port
                    - dscp [old-entry-id new-entry-id]
                - [no] ipv6-criteria 
                    - [no] entry entry-id [create]
                        - action [fc fc-name] [profile {in | out | use-dei}]
                        - no action
                        - description description-string
                        - no description
                        - match [next-header next-header]
                        - no match
                            - dscp dscp-name
                            - no dscp
                            - dst-ip {ip-address/mask | ip-address netmask} 
                            - no dst-ip
                            - dst-port fc {eq} dst-port-number
                            - no dst-port
                            - fragment {true | false}
                            - no fragment
                            - src-ip {ip-address/mask | ip-address netmask} 
                            - no src-ip
                            - src-port {eq} src-port-number
                            - no src-port
                    - dscp [old-entry-id new-entry-id]
                - [no] mac-criteria 
                    - [no] entry entry-id [create]
                        - action [fc fc-name] [profile {in | out | use-dei}]
                        - no action
                        - description description-string
                        - no description
                        - [no] match
                            - dst-mac ieee-address [ieee-address-mask]
                            - no dst-mac
                            - etype 0x0600..0xffff
                            - no etype
                            - 0inner-dot1p dot1p-value [dot1p-mask]
                            - no 0inner-dot1p
                            - inner-tag value [vid-mask]
                            - no inner-tag
                            - no outer-dot1p
                            - outer-dot1p dot1p-value [dot1p-mask]
                            - no outer-tag
                            - outer-tag value [vid-mask]
                            - src-mac ieee-address [ieee-address-mask]
                            - no src-mac
                    - dscp old-entry-id new-entry-id
                - queue queue-id
                - no queue 
                    - [no] adaptation-rule [pir adaptation-rule] [cir adaptation-rule]
                    - cbs size-in-kbyte
                    - no cbs
                    - mbs size in kbytes
                    - no mbs
                    - no priority
                    - priority level
                    - no rate
                    - rate cir cir-rate-in-kbps [pir pir-rate-in-kbps]
                    - no slope-policy
                    - slope-policy name
                    - no weight
                    - weight weight
                - no meter meter-id
                    - [no] adaptation-rule [pir adaptation-rule] [cir adaptation-rule]
                    - cbs size-in-kbyte
                    - no cbs
                    - mbs size in kbytes
                    - no mbs
                    - mode mode
                    - no mode
                    - rate cir cir-rate-in-kbps [pir pir-rate-in-kbps]
                    - no rate
                - scope {exclusive | template}
                - no scope

Operational commands

    - config
        - qos
            - copy sap-ingress src-pol dst-pol [overwrite]

Command descriptions

Configuration commands

Note:

The 7210 SAS QoS capability varies across platforms. In the command descriptions, the term queue/meter is used, and depending on the platform capabilities, either one or both terms can be used.

Generic commands
description
Syntax

description description-string

no description

Context

config>qos>sap-ingress

config>qos>sap-ingress>ip-criteria>entry

config>qos>sap-ingress>mac-criteria>entry

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 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 sap-ingress src-pol dst-pol [overwrite]

copy dot1p-classification src-pol dst-pol [overwrite]

copy dscp-classification 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.

The copy command is a configuration level maintenance tool used to create new policies using existing policies. It also allows bulk modifications to an existing policy with the use of the overwrite keyword.

Parameters
sap-ingress src-pol dst-pol

Specifies that the source policy ID and the destination policy ID are SAP ingress policy IDs. Specify the source policy ID that the copy command will attempt to copy from and specify the destination policy ID to which the command will copy a duplicate of the policy.

Values

1 to 65535

overwrite

Specifies to replace the existing destination policy. 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.

dot1p-classification src-pol-dst-pol

Specifies that the source policy ID and the destination policy ID are dot1p classification policy IDs. Specify the source policy ID that the copy command will attempt to copy from and specify the destination policy ID to which the command will copy a duplicate of the policy.

Values

1 to 65535

dscp -classification src-pol-dst-pol

Specifies that the source policy ID and the destination policy ID are IP DSCP classification policy IDs. Specify the source policy ID that the copy command will attempt to copy from and specify the destination policy ID to which the command will copy a duplicate of the policy.

Values

1 to 65535

dscp
Syntax

dscp dscp-name

no dscp

Context

config>qos>sap-ingress>ip-criteria>entry>match

config>qos>sap-ingress>ipv6-criteria>entry>match

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command configures a DiffServ Code Point (DSCP) code point to be used as a network ingress QOS policy match criterion.

The no form of this command removes the DSCP match criterion.

Parameters
dscp-name

Specifies a dscp name that has been previously mapped to a value using the dscp-name command. The DiffServ code point can only be specified by its name.

Values

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

dst-ip
Syntax

dst-ip {ip-address/mask | ip-address netmask}

dst-ip {ipv6-address/prefix-length}

no dst-ip

Context

config>qos>sap-ingress>ip-criteria>entry>match

config>qos>sap-ingress>ipv6-criteria>entry>match

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command configures a destination address range to be used as a network ingress QoS policy match criterion.

To match on the destination address, specify the address and its associated mask, for example, 10.1.0.0/16. The conventional notation of 10.1.0.0 255.255.0.0 can be used only for IPv4.

The no form of this command removes the destination IP address match criterion.

Parameters
ip-address

Specifies the IP address of the destination IP or IPv6 interface. This address must be unique within the subnet and specified in dotted decimal notation.

Values

ipv4-address —

a.b.c.d

ipv6-address —

x:x:x:x:x:x:x:x (eight 16-bit pieces)

x:x:x:x:x:x:d.d.d.d

x — 0 to FFFF (hexadecimal)

d — 0 to 255 (decimal)

dst-port
Syntax

dst-port {eq} dst-port-number

no dst-port

Context

config>qos>sap-ingress

config>qos>sap-ingress>ip-criteria>entry>match

config>qos>sap-ingress>ipv6-criteria>entry>match

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command configures a destination TCP or UDP port number for a network ingress QoS policy match criterion.

The no form of this command removes the destination port match criterion.

Parameters
eq dst-port-number

Specifies the TCP or UDP port number to match, specified as equal to (eq) the destination port value specified as a decimal integer.

Values

1 to 65535 (decimal)

fragment
Syntax

fragment {true | false}

no fragment

Context

config>qos>ingress>ip-criteria>entry>match

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command configures fragmented or non-fragmented IP packets as a network ingress QoS policy match criterion.

The no form of this command removes the match criterion and matches all packets regardless of whether they are fragmented or not.

Parameters
true

Keyword to configure a match on all fragmented IP packets. A match occurs for all packets that have either the MF (more fragment) bit set OR have the Fragment Offset field of the IP header set to a non-zero value.

false

Keyword to configure a match on all non-fragmented IP packets. Non-fragmented IP packets are packets that have the MF bit set to zero and have the Fragment Offset field also set to zero.

src-ip
Syntax

src-ip {ip-address/mask | ip-address ipv4-address-mask}

src-ip {ipv6-address/prefix-length}

no src-ip

Context

config>qos>sap-ingress>ip-criteria>entry>match

config>qos>sap-ingress>ipv6-criteria>entry>match

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command configures a source IPv4 or IPv6 address range to be used as a network ingress QoS policy match criterion.

To match on the source IPv4 or IPv6 address, specify the address and its associated mask, for example, 10.1.0.0/16. The conventional notation of 10.1.0.0 255.255.0.0 can also be used for IPv4.

The no form of this command removes the source IPv4 or IPv6 address match criterion.

Default

no source IP match criterion

Parameters
ip-address

Specifies the source IPv4 address specified in dotted decimal notation.

Values

ipv4-address — a.b.c.d

mask

Specifies the length in bits of the subnet mask.

Values

1 to 32

ipv4-address-mask

Specifies the subnet mask, in dotted decimal notation.

Values

a.b.c.d (dotted quad equivalent of mask length)

ipv6-address

Specifies the IPv6 prefix for the IP match criterion, in hexadecimal digits.

Values

ipv6-address —

x:x:x:x:x:x:x:x (eight 16-bit pieces)

x:x:x:x:x:x:d.d.d.d

x — 0 to FFFF (hexadecimal)

d — 0 to 255 (decimal)

prefix

Specifies the IPv6 prefix length for the ipv6-address, expressed as a decimal integer.

Values

1 to 128

src-port
Syntax

src-port {eq} src-port-number

no src-port

Context

config>qos>sap-ingress>ip-criteria>entry>match

config>qos>sap-ingress>ipv6-criteria>entry>match

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command configures a source TCP or UDP port number for a network ingress QoS policy match criterion.

The no form of this command removes the source port match criterion.

Parameters
eq src-port-number

Specifies the TCP or UDP port number to match specified as equal to (eq) to the source port value, specified as a decimal integer.

Values

1 to 65535

renum
Syntax

renum old-entry-id new-entry-id

Context

config>qos>sap-ingress>ip-criteria

config>qos>sap-ingress>ipv6-criteria

config>qos>sap-ingress>mac-criteria

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command renumbers existing QoS policy criteria entries to properly sequence policy entries.

This is required in some cases because the 7210 SAS exits when the first match is found and executes the actions in accordance with the accompanying action command. This requires that entries be sequenced correctly from most to least explicit.

Parameters
old-entry-id

Specifies the entry number of an existing entry.

Values

1 to 64

new-entry-id

Specifies the new entry number to be assigned to the old entry.

Values

1 to 64

Service ingress QoS policy commands

sap-ingress
Syntax

[no] sap-ingress policy-id [create]

Context

config>qos

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command creates or edits the ingress policy. The ingress policy defines the Service Level Agreement (SLA) enforcement that service packets receive as they ingress a SAP; the SAP can be configured on an access port or hybrid port. SLA enforcement is accomplished through the definition of meters or queues (depends on the support available on a platform) that have Forwarding Class (FC), Committed Information Rate (CIR), Peak Information Rate (PIR), Committed Burst Size (CBS), and Maximum Burst Size (MBS) characteristics. The simplest policy defines a single queue/meter that all ingress traffic flows through. Complex policies have multiple meters/queues combined with classification entries that indicate which meter/queue a packet flows through.

Policies in effect are templates that can be applied to multiple services as long as the scope of the policy is template. Meters defined in the policy are not instantiated until a policy is applied to a service SAP.

Depending on the support available on different 7210 SAS platforms, SAP ingress policies can be defined with either dot1p as the match criteria or IP DSCP as the match criteria or IP headers as the match criteria or MAC headers or both as the match criteria. On the 7210 SAS, the user has an option to use dot1p, IP DSCP, IPv4/IPv6 criteria and MAC criteria.

Only one service ingress policy can be provisioned. The SAP ingress policy with policy-id 1 is a system-defined policy applied to services when no other policy is explicitly specified. The system SAP ingress policy can be modified but not deleted. The no sap-ingress command restores the factory default settings when used on policy-id 1. See Default SAP-ingress policy for more information about the default SAP Ingress policy for different platforms.

Any changes made to the existing policy, using any of the sub-commands are applied immediately to all services where this policy is applied. For this reason, when many changes are required on a policy, it is 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.

Note:

  • A SAP ingress policy with multiple criteria can be associated with the SAP. The system defines a match-order to match against the classification rules specified in the policy. Please see the QoS overview section to know more about the match order.

  • Before using IPv4, IPv6 and MAC match criteria, resources must be allocated using the CLI command config>system>resource-profile>ingress-internal-tcam>qos-sap-ingress-resource. See the 7210 SAS-D, Dxp, K 2F1C2T, K 2F6C4T, K 3SFP+ 8C Basic System Configuration Guide for information about resource allocation. See Service ingress QoS policies for more information about this CLI command.

  • Service ingress only queues with shapers are supported.

The no form of this command deletes the SAP ingress policy. A policy cannot be deleted until it is removed from all services where it is applied. The system default SAP ingress policy is a special case; the no command restores the factory defaults to policy ID 1.

Parameters
policy-id

Specifies the policy.

Values

1 to 65535

create

Keyword to create a sap ingress policy.

dot1p-classification
Syntax

dot1p-classification policy-id

no dot1p-classification

Context

config>qos>sap-ingress

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command associates a dot1p classification policy, which contains entries used to map traffic received on a hybrid port or SAP to a forwarding class and profile state, based on the dot1p bits in the packet.

When it is defined in a service ingress QoS policy and associated with an access SAP ingress, a packet received on the SAP is used to match with the dot1p values defined in this policy. If a match is found, the corresponding forwarding class and profile are assigned to the packet.

The no form of this command disables use of dot1p classification policy.

Parameters
policy-id

Specifies the policy.

Values

1 to 65535

dscp-classification
Syntax

dscp-classification

no dscp-classification

Context

config>qos>sap-ingress

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command associates an IP DSCP classification policy, which contains entries used to map traffic received on a SAP to a forwarding class and profile state, based on the IP DSCP bits in the packet.

When it is defined in a service ingress QoS policy and associated with an access SAP ingress, a packet received on the SAP is used to match with the IP DSCP values defined in this policy. If a match is found, the corresponding forwarding class and profile are assigned to the packet.

The no form of this command disables use of DSCP classification policy.

Parameters
policy-id

Specifies the policy ID that uniquely identifies the policy.

Values

1 to 65535

scope
Syntax

scope {exclusive | template}

no scope

Context

config>qos>sap-ingress

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command configures the Service Ingress QoS policy scope as exclusive or template.

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

Default

template

Parameters
exclusive

Specifies that the policy can only be applied to one SAP. If a policy with an exclusive scope is assigned to a second SAP an error message is generated. If the policy is removed from the exclusive SAP, it becomes available for assignment to another exclusive SAP.

template

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

Default QoS policies are configured with template scopes. An error is generated when the template scope parameter to exclusive scope on default policies is modified.

default-fc
Syntax

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

Context

config>qos>sap-ingress

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command configures the default forwarding class for the policy. If an ingress packet does not match a higher priority (more explicit) classification command, the default forwarding class is associated with the packet. Unless overridden by an explicit forwarding class classification rule, all packets received on an ingress SAP using this ingress QoS policy are classified to the default forwarding class.

The default forwarding class is best effort (be). The default-fc settings are displayed in the show configuration and save output regardless of inclusion of the detail keyword.

Default

be

Parameters
fc

Specifies the forwarding class name for the queue/meter. The value for fc must be one of the predefined forwarding classes in the system.

profile {in | out}

Specifies that packets matching the classification entry are explicitly classified to either in-profile or out-of-profile. The remove the profile action for an classification entry, the action command must be re-executed without the profile action defined. The profile assigned by the user is used subsequently to determine the slope to use at the ingress and egress queuing points and is used for egress marking (if enabled).

in

Specifies that any packets matching the classification rule are treated as in-profile. Mutually exclusive to the out parameter following the profile classification action keyword.

out

Specifies that any packets matching the classification rule are treated as out-of-profile. Mutually exclusive to the in parameter following the profile classification action keyword.

use-dei
Syntax

[no] use-dei

Context

config>qos>sap-ingress>fc

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command enables DEI based classification. When enabled, the packet classified to this FC the DEI bit is used to determine the ingress profile for the packet. Packets received with DEI bit set to zero are treated as in-profile and packets with DEI bit set to one are treated as out-of-profile packets.

When DEI based classification is enabled, it overrules the profile values specified in the classification entry used to assign the FC.

The no form of this command disables use of DEI bit for classification of packets.

Default

no use-dei

fc
Syntax

[no] fc fc-name [create]

Context

config>qos>sap-ingress

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

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

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

Parameters
fc-name

Specifies the forwarding class name for the queue. The value of the fc-name must be one of the predefined forwarding classes for the system.

Values

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

create

Keyword to create a forwarding class.

multicast-queue
Syntax

multicast-queue queue-id

no multicast-queue

Context

config>qos>sap-ingress>fc

config>qos>network>fc

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command overrides the default multicast forwarding type queue mapping for fc fc-name. The specified queue ID must exist within the policy as a multipoint queue before the mapping can be made. After the forwarding class mapping is executed, all broadcast, unknown unicast, and multicast (BUM) traffic on a SAP or a access-uplink port using this policy is forwarded using the queue ID.

The no form of this command removes the association of the FC and the queue. When the no form is executed, the BUM traffic uses the default multicast forwarding type queue.

Default

1

Parameters
queue-id

Specifies the queue ID.

Values

1 to 8

ip-criteria
Syntax

[no] ip-criteria

Context

config>qos>sap-ingress

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

Commands in this context create or edit policy entries that specify IP criteria used to match supported fields from the IP packet header, including IP DSCP.

IP criteria-based SAP ingress policies are used to select the forwarding class for matched traffic.

The 7210 SAS implementation exits on the first match found and executes the actions in accordance with the accompanying action command. For this reason entries must be sequenced correctly from most to least explicit.

Note:

Before associating a SAP ingress policy configured to use IPv4 criteria with a SAP, resources must be allocated to it. See the 7210 SAS-D, Dxp, K 2F1C2T, K 2F6C4T, K 3SFP+ 8C Basic System Configuration Guide for more information about this CLI command and resource allocation.

The no form of this command deletes all the entries specified under this node. When IP criteria entries are removed from a SAP ingress policy, the IP criteria is removed from all services where that policy is applied.

ipv6-criteria
Syntax

[no] ipv6-criteria

Context

config>qos>sap-ingress

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

Commands in this context create or edit policy entries that specify IPv6 criteria such as IP quintuple lookup or DiffServ code point.

IPv6 criteria-based SAP ingress policies are used to select the forwarding class for matched traffic.

The 7210 SAS implementation exits on the first match found and execute the actions in accordance with the accompanying action command. For this reason entries must be sequenced correctly from most to least explicit.

Note:

Before associating a SAP ingress policy configured to use IPv6 criteria with a SAP, resources must be allocated to it. See the 7210 SAS-D, Dxp, K 2F1C2T, K 2F6C4T, K 3SFP+ 8C Basic System Configuration Guide for more information about this CLI command and resource allocation.

The no form of this command deletes all the entries specified under this node. When ipv6-criteria entries are removed from a SAP ingress policy, the ipv6-criteria is removed from all services where that policy is applied.

mac-criteria
Syntax

[no] mac-criteria

Context

config>qos>sap-ingress

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

Commands in this context create or edit policy entries that specify MAC criteria.

The MAC criteria-based SAP ingress policies are used to select the forwarding class for matched traffic.

The 7210 SAS implementation exits on the first match found and execute the actions in accordance with the accompanying action command. For this reason entries must be sequenced correctly from most to least explicit.

Note:

Before associating a SAP ingress policy configured to use MAC criteria with a SAP, resources must be allocated to it. See the 7210 SAS-D, Dxp, K 2F1C2T, K 2F6C4T, K 3SFP+ 8C Basic System Configuration Guide for more information about this CLI command and resource allocation.

The no form of this command deletes all the entries specified under this node. When mac-criteria entries are removed from a SAP ingress policy, the mac-criteria is removed from all services where that policy is applied.

queue
Syntax

[no] queue queue-id

Context

config>qos>sap-ingress>fc

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command overrides the default unicast forwarding type queue mapping for fc fc-name. The specified queue ID must exist within the policy as a non-multipoint queue before the mapping can be made. When the forwarding class mapping is executed, all unicast traffic (this includes all traffic, even broadcast and multicast for services) on a SAP or an access-uplink port using this policy is forwarded using the queue ID.

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

Parameters
queue-id

Specifies the queue ID for the queue.

multicast-meter
Syntax

multicast-meter meter-id

no multicast-meter

Context

config>qos>sap-ingress>fc

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command overrides the default multicast forwarding type queue mapping for fc fc-name. The specified meter-id must exist within the policy before the mapping can be made. When the forwarding class mapping is executed, all broadcast, unknown unicast, and multicast (BUM) traffic on an access SAP using this policy is forwarded using the meter ID.

The default multicast forwarding type queue is the default unicast queue (queue 1). In other words, if no multicast meter is assigned to a FC, it uses default queue 1.

The no form of this command removes the association of the FC and the meter. When the no form is executed, the BUM traffic uses the default multicast forwarding type queue (queue 1).

Default

1

Parameters
meter-id

Specifies the meter ID for the meter.

Values

1 to 16

meter
Syntax

[no] meter meter-id

Context

config>qos>sap-ingress>fc

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command overrides the default unicast forwarding type queue mapping for fc fc-name. The specified meter-id must exist within the policy before the mapping can be made. When the forwarding class mapping is executed, all unicast traffic (this includes all traffic, even broadcast and multicast for services) on an access SAP using this policy is forwarded using the meter ID.

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

Parameters
meter-id

Specifies the meter ID for the meter.

Values

1 to 16

Service ingress QoS policy entry commands

action
Syntax

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

no action

Context

config>qos>sap-ingress>ip-criteria>entry

config>qos>sap-ingress>mac-criteria>entry

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This mandatory command associates the forwarding class with specific IP or MAC criteria entry ID. The action command supports setting the forwarding class parameter. Packets that meet all match criteria within the entry have their forwarding class overridden based on the parameters included in the action parameters.

The action command must be executed for the match criteria to be added to the active list of entries.

Each time action is executed on a specific entry ID, the previous entered values for fc fc-name is overridden with the newly defined parameters.

The no form of this command removes the entry from the active entry list. Removing an entry on a policy immediately removes the entry from all SAPs using the policy. All previous parameters for the action is lost.

Default

action specified by the default-fc command

Parameters
fc fc-name

Specifies the name of the forwarding class. The value of fc fc-name must be one of the predefined forwarding classes in the system. Specifying the fc fc-name is required. 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}

Specifies the profile assignment. When specified, packets matching the classification entry are explicitly classified to either in-profile or out-of-profile. The remove the profile action for an classification entry, the action command must be re-executed without the profile action defined. The profile assigned by the user is used subsequently to determine the slope to use at the ingress and egress queuing points and is used for egress marking (if enabled).

in

Specifies that any packets matching the classification rule are treated as in-profile. The in parameter is mutually exclusive to the out parameter following the profile classification action keyword. Either in or out must be specified when the profile keyword is present.

out

Specifies that any packets matching the classification rule are treated as out-of-profile. The out parameter is mutually exclusive to the in parameter following the profile classification action keyword. Either in or out must be specified when the profile keyword is present.

use-dei

Specifies whether DEI must be used to determine the initial profile of the packet.

entry
Syntax

[no] entry entry-id [create]

Context

config>qos>sap-ingress>ip-criteria

config>qos>sap-ingress>mac-criteria

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

Commands in this context create or edit an IP or MAC criteria entry for the policy. Multiple entries can be created using unique entry-id numbers.

The list of flow criteria is evaluated in a top down fashion with the lowest entry ID at the top and the highest entry ID at the bottom. If the defined match criteria for an entry within the list matches the information in the egress packet, the system stops matching the packet against the list and performs the matching entries reclassification actions. If none of the entries match the packet, the IP flow reclassification list has no effect on the packet.

An entry is not populated in the list unless the action command is executed for the entry. An entry that is not populated in the list has no effect on egress packets. If the action command is executed without any explicit reclassification actions specified, the entry is populated in the list allowing packets matching the entry to exit the list, preventing them from matching entries lower in the list. Because this is the only flow reclassification entry that the packet matched and this entry explicitly states that no reclassification action is to be performed, the matching packet is not reclassified.

The no form of this command removes the specified entry from the policy. Entries removed from the policy are immediately removed from all services where that policy is applied.

Parameters
entry-id

Specifies a match criterion and the corresponding action. It is recommended that multiple entries be given entry IDs in staggered increments. This allows users to insert a new entry in an existing policy without requiring renumbering of all the existing entries.

An entry cannot have any match criteria defined (in which case, everything matches) but must have at least the keyword action fc fc-name for it to be considered complete. Entries without the action keyword are considered incomplete and therefore are rendered inactive.

Values

1 to 64

create

Keyword to create a flow entry when the system is configured to require the explicit use of the keyword to prevent accidental object creation. Objects may be accidentally created when this protection is disabled and an object name is mistyped when attempting to edit the object. This keyword is not required when the protection is disabled. The keyword is ignored when the flow entry already exists.

match
Syntax

[no] match [protocol protocol-id]

Context

config>qos>sap-ingress>ip-criteria>entry

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command creates a context to configure match criteria for SAP ingress QoS policy match criteria. When the match criteria have been satisfied, the action associated with the match criteria is executed.

If more than one match criteria (within one match statement) are configured, all criteria must be satisfied (AND function) before the action associated with the match is executed.

A match context can consist of multiple match criteria, but multiple match statements cannot be entered per entry.

The no form of this command removes the match criteria for the entry-id.

Parameters
protocol protocol-id

Specifies an IP protocol to be used as a SAP QoS policy match criterion.

The protocol type such as TCP / UDP / OSPF is identified by its respective protocol number.

Well-known protocol numbers include ICMP(1), TCP(6), UDP(17).

Values 0 to 255; check the node for values.

match
Syntax

match

no match

Context

config>qos>sap-ingress>mac-criteria>entry

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

Commands in this context create and edit match MAC criteria for ingress SAP QoS policy match criteria. When the match criteria have been satisfied the action associated with the match criteria is executed.

If more than one match criteria (within one match statement) are configured then all criteria must be satisfied (and function) before the action associated with the match is executed.

A match context can consist of multiple match criteria, but multiple match statements cannot be entered per entry.

The no form of this command removes the match criteria for the entry-id.

match
Syntax

match [next-header next-header]

no match

Context

config>qos>sap-ingress>ipv6-criteria>entry

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command configures match criteria for ingress SAP QoS policy match IPv6 criteria. When the match criteria have been satisfied the action associated with the match criteria is executed.

If more than one match criteria (within one match statement) are configured, then all criteria must be satisfied (and function) before the action associated with the match is executed.

A match context can consist of multiple match criteria, but multiple match statements cannot be entered per entry.

The no form of this command removes the match criteria for the entry-id.

Parameters
next-header next-header

Specifies the next meader to match.

The protocol type such as TCP / UDP / OSPF is identified by its respective protocol number. Well-known protocol numbers include ICMP(1), TCP(6), UDP(17).

Values

protocol numbers accepted in DHB: 0 to 42, 45 to 49, 52 to 59, 61 to 255 keywords: none, crtp, crudp, egp, eigrp, encap, ether-ip, gre, icmp, idrp, igmp, igp, ip, ipv6, ipv6-icmp, ipv6-no-nxt, isis, iso-ip, l2tp, ospf-igp, pim, pnni, ptp, rdp, rsvp, stp, tcp, udp, vrrp * — udp/tcp wildcard

Service ingress MAC QoS policy match commands

dst-mac
Syntax

dst-mac ieee-address [ieee-address-mask]

no dst-mac

Context

config>qos>sap-ingress>mac-criteria>entry

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command configures a destination MAC address or range to be used as a Service Ingress QoS policy match criterion.

The no form of this command removes the destination MAC address as the match criterion.

Parameters
ieee-address

Specifies the MAC address to be used as a match criterion.

Values

HH:HH:HH:HH:HH:HH or HH-HH-HH-HH-HH-HH where H is a hexadecimal digit

ieee-address-mask

Specifies a 48-bit mask to match a range of MAC address values.

This 48-bit mask can be configured using the following formats:

Format style

Format syntax

Example

Decimal

DDDDDDDDDDDDDD

281474959933440

Hexadecimal

0xHHHHHHHHHHHH

0xFFFFFF000000

Binary

0bBBBBBBB...B

0b11110000...B

All packets with a source MAC OUI value of 00-03-FA subject to a match condition should be specified as: 0003FA000000 0x0FFFFF000000

Default

0xFFFFFFFFFFFF (hex) (exact match)

Values

0x00000000000000 to 0xFFFFFFFFFFFF (hex)

etype
Syntax

etype etype-value

no etype

Context

config>qos>sap-ingress>mac-criteria>entry

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command configures an Ethernet type II value for use as a service ingress QoS policy match criterion.

The Ethernet type field is a two-byte field used to identify the protocol carried by the Ethernet frame. For example, 0800 is used to identify IPv4 packets.

The Ethernet type field is used by the Ethernet version-II frames. IEEE 802.3 Ethernet frames use the dsap, ssap or snap-pid fields as match criteria; the Ethernet type field is not used.

The snap-pid, etype, ssap, and dsap fields are mutually exclusive and cannot be part of the same match criteria.

The dataplane processes a maximum of two VLAN tags in a received packet. The Ethertype used in the MAC matching criteria for ACLs is the Ethertype that is found in the packet after processing single-tagged frames, double-tagged frames, and no-tag frames

The packet is considered to have no tags if at least one of the following criteria is true:

  • the packet is a null-tagged frame

  • the packet is a priority-tagged frame

  • the outermost Ethertype does not match the default Ethertype (0x8100)

  • the outermost Ethertype does not match the configured dot1q-etype on Dot1q encapsulated ports

  • the outermost Ethertype does not match the configured qinq-etype on QinQ encapsulated ports

The packet is considered to have a single tag if at least one of the following criteria is true:

  • the outermost Ethertype matches the default Ethertype (0x8100)

  • the outermost Ethertype matches the configured dot1q-etype on Dot1q encapsulated ports

  • the outermost Ethertype matches the configured qinq-etype on QinQ encapsulated ports

The packet is considered to have double tags if at least one of the following criteria is true:

  • the outermost Ethertype matches the default Ethernet type (0x8100)

  • the configured dot1q-etype on Dot1q encapsulated ports and the immediately following Ethertype match the default Ethertype (0x8100)

  • the configured qinq-etype on QinQ encapsulated ports and the immediately following Ethertype match the default Ethertype (0x8100)

The no form of this command removes the previously entered etype field as the match criteria.

Parameters
etype-value

Specifies the Ethernet type II frame Ether type value to be used as a match criterion, expressed in hexadecimal or decimal notation.

Values

0x0600 to 0xFFFF (hexadecimal)

1536 to 65535 (decimal)

0inner-dot1p
Syntax

inner-dot1p dot1p-value [dot1p-mask]

no inner-dot1p

Context

config>qos>sap-ingress>mac-criteria>entry

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command configures the dot1p value to be used as a service ingress QoS policy match criterion to match against the dot1p value in the inner tag (the one that follows the outermost tag in the packet) of the received packet.

The no form of this command removes the previously entered dot1p value as the match criteria.

Default

no inner-dot1p

Parameters
dot1p-value

Specifies the dot1p value to match.

Values

0 to 7

dot1p-mask

Specifies the mask value to match a range of dot1p values, expressed in hexadecimal or decimal notation.

Values

0 to 7

inner-tag
Syntax

inner-tag value [vid-mask]

no inner-tag

Context

config>qos>sap-ingress>mac-criteria>entry

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command configures the VLAN value to be used as a service ingress QoS policy match criterion to match against the VLAN value in the inner tag (the one that follows the outermost tag in the packet) of the received packet.

The no form of this command removes the previously entered VLAN tag value as the match criteria.

Default

no inner-tag

Parameters
value

Specifies the VLAN value to use for the match.

Values

0 to 4095 (decimal)

0x0 to 0xFFF (hexadecimal)

vid-mask

Specifies the mask value to match a range of VLAN values.

Values

1 to 4095 (decimal)

1x0 to 0xFFF (hexadecimal)

outer-dot1p
Syntax

outer-dot1p dot1p-value [dot1p-mask]

no outer-dot1p

Context

config>qos>sap-ingress>mac-criteria>entry

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command configures the dot1p value to be used as a service ingress QoS policy match criterion to match against the dot1p value in the outermost tag of the received packet.

The no form of this command removes the previously entered dot1p value as the match criteria.

Default

no outer-dot1p

Parameters
dot1p-value

Specifies the dot1p value to match.

Values

0 to 7

dot1p-mask

Specifies the mask value to match a range of dot1p values, expressed in hexadecimal or decimal notation.

Values

0 to 7

outer-tag
Syntax

outer-tag value [vid-mask]

no outer-tag

Context

config>qos>sap-ingress>mac-criteria>entry

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command configures the VLAN value to be used as a service ingress QoS policy match criterion to match against the VLAN value in the outermost tag in the packet of the received packet.

The no form of this command removes the previously entered VLAN tag value as the match criteria.

Default

no outer-tag

Parameters
value

Specifies the VLAN value to use for the match.

Values

0 to 4095 (decimal)

0x0 to 0xFFF (hexadecimal)

vid-mask

Specifies the mask value to match a range of VLAN values.

Values

0 to 4095 (decimal)

0x0 to 0xFFF (hexadecimal)

src-mac
Syntax

src-mac ieee-address [ieee-address-mask]

no src-mac

Context

config>qos>sap-ingress>mac-criteria>entry

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command configures a source MAC address or range to be used as a service ingress QoS policy match criterion.

The no form of this command removes the source MAC address as the match criteria.

Parameters
ieee-address

Specifies the 48-bit IEEE mac address to be used as a match criterion.

Values

HH:HH:HH:HH:HH:HH or HH-HH-HH-HH-HH-HH where H is a hexadecimal digit

ieee-address-mask

Specifies a 48-bit mask.

This 48 bit mask can be configured using the following formats

Format style

Format syntax

Example

Decimal

DDDDDDDDDDDDDD

281474959933440

Hexadecimal

0xHHHHHHHHHHHH

0x0FFFFF000000

Binary

0bBBBBBBB...B

0b11110000...B

To configure all packets with a source MAC OUI value of 00-03-FA are subject to a match condition, then the entry should be specified as: 003FA000000 0xFFFFFF000000

Default

0xFFFFFFFFFFFF (hexadecimal) (exact match)

Values

0x00000000000000 to 0xFFFFFFFFFFFF (hexadecimal)

SAP ingress queue and meter QoS policy commands

queue
Syntax

queue queue-id [create]

Context

config>qos>sap-ingress

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

Commands in this context create a queue and modify queue parameters associated with a particular queue. The queue-ID to FC map is user-defined.

The 7210 SAS-K 2F1C2T and 7210 SAS-K 2F6C4T support two, four, six, or eight queues per SAP. The 7210 SAS-K 3SFP+ 8C supports four or eight queues per SAP

The no form of this command removes the queue.

Parameters
queue-id

Specifies the ID of the queue.

Values

1 to 8

create

Keyword to create a network queue policy.

meter
Syntax

meter meter-id

no meter

Context

config>qos>sap-ingress

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command modifies meter parameters associated with a particular meter. The queue-ID to FC map is user-defined.

The no form of this command remove the meter definition.

Default

no meter

Parameters
meter-id

Specifies the ID of the meter.

Values

1 to 16

adaptation-rule
Syntax

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

no adaptation-rule

Context

config>qos>sap-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 cir and pir apply.

Default

adaptation-rule pir closest cir 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 cir 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. 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 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 rate 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. 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.

adaptation-rule
Syntax

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

no adaptation-rule

Context

config>qos>sap-ingress>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 cir and pir apply.

Default

adaptation-rule pir closest cir 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.

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.

cbs
Syntax

[no] cbs size-in-kbytes

Context

config>qos>sap-ingress>queue

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command specifies the CBS value (minimum depth of the queue).

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

Default

10

Parameters
size-in-kbytes

Specifies the CBS in kilobytes.

Values

0 to 10240 (7210 SAS-K 2F1C2T and 7210 SAS-K 2F6C4T)

0 to 102400 (7210 SAS-K 3SFP+ 8C)

cbs
Syntax

[no] cbs size [kbits | bytes | kbytes]

Context

config>qos>sap-ingress>meter

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command specifies the CBS value of 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 out-profile by the meter to indicate that the traffic is complying with the meter-configured CIR rate.

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

Default

kbits

Parameters
[kbits | bytes | kbytes]

Specifies the maximum burst size.

Values

size-in-kbits — 1 to 16384, default

size-in-bytes — 64 to 2097152, default

size-in-kbytes — 1 to 2048, default

mbs
Syntax

[no] mbs size-in-kbytes

Context

config>qos>sap-ingress>queue

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command specifies the MBS value (maximum depth of the queue).

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

Default

60

Parameters
size-in-kbytes

Specifies the MBS value in kilobytes.

Values

0 to 12800 (7210 SAS-K 2F1C2T and 7210 SAS-K 2F6C4T)

0 to 63488 (7210 SAS-K 3SFP+ 8C)

mbs
Syntax

[no] mbs size [kbits | bytes | kbytes]

Context

config>qos>sap-ingress>meter

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command specifies the MBS value of the meter. The maximum burst size parameter specifies the maximum burst size that can be transmitted by the source while still complying with the PIR. If the transmitted burst is lower than the MBS value, the packets are marked as out-profile by the meter to indicate that the traffic is complying with the meter-configured PIR rate.

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

Default

kbits

Parameters
[kbits | bytes | kbytes]

Specifies the maximum burst size.

Values

size-in-kbits — 1 to 16384, default

size-in-bytes — 64 to 2097152, default

size-in-kbytes — 1 to 2048, default

priority
Syntax

[no] priority level

Context

config>qos>sap-ingress>queue

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command defines the queue priority. The queue priority is used by the scheduler to determine the order of service in both the within-cir loop and within-pir loop. Higher priority queues are serviced before lower priority queues.

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

Default

1

Parameters
level

Specifies the priority of the queue.

Values

1 to 4

mode
Syntax

mode mode

no mode

Context

config>qos>sap-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 (trTCM) or Single Rate Three Color Marker (srTCM). The mode command can be executed at any time. The no form of this command sets it to default mode.

Default

trtcm2

Parameters
mode

Specifies the mode of the meter.

Values

srtcm — meters a packet stream and marks its packets either green, yellow, or red. Marking is based on a CIR and two associated burst sizes, a CBS and an Maximum Burst Size (MBS). A packet is marked green if it does not exceed the CBS and yellow if it does exceed the CBS, but not the MBS; otherwise, it is marked red and is dropped. The srTCM mode is useful, for example, for ingress policing of a service, where only the length, not the peak rate, of the burst determines service eligibility.

trtcm2 — implements the policing algorithm defined in RFC 4115. The trTCM2 mode meters the packet stream and marks the packets either green, yellow, or red. A packet is marked red and is dropped if it exceeds the PIR. Otherwise, it is marked either yellow or green depending on whether it exceeds or does not exceed the CIR. The trTCM2 mode is useful, for example, for ingress policing of a service, where a peak rate needs to be enforced separately from a committed rate.

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.

rate
Syntax

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

no rate

Context

config>qos>sap-ingress>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 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.

The no form of this command returns all queues created with the queue ID by association with the QoS policy to the default PIR and CIR parameters (max, 0).

Default

rate 0 pir max

Parameters
cir-rate-in-kbps

Specifies the administrative CIR rate, in kilobits, for the queue. If the rate command is not executed or the cir parameter is not explicitly specified, the default CIR value is used.

Default

0

Values

0 to 3000000, max (7210 SAS-K 2F1C2T, 7210 SAS-K 2F6C4T)

0 to 20000000, max (7210 SAS-K 3SFP+ 8C)

pir-rate-in-kbps

Specifies the administrative PIR rate, in kilobits, for the queue. When the rate command is executed, a PIR setting is optional. If the rate command is not executed, the default PIR of maximum value is used.

Default

max

Values

1 to 3000000, max (7210 SAS-K 2F1C2T, 7210 SAS-K 2F6C4T)

1 to 20000000, max (7210 SAS-K 3SFP+ 8C)

rate
Syntax

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

no rate

Context

config>qos>sap-ingress>meter

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 meter. The PIR defines the maximum rate at which the meter can admit the packet into the system for forwarding. Defining a PIR does not necessarily guarantee that the queue can transmit at the intended rate. The actual rate sustained by the flow can be limited by oversubscription factors or available egress bandwidth.

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.

The no form of this command returns all meters created with the meter-id by association with the QoS policy to the default PIR and CIR parameters (max, 0).

Default

rate 0 pir max

Parameters
cir-rate-in-kbps

Specifies the administrative CIR rate, in kilobits, for the queue. If the rate command is not executed or the cir parameter is not explicitly specified, the default CIR value is used.

Default

0

Values

0 to 3000000, max (7210 SAS-K 2F1C2T, 7210 SAS-K 2F6C4T)

0 to 20000000, max (7210 SAS-K 3SFP+ 8C)

pir-rate-in-kbps

Specifies the administrative PIR rate, in kilobits, for the queue. When the rate command is executed, a PIR setting is optional. If the rate command is not executed, the default PIR of maximum value is used.

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.

Default

max

Values

1 to 3000000, max (7210 SAS-K 2F1C2T, 7210 SAS-K 2F6C4T)

1 to 20000000, max (7210 SAS-K 3SFP+ 8C)

Show commands

sap-ingress
Syntax

sap-ingress [policy-id] [detail | association | match-criteria]

Context

show>qos

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command displays SAP ingress QoS policy information.

Parameters
policy-id

Displays information about the specific policy ID.

Default

all SAP ingress policies

Values

1 to 65535

detail

Displays detailed policy information including policy associations.

associations

Displays the policy associations of the sap-ingress policy.

match-criterion

Displays the match-criterion of the sap-ingress policy.

Output

The following output is an example of SAP ingress QoS policy information, and Output fields: SAP ingress describes the output fields.

Sample output
*A:Dut-B>show>qos# sap-ingress 1 detail
===============================================================================
QoS Sap Ingress
===============================================================================
-------------------------------------------------------------------------------
Sap Ingress Policy (1)
-------------------------------------------------------------------------------
Policy-id                 : 1                 Scope                : Template
Default FC                : be
Criteria-type             : None
Mac Sub-Criteria          : None              IP Sub-Criteria      : None
IPv6 Enabled              : False
DOT1P Class Policy Id     : 0                 DSCP Class Policy Id : 0
MPLS Lsp Exp Class Policy*: 0
Name                      : default
Description               : Default SAP ingress QoS policy.
-------------------------------------------------------------------------------
FC        Queue       MCast Queue Use Dei
-------------------------------------------------------------------------------
be        1           1           false
l2        1           1           false
af        1           1           false
l1        1           1           false
h2        1           1           false
ef        1           1           false
h1        1           1           false
nc        1           1           false
-------------------------------------------------------------------------------
FC        Meter       MCast Meter Use Dei
-------------------------------------------------------------------------------
be        -           -           false
l2        -           -           false
af        -           -           false
l1        -           -           false
h2        -           -           false
ef        -           -           false
h1        -           -           false
nc        -           -           false
-------------------------------------------------------------------------------
Queue Rates and Rules
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
QueueId        CIR          CIR Adpt Rule        PIR          PIR Adpt Rule
-------------------------------------------------------------------------------
Queue1          0              closest            max            closest
-------------------------------------------------------------------------------
Queue Priority and Weight Details
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
QueueId         Priority      Weight
-------------------------------------------------------------------------------
Queue1          1             1
-------------------------------------------------------------------------------
High Slope Non Ring
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
QueueId        State      Start-Avg(%)   Max-Avg(%)   Max-Prob(%)
-------------------------------------------------------------------------------
Queue1          Down            70           90            80
-------------------------------------------------------------------------------
Low Slope Non Ring
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
QueueId        State      Start-Avg(%)   Max-Avg(%)   Max-Prob(%)
-------------------------------------------------------------------------------
Queue1          Down            50           75            80
-------------------------------------------------------------------------------
High Slope Ring
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
QueueId        State      Start-Avg(%)   Max-Avg(%)   Max-Prob(%)
-------------------------------------------------------------------------------
Queue1          Down            70           90            80
-------------------------------------------------------------------------------
Low Slope Ring
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
QueueId        State      Start-Avg(%)   Max-Avg(%)   Max-Prob(%)
-------------------------------------------------------------------------------
Queue1          Down            50           75            80
-------------------------------------------------------------------------------
Slope Policies
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
QueueId        CBS(KBytes)  MBS(KBytes)    Slope-Policy
-------------------------------------------------------------------------------
Queue1           10          60            default
-------------------------------------------------------------------------------
Match Criteria
-------------------------------------------------------------------------------
No Matching Criteria.
SAP Associations
-------------------------------------------------------------------------------
No Associations Found.
-------------------------------------------------------------------------------
Meter Mode        CIR Admin CIR Rule PIR Admin PIR Rule CBS Admin MBS Admin
                  CIR Oper           PIR Oper           CBS Oper  MBS Oper
-------------------------------------------------------------------------------
No Matching Entries
===============================================================================
* indicates that the corresponding row element may have been truncated.
*A:Dut-B>show>qos#
Table 2. Output fields: SAP ingress

Label

Description

Policy-Id

The ID that uniquely identifies the policy

Scope

Exclusive — Implies that this policy can only be applied to a single SAP

Template — Implies that this policy can be applied to multiple SAPs on the router

Description

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

Default FC

Specifies the default forwarding class for the policy

Criteria-type

IP — Specifies that an IP criteria-based SAP ingress policy is used to select the appropriate ingress meter and corresponding forwarding class for matched traffic

MAC — Specifies that a MAC criteria-based SAP is used to select the appropriate ingress meters and corresponding forwarding class for matched traffic

Meter

Displays the meter ID

Mode

Specifies the configured mode of the meter (trTCM2 or srTCM)

CIR Admin

Specifies the administrative Committed Information Rate (CIR) parameters for the meters

CIR Rule

min — The operational CIR for the meters will be equal to or greater than the administrative rate specified using the rate command

max — The operational CIR for the meter will be equal to or less than the administrative rate specified using the rate command

closest — The operational PIR for the meters will be the rate closest to the rate specified using the rate command without exceeding the operational PIR

PIR Admin

Specifies the administrative Peak Information Rate (PIR) parameters for the meters

PIR Rule

min — The operational PIR for the meter will be equal to or greater than the administrative rate specified using the rate command

max — The operational PIR for the meters will be equal to or less than the administrative rate specified using the rate command

closest — The operational PIR for the meters will be the rate closest to the rate specified using the rate command

CBS

def — Specifies the default CBS value for the meters

value — Specifies the value to override the default reserved buffers for the meters

MBS

def — Specifies the default MBS value

value — Specifies the value to override the default MBS for the meter

UCastM

Specifies the default unicast forwarding type meters mapping

MCastM

Specifies the overrides for the default multicast forwarding type meter mapping

BCastM

Specifies the default broadcast forwarding type meters mapping

UnknownM

Specifies the default unknown unicast forwarding type meters mapping

Match Criteria

Specifies an IP or MAC criteria entry for the policy

DSCP

Specifies a DiffServ Code Point (DSCP) name used for an ingress SAP QoS policy match

FC

Specifies the entry’s forwarding class

Src MAC

Specifies a source MAC address or range to be used as a Service Ingress QoS policy match

Dst MAC

Specifies a destination MAC address or range to be used as a Service Ingress QoS policy match

Dot1p

Specifies a IEEE 802.1p value to be used as the match

Ethernet-type

Specifies an Ethernet type II Ether type value to be used as a Service Ingress QoS policy match

FC

Specifies the entry’s forwarding class

Service-Id

The unique service ID number which identifies the service in the service domain

Customer-Id

Specifies the customer ID which identifies the customer to the service

SAP

Specifies the a Service Access Point (SAP) within the service where the SAP ingress policy is applied

Classifiers required

Indicates the number of classifiers for a VPLS or Epipe service

Meters required

Indicates the number of meters for a VPLS or Epipe service

Meters mode

Displays the configured meter mode

dot1p-classification
Syntax

dot1p-classification [policy-id] [detail]

Context

show>qos

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command displays dot1p-classification QoS policy information.

Parameters
policy-id

Displays information about the specific policy ID.

detail

Displays detailed policy information.

Output

The following output is an example of dot1p classification policy information, and Output fields: dot1p classification describes the output fields.

Sample output
A:SAH01-050>config>qos>sap-ingress# show  qos dot1p-classification 10
===============================================================================
DOT1P Classification Maps
===============================================================================
-------------------------------------------------------------------------------
Dot1P Class Id     : 10
Description        : (Not Specified)
-------------------------------------------------------------------------------
A:SAH01-050>config>qos>sap-ingress#


A:SAH01-050>config>qos>sap-ingress# show  qos dot1p-classification 10  detail

===============================================================================
DOT1P Classification Maps
===============================================================================
-------------------------------------------------------------------------------
Dot1P Class Id     : 10
Description        : (Not Specified)

-------------------------------------------------------------------------------
Dot1P Bit Map                         Forwarding Class                Profile
-------------------------------------------------------------------------------
6                                       h1                              None
7                                       nc                              None

-------------------------------------------------------------------------------
Network Policy Associations
-------------------------------------------------------------------------------
No Network Policy Associations found.
-------------------------------------------------------------------------------

-------------------------------------------------------------------------------
SAP Ingress Associations
-------------------------------------------------------------------------------
SAP Ingress Id             : 10
-------------------------------------------------------------------------------
===============================================================================
Table 3. Output fields: dot1p classification

Label

Description

Dot1P Class Id

The ID that uniquely identifies the policy

Dot1P Bit Map

The dot1p value specified in the policy

Forwarding Class

The forwarding class to assigned to the packet if the received packet's dot1p values match the dot1p value configured

Description

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

Profile

Specifies the profile to be assigned to the packet

dscp-classification
Syntax

dscp-classification [policy-id] [detail]

Context

show>qos

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command displays DSCP classification QoS policy information.

Parameters
policy-id

Displays information about the specific policy ID.

detail

Displays detailed policy information.

Output

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

Sample output
*A:SAH01-071>config>qos# show qos dscp-classification 6335 detail 

===============================================================================
DSCP Classification Maps
===============================================================================
-------------------------------------------------------------------------------
Dscp Class Id      : 6335
Description        : (Not Specified)
 
-------------------------------------------------------------------------------
Dscp Bit Map                         Forwarding Class                Profile
-------------------------------------------------------------------------------
cp7                                     nc                              In
cp15                                    h1                              In
cp23                                    ef                              In
cp31                                    h2                              In
cp39                                    l1                              In
cp47                                    af                              In
cp55                                    l2                              In
 
-------------------------------------------------------------------------------
Network Policy Associations
-------------------------------------------------------------------------------
No Network Policy Associations found. 
-------------------------------------------------------------------------------
 
-------------------------------------------------------------------------------
SAP Ingress Associations
-------------------------------------------------------------------------------
SAP Ingress Id             : 17
-------------------------------------------------------------------------------
===============================================================================
Table 4. Output fields: DSCP classification

Label

Description

Dot1P Class Id

The ID that uniquely identifies the policy

Dot1P Bit Map

The dot1p value specified in the policy

Forwarding Class

The forwarding class to assigned to the packet if the received packet's dot1p values match the dot1p value configured

Description

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

Profile

Specifies the profile to be assigned to the packet