counter-mode {in-out-profile-count | forward-drop-count}
no counter-mode
config>qos>access-ingress
7210 SAS-Mxp, 7210 SAS-R6, 7210 SAS-R12, 7210 SAS-Sx/S 1/10GE (standalone), and 7210 SAS-Sx 10/100GE (standalone)
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.
counter-mode in-out-profile-count
Specifies that the in-profile and out-profile packets and octets are counted per meter.
Specifies that the forwarded and dropped packets and octets are counted per meter.
default-fc fc-name profile {in | out}
no default-fc
config>qos>access-ingress
7210 SAS-Mxp, 7210 SAS-R6, 7210 SAS-R12, 7210 SAS-Sx/S 1/10GE (standalone), and 7210 SAS-Sx 10/100GE (standalone)
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-fc be profile out
Specifies the forwarding class name.
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 policy-id
no dot1p-classification
config>qos>access-ingress
7210 SAS-Mxp, 7210 SAS-R6, 7210 SAS-R12, 7210 SAS-Sx/S 1/10GE (standalone), and 7210 SAS-Sx 10/100GE (standalone)
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.
dot1p-classification 1
Specifies the dot1p classification policy ID.
dscp-classification policy-id
no dscp-classification
config>qos>access-ingress
7210 SAS-Mxp, 7210 SAS-R6, 7210 SAS-R12, 7210 SAS-Sx/S 1/10GE (standalone), and 7210 SAS-Sx 10/100GE (standalone)
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.
dscp-classification 1
Specifies the DSCP classification policy ID.
fc fc-name [create]
no fc fc-name
config>qos>access-ingress
7210 SAS-Mxp, 7210 SAS-R6, 7210 SAS-R12, 7210 SAS-Sx/S 1/10GE (standalone), and 7210 SAS-Sx 10/100GE (standalone)
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.
Undefined forwarding classes default to the configured parameters in the default policy policy-id 1.
Specifies the case-sensitive, system-defined FC name for which policy entries will be created.
Keyword to create the forwarding class. The create keyword requirement can be enabled or disabled in the environment>create context.
meter meter-id
no meter
config>qos>access-ingress>fc
7210 SAS-Mxp, 7210 SAS-R6, 7210 SAS-R12, 7210 SAS-Sx/S 1/10GE (standalone), and 7210 SAS-Sx 10/100GE (standalone)
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.
meter 1
Specifies the meter ID, which must be an existing, non-multipoint meter defined in the config>qos>access-ingress context.
multicast-meter meter-id
no multicast-meter
config>qos>access-ingress>fc
7210 SAS-Mxp, 7210 SAS-R6, 7210 SAS-R12, 7210 SAS-Sx/S 1/10GE (standalone), and 7210 SAS-Sx 10/100GE (standalone)
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.
multicast-meter 9
Specifies the multicast meter, which must be an existing, multipoint meter defined in the config>qos>access-ingress context.
meter meter-id [create] [multi-point]
no meter meter-id
config>qos>access-ingress
7210 SAS-Mxp, 7210 SAS-R6, 7210 SAS-R12, 7210 SAS-Sx/S 1/10GE (standalone), and 7210 SAS-Sx 10/100GE (standalone)
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.
meter 1 (for unicast traffic)
meter 9 multipoint (for traffic other than unicast traffic)
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.
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.
Keyword to create a meter.
adaptation-rule [cir adaptation-rule] [pir adaptation-rule]
no adaptation-rule
config>qos>access-ingress>meter
7210 SAS-Mxp, 7210 SAS-R6, 7210 SAS-R12, 7210 SAS-Sx/S 1/10GE (standalone), and 7210 SAS-Sx 10/100GE (standalone)
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.
adaptation-rule cir closest pir closest
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 Table: 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.
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 Table: 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 size [kbits | bytes | kbytes]
no cbs
config>qos>access-ingress>meter
7210 SAS-Mxp, 7210 SAS-R6, 7210 SAS-R12, 7210 SAS-Sx/S 1/10GE (standalone), and 7210 SAS-Sx 10/100GE (standalone)
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.
cbs 32 kbits
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 {color-aware | color-blind}
no color-mode
config>qos>access-ingress>meter
7210 SAS-Mxp, 7210 SAS-R6, 7210 SAS-R12, 7210 SAS-Sx/S 1/10GE (standalone), and 7210 SAS-Sx 10/100GE (standalone)
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.
color-mode color-aware
Specifies that the meter will operate in color-aware mode.
Specifies that the meter will operate in color-blind mode.
mbs size [kbits | bytes | kbytes]
no mbs
config>qos>access-ingress>meter
7210 SAS-Mxp, 7210 SAS-R6, 7210 SAS-R12, 7210 SAS-Sx/S 1/10GE (standalone), and 7210 SAS-Sx 10/100GE (standalone)
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.
512 kbits
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 {trtcm1 | trtcm2 | srtcm}
no mode
config>qos>access-ingress>meter
7210 SAS-Mxp, 7210 SAS-R6, 7210 SAS-R12, 7210 SAS-Sx/S 1/10GE (standalone), and 7210 SAS-Sx 10/100GE (standalone)
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.
mode 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.
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.
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 cir cir-rate-in-kbps [pir pir-rate-in-kbps]
no rate
config>qos>access-ingress>meter
7210 SAS-Mxp, 7210 SAS-R6, 7210 SAS-R12, 7210 SAS-Sx/S 1/10GE (standalone), and 7210 SAS-Sx 10/100GE (standalone)
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.
rate 0 pir max
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.
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.
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 num-resources
no num-qos-classifiers
config>qos>access-ingress
7210 SAS-Mxp, 7210 SAS-R6, 7210 SAS-R12, 7210 SAS-Sx/S 1/10GE (standalone), and 7210 SAS-Sx 10/100GE (standalone)
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.
num-qos-classifiers 4
Specifies the number of resources planned for use by the configured access-ingress policy, expressed as a multiple of 2.
table-classification-criteria table-classification-criteria
config>qos>access-ingress
7210 SAS-Mxp, 7210 SAS-R6, 7210 SAS-R12, 7210 SAS-Sx/S 1/10GE (standalone), and 7210 SAS-Sx 10/100GE (standalone)
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
table-classification-criteria both-dscp-dot1p
Specifies the table classification criteria to use.