18.3. Access-Ingress QoS Policy Command Reference

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

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

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.

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.

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.

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.

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.

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.

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.

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.

This command enables the context to configure 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 due to 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.

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.

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.

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.

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

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.

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.

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.

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

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.