A through C

To configure an access list for use with committed access rate (CAR) policies, use the access-listrate-limitcommand in global configuration mode. To remove the access list from the configuration, use the no form of this command.

Syntax Description

Command Default

No CAR access lists are configured.

Command Modes

Global configuration

Command History

Usage Guidelines

Use this command to classify packets by the specified IP precedence, MAC address, or MPLS experimental field values for a particular CAR access list. You can then apply CAR policies, using the rate-limit command, to individual rate-limit access lists. When packets in an access list are classified in this manner, the packets with different IP precedences, MAC addresses, or MPLS experimental field values are treated differently by the CAR process.

You can specify only one command for each rate-limit access list. If you enter this command multiple times using the same access list number, the new command overwrites the previous command.

Use the mask keyword to assign multiple IP precedences or MPLS experimental field values to the same rate-limit list. To ascertain the mask value, perform the following steps.

1. Decide which precedences you want to assign to this rate-limit access list.
2. Convert the precedences or MPLS experimental field values into 8-bit numbers with each bit corresponding to one value. For example, an MPLS experimental field value of 0 corresponds to 00000001; 1 corresponds to 00000010; 6 corresponds to 01000000; and 7 corresponds to 10000000.
3. Add the 8-bit numbers for the selected MPLS experimental field values. For example, the mask for MPLS experimental field values 1 and 6 is 01000010.
4. The access-listrate-limit command expects hexadecimal format. Convert the binary mask into the corresponding hexadecimal number. For example, 01000010 becomes 42 and is used in the command. Any packets that have an MPLS experimental field value of 1 or 6 will match this access list.

A mask of FF matches any precedence, and 00 does not match any precedence.

Related Commands

To enable collection of statistics for packets matching the traffic class where this command is configured, use the account command in policy-map class configuration mode. To disable statistics collection, use the no form of this command.

Syntax Description

Command Default

When the account command is configured, the default behavior is collection of drop statistics. No statistics are collected if the account command is not configured.

Command Modes

Policy-map class (config-pmap-c)

Command History

Usage Guidelines

The account command was implemented as part of the QoS: Policies Aggregation Enhancements feature in Cisco IOS XE Release 2.6 on the Cisco ASR 1000 Series Aggregation Services Routers to support the collection of per-subscriber statistics.

By default when configured, the command enables collection of drop statistics for traffic in the class where it is configured. Therefore, the optional drop keyword is not required to enable collection of drop statistics.

You can display the subscriber statistics collected for a certain traffic class using the showpolicy-mapinterface command.

Related Commands

To specify the QoS parameters associated with a particular ATM address, use the atm-address command in LANE QoS database configuration mode. To revert to the default value, use the no form of this command.

Syntax Description

Command Default

No default ATM address.

Command Modes

LANE QoS database configuration

Command History

Related Commands

To add attributes to an attribute profile, use the attribute command in attribute map configuration mode.

Syntax Description

Command Modes

Attribute map configuration (config-attribute-map)

Command History

Usage Guidelines

This command does not have a no form.

Related Commands

To begin discovering and collecting data for configuring the AutoQoS for the Enterprise feature, use the autodiscoveryqos command in interface configuration mode. To stop discovering and collecting data, use the no form of this command.

Syntax Description

Command Default

No data collection is performed.

Command Modes

Interface configuration

Command History

Usage Guidelines

The autodiscoveryqos command initiates the Auto-Discovery (data collection) phase of the AutoQoS for the Enterprise feature. This command invokes NBAR protocol discovery to collect data and analyze the traffic at the egress direction of the interface.

The noautodiscoveryqoscommand terminates the Auto-Discovery phase and removes any data collection reports generated.

The trust keyword is used for the trusted model based on the specified DSCP marking. For more information, see the "Trusted Boundary" section of the AutoQoS for the Enterprise feature module, Cisco IOS Release 12.3(7)T.

Related Commands

To install the quality-of-service (QoS) class maps and policy maps created by the AutoQoS for the Enterprise feature, use the autoqos command in interface configuration mode. To remove the QoS policies, use the no form of this command.

Syntax Description

This command has no arguments or keywords.

Command Default

No QoS policies are installed.

Command Modes

Interface configuration (config-if)

Command History

Usage Guidelines

The class maps and policy maps are created from the templates that are automatically generated by the AutoQoS for the Enterprise feature. These templates (and the resulting class maps and policy maps) are generated on the basis of the data collected during the Auto-Discovery phase of the AutoQoS for the Enterprise feature. For more information about the Auto-Discovery phase, see the "Configuration Phases" section of the AutoQoS for the Enterprise feature module, Cisco IOS Release 12.3(7)T.

The noautoqos command removes any AutoQoS-generated class maps and policy maps installed on the interface.

Theautoqos command is not supported on gigabit interfaces.

Related Commands

To configure the AutoQoS--VoIP feature on an interface, use the autoqosvoip command in interface configuration mode or Frame Relay DLCI configuration mode. To remove the AutoQoS--VoIP feature from an interface, use the no form of this command.

Syntax Description

Command Default

Default mode is disabled.

Command Modes

Interface configuration (config-if)
Frame Relay DLCI configuration (for use with Frame Relay DLCIs) (config-fr-dlci)

Command History

Usage Guidelines

To enable the AutoQoS--VoIP feature for Frame-Relay-to-ATM interworking, the fr-atmkeyword must be configured explicitly. However, the fr-atm keyword affects low-speed DLCIs only . It does not affect high-speed DLCIs.

Note	DLCIs with link speeds lower than or equal to 768 kbps are considered low-speed DLCIs; DLCIs with link speeds higher than 768 kbps are considered high-speed DLCIs.

Depending on whether the trust keyword has been configured for this command, the AutoQoS--VoIP feature automatically creates one of the following two policy maps:

• "AutoQoS-Policy-Trust" (created if the trust keyword is configured)
• "AutoQoS-Policy-UnTrust" (created if the trust keyword is not configured)

Both of these policy maps are designed to handle the Voice over IP (VoIP) traffic on an interface or a permanent virtual circuit (PVC) and can be modified to suit the quality of service (QoS) requirements of the network. To modify these policy maps, use the appropriate Cisco IOS command.

These policy maps should not be attached to an interface or PVC by using the service-policy command. If the policy maps are attached in this manner, the AutoQoS--VoIP feature (that is, the policy maps, class maps, and access control lists [ACLs]) will not be removed properly when thenoautoqosvoip command is configured.

For low-speed Frame Relay DLCIs that are interconnected with ATM PVCs in the same network, the fr-atm keyword must be explicitly configured in the autoqosvoip command to configure the AutoQoS--VoIP feature properly. That is, the command must be configured as autoqosvoipfr-atm.

For low-speed Frame Relay DLCIs that are configured with Frame-Relay-to-ATM, Multilink PPP (MLP) over Frame Relay (MLPoFR) is configured automatically. The subinterface must have an IP address. When MLPoFR is configured, this IP address is removed and put on the MLP bundle. The AutoQoS--VoIP feature must also be configured on the ATM side by using the autoqosvoip command.

The autoqosvoipcommand is not supported on subinterfaces or gigabit interfaces.

The autoqosvoip command is available for Frame Relay DLCIs.

Disabling AutoQoS--VoIP

The noautoqosvoip command disables the AutoQoS--VoIP feature and removes the configurations associated with the feature.

When the noautoqosvoip command is used, the no forms of the individual commands originally generated by the AutoQoS--VoIP feature are configured. With the use of individual no forms of the commands, the system defaults are reinstated. The no forms of the commands will be applied just as if the user had entered the commands individually. As the configuration reinstating the default setting is applied, any messages resulting from the processing of the commands are displayed.

Note	If you delete a subinterface or PVC (either ATM or Frame Relay PVCs) without configuring the noautoqosvoip command, the AutoQoS--VoIP feature will not be removed properly.

Related Commands

To configure AutoQoS on a voice over IP (VoIP) port interface, use the autoqosvoip command in interface configuration mode. To remove AutoQos from the configuration, use the no form of this command.

Syntax Description

Command Default

AutoQos trusts DSCP and CoS traffic markings.

Command Modes

Interface configuration (config-if)

Command History

Usage Guidelines

The autoqosvoipcommand is not supported on gigabit interfaces.

The automation of QoS (AutoQoS) allows you to specify the type of QoS parameters desired on a particular port. For example, entering the autoqosvoipcisco-softphone command enables the QoS ingress macro for the Cisco IP SoftPhone.

The Smartports feature provides a set of tools for configuring all switch settings related to a specific application with a single command. For example, entering the autoqosvoipcisco-phonecommand configures all the settings necessary to connect an IP phone to the switch.

You can enter theshowautoqos command to display the configured AutoQoS macros.

AutoQoS and Smartports are supported on the following modules:

• WS-X6548-RJ45
• WS-X6548-RJ21
• WS-X6148-GE_TX
• WS-X6548-GE-TX-CR
• WS-X6148-RJ45V
• WS-X6148-RJ21V
• WS-X6348-RJ45
• WS-X6348-RJ21
• WS-X6248-TEL

Note	Thenoautoqosvoip interface configuration command does not disable QoS globally or delete the received CoS-to-internal-DSCP maps created by AutoQoS.

The autoqosvoipcisco-phone and the autoqosvoipcisco-softphonecommands allow you to enable the inbound QoS configuration macros for AutoQoS on an interface. In some cases, the interface-specific autoqosvoipcommands also generate configuration commands that are applied globally.

You must configure the interface with the switchport command if you enter the autoqosvoipcisco-phone command. You cannot configure the interface with the switchport command if you enter the autoqosvoipcisco-softphone command.

If you configure an interface with the switchportcommand, AutoQoS configures the interface to trust CoS. If you do not configure the interface with the switchport command, AutoQoS configures the interface to trust DSCP.

AutoQoS uses a nondefault CoS-to-DSCP map. For this reason, you must configure port trust on a per-port-ASIC basis.

When you enter the autoqosvoipcisco-phone command, the following behavior occurs:

• QoS is enabled if it is disabled.
• The port is changed to port-based QoS.
• The appropriate CoS map is set.
• All ports are changed to port-based mode (if applicable).
• A trust-CoS QoS policy is created and applied for the ports that need a trust-CoS QoS policy (COIL2 and COIL1).
• A trusted boundary is enabled on the port.
• The CoS value for a trust boundary is set to zero.
• The port trust is set to trust-cos.
• Only 10/100 ports and 10/100/1000 ports are supported.
• A warning message is displayed if the CDP version is not version 2.

When you enter the autoqosvoipcisco-softphone command, the following behavior occurs:

• The cisco-softphonemacro is a superset of the cisco-phone macro and configures all features that are required for a Cisco IP Phone to work properly on the Catalyst 6500 series switch.
• The global settings for AutoQoS policy maps, class maps, and access lists are created to classify VoIP packets and to put them in the priority queue or another low-latency queue. The interface settings are created depending on the type of interface and the link speed.
• Two rate limiters are associated with the interface on which the cisco-softphone port-based autoqos macro is executed. The two rate limiters ensure that all inbound traffic on a cisco-softphone port have the following characteristics:
  • The rate of DCSP 46 is at or less than that of the expected softphone rate.
  • The rate of DSCP 26 is at or less than the expected signaling rate.
  • All other traffic is re-marked to DSCP 0 (default traffic).
• DSCP 46 is policed at the rate of 320 kbps with a burst of 2 Kb. DSCP 26 is policed at 32 kbps with a burst of 8 Kb.
• The port is set to untrusted for all port types. The policed-dscp-map is set to ensure that DSCP 46 is marked down to DSCP 0 and DSCP 26 is marked down to DSCP 0. The default QoS IP ACL re-marks all other traffic to DSCP 0.

When you enter the autoqosvoipsoft-phone command, the following behavior occurs:

• Enables QoS if QoS is disabled.
• Changes the port to port-based QoS.
• Sets the appropriate police-dscp-map.
• Sets the appropriate CoS-to-DSCP map.
• Changes all ports to port-based mode (if applicable).
• Creates a trust-dscp QoS policy for the ports that need it (COIL2 and COIL1).
• Applies the trust-dscp QoS policy to the port (COIL2 and COIL1).
• Disables a trusted boundary on the port.
• Changes trust to untrusted.
• Allows 10/100 ports and 10/100/1000 ports only.
• Applies two rate limiters, one for DSCP 46 and one for DSCP 26 inbound traffic, and trusts only inbound DSCP 46 and DSCP 26 traffic.
• Marks violations of either rate limiter results in traffic down to DSCP 0.
• Re-marks all other (non-DSCP 26 and 46) inbound traffic to DSCP 0.

When you enter the autoqosvoiptrustcommand, the following applies:

• The DSCP and the CoS markings are trusted for classification of the voice traffic.
• Enables QoS if QoS is disabled.
• Changes the port to port-based QoS.
• Changes all ports to port-based mode (if applicable).
• Creates a trust-dscp and a trust-cos QoS policy for the ports that need it (COIL2 and COIL1).
• Applies the trust-dscp and a trust-cos QoS policy to the port (COIL2 and COIL1).
• Disables the trusted boundary on the port.
• Sets port trust to trust-cos.
• All ports are supported.
• Bases queueing for all ports that allow dscp-to-q mapping on DSCP. If not, queueing is based on CoS.

Related Commands

To specify or modify the bandwidth allocated for a class belonging to a policy map, or to enable ATM overhead accounting, use the bandwidth command in QoS policy-map class configuration mode. To remove the bandwidth specified for a class or disable ATM overhead accounting, use the no form of this command.

Syntax Description

Command Default

No bandwidth is specified.

ATM overhead accounting is disabled.

Command Modes

QoS policy-map class configuration (config-pmap-c)

Command History

Usage Guidelines

Configuring a Policy Map

Use the bandwidth command when you configure a policy map for a class defined by the class-map command. The bandwidth command specifies the bandwidth for traffic in that class. Class-based weighted fair queueing (CBWFQ) derives the weight for packets belonging to the class from the bandwidth allocated to the class. CBWFQ then uses the weight to ensure that the queue for the class is serviced fairly.

Configuring Strict Priority with Bandwidth

You can configure only one class with strict priority. Other classes cannot have priority or bandwidth configuration. To configure minimum bandwidth for another class, use thebandwidthremainingpercent command.

Specifying Bandwidth as a Percentage for All Supported Platforms Except the Cisco 10000 Series Routers

Besides specifying the amount of bandwidth in kilobits per second (kbps), you can specify bandwidth as a percentage of either the available bandwidth or the total bandwidth. During periods of congestion, the classes are serviced in proportion to their configured bandwidth percentages. The bandwidth percentage is based on the interface bandwidth. Available bandwidth is equal to the interface bandwidth minus the sum of all bandwidths reserved by the Resource Reservation Protocol (RSVP) feature, the IP RTP Priority feature, and the low latency queueing (LLQ) feature.

Note

It is important to remember that when the bandwidth remaining percent command is configured, hard bandwidth guarantees may not be provided and only relative bandwidths are assured. That is, class bandwidths are always proportional to the specified percentages of the interface bandwidth. When the link bandwidth is fixed, class bandwidth guarantees are in proportion to the configured percentages. If the link bandwidth is unknown or variable, the router cannot compute class bandwidth guarantees in kbps.

Specifying Bandwidth as a Percentage for the Cisco 10000 Series Routers

Besides specifying the amount of bandwidth in kilobits per second (kbps), you can specify bandwidth as a percentage of either the available bandwidth or the total bandwidth. During periods of congestion, the classes are serviced in proportion to their configured bandwidth percentages. The minimum bandwidth percentage is based on the nearest parent shape rate.

Note

It is important to remember that when the bandwidth remaining percent command is configured, hard bandwidth guarantees may not be provided and only relative bandwidths are assured. That is, class bandwidths are always proportional to the specified percentages of the interface bandwidth. When the link bandwidth is fixed, class bandwidth guarantees are in proportion to the configured percentages. If the link bandwidth is unknown or variable, the router cannot compute class bandwidth guarantees in kbps.

The router converts the specified bandwidth to the nearest multiple of 1/255 (ESR-PRE1) or 1/65535 (ESR-PRE2) of the interface speed. Use the show policy-map interface command to display the actual bandwidth.

Restrictions for All Supported Platforms

The following restrictions apply to the bandwidth command:

• The amount of bandwidth configured should be large enough to also accommodate Layer 2 overhead.
• A policy map can have all the class bandwidths specified in either kbps or percentage, but not both, in the same class. However, the unit for the prioritycommand in the priority class can be different from the bandwidth unit of the nonpriority class.
• When the bandwidth percent command is configured, and a policy map containing class policy configurations is attached to the interface to stipulate the service policy for that interface, available bandwidth is assessed. If a policy map cannot be attached to a particular interface because of insufficient interface bandwidth, the policy is removed from all interfaces to which it was successfully attached. This restriction does not apply to the bandwidth remaining percent command.

Note

With CSCsy73939, if the bandwidth percent command results in a bandwidth value that is lower than the valid range then the policy map specifying this value cannot be attached to an interface, and the router displays the following error message: "service-policy output parent Configured Percent results in out of range kbps. Allowed range is min-value-max-value. The present CIR value is n."

For more information on bandwidth allocation, see the "Congestion Management Overview" module in the Cisco IOS Quality of Service Solutions Configuration Guide.

Note that when the policy map containing class policy configurations is attached to the interface to stipulate the service policy for that interface, available bandwidth is assessed. If a policy map cannot be attached to a particular interface because of insufficient interface bandwidth, then the policy is removed from all interfaces to which it was successfully attached.

Modular QoS CLI Queue Limits

The bandwidth command can be used with MQC to specify the bandwidth for a particular class. When used with MQC, the bandwidth command uses a default queue limit for the class. This queue limit can be modified using the queue-limit command, thereby overriding the default set by the bandwidth command.

Note	To meet the minimum bandwidth guarantees required by interfaces, modify the default queue limit of high-speed interfaces by using the queue-limit command.

Cisco 10000 Series Router

The Cisco 10000 series routers supports the bandwidth command on outbound interfaces only. They do not support this command on inbound interfaces.

On the PRE2, you specify a bandwidth value and a unit for the bandwidth value. Valid values for the bandwidth are from 1 to 2488320000. The units are bps, kbps, mbps, and gbps. The default unit is kbps. For example, the following commands configure a bandwidth of 10000 bps and 10000 kbps on the PRE2:

bandwidth 10000 bps
bandwidth 10000

On the PRE3, youspecify only a bandwidth value. Because the unit is always kbps, the PRE3 does not support the unit argument. Valid values are from 1 to 2000000. For example, the following command configures a bandwidth of 128,000 kbps on the PRE3:

bandwidth 128000

The PRE3 accepts the PRE2 bandwidth command only if the command is used without the unit argument. The PRE3 rejects the PRE2 bandwidth command if the specified bandwidth is outside the valid PRE3 bandwidth value range (1 to 2000000).

Besides specifying the amount of bandwidth in kilobits per second (kbps), you can specify bandwidth as a percentage of either the available bandwidth or the total bandwidth. During periods of congestion, the classes are serviced in proportion to their configured bandwidth percentages. The bandwidth percentage is based on the interface bandwidth. However, in a hierarchical policy the minimum bandwidth percentage is based on the nearest parent shape rate.

Note

When the bandwidth remaining percent command is configured, hard bandwidth guarantees may not be provided and only relative bandwidths are assured. Class bandwidths are always proportional to the specified percentages of the interface bandwidth. When the link bandwidth is fixed, class bandwidth guarantees are in proportion to the configured percentages. If the link bandwidth is unknown or variable, the router cannot compute class bandwidth guarantees in kbps.

The router converts the specified bandwidth to the nearest multiple of 1/255 (PRE1) or 1/65535 (PRE2, PRE3) of the interface speed. Use the show policy-map interface command to display the actual bandwidth.

Overhead Accounting for ATM (Cisco 10000 Series Router)

When configuring ATM overhead accounting, you must specify the BRAS-DSLAM, DSLAM-CPE, and subscriber line encapsulation types. The router supports the following subscriber line encapsulation types:

• mux-1483routed
• mux-dot1q-rbe
• snap-pppoa
• mux-rbe
• snap-1483routed
• snap-dot1q-rbe
• mux-pppoa
• snap-rbe

The router calculates the offset size unless you specify the user-defined offset option.

For hierarchical policies, configure ATM overhead accounting in the following ways:

• Enabled on parent--If you enable ATM overhead accounting on a parent policy, you are not required to enable accounting on the child policy.
• Enabled on child and parent--If you enable ATM overhead accounting on a child policy, then you must enable ATM overhead accounting on the parent policy.

The encapsulation types must match for the child and parent policies.

The user-defined offset values must match for the child and parent policies.

Related Commands

To configure bandwidth to be used as a reference for calculating rates of quality of service (QoS) percent configurations on a physical or logical interface, use the bandwidthqos-reference command in interface configuration or subinterface configuration mode. To remove this explicitly specified reference bandwidth, use the no form of this command.

Syntax Description

Command Default

This command is disabled. Reference bandwidth for a logical interface is derived from the main interface or the main interface QoS policy.

Command Modes

Interface configuration (config-if)
Subinterface configuration (config-subif)

Command History

Usage Guidelines

The bandwidthqos-referencecommand is used only as reference for calculating rates of QoS percent configurations on a logical interface. This command does not actually allocate a specified amount of bandwidth for a logical interface.

Note	In Cisco IOS Release 12.2(33)XNE, the bandwidthqos-referencecommand is supported only on a tunnel logical interface. In Cisco IOS Release 15.1(3)T, support is expanded to include main interface, subinterface, and Frame Relay as well as tunnel logical interfaces.

Compatibility with the shape (percent) and the police (percent) Commands

The bandwidthqos-referencecommand is compatible with and related to the shape(percent) and police(percent) commands. The shape(percent) command allows you to configure average-rate or peak-rate traffic shaping on the basis of a percentage of bandwidth available on an interface. The police(percent) command allows you to configure traffic policing on the basis of a percentage of bandwidth available on an interface.

The bandwidthqos-referencecommand interacts with theshape(percent) and police (percent) commands in the following ways:

• If the bandwidthqos-referencecommand is used to specify the bandwidth, theshape (percent) command and the police (percent) commands will use this specified amount to calculate the respective bandwidth percentages.
• If the bandwidthqos-referencecommand is not used to specify the bandwidth, the shape (percent) command and the police(percent) commands will use the amount of bandwidth available on the interface to calculate the respective bandwidth percentages.

Compatibility with bandwidth (interface) Command

The bandwidth(interface) command allows you to set the inherited and received bandwidth values for an interface.

If both the bandwidth (interface) and bandwidthqos-referencecommands are enabled on any interface, the value specified by the bandwidthqos-referencecommand is used as the reference for calculating rates for QoS percent configurations on that particular physical or logical interface. The value specified by the bandwidth(interface) command is disregarded.

In the sample configuration shown below, the value for the bandwidthqos-reference command is entered as 8000 kb/s, and the value for the bandwidth (interface) command is entered as 900 kb/s. The value for the shapeaveragepercent command is set to 50. The effect is seen in the output for the targetshaperate command, which is set to 4000000 bits per second (50 percent of 8000 kb/s):

Router(config)# interface e0/1
Router(config-if)# bandwidth qos-reference 8000
Router(config-if)# bandwidth 900
     
Router(config)# interface e0/1
Router(config-if)# bandwidth 900
Router(config-if)# end
Router# show running-config interface e0/1
interface Ethernet0/1
 bandwidth 900 
 bandwidth qos-reference 8000
 no ip address
 load-interval 30
end
Router(config-if)# policy-map test
Router(config-pmap)# class class-default
Router(config-pmap-c)# shape average percent 50
Router(config-pmap-c)# interface e0/1
Router(config-if)# service-policy out test
Router# show policy-map interface
 Ethernet0/1 
Service-policy output: test
 Class-map: class-default (match-any)
  79 packets, 7837 bytes
  30 second offered rate 0 bps, drop rate 0 bps
  Match: any 
  Queueing
  queue limit 64 packets
  (queue depth/total drops/no-buffer drops) 0/0/0
  (pkts output/bytes output) 79/7837
  shape (average) cir 4000000, bc 40000, be 40000
  target shape rate 4000000 

Related Commands

To specify a bandwidth-remaining ratio for class-level or subinterface-level queues to be used during congestion to determine the amount of excess bandwidth (unused by priority traffic) to allocate to nonpriority queues, use thebandwidthremainingratio command in policy-map class configuration mode. To remove the bandwidth-remaining ratio, use the no form of this command.

Syntax Description

Cisco 10000 Series Router

For most platforms, the default bandwidth ratio is 1.

When you use default bandwidth-remaining ratios at the subinterface level, the Cisco 10000 series router distinguishes between interface types. At the subinterface level, the default bandwidth-remaining ratio is 1 for VLAN subinterfaces and Frame Relay Data Link Connection Identifiers (DLCI). For ATM subinterfaces, the router computes the default bandwidth-remaining ratio based on the subinterface speed.

When you use default bandwidth-remaining ratios at the class level, the Cisco 10000 series router makes no distinction between interface types. At the class level, the default bandwidth-remaining ratio is 1.

Command Modes

Policy-map class (config-pmap-c)

Command History

Usage Guidelines

Cisco 10000 Series Router

The scheduler uses the ratio specified in the bandwidthremainingratio command to determine the amount of excess bandwidth (unused by priority traffic) to allocate to a class-level queue or a subinterface-level queue during periods of congestion. The scheduler allocates the unused bandwidth relative to other queues or subinterfaces.

The bandwidthremainingratio command cannot coexist with another bandwidth command in different traffic classes of the same policy map. For example, the following configuration is not valid and causes an error message to display:

policy-map Prec1
 class precedence_0
  bandwidth remaining ratio 10
 class precedence_2
  bandwidth 1000

For the PRE2, the bandwidthremainingratio command can coexist with another bandwidth command in the same class of a policy map. On the PRE3, the bandwidthremainingratio command cannot coexist with another bandwidthcommand in the same class. For example, the following configuration is not valid on the PRE3 and causes an error message to display:

policy-map Prec1
 class precedence_0
  bandwidth 1000
  bandwidth remaining ratio 10

In a hierarchical policy map in which the parent policy has only the class-default class defined with a child queuing policy applied, the router accepts only the bandwidthremainingratio form of the bandwidth command in the class-default class.

The bandwidthremainingratio command cannot coexist with the priority command in the same class. For example, the following configuration is not valid and causes an error message to display:

policy-map Prec1
 class precedence_1
  priority
  police percent 30
  bandwidth remaining ratio 10

All of the queues for which the bandwidthremainingratio command is not specified receive the platform-specified minimum bandwidth-remaining ratio. The router determines the minimum committed information rate (CIR) based on the configuration.

ATM Overhead Accounting (Optional)

The bandwidthremainingratio command can also be used to enable ATM overhead accounting. To enable ATM overhead accounting, use the account keyword and the subsequent keywords and arguments as documented in the Syntax Description table.

Cisco 7200 Series Routers

Thebandwidthremainingratio command is not supported on the Cisco 7200 series routers. If you have upgraded from Cisco IOS Release 12.2(33)SRD to Cisco IOS Release 12.2(33)SRE, you may see parser errors when you run this command. You can use the bandwidthremainingpercent command in place of the bandwidthremainingratiocommand on Cisco 7200 series routers to achieve the same functionality.

Related Commands

To configure the bump ing rules for a virtual circuit (VC) class that can be assigned to a VC bundle, use the bump command in VC-class configuration mode. To remove the explicit bumping rules for the VCs assigned to this class and return to the default condition of implicit bumping, use the nobumpexplicitcommandor the bumpimplicit command. To specify that the VC bundle members do not accept any bumped traffic, use the noform of thiscommand.

To configure the bumping rules for a specific VC or permanent virtual circuit (PVC) member of a bundle, use the bump command in bundle-vc or SVC-bundle-member configuration mode. To remove the explicit bumping rules for the VC or PVC bundle member and return to the default condition of implicit bumping, use the bumpimplicitcommand. To specify that the VC or PVC bundle member does not accept any bumped traffic, use the nobumptrafficcommand.

Syntax Description

Command Default

Implicit bumping

Permit bumping (VCs accept bumped traffic)

Command Modes

VC-class configuration (for a VC class)
Bundle-vc configuration (for an ATM VC bundle member)
SVC-bundle-member configuration (for an SVC bundle member)

Command History

Usage Guidelines

Use the bump command in bundle-vc configuration mode (for an ATM VC bundle member) or SVC-bundle-member configuration mode (for an SVC bundle member) to configure bumping rules for a discrete VC or PVC bundle member. Use the bump command in VC-class configuration mode to configure a VC class that can be assigned to a bundle member.

The effects of different bumping configuration approaches are as follows:

• Implicit bumping--If you configure implicit bumping, bumped traffic is sent to the VC or PVC configured to handle the next lower precedence level. When the original VC or PVC that bumped the traffic comes back up, the traffic that it is configured to carry is restored to it. If no other positive forms of the bump command are configured, the bumpimplicitcommandtakes effect.
• Explicit bumping--If you configure a VC or PVC with the bumpexplicit command, you can specify the precedence level to which traffic will be bumped when that VC or PVC goes down, and the traffic will be directed to a VC or PVC mapped with that precedence level. If the VC or PVC that picks up and carries the traffic goes down, the traffic is subject to the bumping rules for that VC or PVC. You can specify only one precedence level for bumping.
• Permit bumping--The VC or PVC accepts bumped traffic by default. If the VC or PVC has been previously configured to reject bumped traffic, you must use the bumptraffic command to return the VC or PVC to its default condition.
• Reject bumping--To configure a discrete VC or PVC to reject bumped traffic when the traffic is directed to it, use the nobumptraffic command.

Note	When no alternative VC or PVC can be found to handle bumped traffic, the bundle is declared down. To avoid this occurrence, configure explicitly the bundle member VC or PVC that has the lowest precedence level.

To use this command in VC-class configuration mode, you must enter the vc-classatm global configuration command before you enter this command.

To use this command to configure an individual bundle member in bundle-VC configuration mode, first issue the bundle command to enter bundle configuration mode for the bundle to which you want to add or modify the VC member to be configured. Then use the pvc-bundle command to specify the VC to be created or modified and enter bundle-vc configuration mode.

This command has no effect if the VC class that contains the command is attached to a standalone VC; that is, if the VC is not a bundle member. In this case, the attributes are ignored by the VC.

VCs in a VC bundle are subject to the following configuration inheritance guidelines (listed in order of next-highest precedence):

• VC configuration in bundle-vc mode
• Bundle configuration in bundle mode (with the effect of assigned VC-class configuration)
• Subinterface configuration in subinterface mode

Related Commands

To create a bundle or modify an existing bundle to enter bundle configuration mode, use the bundle command in subinterface configuration mode. To remove the specified bundle, use the noform of this command.

Syntax Description

Command Default

No bundle is specified.

Command Modes

Subinterface configuration

Command History

Usage Guidelines

From within bundle configuration mode you can configure the characteristics and attributes of the bundle and its members, such as the encapsulation type for all virtual circuits (VCs) in the bundle, the bundle management parameters, and the service type. Attributes and parameters you configure in bundle configuration mode are applied to all VC members of the bundle.

VCs in a VC bundle are subject to the following configuration inheritance guidelines (listed in order of next highest precedence):

• VC configuration in bundle-vc mode
• Bundle configuration in bundle mode
• Subinterface configuration in subinterface mode

To display status on bundles, use the showatmbundle and showatmbundlestatisticscommands.

Related Commands

To create or modify a switched virtual circuit (SVC) bundle, use the bundlesvccommand in interface configuration mode. To remove the specified bundle, use the noform of this command.

Syntax Description

Command Default

No SVC bundle is created or modified.

Command Modes

Interface configuration

Command History

Usage Guidelines

This command causes the system to enter SVC-bundle configuration mode. The bundle name must be the same on both sides of the VC.

From SVC-bundle configuration mode, you can configure the characteristics and attributes of the bundle and its members, such as the encapsulation type for all virtual circuits (VCs) in the bundle, the bundle management parameters, the service type, and so on. Attributes and parameters you configure in SVC-bundle configuration mode are applied to all VC members of the bundle.

VCs in a VC bundle are subject to the following configuration inheritance guidelines (listed in order of next-highest precedence):

• VC configuration in bundle-VC mode
• Bundle configuration in bundle mode
• Subinterface configuration in subinterface mode

To display the status of bundles, use the showatmbundlesvc and showatmbundlesvcstatisticscommands.

Related Commands

To define a traffic classification for a policy to act on using the class-map name or access group, use the class command in policy-map configuration mode. To delete an existing class map, use the noform of this command.

Syntax Description

Command Default

No policy-map class maps are defined.

Command Modes

Policy-map configuration

Command History

Usage Guidelines

Before you use the class (EtherSwitch) command, use the policy-map global configuration command to identify the policy map and to enter policy-map configuration mode. After you specify a policy map, you can configure a policy for new classes or modify a policy for any existing classes in that policy map. You attach the policy map to an interface by using the service-policyinterface configuration command; however, you cannot attach one that uses an ACL classification to the egress direction.

The class name that you specify in the policy map ties the characteristics for that class to the class map and its match criteria as configured by using the class-map global configuration command.

The class (EtherSwitch) command performs the same function as theclass-mapglobal configuration command. Use the class (EtherSwitch) command when a new classification, which is not shared with any other ports, is needed. Use the class-map command when the map is shared among many ports.

Note	In a policy map, the class named "class-default" is not supported. The Ethernet switch network module does not filter traffic on the basis of the policy map defined by the classclass-default policy-map configuration command.

After entering the class (EtherSwitch) command, you enter policy-map class configuration mode. When you are in this mode, these configuration commands are available:

• default --Sets a command to its default.
• exit --Exits policy-map class configuration mode and returns to policy-map configuration mode.
• no --Returns a command to its default setting.
• police --Defines a policer for the classified traffic. The policer specifies the bandwidth limitations and the action to take when the limits are exceeded. For more information, see the police command.

To return to policy-map configuration mode, use the exit command. To return to privileged EXEC mode, use the end command.

Note	For more information about configuring IP ACLs, refer to the "Configuring IP Services" chapter in the Cisco IOS IP Application Services Configuration Guide.

Related Commands

To specify the name of the class whose policy you want to create or change or to specify the default class (commonly known as the class-default class) before you configure its policy, use the classcommand in policy-map configuration mode. To remove a class from the policy map, use the no form of this command.

Syntax Description

Command Default

No class is specified.

Command Modes

Policy-map configuration (config-pmap)

Command History

Usage Guidelines

Policy Map Configuration Mode

Within a policy map, the class(policy-map)command can be used to specify the name of the class whose policy you want to create or change. First, the policy map must be identified.

To identify the policy map (and enter the required policy-map configuration mode), use the policy-map command before you use the class(policy-map)command. After you specify a policy map, you can configure policy for new classes or modify the policy for any existing classes in that policy map.

Class Characteristics

The class name that you specify in the policy map ties the characteristics for that class--that is, its policy--to the class map and its match criteria, as configured using the class-map command.

When you configure policy for a class and specify its bandwidth and attach the policy map to an interface, class-based weighted fair queueing (CBWFQ) determines if the bandwidth requirement of the class can be satisfied. If so, CBWFQ allocates a queue for the bandwidth requirement.

When a class is removed, available bandwidth for the interface is incremented by the amount previously allocated to the class.

The maximum number of classes that you can configure for a router--and, therefore, within a policy map--is 64.

Predefined Default Class

The class-default keyword is used to specify the predefined default class called class-default. The class-default class is the class to which traffic is directed if that traffic does not match any of the match criteria in the configured class maps.

Tail Drop or WRED

You can define a class policy to use either tail drop by using the queue-limit command or Weighted Random Early Detection (WRED) by using the random-detect command. When using either tail drop or WRED, note the following points:

• The queue-limit and random-detect commands cannot be used in the same class policy, but they can be used in two class policies in the same policy map.
• You can configure the bandwidth command when either the queue-limit command or the random-detect command is configured in a class policy. The bandwidth command specifies the amount of bandwidth allocated for the class.
• For the predefined default class, you can configure the fair-queue (class-default) command. The fair-queue command specifies the number of dynamic queues for the default class. The fair-queue command can be used in the same class policy as either the queue-limit command or the random-detect command. It cannot be used with the bandwidth command.

Fragments

A default traffic class is marked as a fragment within a policy map class statement using the fragmentkeyword. Multiple fragments can then be classified collectively in a separate policy map that is created using the service-fragment keyword. When fragments are used, default traffic classes marked as fragments have QoS applied separately from the non-default traffic classes.

When using fragments, note the following guidelines:

• Only default traffic classes can be marked as fragments.
• Thefragmentfragment-class-nameoption within a default class statement marks that default class as a fragment.
• Theservice-fragmentfragment-class-nameoption when defining a class in a policy map is used to specify a class of traffic within the Modular QoS CLI that contains all fragments sharing the same fragment-class-name.
• Fragments can only be used within the same physical interface. Policy maps with fragments sharing the same fragment-class-name on different interfaces cannot be classified collectively using a class with the service-fragmentfragment-class-name option.

Cisco 10000 Series Router

The PRE2 allows you to configure 31 class queues in a policy map.

In a policy map, the PRE3 allows you to configure one priority level 1 queue, plus one priority level 2 queue, plus 12 class queues, plus one default queue.

Cisco ASR 1000 Series Routers

The maximum number of classes that you can configure for a Cisco ASR 1000 Series Router--and, therefore, within a policy map--is 8.

Related Commands

To create a class map to be used for matching Address Resolution Protocol (ARP) per-user packets, use the class-maparp-peruser command in global configuration mode. To disable this functionality, use the no form of the command.

Syntax Description

This command has no arguments or keywords.

Command Default

No class map is configured.

Command Modes

Global configuration

Command History

Usage Guidelines

Use this command to create an ARP class map when configuring CoPP.

Related Commands

To configure a virtual circuit (VC) bundle with the bundle-level commands contained in the specified VC class, use the class-bundle command in bundle or SVC-bundle configuration mode. To remove the VC class parameters from a VC bundle, use the no form of this command.

Syntax Description

Command Default

No VC class is assigned to the VC bundle.

Command Modes

Bundle configuration
SVC-bundle configuration

Command History

Usage Guidelines

To use this command, you must first enter the bundle or bundlesvccommand to create the bundle and enter bundle or SVC-bundle configuration mode.

Use this command to assign a previously defined set of parameters (defined in a VC class) to an ATM VC bundle. Parameters set through bundle-level commands that are contained in a VC class are applied to the bundle and its VC members.

You can add the following commands to a VC class to be used to configure a VC bundle: broadcast, encapsulation, inarp,oam-bundle, oamretry, and protocol.

Bundle-level parameters applied through commands that are configured directly on a bundle supersede bundle-level parameters applied through a VC class by the class-bundle command. Some bundle-level parameters applied through a VC class or directly to the bundle can be superseded by commands that you directly apply to individual VCs in bundle-VC configuration mode.

Related Commands

To create a class map to be used for matching packets to a specified class and to enter QoS class-map configuration mode, use the class-map command in global configuration mode. To remove an existing class map from a device, use the no form of this command.

Syntax Description

Command Default

A class map is not configured.

Command Modes

Global configuration (config)

Command History

Usage Guidelines

Cisco Performance Monitor in Cisco IOS Release 15.1(3)T and 12.2(58)SE

Only the class-map-name argument is available.

Cisco 2600, 3660, 3845, 6500, 7200, 7401, 7500, and ASR 1000 Series Routers

Use the class-map command to specify the class that you will create or modify to meet the class-map match criteria. This command enters QoS class-map configuration mode in which you can enter one or more match commands to configure the match criteria for this class. Packets that arrive at either the input interface or the output interface (determined by how the service-policy command is configured) are checked against the match criteria that are configured for a class map to determine if packets belong to that class.

When configuring a class map, you can use one or more match commands to specify the match criteria. For example, you can use the match access-group command, the match protocol command, or the match input-interface command. The match commands vary according to the Cisco software release. For more information about match criteria and match commands, see the "Modular Quality of Service Command-Line Interface (CLI) (MQC)" chapter of the Cisco IOS Quality of Service Solutions Configuration Guide.

Cisco 7600 Series Routers

Apply the class-map command and commands available in QoS class-map configuration mode on a per-interface basis to define packet classification, marking, aggregating, and flow policing as part of a globally named service policy.

You can attach a service policy to an EtherChannel. Do not attach a service policy to a port that is a member of an EtherChannel.

When a device is in QoS class-map configuration mode, the following configuration commands are available:

• description--Specifies the description for a class-map configuration.
• exit--Exits from QoS class-map configuration mode.
• match--Configures classification criteria.
• no--Removes a match statement from a class map.

The following commands appear in the CLI help but are not supported on LAN interfaces or WAN interfaces on Optical Service Modules (OSMs):

• destination-address mac mac-address
• input-interface {interface-type interface-number | null number | vlan vlan-id}
• protocol link-type
• source-address mac mac-address

OSMs are not supported on Cisco 7600 series routers that are configured with a Supervisor Engine 32.

Policy Feature Card (PFC) QoS does not support the following commands:

• destination-address mac mac-address
• input-interface {interface-type interface-number | null number | vlan vlan-id}
• protocol link-type
• qos-group group-value
• source-address mac mac-address

If you enter these commands, PFC QoS does not detect unsupported keywords until you attach a policy map to an interface. When you try to attach the policy map to an interface, an error message is generated. For additional information, see the Cisco 7600 Series Router Cisco IOS Software Configuration Guide and Cisco IOS command references.

After configuring the class-map name and the device you can enter the match access-group and match ip dscp commands in QoS class-map configuration mode. The syntax for these commands is as follows:

match [access-group {acl-index | acl-name} | ip dscp | precedence} value]

See the table below for a description of match command keywords.

Related Commands

To create a class map to be used for matching Address Resolution Protocol (ARP) per-user packets, use the class-maparp-peruser command in global configuration mode. To disable, use the no form of the command.

Syntax Description

Command Default

Enabled

Command Modes

Global configuration

Command History

Usage Guidelines

Use this command to create an ARP class map when configuring CoPP.

Related Commands

To associate a class map with a policy map, use the classtypetagcommand in policy map configuration mode. To disassociate the command, use the no form of this command.

Syntax Description

Command Default

A class map is not associated with a policy map.

Command Modes

Policy map configuration

Command History

Usage Guidelines

If this command is used and the class is not configured, an error is generated. The error may be something such as "% class map {name } not configured." If the class needs to be inserted before a specific class map, the insert-before keyword can be used. The insert-before keyword is typically needed if the administrator is configuring any per-host class maps and would like it inserted before a specific class map. The classtypetag command creates the policy-map class configuration mode. There can be multiple classes under the policy map.

Related Commands

To clear counters for control-plane interfaces or subinterfaces, use the clearcontrol-plane command in privileged EXEC mode.

Syntax Description

Command Modes

Privileged EXEC

Command History

Usage Guidelines

Use the clearcontrol-plane command to clear counters for all features on the control-plane interfaces or subinterfaces.

Related Commands

To clear buffers, filters, and port statistics gathered by Network-Based Application Recognition (NBAR), use the clear ip nbar command in privileged EXEC mode.

Syntax Description

Command Modes

Privileged EXEC (#)

Command History

Related Commands

To clear the statistics gathered by the network-based application recognition (NBAR) Protocol Discovery feature, use the clearipnbarprotocol-discovery command in privileged EXEC mode.

Syntax Description

Command Modes

Privileged EXEC

Command History

Usage Guidelines

Use the clearipnbarprotocol-discovery command to clear the statistics gathered by the NBAR Protocol Discovery feature. By default, this command clears the statistics for all the interfaces on which the protocol discovery feature is enabled.

Related Commands

To eliminate Resource Reservation Protocol (RSVP) security associations before their lifetimes expire, use the clear iprsvpauthenticationcommand in privileged EXEC mode.

Syntax Description

Note	The difference between theip-address andhostname arguments is the difference of specifying the neighbor by its IP address or by its name.

Command Default

The default behavior is to clear all security associations.

Command Modes

Privileged EXEC

Command History

Usage Guidelines

Use the clear iprsvpauthentication command for the following reasons:

• To eliminate security associations before their lifetimes expire
• To free up memory
• To resolve a problem with a security association being in some indeterminate state
• To force reauthentication of neighbors

You can delete all RSVP security associations if you do not enter an IP address or a hostname, or just the ones with a specific RSVP neighbor or host.

If you delete a security association, it is re-created as needed when the trusted RSVP neighbors start sending more RSVP messages.

Related Commands

To clear (set to zero) all IP Resource Reservation Protocol (RSVP) counters that are being maintained, use the cleariprsvpcounterscommand in privileged EXEC mode.

Syntax Description

Command Modes

Privileged EXEC

Command History

Usage Guidelines

This command allows you to set all IP RSVP counters to zero so that you can see changes easily.

Related Commands

To clear (refresh) the values for hello instance counters, use the cleariprsvphelloinstancecounterscommand in privileged EXEC mode.

Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC

Command History

Related Commands

To clear hello statistics for an instance, use the cleariprsvphelloinstancestatisticscommand in privileged EXEC mode.

Syntax Description

This command has no arguments or keywords.

Command Default

Hello statistics are not cleared for an instance.

Command Modes

Privileged EXEC

Command History

Related Commands

To clear hello statistics globally, use the cleariprsvphellostatisticscommand in privileged EXEC mode.

Syntax Description

This command has no arguments or keywords.

Command Default

Hello statistics are not globally cleared.

Command Modes

Privileged EXEC

Command History

Usage Guidelines

Use this command to remove all information about how long hello packets have been in the hello input queue.

Related Commands

To clear (set to zero) the Resource Reservation Protocol (RSVP) traffic engineering (TE) high availability (HA) counters that are being maintained by a Route Processor (RP), use the clear ip rsvp high-availability counters command in privileged EXEC mode.

Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC

Command History

Usage Guidelines

Use the clear ip rsvp high-availability counterscommand to clear (set to zero) the HA counters, which include state, ISSU, resource failures, and historical information.

Related Commands

Note	Effective with Cisco IOS Release 12.4(20)T, the cleariprsvpmsg-pacingcommand is not available in Cisco IOS software. This command was replaced by thecleariprsvpsignallingrate-limit command.

To clear the Resource Reservation Protocol (RSVP) message pacing output from the showiprsvpneighbor command, use the cleariprsvpmsg-pacing command in privileged EXEC mode.

Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC

Command History

Related Commands

To remove Resource Reservation Protocol (RSVP) RESV-related receiver information currently in the database, use the cleariprsvpreservationcommand in EXEC mode.

Syntax Description

Command Modes

EXEC

Command History

Usage Guidelines

Use the cleariprsvpreservationcommand to remove the RESV-related sender information currently in the database so that when reservation requests arrive, based on the RSVP admission policy, the relevant ones can be reestablished.

Whenever you change the clockrate or bandwidth of an interface, RSVP does not update its database to reflect the change. This is because such a change requires that RSVP reestablish reservations based on the new clockrate or bandwidth value and arbitrarily dropping some reservations while retaining others is not desired. The solution is to clear the RESV state by issuing the cleariprsvpreservationcommand.

The cleariprsvpreservationcommand clears the RESV state from the router on which you issued the command and causes the router to send a PATH TEAR message to the upstream routers thereby clearing the RESV state for that reservation on all the upstream routers.

Related Commands

To remove Resource Reservation Protocol (RSVP) PATH-related sender information currently in the database, use the cleariprsvpsendercommand in EXEC mode.

Syntax Description

Command Modes

EXEC

Command History

Usage Guidelines

Use the cleariprsvpsender command to remove the PATH-related sender information currently in the database so that when reservation requests arrive, based on the RSVP admission policy, the relevant ones can be reestablished.

Whenever you change the clockrate or bandwidth of an interface, RSVP does not update its database to reflect the change. This is because such a change requires that RSVP reestablish reservations based on the new clockrate or bandwidth value and arbitrarily dropping some reservations while retaining others is not desired. The solution is to clear the PATH state by issuing the cleariprsvpsender command.

The cleariprsvpsender command clears the PATH state from the router on which you issued the command and causes the router to send a PATH TEAR message to the downstream routers thereby clearing the PATH state for that reservation on all the downstream routers.

Related Commands

To clear (set to zero) the Resource Reservation Protocol (RSVP) fast local repair (FLR) counters, use the cleariprsvpsignallingfast-local-repairstatistics command in user EXEC or privileged EXEC mode.

Syntax Description

This command has no arguments or keywords.

Command Default

The default is to clear all the RSVP FLR counters.

Command Modes

User EXEC (>)
Privileged EXEC (#)

Command History

Usage Guidelines

Use the cleariprsvpsignallingfast-local-repairstatisticscommand to set all the RSVP FLR counters to zero. The statistics include information about FLR procedures such as the current state, the start time, and the repair rate.

Related Commands