Access ingress QoS policies

Note:

This feature is supported only on the 7210 SAS-Mxp, 7210 SAS-R6, 7210 SAS-R12, 7210 SAS-Sx/S 1/10GE (standalone), and 7210 SAS-Sx 10/100GE (standalone).

This chapter provides information about configuring access ingress QoS policies using the command line interface.

Overview

An access ingress QoS policy is applied to the physical port instead of the SAP. It applies to all SAPs configured on the specific access port. To configure a port-based access ingress QoS policy, the access-ingress-qos-mode command must be configured with the port-mode option specified.

Note:

See the 7210 SAS-Mxp, R6, R12, S, Sx, T Interface Configuration Guide for more information about the access-ingress-qos-mode command.

At ingress, the access ingress QoS policy uses dot1p, DEI with dot1p, or IP DSCP values to assign a forwarding class and profile to traffic, which facilitates the classification of traffic received on the access port. The user can assign a profile using DEI configured with a dot1p classification policy. The forwarding class is associated with meters or policers at ingress. The FC meters for unicast and multicast traffic and meter characteristics (for example, the CIR and PIR) are defined in the policy.

An access ingress QoS policy supports the definition of up to one (1) meter per forwarding class for unicast traffic, and up to one (1) meter per forwarding class for multipoint traffic (that is, broadcast, multicast, and unknown-unicast) for multipoint services. The definition of a maximum of 16 meters per access ingress QoS policy is supported.

For VPLS, the following four forwarding types (not to be confused with forwarding classes) are supported: unicast, multicast, broadcast, and unknown. The multicast, broadcast, and unknown traffic types are flooded to all destinations in the service and use the multipoint meter associated with the forwarding class. The unicast traffic type is handled in a point-to-point manner in the service and uses the unicast meter associated with the forwarding class.

Note:

An access ingress policy is supported only when the node is configured to operate in the high SAP scale mode using the configure system resource-profile sap-scale-mode high command on the 7210 SAS-Mxp, 7210 SAS-Sx/S 1/10GE, and 7210 SAS-Sx 10/100GE and configure system global-res-profile sap-scale-mode high command on the 7210 SAS-R6 and 7210 SAS-R12.

See the 7210 SAS-Mxp, S, Sx, T Services Guide and 7210 SAS-R6, R12 Services Guide for more information about high SAP scale mode.

See the 7210 SAS-Mxp, R6, R12, S, Sx, T Basic System Configuration Guide for more information about the sap-scale-mode command.

Shared access ingress QoS policies on the 7210 SAS-Mxp

In addition to non-shareable access ingress port policies, users can configure and use shared access ingress policies. Shared policies optimize resource usage by associating a single instance of an access ingress QoS policy with multiple access ports. The software then allocates a single instance of classification entries and policing resources defined in the policy to classify and rate-limit ingress traffic received on all access ports. To use a shared access ingress QoS policy, enable the config>system>resource-profile>qos-access-port-shared-res-mode command. This mode is mutually exclusive to use non-shared mode. To use an access ingress policy exclusively with a port (to emulate the behavior of a non-shared access ingress policy), create a shared access ingress policy and associate it with only one port, instead of associating it with multiple ports.

With shared access ingress QoS policies, for traffic classification, the user has an option to use either table criteria or CAM criteria. With table criteria, the access ingress QoS policy uses dot1p, DEI with dot1p, or IP DSCP values to assign a forwarding class and profile to traffic. With CAM criteria, the access ingress QoS policy uses IP criteria to assign forwarding class to traffic. Shared access ingress policies provide similar capabilities for a policer definition as the non-shared access ingress policy.

Meter allocaton rules for shared access ingress QoS policies

The following rules are used to allcoate meters in a shared access ingress QoS policy.

  • Sharing of a single meter for both unicast and multipoint traffic is allowed. Users can configure any of the available meters for multipoint traffic.

  • When the num-qos-classifiers command is set to a value of 2, only a single meter is available for use for both unicast and multicast traffic. That is, a separate multipoint meter cannot be configured.

  • When associating a meter with an FC for broadcast, unknown-unicast, or multicast (BUM) traffic, the system does not validate whether the meter is a multipoint meter. This allows a single meter to be used for unicast and BUM traffic, which allows for efficient use of access ingress QoS resources.

  • The use of the multipoint keyword is not mandatory for meter creation. If a multipoint meter is specified during meter creation, Nokia recommends that it should be used only with BUM traffic when it is explicitly configured for an FC.

  • Unlike the special semantics associated with meter 11 in a service ingress policy or meter 9 in non-shared access ingress QoS policy, there are no special semantics associated with meter 9 in a shared access ingress policy. In other words, meter 9 is not treated as the default multipoint meter for all FCs in a shared access ingress QoS policy. The user can configure meter 9 as a non-multipoint meter and use it for policing unicast traffic from any FC.

Resource allocation for non-shared access ingress QoS policies

This section describes the allocation of QoS resources from the CAM pool allocated to the policy to access ingress QoS policies using the configure system resource-profile ingr-internal-tcam qos-access-port-ingress-resource command.

For every FC in use, the system allocates two classification entries from the qos-access-port-ingress-resource CAM pool: one entry for the unicast meter and one for the multicast meter. Regardless of the number of dot1p entries in the dot1p classification policy and IP DSCP entries in the DSCP classification policy that map to a specific FC name, a maximum of two entries are required for the FC. That is, if the user defines a dot1p classification policy with all seven dot1p values mapped to FC af, FC af needs only two classification entries in the CAM. An FC is considered to be in use if a dot1p classification entry, DSCP classification entry, or the default FC is mapped to the FC name.

For every meter or policer in use, the system allocates one meter in the hardware. A meter or policer is considered to be in use when it is associated with an FC that is in use.

The number of access ports that can be configured in access-ingress-qos-mode port-mode is limited by the number of classification resources available in the hardware and the number of access ports supported by the system.

Using index file for access ingress QoS policies

7210 SAS platforms use an index file to store the map that indicates the QoS resource allocation to access ports (for both non-shared and shared policies). After a reboot, the file is used to ensure appropriate resource allocation for all access ports that were using the access ingress policy before the reboot. In the absence of an index file, access ports that were configured successfully before the reboot may fail after the reboot. After the configuration file is saved, the index file is stored in flash memory. On system reboot, if the file is found, the system allocates resources as indicated in the stored map. If the file is not found, the system implements a best-fit algorithm and attempts to allocate resources for all access ports on a first-come-first-served basis. If the file is not found after reboot, the saved configuration may not execute successfully because resources may not be allocated to all access ports.

Note:

The index file used for the QoS map is different from the file used for storing interface indexes.

Calculating the number of QoS resources for non-shared access ingress QoS policies

To calculate the number of QoS resources used by a port-based access ingress QoS policy, the user must determine the number of FCs to use.

Only the FCs used by the match criteria classification entries configured in the dot1p and DSCP classification policies, which are referred to as ‟FCs in use,” are considered to calculate the number of FCs.

Default unicast meter 1 and default mulitpoint meter 9, which are created by default when a new policy is created, cannot be deleted. Unless the user explicitly configures another unicast meter or multicast meter for the FCs, the default unicast meter 1 is used for all unicast traffic and default mulitpoint meter 9 is used for all multipoint traffic (that is, broadcast, multicast, and unknown-unicast).

Use the following rules to compute the number of classification entries per FC in use:

  • If an FC is in use and is created without explicit meters, use default meter 1 for unicast traffic and default meter 9 for all other traffic (that is, broadcast, multicast, and unknown-unicast). The FC requires two classification entries in the hardware.

  • If an FC is in use and is created with an explicit unicast meter, use the unicast meter for unicast traffic and default meter 9 for all other traffic. The FC requires two classification entries in the hardware.

  • If an FC is in use and is created with an explicit unicast meter and an explicit multicast meter, use the unicast meter for unicast traffic and the multicast meter for all other traffic. The FC requires two classification entries in the hardware.

  • Two classification entries are used for the default fc-name configured using the config qos access-ingress default-fc command. The entries for the default FC are in addition to the FCs configured in the dot1p and DSCP classification policies.

Using the number of match criteria and FCs in use, calculate the total number of classification entries per policy with the following formula.

TC = ∑ 2 * E(i) + 2
i = nc, h1, ef, h2, l1, af, l2, be

where:

  • TC is the total number of classification entries per policy

  • E(i) is the number of match criteria entries that classify packets to FCi. E(i) is one (1) if there is a dot1p or DSCP classification entry that classifies packets to FCi; itherwise, E(i) is zero.

  • the number is multiplied by two for the number of classification entries that FCi requires

  • another two entries are added for the default FC

Calculating the number of meters or policers for non-shared access ingress QoS policies

The total number of policers (TP) used is the number of meters configured in the policy. From the meters configured in the policy, only meters configured for use with an FC are counted for resource allocation. That is, meters that are created but not associated with an FC are not counted for resource allocation. A maximum of 16 meters are available per access ingress QoS policy.

Example of non-shared access ingress QoS policy resource calculations

The following sections describe example calculations for a non-shared access ingress QoS policy.

Example 1

The following output example shows the FC mapping in a configured dot1p classification policy, in which the FC is using the default meters (meter 1 for unicast and meter 9 for multicast).

configure> qos> dot1p-classification 10
dot1p 7 fc nc
dot1p 6 fc nc
default-dot1p-fc be profile out
exit
configure> qos> access-ingress 10
     dot1p-classification 10
     meter 1 create
        rate pir max cir 0
     exit
meter 9 multi-point create
     rate pir 100 cir 0
     exit
table-classification-criteria use-dot1p 
     default-fc h1 profile in
exit

TC = 2 x 1 (for FC nc) + 2 x 1 (for default-dot1p-fc be) + 2 (for default-fc h1) = 6

TP = 2 x 2 = 4; (only 2 default meters)

The num-qos-classifiers value should be set to max (TC, TP) = max (6, 4) = 6

Example 2

The following output example shows the FC mapping in a configured dot1p classification policy, in which the FC is using the default meters (meter 1 for unicast and meter 9 for multicast).

configure> qos> dot1p-classification 10
dot1p 7 fc nc
dot1p 6 fc nc
default-dot1p-fc be profile out
exit
configure> qos> access-ingress 20
     dot1p-classification 10
     meter 1 create
        rate pir max cir 0
     exit
meter 9 multi-point create
     rate pir 100 cir 0
     exit
table-classification-criteria use-dot1p 
     default-fc be profile out
exit

TC = 2 x 1 (for FC nc) + 2 x 1 (for default-dot1p-fc be) + 2 (for default-fc be) = 6

TP = 2 x 2= 4; (only 2 default meters)

The num-qos-classifiers value should be set to max (TC, TP) = max (6, 4) = 6

Example 3

The following output example shows the configuration of the FC mapping in a dot1p classification policy, in which the FC is using both user-defined and default meters.

Note:

By default, unicast meter 1 and multipoint meter 9 are used if no explicit meter mapping is defined for the FC.

configure> qos> dot1p-classification 10
dot1p 7 fc nc
dot1p 6 fc nc
default-dot1p-fc be profile out
exit
 
configure> qos> access-ingress 30
dot1p-classification 10
meter 1 create
rate pir max cir 0
     exit
     meter 9 multi-point create
          rate pir 100 cir 0
     exit
     meter 2 create
     rate 100 max cir 100
exit
     meter 10 multi-point create
     rate pir 100 cir 0
     exit
 
     fc nc
     meter 2
     multicast-meter 10
 exit
table-classification-criteria use-dot1p 
     default-fc be profile out
exit

TC = 2 x 1 (for FC nc) + 2 x 1 (for default-dot1p-fc be) + 2 (for default-fc be) = 6

TP = 2 x 4 = 8; (2 default meters and 2 user-defined meters)

The num-qos-classifiers value should be set to max (TC, TP) = max (6, 8) = 8

Resource allocation for shared access ingress QoS policies on the 7210 SAS-Mxp

This section describes the allocation of QoS resources from the CAM pool allocated to the policy to shared access ingress QoS policies using the config>system>resource-profile>ingr-internal-tcam>qos-access-port-shared-res command.

The resource allocation varies based on the classification criteria configured for the policy. The following sections describe the resource allocation with table-criteria and cam-criteria.

With the table-criteria option, for every FC in use, the system allocates two classification entries from the qos-access-port-shared-res CAM pool: one entry to map the traffic for the unicast meter and one to map the traffic for the multicast meter.

Regardless of the number of dot1p entries in the dot1p classification policy and IP DSCP entries in the DSCP classification policy that map to a specific FC name, a maximum of two entries are required for the FC. That is, if the user defines a dot1p classification policy with all seven dot1p values mapped to FC af, FC af needs only two classification entries in the CAM. An FC is considered to be in use if a dot1p classification entry, DSCP classification entry, or the default FC is mapped to the FC name. For every meter or policer in use, the system allocates one meter in the hardware. A meter or policer is considered to be in use when it is associated with an FC in use.

With the cam-criteria option, for every classification entry and FC in use, the system allocates two classification entries from the qos-access-port-shared-res CAM pool; one entry for the unicast meter and one for the multicast meter. That is, if the user defines a IP criteria with 10 entries, then all the classification entries are configured to FC "af", FC "af" needs two classification entries in the CAM per each IP criteria entry for a total of 20 entries in the CAM. An FC is considered to be in use if a cam-criteria classification entry or the default FC is mapped to the FC name. For every meter or policer in use, the system allocates one meter in the hardware. A meter or policer is considered to be in use when it is associated with an FC in use.

The number of access ports that can be configured in access-ingress-qos-mode port-mode is limited by the number of classification resources available in the hardware and the number of access ports supported by the system.

Calculating the number of QoS resources for shared access ingress QoS policies

To calculate the number of QoS resources used by a port-based shared access ingress QoS policy, the user must determine the number of FCs to use and the criteria used for classification of traffic to FC.

If using table-criteria, the QoS resource calculation is exactly the same as the non-shared access ingress QoS policy described in Calculating the number of QoS resources for non-shared access ingress QoS policies. Resources are shared by all access ports the access ingress QoS policy is associated with.

If using cam-criteria, the QoS resource calculation for a port-based shared access ingress QoS policy using cam-criteria, the user must determine the number of FCs and the number of classification entries to use for classification of traffic to the FC.

Only the FCs used by the match criteria classification entries configured in the policy, which are referred to as ‟FCs in use,” are considered in the calculation of the number of FCs.

The default unicast meter 1, which is created by default when a new policy is created, cannot be deleted. Unless the user explicitly configures another unicast meter or multicast meter for the FCs, the default unicast meter 1 is used for all unicast and multipoint traffic (for example, broadcast, multicast, and unknown-unicast).

The following meter selection rules are used by different traffic types under various configurations to compute the number of classification entries per FC in use:

  • Only meter 1 is defined in the default policy; Meter 9 is not created. All FC and all traffic types use meter 1 by default. The following is a sample configuration output:

    *7210-SAS>config>qos# access-ingress share-resources 65535 create 
*7210-SAS>config>qos>access-ingress$ info
----------------------------------------------
     num-qos-classifiers 2
     meter 1 create
     exit
----------------------------------------------
*7210-SAS>config>qos>access-ingress$

  • If an FC is created without explicit meters, the default meter 1 is used for unicast traffic and BUM traffic types (for example, broadcast, multicast, and unknown-unicast traffic). When cam-criteria is configured, this uses a single entry in the CAM for each classification entry configured in the policy. When table-criteria is configured, this uses a single entry in the CAM for each FC.

  • If an FC is created with only an explicit unicast meter, that meter is used for unicast traffic and for BUM traffic types. When cam-criteria is configured, this uses a single entry in the CAM for each classification entry configured in the policy. When table-criteria is configured, this uses a single entry in the CAM for each FC.

  • If an FC is created with an explicit unicast meter and explicit multicast meter, use the configured unicast meter for unicast traffic and the configured multicast meter for all other traffic types. When cam-criteria is configured, this uses two entries in the CAM for each classification entry configured in the policy. When table-criteria is configured, this uses two entries in the CAM for each FC.

  • If an FC is created with only an explicit multicast meter, use the default meter 1 for unicast traffic and the configured multicast meter for BUM traffic. When cam-criteria is configured, this uses two entries in the CAM for each classification entry configured in the policy. When table-criteria is configured, this uses two entries in the CAM for each FC.

  • If an FC is configured explicitly to use a unicast meter and a multicast meter and both the traffic types are configured to use the same meter ID, the software allocates two entries in the CAM. When cam-criteria is configured, this uses two entries in the CAM for each classification entry configured in the policy. When table-criteria is configured, this uses two entries in the CAM for each FC.

Using the number of match criteria and FCs in use, calculate the total number of classification entries per policy with the following formula.

TC = ∑ (M(i) * E(i) + 2
i = 1 – maximum number of classification entries
where:

  • TC is the total number of classification entries per policy

  • E(i) is the number of match criteria entries that classify packets to FCi. The E(i) is one (1) if there is a CAM criteria classification entry that classifies packets to FCi; otherwise, the E(i) is zero.

  • The M(i) is the number of meters FCi requires and determined using the meter selection rules provided in the preceding list. Each meter defined for the FC consumes a CAM entry to map the traffic flow to defined FCi.

  • two additional entries are added for the default FC

Calculating the number of meters or policers for shared access ingress QoS policies

The total number of policers (TP) used is the number of meters configured in the policy. Only meters configured for use with an FC are counted for resource allocation. That is, meters that are created but not associated with an FC are not counted. A maximum of 16 meters are available per access ingress QoS policy.

Determining the number of resources allocated to shared access ingress QoS policies

The user must determine the value for the config>qos>access-ingress>num-qos-classifiers command using the following formula.

max (TC, TP)
where:

  • TC is the total number of classification entries per policy

  • TP is the total number of policers

See sections Calculating the number of QoS resources for shared access ingress QoS policies and Calculating the number of meters or policers for shared access ingress QoS policies for information about determining the values for the TC and TP parameters.

Examples of shared access ingress QoS policy resource calculations

This section provides example resource calculations for a shared access ingress QoS policy.

Example 1

The following output is an example of the FC mapping for a cam-criteria (IP criteria) access ingress QoS policy, in which the FC is using the the default meters (meter 1).

configure> qos> access-ingress 10
meter 1 create
rate pir max cir 0
exit
classification-criteria cam-criteria
fc h1
	meter 1
exit
fc nc
	meter 1
exit
default-fc h1 profile in
ip-criteria
	entry 1
		action fc nc 
		match src-ip 192.168.1.1/32
	exit
exit

where:

TC = 1 x 1 (for FC nc) + 1 x 1 (for default-fc h1) = 2

TP = 1 x 2 = 2; (only 1 default meter)

The num-qos-classifiers value should be set to max (TC, TP) = max (2, 2) = 2.

Example 2

The following output is an example of the FC mapping for a cam-criteria (IP criteria) access ingress QoS policy, in which the FC is using the non-default meters (meter 1 and meter 3).

configure> qos> access-ingress 10
meter 1 create
rate pir max cir 0
exit
meter 3 create
rate pir max cir 10
exit
fc h1
	meter 1
	multicast-meter 3
exit
fc nc
	meter 1
exit

classification-criteria cam-criteria
default-fc h1 profile in
ip-criteria
	entry 1
		action fc nc 
		match src-ip 192.168.1.1/32
	exit
exit

where:

TC = 1 x 1 (for FC nc) + 1 x 2 (for default-fc h1) = 3

TP = 2 x 2 = 4; (2 meters; meter 3 and meter 1)

The num-qos-classifiers value should be set to max (TC, TP) = max (3, 4) = 4.

Example 3

The following output is an example of the FC mapping for a cam-criteria (IP criteria) access ingress QoS policy in which a mix of FCs are in use and where some FCs use the non-default meters (meter 1 and meter 3) and some use the default meter 1.

Note: By default, unicast meter 1 is used if no explicit meter mapping is defined for the FC.
configure> qos> access-ingress 10
meter 1 create
rate pir max cir 0
exit
meter 3 create
rate pir max cir 10
exit
fc h1
	meter 1
	multicast-meter 3
exit
fc nc
	multicast-meter 9
exit
fc af 
	multicast-meter 4
exit
fc be
exit

classification-criteria cam-criteria
default-fc be profile in
ip-criteria
	entry 1
		action fc nc 
		match src-ip 192.168.1.1/32
	exit
	entry 10
		action fc af 
		match dst-ip 192.168.100.1/32
	exit
	entry 20
		action fc h1 
		match src-ip 192.168.200.1/32
	exit
	entry 30
		action fc af 
		match dst-ip 192.168.300.1/32
	exit
	entry 40
		action fc af 
		match src-ip 192.168.400.1/32
	exit

exit

where:

TC = 1 x 2 (for FC nc) + 3 x 2 (for FC af) + 1 x 1 (for default-fc be) = 11

TP = 2 x 2 = 4; (2 meters; meter 3 and meter 1)

The num-qos-classifiers value should be set to max (TC, TP) = max (11, 4) = 11 (rounded off to the nearest even number greater than 11, which is 12).

Configuration guidelines for a port-based access ingress QoS policy

Use the following guidelines to configure a port-based access ingress QoS policy.

Note: The following guidelines are generic and some of the commands are not available on all platforms.

  • Delete all SAPs on the port or the LAG before switching between the sap-mode and port-mode options for the access-ingress-qos-mode command.

  • Perform the following steps before changing the access-ingress-qos-mode command to port-mode:

    1. Reboot the node in sap-scale-mode high.

    2. If shared mode is enabled (config>system>resource-profile>qos-access-port-shared-res-mode), ensure that the following resources are allocated:
      • config>system>resource-profile>ingress-internal-tcam>qos-access-ingress-resource
      • config>system>resource-profile>ingress-internal-tcam>qos-access-port-shared-res

    3. Configure an access port using the config>port>ethernet>mode command with the access option specified.

  • If the config>port>ethernet>access-ingress-qos-mode command is set to port-mode, access ingress policy 1 is attached to the port by default. In shared mode, the access ingress policy ID 65536 is attached to the port by default. The policy can be replaced with a user-defined access ingress QoS policy provided that sufficient resources are available in the qos-access-port-ingress-resource slice or qos-access-port-shared-res slice in shared mode.

  • Resource allocation using qos-access-port-ingress-resource has no restrictions and resources can be configured using this command in sap-scale-mode low, high, or in shared mode; however, allocating resources in sap-scale-mode low or in shared mode wastes resources because an access ingress QoS policy can only be attached in sap-scale-mode high and resources for shared policies are allocated from the qos-access-port-shared-res slice.

  • Reset the user-defined access ingress QoS policy to 1 or 65536 on the port before changing the access-ingress-qos-mode command to sap-mode.

  • If the access-ingress-qos-mode command is configured in the config>lag context, reset the user-defined access ingress QoS policy to 1 or 65536 on the primary LAG member before changing the access-ingress-qos-mode command to sap-mode.

Basic configurations for non-shared access ingress QoS policies

A basic non-shared access ingress QoS policy must conform to the following configuration rules:

  • The policy must have a unique access ingress QoS policy ID.

  • The policy can specify meter parameters, such as CIR and PIR, to define meters for use.

  • The policy may include a dot1p and DSCP template attachment to map dot1p and IP DSCP values to the FC.

  • Optionally, the policy may configure either the IP DSCP or dot1p or both for classification. The user can also assign an ingress profile based on either a dot1p, DEI with dot1p, or IP DSCP.

The following output is an example configuration of an access ingress QoS policy.

*A:Dut-A>config>qos# access-ingress 10 
*A:Dut-A>config>qos>access-ingress# info 
----------------------------------------------
            meter 1 create
                mode trtcm2 
                adaptation-rule cir min
                rate cir 1010 pir 4040
                color-mode color-blind
                mbs 512 bytes
                cbs 100 kbytes
            exit
            meter 3 create
            exit
            meter 5 multi-point create
            exit
            meter 9 multi-point create
            exit
            fc "ef" create
                meter 3
                multicast-meter 5
            exit
            counter-mode forward-drop-count
            default-fc "ef" profile in 
            dot1p-classification 40
            dscp-classification 30
            table-classification-criteria use-dscp
            num-qos-classifiers 8
----------------------------------------------

Editing a non-shared access ingress QoS policy configuration

The user can edit existing policies and entries through the CLI or NMS. The changes are applied immediately to all services to which the policy applies.

Note:

The num-resources parameter value for the config>qos>access-ingress>num-qos-classifiers command cannot be modified when the policy is in use.

Perform the following to prevent configuration errors:

  • Copy the policy to a work area.

  • Edit the policy.

  • Overwrite the original policy.

Removing a non-shared policy from the QoS configuration

Use the following syntax to remove an access ingress policy from the QoS configuration.

config>qos# no access-ingress policy-id

config>qos# no access-ingress 100
    config>qos# no access-ingress 1010

Deleting a non-shared access ingress QoS policy

Every access Ethernet port is associated, by default, with the default access ingress policy (policy-id 1) when the access-ingress-qos mode command is set to port-mode. You can replace the default policy with a user-defined policy. If the non-default access ingress policy is removed, the association reverts to default policy-id 1. A QoS policy cannot be deleted until it is removed from all access ports where it is applied.

*A:card-1>config>qos# no access-ingress 30
MINOR: CLI Could not remove Access ingress policy "30" because it is in use.
Note:

The access-ingress-qos-mode command can only be changed to sap-mode if access ingress policy 1 is attached to the port.

Basic configurations for shared access ingress QoS policies

A basic shared access ingress QoS policy must conform to the following configurations rules:

  • The policy must have a unique access ingress QoS policy ID.

  • The policy can specify meter parameters, such as CIR and PIR, to define meters for use.

  • The policy may include a dot1p and DSCP template attachment to map dot1p and IP DSCP values to the FC.

  • Optionally, the policy may configure either the IP DSCP or dot1p or both for classification. The user can also assign an ingress profile based on either a dot1p, DEI with dot1p, or IP DSCP.

The following output is an example configuration of a shared access ingress QoS policy.

*A:Mxp> configure qos access-ingress 65536 
*A:Mxp>config>qos>access-ingress# info detail 
----------------------------------------------
            description "Default ACCESS ingress shared QoS policy."
            meter 1 create
                mode trtcm1 
                adaptation-rule cir closest pir closest
                rate cir 0 pir max
                color-mode color-aware
                mbs default kbits
                cbs default kbits
            exit
            classification-criteria table-criteria
            counter-mode in-out-profile-count
            default-fc "be" profile out 
            dot1p-classification 1
            dscp-classification 1
            table-classification-criteria both-dscp-dot1p
            num-qos-classifiers 2
----------------------------------------------

Editing a shared access ingress QoS policy configuration

The user can edit existing policies and entries through the CLI or NMS. The changes are applied immediately to all services to which the policy applies.

Note:

The num-resources parameter value for the config>qos>access-ingress>num-qos-classifiers command cannot be modified when the policy is in use.

Perform the following to prevent configuration errors:

  • Copy the policy to a work area.

  • Edit the policy.

  • Overwrite the original policy.

Removing a shared policy from the QoS configuration

Use the following syntax to remove an access ingress policy from the QoS configuration.

config>qos# no access-ingress policy-id

config>qos# no access-ingress 100
    config>qos# no access-ingress 1010

Deleting a shared access ingress QoS policy

Every access Ethernet port is associated, by default, with the default access ingress shared QoS policy (policy ID 65536) when the access-ingress-qos-mode command is set to port-mode. Users can replace the default policy with a user-defined policy. If the non-default access ingress shared QoS policy is removed, the association reverts to the default policy ID 65536. A QoS policy cannot be deleted until it is removed from all access ports where it is applied.
Mxp>config>qos# no access-ingress 20
MINOR: QOS #11031 Access ingress policy is already in use
Note:

The access-ingress-qos-mode command can only be changed to sap-mode if access ingress policy 65535 is attached to the port.

Access-ingress QoS policy command reference

Command hierarchies

Access-ingress QoS configuration commands 

config
    - qos
        - access-ingress policy-id [share-resources] [create]
        - no access-ingress policy-id
            - classification-criteria classification-criteria
            - no classification-criteria
            - counter-mode {in-out-profile-count | forward-drop-count}
            - no counter-mode 
            - description description-string
            - no description
            - default-fc fc-name profile {in | out}
            - no default-fc 
            - dot1p-classification description-string
            - no dot1p-classification
            - dscp-classification description-string
            - no dscp-classification
            - fc fc-name [create]
            - no fc fc-name
                - meter meter-id
                - no meter
                - multicast-meter meter-id
                - no multicast-meter
            - ip-criteria [use-port-range] 
            - no ip-criteria
                - entry entry-id [create]
                - no entry entry-id
                    - action [fc fc]
                    - no action
                    - description description-string
                    - no description
                    - match [protocol protocol-id]
                    - no match
                        - dscp dscp-value | dscp-name [dscp-mask]
                        - no dscp
                        - dst-ip ip-address [ipv4-address-mask]
                        - dst-ip ip-address/mask
                        - no dst-ip
                        - dst-port {eq} dst-port-number
                        - dst-port {range} dst-port-number1 dst-port-number2
                        - no dst-port
                        - ip-prec ip-prec-value [ip-prec-mask]
                        - no ip-prec
                        - src-ip ip-address/mask
                        - src-ip ip-address [ipv4-address-mask]
                        - no src-ip 
                        - src-port {eq} src-port-number
                        - src-port {range} src-port-number1 src-port-number2
                        - no src-port
                - renum old-entry-id new-entry-id
            - meter meter-id [create] [multi-point] 
            - no meter meter-id
                - adaptation-rule [cir adaptation-rule] [pir adaptation-rule]
                - no adaptation-rule
                - cbs size [kbits | bytes | kbytes]
                - no cbs
                - color-mode {color-aware | color-blind}
                - no color-mode 
                - mbs size [kbits | bytes | kbytes]
                - no mbs
                - mode mode
                - no mode
                - rate [cir cir-rate] [pir pir-rate]
                - no rate
            - num-qos-classifiers num-resources
            - no num-qos-classifiers
            - table-classification-criteria table-classification-criteria

Command descriptions

Generic commands

access-ingress
Syntax

access-ingress policy-id [share-resources] [create]

no access-ingress policy-id

Context

config>qos

Platforms

7210 SAS-Mxp, 7210 SAS-R6, 7210 SAS-R12, 7210 SAS-Sx/S 1/10GE (standalone), and 7210 SAS-Sx 10/100GE (standalone)

Description

This command creates or edits an access ingress QoS policy, which is used when the access-ingress-qos-mode command is set to port-mode. See the 7210 SAS-Mxp, R6, R12, S, Sx, T Interface Configuration Guide for more information about the access-ingress-qos-mode command.

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

Default

access-ingress 1 (for non-shared mode)

access-ingress 65536 (for shared mode)

Parameters
policy-id

Specifies the access-ingress policy ID.

Values

1 to 65535

1 to 65536 (only on the 7210 SAS-Mxp)

Note: The value of 65536 is the default policy reserved for use when the node is configured to share access-ingress QoS policies across ports and is not modifiable by the user in the description.
create

Keyword to create an access-ingress policy. The create keyword requirement can be enabled or disabled in the environment>create context.

share-resources

Keyword to indicate that if the policy is associated with a port, it shares existing resources if another port has already been instantiated with this policy. If this keyword is not specified, the port allocates new resources if they are available and fails if there are no resources. This keyword is only available on the 7210 SAS-Mxp and can only be used when the config>system>resource-profile>qos-access-port-shared-res-mode command is enabled.

description
Syntax

description description-string

no description

Context

config>qos>access-ingress

config>qos>access-ingress>ip-criteria>entry (only on the 7210 SAS-Mxp)

Platforms

7210 SAS-Mxp, 7210 SAS-R6, 7210 SAS-R12, 7210 SAS-Sx/S 1/10GE (standalone), and 7210 SAS-Sx 10/100GE (standalone)

Description

This command creates a text description stored in the configuration file for a configuration context. The text string is stored in the configuration file and identifies the context in the file.

The no form of this command removes the description string for the configuration context.

Parameters
description-string

Specifies a text string that describes 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.

Access ingress QoS policy commands

classification-criteria
Syntax

classification-criteria classification-criteria

no classification-criteria

Context

config>qos>access-ingress

Platforms

7210 SAS-Mxp

Description

This command specifies whether table-based or CAM-based classification criteria is used for the access ingress QoS policy. The classification-criteria value cannot be changed when the policy is associated with a port.

Dot1p classification and IP DSCP classification policy-based classification entries can be used when using table-based classification criteria.

IP criteria classification entries can be used when using CAM-based classification criteria.

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

Default

classification-criteria table-criteria

Parameters
classification-criteria

Specifies if table-based or CAM-based classification criteria is used for the access ingress QoS policy.

Values

cam-criteria, table-criteria

counter-mode
Syntax

counter-mode {in-out-profile-count | forward-drop-count}

no counter-mode

Context

config>qos>access-ingress

Platforms

7210 SAS-Mxp, 7210 SAS-R6, 7210 SAS-R12, 7210 SAS-Sx/S 1/10GE (standalone), and 7210 SAS-Sx 10/100GE (standalone)

Description

This command allows the user to set the counter mode for the counters associated with access port ingress meters (also known as policers). A pair of counters is available with each meter. These counters count different events based on the counter mode value.

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

Default

counter-mode in-out-profile-count

Parameters
in-out-profile-count

Specifies that the in-profile and out-profile packets and octets are counted per meter.

fwd-drop-count

Specifies that the forwarded and dropped packets and octets are counted per meter.

default-fc
Syntax

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

no default-fc

Context

config>qos>access-ingress

Platforms

7210 SAS-Mxp, 7210 SAS-R6, 7210 SAS-R12, 7210 SAS-Sx/S 1/10GE (standalone), and 7210 SAS-Sx 10/100GE (standalone)

Description

This command defines or edits the default forwarding class to be assigned to packets that do not match the explicitly configured classification entries. See the table-classification-criteria command for more information about configuring the default FC.

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

Default

default-fc be profile out

Parameters
fc-name

Specifies the forwarding class name.

Values

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

profile {in | out}

Specifies whether packets are in-profile or out-of-profile. All packets that are assigned to this forwarding class are considered in or out of profile based on which keyword is configured. A value of in defines the packet as being in-profile and a value of out defines the packet as being out-of-profile.

dot1p-classification
Syntax

dot1p-classification policy-id

no dot1p-classification

Context

config>qos>access-ingress

Platforms

7210 SAS-Mxp, 7210 SAS-R6, 7210 SAS-R12, 7210 SAS-Sx/S 1/10GE (standalone), and 7210 SAS-Sx 10/100GE (standalone)

Description

This command associates a dot1p classification policy with an access ingress QoS policy. See IP DSCP and dot1p classification policy support for more information about dot1p classification policies.

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

Default

dot1p-classification 1

Parameters
policy-id

Specifies the dot1p classification policy ID.

Values

1 to 65535

dscp-classification
Syntax

dscp-classification policy-id

no dscp-classification

Context

config>qos>access-ingress

Platforms

7210 SAS-Mxp, 7210 SAS-R6, 7210 SAS-R12, 7210 SAS-Sx/S 1/10GE (standalone), and 7210 SAS-Sx 10/100GE (standalone)

Description

This command associates a DSCP classification policy with an access ingress QoS policy. See IP DSCP and dot1p classification policy support for more information about dot1p classification policies.

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

Default

dscp-classification 1

Parameters
policy-id

Specifies the DSCP classification policy ID.

Values

1 to 65535

fc
Syntax

fc fc-name [create]

no fc fc-name

Context

config>qos>access-ingress

Platforms

7210 SAS-Mxp, 7210 SAS-R6, 7210 SAS-R12, 7210 SAS-Sx/S 1/10GE (standalone), and 7210 SAS-Sx 10/100GE (standalone)

Description

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

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

Default

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

Parameters
fc-name

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

Values

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

create

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

meter
Syntax

meter meter-id

no meter

Context

config>qos>access-ingress>fc

Platforms

7210 SAS-Mxp, 7210 SAS-R6, 7210 SAS-R12, 7210 SAS-Sx/S 1/10GE (standalone), and 7210 SAS-Sx 10/100GE (standalone)

Description

This command overrides the default unicast forwarding type meter mapping for fc fc-name. The specified meter ID must exist within the policy as a non-multipoint meter before the mapping can be made. After the FC mapping is applied, the meter ID is used to forward all unicast traffic that uses this policy on the port.

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

Default

meter 1

Parameters
meter-id

Specifies the meter ID, which must be an existing, non-multipoint meter defined in the config>qos>access-ingress context.

Values

1 to 16

multicast-meter
Syntax

multicast-meter meter-id

no multicast-meter

Context

config>qos>access-ingress>fc

Platforms

7210 SAS-Mxp, 7210 SAS-R6, 7210 SAS-R12, 7210 SAS-Sx/S 1/10GE (standalone), and 7210 SAS-Sx 10/100GE (standalone)

Description

This command overrides the default multicast forwarding type meter mapping for fc fc-name. The specified meter ID must exist within the policy as a multipoint meter before the mapping can be made. After the FC mapping is applied, the meter ID is used to forward all multicast traffic that uses this policy on the port.

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

Default

multicast-meter 9

Parameters
meter-id

Specifies the multicast meter, which must be an existing, multipoint meter defined in the config>qos>access-ingress context.

Values

1 to 16

ip-criteria
Syntax

ip-criteria [use-port-range]

no ip-criteria

Context

config>qos>access-ingress

Platforms

7210 SAS-Mxp

Description

This command creates or edits policy entries that specify an IP criteria (such as, IP DSCP, IP addresses, and so on.). IP criteria-based access ingress QoS policies are used to select the appropriate ingress meter and corresponding 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.

The no form of this command deletes all entries specified under this node. Once IP criteria entries are removed from an access ingress QoS policy, the IP criteria is removed from all services where that policy is applied.

Parameters
use-port-range

Specifies that classification entries are used to specify range values for TCP/UDP source and destination port fields, in addition to other IP criteria fields. If an IP criteria classification policy is created without this option, the filter entries can only use exact values for TCP/UDP source and destination port fields. By default, an IP criteria classification policy is created without the use-port-range option.

There are limited amount of unique port range values that can be used (see the tools>dump>system-resources command to know the current usage). The port range entries are shared among QoS and ACLs, along with source and destination port range values.

entry
Syntax

entry entry-id [create]

no entry entry-id

Context

config>qos>access-ingress>ip-criteria

Platforms

7210 SAS-Mxp

Description

This command creates or edits an IP 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 reclassification actions for the matching entries. 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 an entry-id 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 are rendered inactive.

Values

1 to 250

create

Keyword to create a flow entry when the system is configured. 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.

action
Syntax

action [fc fc]

no action

Context

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

Platforms

7210 SAS-Mxp

Description

This mandatory command associates the forwarding class with a specific IP 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 are 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 are lost.

Default

action specified by the default-fc

Parameters
fc

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

Values

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

match
Syntax

match [protocol protocol-id]

Context

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

Platforms

7210 SAS-Mxp

Description

This command configures match criteria for access ingress QoS policies. When the match criteria have been satisfied, the action associated with the match criteria is executed.

Parameters
protocol-id

Specifies an IP protocol used as an access ingress QoS policy match criterion.

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

Values

0 to 255

dscp
Syntax

dscp dscp-value | dscp-name [dscp-mask]

no dscp

Context

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

Platforms

7210 SAS-Mxp

Description

This command configures a DiffServ Code Point (DSCP) to be used for classification of packets from the specified FC.

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

Note:

  • Either the DSCP name or DSCP value with a mask can be configured.

  • When the user configures the dscp value alone, the show command displays the dscp value as the configured value and the dscp-mask as the FC.

Parameters
dscp-value

Specifies the DSCP value in hexadecimal, decimal, or binary format.

Values

0 to 63

dscp-name

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

Values

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

dscp-mask

Specifies a 6-bit mask that can be configured using the following formats:

Format Style Format Syntax Example

Decimal

D

4

Hexadecimal

0xH

0x4

Binary

0bBBB

0b100

To select a range from 4 up to 7, specify 4 and 0b000100 for value and mask.

Values

0 to 63 (decimal, hexadecimal, or binary)

Default

63 (exact match)

dst-ip
Syntax

dst-ip ip-address [ipv4-address-mask]

dst-ip ip-address/mask

no dst-ip

Context

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

Platforms

7210 SAS-Mxp

Description

This command configures a destination address range to be used as an access 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 also be used.

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

Parameters
ip-address

Specifies the IPv4 address of the destination IP. This address must be unique within the subnet and specified in dotted-decimal notation.

Values

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)

dst-port
Syntax

no dst-port

dst-port {eq} dst-port-number

dst-port {range} dst-port-number1 dst-port-number2

Context

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

Platforms

7210 SAS-Mxp

Description

This command configures a destination TCP or UDP port number or a range of port numbers for an access ingress QoS policy match criterion.

Note:
  • The IP criteria must be created with the use-port-range option to configure a range of port numbers.
  • A limited number of unique port range values are available for use (see the tools>dump>system-resources command for the current usage). The port range entries are shared among the QoS classification and ACL entries, and among source and destination port range values. The available entries in the hardware port range resource pool is allocated on a first come, first served basis. The following rules apply to the allocation of these port range pool entries:
    • One port range hardware entry is required to match a unique combination of port range values configured by the user. Two port range values (for example, port range 1024 to 2048 and port range 3050 to 3055) are considered to be unique if their range 1 and range 2 values do not match. Each unique port range value consumes one entry each in hardware.
    • Each unique port range entry requires two entries in the hardware table if it is used for both a source and destination match. In other words, a unique port range value requires one entry for matching a source port and another entry for matching a destination port.
    • If one or more QoS or ACL policy use the same unique port range value for either the source port match or destination port match but not both, only a single entry in the hardware table is required. For example, if port range 1000 to 2000 is used in both the access ingress policy and filter policy to match on source port, it requires one entry in the hardware port range table.
    • If one or more QoS and or ACL policy use the same unique port range value for both source port match and destination port, two entries in the hardware table are required. For example, if port range 1000 to 2000 is used in both access ingress policy and filter policy to match on both the source port and destination port, it requires two entries in the hardware port range table.

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 hex or binary)

range dst-port-number1

Specifies the first destination port number in the range to match a range of ports.

Values

1 to 65535 (decimal hex or binary)

range dst-port-number2

Specifies the last destination port number in the range to match a range of ports. The second number must be greater than the first number in the range.

Values

1 to 65535 (decimal hex or binary)

ip-prec
Syntax

ip-prec ip-prec-value [ip-prec-mask]

no ip-prec

Context

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

Platforms

7210 SAS-Mxp

Description

This command defines a specific IP precedence value that must be matched to perform the associated classification actions. If an ingress packet on the port where the access ingress QoS policy is applied to matches the specified IP precedence value, the actions associated with this entry are taken.

The ip-prec-value is derived from the most significant three bits in the IP header ToS byte field (precedence bits). The three precedence bits define eight Class-of-Service (CoS) values commonly used to map packets to per-hop QoS behavior. The precedence bits are also part of the newer DSCP method of mapping packets to QoS behavior. The DSCP uses the most significant six bits in the IP header ToS byte and so overlaps with the precedence bits.

Both IP precedence and DSCP classification rules are supported. A match entry cannot match on both IP DSCP and IP precedence values. That is, the user can use either an IP DSCP or IP precedence match in a match entry, but not both. The software blocks configuration of an IP precedence match if ip-dscp is configured already. The converse is also true. A single policy having multiple match entries can have entries so that some of them match IP DSCP and some others match IP precedence. The order of the entry determines the priority of the match.

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

Parameters
ip-prec-value

Specifies the unique IP header ToS byte precedence bits value that match the IP precedence rule.

Values

0 to 7

ip-prec-mask

Specifies the mask to use for the match.

Values

0 to 7

src-ip
Syntax

src-ip ip-address/mask

src-ip ip-address [ipv4-address-mask]

no src-ip

Context

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

Platforms

7210 SAS-Mxp

Description

This command configures a source IPv4 address range to be used as an access ingress QoS policy match criterion.

To match on the source IPv4 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.

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

Parameters
ip-address

Specifies the IPv4 address of the destination IP. This address must be unique within the subnet and specified in dotted-decimal notation.

Values

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)

src-port
Syntax

src-port {eq} src-port-number

src-port {range} src-port-number1 src-port-number2

no src-port

Context

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

Platforms

7210 SAS-Mxp

Description

This command configures a source TCP or UDP port number or a range of port numbers for an access ingress QoS policy match criterion.

Note:
  • The IP criteria must be created with the use-port-range option to configure a range of port numbers.
  • A limited number of unique port range values are available for use (see the tools>dump>system-resources command for the current usage). The port range entries are shared among the QoS classification and ACL entries, and among source and destination port range values. The available entries in the hardware port range resource pool is allocated on a first come, first served basis. The following rules apply to the allocation of these port range pool entries:
    • One port range hardware entry is required to match a unique combination of port range values configured by the user. Two port range values (for example, port range 1024 to 2048 and port range 3050 to 3055) are considered to be unique if their range 1 and range 2 values do not match. Each unique port range value consumes one entry each in hardware.
    • Each unique port range entry requires two entries in the hardware table if it is used for both a source and destination match. In other words, a unique port range value requires one entry for matching a source port and another entry for matching a destination port.
    • If one or more QoS or ACL policy use the same unique port range value for either the source port match or destination port match but not both, only a single entry in the hardware table is required. For example, if port range 1000 to 2000 is used in both the access ingress policy and filter policy to match on source port, it requires one entry in the hardware port range table.
    • If one or more QoS and or ACL policy use the same unique port range value for both source port match and destination port, two entries in the hardware table are required. For example, if port range 1000 to 2000 is used in both access ingress policy and filter policy to match on both the source port and destination port, it requires two entries in the hardware port range table.

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) the destination port value specified as a decimal integer.

Values

1 to 65535 (decimal hex or binary)

range src-port-number1

Specifies the first source port number in the range to match a range of ports.

Values

1 to 65535 (decimal hex or binary)

range src-port-number2

Specifies the last source port number in the range to match a range of ports. This value must be greater than the first value specified in the range command.

Values

1 to 65535 (decimal hex or binary)

renum
Syntax

renum old-entry-id new-entry-id

Context

config>qos>access-ingress>ip-criteria

Platforms

7210 SAS-Mxp

Description

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

This can be 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 ID of the existing QoS policy criteria entry.

Values

1 to 250

new-entry-id

Specifies the entry ID for the new QoS policy criteria entry.

Values

1 to 250

meter
Syntax

meter meter-id [create] [multi-point]

no meter meter-id

Context

config>qos>access-ingress

Platforms

7210 SAS-Mxp, 7210 SAS-R6, 7210 SAS-R12, 7210 SAS-Sx/S 1/10GE (standalone), and 7210 SAS-Sx 10/100GE (standalone)

Description

This command configures an access ingress QoS policy meter (also known as a policer). The meter command allows the creation of unicast and multipoint meters.

A meter can be shared by multiple FCs, but the unicast and multicast traffic of an FC cannot share the same meter. That is, two or more FCs can share the same unicast and multicast meter for unicast and multicast traffic, but a minimum of 2 meters are required; one for unicast traffic and another for multicast traffic.

Multipoint meters receive ingress packets destined for multiple destinations, and handle traffic bound to these destinations. In non-multipoint services, such as Epipe services, all traffic is considered unicast because of the nature of the service type. Multicast and broadcast-destined traffic in an Epipe service is not mapped to a multipoint service meter.

The no form of this command removes the meter ID from the access ingress QoS policy and from existing ports that use the policy. If any forwarding class forwarding types are mapped to the meter, they revert to their default meters. When a meter is removed, pending accounting information for each port meter created when the meter is defined in the policy is discarded.

Default

meter 1 (for unicast traffic)

meter 9 multipoint (for traffic other than unicast traffic)

Parameters
meter-id

Specifies the meter ID that uniquely identifies the meter within the policy. This is a required parameter and must be specified each time the meter command is run.

Values

1 to 16

multipoint

Specifies that the defined meter-id is for multipoint forwarded traffic only. This meter-id can only be explicitly mapped to the forwarding class multicast, broadcast, or unknown unicast ingress traffic. Attempting to map forwarding class unicast traffic to a multipoint meter causes the system to generate an error and the current unicast traffic meter mapping is unchanged.

A meter must be defined as multipoint when it is created using the create keyword. Applying the keyword after the meter is created is not allowed. Attempting to modify the command to include the multipoint keyword will cause the system to generate an error and the command will not execute.

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

create

Keyword to create a meter.

adaptation-rule
Syntax

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

no adaptation-rule

Context

config>qos>access-ingress>meter

Platforms

7210 SAS-Mxp, 7210 SAS-R6, 7210 SAS-R12, 7210 SAS-Sx/S 1/10GE (standalone), and 7210 SAS-Sx 10/100GE (standalone)

Description

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

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

Default

adaptation-rule cir closest pir closest

Parameters
cir adaptation-rule

Specifies the adaptation rule and defines the constraints enforced to adapt the CIR rate defined using the meter meter-id rate command. The cir parameter requires a qualifier that defines the constraint used to derive the operational CIR rate for the meter. When the cir command is not specified, the default constraint applies. The max (maximum), min (minimum), and closest qualifiers are mutually exclusive. See Supported hardware rates and burst step sizes for CIR and PIR values on the 7210 SAS-Mxp, 7210 SAS-R6, 7210 SAS-R12, 7210 SAS-Sx/S 1/10GE, and 7210 SAS-T for information about supported hardware step-size rates.

Default

closest

Values

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

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

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

pir adaptation-rule

Specifies the adaptation rule and defines the constraints enforced to adapt the PIR 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. See Supported hardware rates and burst step sizes for CIR and PIR values on the 7210 SAS-Mxp, 7210 SAS-R6, 7210 SAS-R12, 7210 SAS-Sx/S 1/10GE, and 7210 SAS-T for information about supported hardware step-size rates.

Default

closest

Values

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

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

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

cbs
Syntax

cbs size [kbits | bytes | kbytes]

no cbs

Context

config>qos>access-ingress>meter

Platforms

7210 SAS-Mxp, 7210 SAS-R6, 7210 SAS-R12, 7210 SAS-Sx/S 1/10GE (standalone), and 7210 SAS-Sx 10/100GE (standalone)

Description

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

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

Default

cbs 32 kbits

Parameters
size

Specifies the size as an integer expression of the number of kilobits or kilobytes or bytes reserved for the meter. For example, if a value of 100 kbits is required, enter the value 100. The bucket size is rounded off to the next highest 4096 bytes boundary. The value can be specified in kilobits, kilobytes, or bytes.

Values

kbits — 4 to 2146959, default

bytes — 512 to 274810752, default

kbytes — 1 to 268369, default

color-mode
Syntax

color-mode {color-aware | color-blind}

no color-mode

Context

config>qos>access-ingress>meter

Platforms

7210 SAS-Mxp, 7210 SAS-R6, 7210 SAS-R12, 7210 SAS-Sx/S 1/10GE (standalone), and 7210 SAS-Sx 10/100GE (standalone)

Description

This command specifies whether the meter will operate in the color-aware or color-blind mode.

In color-blind mode, the profile and color assigned to the packet on ingress is ignored. The CIR and PIR rate configured for the meter is used to determine the final color and profile for the packet. If the packet is within the CIR, then the final profile and color assigned to the packet is in-profile and green. If the packet exceeds the CIR and is within the PIR, then the final profile and color assigned to the packet is out-of-profile and yellow. Packets that exceed the PIR rate are dropped.

In color-aware mode, the meter uses the profile assigned to the packet on ingress. The ingress profile can be assigned to the packet using either dot1p, DEI configured with dot1p, or IP DSCP values from the packet header.

In color-aware mode, the following behavior is expected.

  • If the packet is pre-colored as an ‟in-profile” packet (also called ‟green” packets), depending on the burst size of the packet, the meter can mark the packet in-profile or out-profile.

  • If the packet is pre-colored as an ‟out-profile” packet (which are also called ‟yellow” packets), even if the packet burst is less than the current available CBS, it would not be marked as in-profile and remain as out-profile.

  • If the packet burst is higher than the MBS, it is marked as ‟red” and dropped by the meter at ingress.

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

Default

color-mode color-aware

Parameters
color-aware

Specifies that the meter will operate in color-aware mode.

color-blind

Specifies that the meter will operate in color-blind mode.

mbs
Syntax

mbs size [kbits | bytes | kbytes]

no mbs

Context

config>qos>access-ingress>meter

Platforms

7210 SAS-Mxp, 7210 SAS-R6, 7210 SAS-R12, 7210 SAS-Sx/S 1/10GE (standalone), and 7210 SAS-Sx 10/100GE (standalone)

Description

This command provides a mechanism to override the default MBS for the meter. The Maximum Burst Size (MBS) value 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 configured MBS value, the packets are marked as in-profile by the meter to indicate that the traffic is complying meter configured parameters.

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

Default

512 kbits

Parameters
size

Specifies the size as integer expression of the number of kilobits reserved for the meter. For example, if a value of 100 KBits is required, enter the value 100. The bucket size is rounded off to the next highest 4096 bytes boundary.

Values

kbits — 4 to 2146959, default

bytes — 512 to 274810752, default

kbytes — 1 to 268369, default

mode
Syntax

mode {trtcm1 | trtcm2 | srtcm}

no mode

Context

config>qos>access-ingress>meter

Platforms

7210 SAS-Mxp, 7210 SAS-R6, 7210 SAS-R12, 7210 SAS-Sx/S 1/10GE (standalone), and 7210 SAS-Sx 10/100GE (standalone)

Description

This command defines the mode of the meter. The mode can be configured as trtcm1, trtcm2, or srtcm. The mode command can be run at any time.

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

Default

mode trtcm1

Parameters
trtcm1

Keyword to implement the policing algorithm defined in RFC2698. Meters a packet stream and marks its packets either green, yellow, or red. A packet is marked red 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 trTCM1 is useful, for example, for ingress policing of a service, where a peak rate needs to be enforced separately from a committed rate.

trtcm2

Keyword to implement the policing algorithm defined in RFC4115. Meters a packet stream and marks its packets either green, yellow, or red. A packet is marked red 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 is useful, for example, for ingress policing of a service, where a peak rate needs to be enforced separately from a committed rate.

srtcm

Keyword to implement the policing algorithm defined in RFC2697. 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 MBS. A packet is marked green if it does not exceed the CBS, yellow if it exceeds the CBS but not the CIR, and red otherwise. The srTCM is useful, for example, for ingress policing of a service, where only the length, not the peak rate, of the burst determines service eligibility.

rate
Syntax

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

no rate

Context

config>qos>access-ingress>meter

Platforms

7210 SAS-Mxp, 7210 SAS-R6, 7210 SAS-R12, 7210 SAS-Sx/S 1/10GE (standalone), and 7210 SAS-Sx 10/100GE (standalone)

Description

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

The rate command can be run at any time, altering the PIR and CIR rates for all meters created through the association of the network QoS policy with the meter ID.

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

Note:

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

Default

rate 0 pir max

Parameters
cir cir-rate-in-kbps

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

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

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

Values

0 to 40000000, max (7210 SAS-Sx/S 1/10GE)

0 to 64000000, max (7210 SAS-Mxp)

0 to 400000000, max (7210 SAS-Sx 10/100GE)

0 to 100000000, max (7210 SAS-R6 and 7210 SAS-R12)

Default

0

pir pir-rate-in-kbps

Specifies the administrative PIR rate, in kilobits, for the meter. When this parameter is configured, a valid PIR setting must be explicitly defined. If the rate command has not been run, the default PIR of max is assumed. If the rate command is run, a PIR setting is optional. The max default specifies the amount of bandwidth in kilobits per second (thousand bits per second). The max value is mutually exclusive to the pir pir-rate-in-kbps value.

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

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

Note:

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

Values

0 to 40000000, max (7210 SAS-Sx/S 1/10GE)

0 to 64000000, max (7210 SAS-Mxp)

0 to 400000000, max (7210 SAS-Sx 10/100GE)

0 to 100000000, max (7210 SAS-R6 and 7210 SAS-R12)

Default

max

num-qos-classifiers
Syntax

num-qos-classifiers num-resources

no num-qos-classifiers

Context

config>qos>access-ingress

Platforms

7210 SAS-Mxp, 7210 SAS-R6, 7210 SAS-R12, 7210 SAS-Sx/S 1/10GE (standalone), and 7210 SAS-Sx 10/100GE (standalone)

Description

This command configures the number of CAM meter or policer resources that are allocated to rate-limit the forwarding class (FC) and classification entries to map the FC and traffic type to the configured meter. The maximum number of meters available for use by the FC defined under the policy is equal to half the value specified for the num-resources parameter. These meters are available for policing unicast or multipoint traffic, and for use by more than one FC.

Note:

  • A user cannot modify the num-resources parameter when it is in use (that is, when the policy is applied to the port). To modify the meter or policer resources available for the policy, remove the association of the policy with the port, change the parameter to the desired value, and associate the policy with the port again.

  • See section Resource allocation for non-shared access ingress QoS policies for information about resource allocation for access ingress QoS policies.

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

Default

num-qos-classifiers 4

Parameters
num-resources

Specifies the number of resources planned for use by the configured access ingress policy, expressed as a multiple of 2.

Values

4 to 32

4 to 252 (only on the 7210 SAS-Mxp)

table-classification-criteria
Syntax

table-classification-criteria table-classification-criteria

Context

config>qos>access-ingress

Platforms

7210 SAS-Mxp, 7210 SAS-R6, 7210 SAS-R12, 7210 SAS-Sx/S 1/10GE (standalone), and 7210 SAS-Sx 10/100GE (standalone)

Description

This command allows the user to choose the classification policies to classify traffic to an FC when table-based classification is in use.

The following options can be used to configure the classification policy.

  • If the none option is configured

    • use default-fc fc-name profile {in | out} (from the access ingress policy)

  • If the use-dscp option is configured

    • use the DSCP classification policy for IP packets

    • use default-fc fc-name profile {in | out} (from the access ingress policy) for non-IP packets

  • If the use-dot1p option is configured

    • use the dot1p classification policy for all tagged packets (IP and non-IP)

    • use default-fc fc-name profile {in | out} (from the access ingress policy) for untagged packets

  • If the both-dscp-dot1p option is configured

    • use the DSCP classification policy for IP packets

    • use the dot1p classification policy for non-IP tagged packets

    • use default-fc fc-name profile {in | out} (from the access ingress policy) for non-IP untagged traffic

Default

table-classification-criteria both-dscp-dot1p

Parameters
table-classification-criteria

Specifies the table classification criteria to use.

Values

use-dscp, use-dot1p, both-dscp-dot1p, none

Show commands

access-ingress
Syntax

access-ingress [policy-id] association

access-ingress [policy-id] [detail]

Context

show>qos

Platforms

7210 SAS-Mxp

Description

This command displays access ingress QoS policy information.

Parameters
policy-id

Displays information for the specified existing access ingress QoS policy.

association

Displays associations related to the access ingress QoS policy.

detail

Displays detailed access ingress QoS policy information.

Output

The following outputs are examples of access ingress QoS policy information, and and the associated table describes the output fields:

Sample output (shared access ingress QoS policy 61)
Note: For conciseness, some classificaiton entries have been removed.
*A:Mxp# show qos access-ingress 61 

===============================================================================
QoS Access Ingress
===============================================================================
-------------------------------------------------------------------------------
Access Ingress Policy (61)
-------------------------------------------------------------------------------
Policy-id           : 61            Counter Mode         : forward-drop-count
Default FC          : ef            Profile              : In
DSCP Class Policy Id: 11            DOT1P Class Policy Id: 11
Share resources     : True          Classification crite*: cam
Table Classification criteria : both-dscp-dot1p
Description         : (Not Specified)
Criteria Type       : IP
Classifiers Allowed : 132           Meters Allowed       : 16
 
-------------------------------------------------------------------------------
Table-based Resource Requirement
-------------------------------------------------------------------------------
Classifiers Reqrd   : 9             Meters Reqrd         : 8 
 
-------------------------------------------------------------------------------
Cam-based Resource Requirement
-------------------------------------------------------------------------------
Classifiers Reqrd   : 31            Meters Reqrd         : 2 
 
===============================================================================
* indicates that the corresponding row element may have been truncated.
 
*A:Mxp# show qos access-ingress 61 detail 

===============================================================================
QoS Access Ingress
===============================================================================
-------------------------------------------------------------------------------
Access Ingress Policy (61)
-------------------------------------------------------------------------------
Policy-id           : 61            Counter Mode         : forward-drop-count
Default FC          : ef            Profile              : In
DSCP Class Policy Id: 11            DOT1P Class Policy Id: 11
Share resources     : True          Classification crite*: cam
Table Classification criteria : both-dscp-dot1p
Description         : (Not Specified)
Criteria Type       : IP
Classifiers Allowed : 132           Meters Allowed       : 16
 
-------------------------------------------------------------------------------
Table-based Resource Requirement
-------------------------------------------------------------------------------
Classifiers Reqrd   : 9             Meters Reqrd         : 8 
 
-------------------------------------------------------------------------------
Cam-based Resource Requirement
-------------------------------------------------------------------------------
Classifiers Reqrd   : 31            Meters Reqrd         : 2 
 
-------------------------------------------------------------------------------
Meter Mode        CIR Admin CIR Rule PIR Admin PIR Rule CBS Admin MBS Admin
      Color Mode  CIR Oper           PIR Oper           CBS Oper  MBS Oper 
-------------------------------------------------------------------------------
1     SrTcm       80000     closest  -         closest  5120 kbytes 5120 kbytes
      color-aware 80000              -                  5000 kbytes 5000 kbytes
2     SrTcm       81000     closest  -         closest  10024 kbyt* 10024 kbyt*
      color-aware 81024              -                  9792 kbytes 9792 kbytes
3     SrTcm       82000     closest  -         closest  4096 kbits  4096 kbits
      color-aware 82000              -                  4000 kbits  4000 kbits
4     TrTcm1      50000     closest  83000     closest  100000 byt* 200000 byt*
      color-aware 50000              83000              97792 bytes 195584 byt*
5     TrTcm1      45000     closest  84000     closest  250000 kbi* 250000 kbi*
      color-blind 45056              83968              244160 kbi* 244160 kbi*
6     TrTcm1      55000     closest  85000     closest  90000 kbits 10000 kbits
      color-blind 54976              85000              87904 kbits 9768 kbits
7     TrTcm1      56000     closest  86000     closest  80000 bytes 90000 bytes
      color-aware 56000              86000              78336 bytes 88064 bytes
8     TrTcm2      37000     closest  50000     closest  8092 kbytes 9012 kbytes
      color-aware 36992              49984              7904 kbytes 8804 kbytes
9     TrTcm2      37000     closest  51000     closest  10024 kbits 10082 kbits
      color-aware 37000              51000              9792 kbits  9848 kbits
10    TrTcm2      37000     closest  52000     closest  def kbits   def kbits
      color-aware 37000              52000              32 kbits    1000 kbits
11    TrTcm1      38000     closest  90000     closest  20048 kbits 40048 kbits
      color-aware 38000              90016              19584 kbits 39120 kbits
12    TrTcm2      45000     closest  46000     closest  2100000 by* 2100000 by*
      color-aware 45000              46000              2051072 by* 2051072 by*
13    TrTcm1      45000     closest  92000     closest  9000 kbits  9000 kbits
      color-aware 45000              92000              8792 kbits  8792 kbits
14    TrTcm1      50000     closest  93000     closest  10000 kbits 10000 kbits
      color-aware 50000              93000              9768 kbits  9768 kbits
15    TrTcm1      51000     closest  94000     closest  def kbits   def kbits
      color-aware 51000              94000              32 kbits    1000 kbits
16    TrTcm2      52000     closest  43000     closest  100034 byt* 100044 kby*
      color-aware 52000              43008              97792 bytes 97728 kbyt*
 
-------------------------------------------------------------------------------
FC        UCastM      MCastM         
-------------------------------------------------------------------------------
be        2           def
l2        7           def
af        def         def
l1        6           def
h2        5           def
ef        3           def
h1        4           def
nc        8           def
 
-------------------------------------------------------------------------------
Port Attachments
-------------------------------------------------------------------------------
Port-id : 1/1/12
Port-id : 1/1/13                      
Port-id : 1/1/14
Port-id : lag-1
-------------------------------------------------------------------------------
Match Criteria
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
IP Match Criteria
-------------------------------------------------------------------------------
Entry               : 1             
Description         : (Not Specified)
Source IP           : Undefined
Dest. IP            : Undefined
Source Port         : None          Dest. Port           : None
Protocol            : none          DSCP                 : None
FC                  : af            Ip Precedence        : None


===============================================================================
* indicates that the corresponding row element may have been truncated.
Sample output (shared access ingress QoS policy 65536)
*A:Mxp# show qos access-ingress 65536        

===============================================================================
QoS Access Ingress
===============================================================================
-------------------------------------------------------------------------------
Access Ingress Policy (65536)
-------------------------------------------------------------------------------
Policy-id           : 65536         Counter Mode         : in-out-profile-count
Default FC          : be            Profile              : Out
DSCP Class Policy Id: 1             DOT1P Class Policy Id: 1
Share resources     : True          Classification crite*: table
Table Classification criteria : both-dscp-dot1p
Description         : Default ACCESS ingress shared QoS policy.
Criteria Type       : None
Classifiers Allowed : 2             Meters Allowed       : 1
 
-------------------------------------------------------------------------------
Table-based Resource Requirement
-------------------------------------------------------------------------------
Classifiers Reqrd   : 2             Meters Reqrd         : 1 
 
-------------------------------------------------------------------------------
Cam-based Resource Requirement
-------------------------------------------------------------------------------
Classifiers Reqrd   : 1             Meters Reqrd         : 1 
 
===============================================================================
* indicates that the corresponding row element may have been truncated.


*A:Mxp# show qos access-ingress 65536 detail 

===============================================================================
QoS Access Ingress
===============================================================================
-------------------------------------------------------------------------------
Access Ingress Policy (65536)
-------------------------------------------------------------------------------
Policy-id           : 65536         Counter Mode         : in-out-profile-count
Default FC          : be            Profile              : Out
DSCP Class Policy Id: 1             DOT1P Class Policy Id: 1
Share resources     : True          Classification crite*: table
Table Classification criteria : both-dscp-dot1p
Description         : Default ACCESS ingress shared QoS policy.
Criteria Type       : None
Classifiers Allowed : 2             Meters Allowed       : 1
 
-------------------------------------------------------------------------------
Table-based Resource Requirement
-------------------------------------------------------------------------------
Classifiers Reqrd   : 2             Meters Reqrd         : 1 
 
-------------------------------------------------------------------------------
Cam-based Resource Requirement
-------------------------------------------------------------------------------
Classifiers Reqrd   : 1             Meters Reqrd         : 1 
 
-------------------------------------------------------------------------------
Meter Mode        CIR Admin CIR Rule PIR Admin PIR Rule CBS Admin MBS Admin
      Color Mode  CIR Oper           PIR Oper           CBS Oper  MBS Oper 
-------------------------------------------------------------------------------
1     TrTcm1      0         closest  max       closest  def kbits   def kbits
      color-aware 0                  64000000           32 kbits    1024 kbits
 
 
-------------------------------------------------------------------------------
FC        UCastM      MCastM         
-------------------------------------------------------------------------------
No FC-Map Entries Found.
 
                                      
-------------------------------------------------------------------------------
Port Attachments
-------------------------------------------------------------------------------
Port-id : 1/1/2
Port-id : 1/1/10
Port-id : 1/1/11
Port-id : lag-20
-------------------------------------------------------------------------------
Match Criteria
-------------------------------------------------------------------------------
No Matching Criteria.

===============================================================================
* indicates that the corresponding row element may have been truncated.
Sample output (non-shared access ingress QoS policy 1)
*A:Mxp# show qos access-ingress 1

===============================================================================
QoS Access Ingress
===============================================================================
-------------------------------------------------------------------------------
Access Ingress Policy (1)
-------------------------------------------------------------------------------
Policy-id           : 1             Counter Mode         : in-out-profile-count
Default FC          : be            Profile              : Out
DSCP Class Policy Id: 1             DOT1P Class Policy Id: 1
Share resources     : False         Classification crite*: table
Table Classification criteria : both-dscp-dot1p
Description         : Default ACCESS ingress QoS policy.
Criteria Type       : None
Classifiers Allowed : 4             Meters Allowed       : 2

-------------------------------------------------------------------------------
Access Ingress Resource Requirement
-------------------------------------------------------------------------------
Filters Reqrd       : 4             Meters Reqrd         : 2

===============================================================================
* indicates that the corresponding row element may have been truncated.
Table 1. Output fields: access ingress QoS policy (shared and non-shared)
Label Description

Policy-Id

Displays the ID of the policy

Counter Mode

in-out-profile-count — Displays the in-profile and out-profile packet count per meter

forward-drop-count — Displays the forwarded and dropped packets count per meter

Default FC

Displays the default FC for the policy

Profile

Displays the profile configured

DSCP Class Policy Id

Displays the DSCP classification policy ID

DOT1P Class Policy Id

Displays the dot1p classification policy ID

Share Resources

true — Policy is configured to share resources

false — Policy is not configured to share resources

Classification criteria

cam — Policy is configured with CAM-based classification criteria

table — Policy is configured with table-based classification criteria

Table classification criteria

Displays the table classification criteria used for the policy

Description

Description of the policy

Criteria Type

Displays the type of cam-criteria configured (for exmaple, IP criteria).

Classifiers Allowed

Displays the number of classifiers allowed for the policy

Meters Allowed

Displays the number of meters allowed for the policy

Meter

Displays the meter ID

Mode

Displays the configured mode of the meter (trTcm1 or srTcm)

Color Mode

Displays the color mode of the meter (color-blind or color-aware)

CIR Admin

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

CIR Oper

Displays the operational Committed Information Rate (CIR) parameters for the meters

CIR Rule

min — Operational CIR for the meters is equal to or greater than the administrative rate specified using the rate command

max — Operational CIR for the meter is equal to or less than the administrative rate specified using the rate command

closest — Operational PIR for the meters are the rate closest to the rate specified using the rate command, without exceeding the operational PIR

PIR Admin

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

PIR Oper

Displays the operational PIR parameters for the meter

PIR Rule

min — Operational PIR for the meter is equal to or greater than the administrative rate specified using the rate command

max — Operational PIR for the meters is equal to or less than the administrative rate specified using the rate command

closest — Operational PIR for the meters is the rate closest to the rate specified using the rate command

CBS Admin

CBS Oper

def — Displays the default CBS value for the meters

value — Displays the value to override the default CBS for the meters

MBS Admin

MBS Oper

def — Displays the default MBS value

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

FC

Displays the forwarding class

UCastM

Displays the default unicast forwarding type meter mapping

MCastM

Displays the overrides for the default multicast forwarding type meter mapping

Entry

Displays the entry number for the IP match criteria

Source IP

Displays the source IP address for the IP match criteria

Dest. IP

Displays the destination IP address for the IP match criteria

Source Port

Displays the source port for the IP match criteria

Dest. Port

Displays the destination port for the IP match criteria

Protocol

Displays the protocol for the IP match criteria

DSCP

Displays the DSCP for the IP match criteria

FC

Displays the FC for the IP match criteria

IP Precedence

Displays the IP precedence for the IP match criteria