Access ingress QoS policies
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.
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.
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.
Resource allocation for 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.
Use of 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. 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.
The index file used for the QoS map is different from the file used for storing interface indexes.
Calculating the number of QoS resources
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.
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
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.
Determining the number of resources allocated to the policy
The user must determine the value for the config qos access-ingress num-qos-classifiers command using the following formula.
See sections Calculating the number of QoS resources and Calculating the number of meters or policers for information about determining the values for TC and TP respectively.
Example of access ingress QoS policy resource calculations
The following sections describe example calculations for an 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.
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
Configuration guidelines for using a port-based access ingress QoS policy
Use the following guidelines to configure a port-based access ingress QoS policy on the 7210 SAS-Mxp:
Delete all SAPs on the port or the LAG before changing 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:
Reboot the node in sap-scale-mode high.
Ensure that resources are allocated to qos-access-ingress-resource.
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. 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.
Resource allocation from qos-access-port-ingress-resource has no restrictions. Resources can be allocated in sap-scale-mode low and high; however, allocating resources in sap-scale-mode low wastes resources because an access ingress QoS policy can only be attached in sap-scale-mode high.
Reset the user-defined access ingress QoS policy to 1 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 on the primary LAG member before changing the access-ingress-qos-mode command to sap-mode.
Basic configurations
A basic access ingress QoS policy must conform to the following configurations:
The policy must have a unique access ingress QoS policy ID.
The policy can have meters defined for use with meter parameters specified, such as CIR and PIR.
The policy can have a dot1p and DSCP template attachment to map dot1p and IP DSCP values to the FC.
The policy has an optional configuration to choose either 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 an 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.
Perform the following to prevent configuration errors:
Copy the policy to a work area.
Edit the policy.
Overwrite the original policy.
The num-resources parameter value for the config>qos>access-ingress>num-qos-classifiers command cannot be modified when the policy is in use.
Removing a 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 access ingress QoS policies
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.
The access-ingress-qos-mode command can only be changed to sap-mode if access ingress policy 1 is attached to the port.
Access-ingress QoS policy command reference
Command hierarchies
Access-ingress QoS configuration commands
config
- qos
- access-ingress policy-id [create]
- no access-ingress policy-id
- 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
- 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 [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
Parameters
- policy-id
Specifies the access-ingress policy ID.
- create
Keyword to create an access-ingress policy. The create keyword requirement can be enabled or disabled in the environment>create context.
description
Syntax
description description-string
no description
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 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
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.
- 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.
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.
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.
- 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.
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.
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.
- 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.
- 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.
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.
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.
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).
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.
- 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.
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.
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 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.
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.