Cisco IOS Quality of Service Solutions Command Reference

mls qos (global configuration mode)

To enable the quality of service (QoS) functionality globally, use the mls qos command in global configuration mode. To disable the QoS functionality globally, use the no form of this command.

mls qos

no mls qos

Syntax Description

This command has no arguments or keywords.

Command Default

QoS is globally disabled.

Command Modes

Global configuration (config)

Command History

Usage Guidelines

If you enable QoS globally, QoS is enabled on all interfaces with the exception of the interfaces where you disabled QoS. If you disable QoS globally, all traffic is passed in QoS pass-through mode.

In port-queueing mode, Policy Feature Card (PFC) QoS (marking and policing) is disabled, and packet type of service (ToS) and class of service (CoS) are not changed by the PFC. All queueing on rcv and xmt is based on a QoS tag in the incoming packet, which is based on the incoming CoS.

For 802.1Q or Inter-Switch Link (ISL)-encapsulated port links, queueing is based on the packet 802.1Q or ISL CoS.

For the router main interfaces or access ports, queueing is based on the configured per-port CoS (the default CoS is 0).

This command enables or disables ternary content addressable memory (TCAM) QoS on all interfaces that are set in the OFF state.

Examples

This example shows how to enable QoS globally:

Router(config)# mls qos

Router(config)#

This example shows how to disable QoS globally on the Cisco 7600 series router:

Router(config)# no mls qos

Router(config)#

Related Commands

mls qos (interface configuration mode)

To enable the quality of service (QoS) functionality on an interface, use the mls qos command in interface configuration command mode. To disable QoS functionality on an interface, use the no form of this command.

mls qos

no mls qos

Syntax Description

This command has no arguments or keywords.

Command Default

Enabled

Command Modes

Interface configuration (config-if)

Command History

Usage Guidelines

This command is deprecated on Cisco 7600 series routers that are configured with a Supervisor Engine 2.

Although the CLI allows you to configure PFC-based QoS on the WAN ports on the OC-12 ATM OSMs and on the WAN ports on the channelized OSMs, PFC-based QoS is not supported on the WAN ports on these OSMs.

If you disable QoS globally, it is also disabled on all interfaces.

This command enables or disables TCAM QoS (classification, marking, and policing) for the interface.

Examples

This example shows how to enable QoS on an interface:

Router(config-if)# mls qos

Related Commands

mls qos 10g-only

To enable quality of service (QoS) in 10g-only mode, in which only the supervisor engine's 10-Gigabit Ethernet uplink ports are used, use the mls qos 10g-only command in global configuration mode. To allow the use of all uplink ports, including the 1-Gigabit Ethernet ports, use the no form of this command.

mls qos 10g-only

no mls qos 10g-only

Syntax Description

This command has no arguments or keywords.

Command Default

All ports are active on the supervisor engine.

Command Modes

Global configuration (config)

Command History

Usage Guidelines

When you enter the mls qos 10g-only command, a supervisor engine with both 1-Gigabit and 10-Gigabit Ethernet uplink ports reallocates the interface queue capacity to improve the performance of its 10-Gigabit Ethernet ports. The reallocation is possible only in 10g-only mode, in which the supervisor engine's 1-Gigabit Ethernet ports are not used. In the normal mode, when all supervisor engine ports are active, the queue structure is 2q4t on receive and 1p3q4t on transmit. In 10g-only mode, the queue structure is 8q4t on receive and 1p7q4t on transmit.

Note To display detailed information about the queues, use the show queueing interface command.

When you switch between normal and 10g-only modes, any existing QoS configuration on the uplink ports is lost, and you must reconfigure QoS. In addition, service will be temporarily lost on the ports during the transition.

If you do not shut down the 1-Gigabit Ethernet ports before entering the mls qos 10g-only command, the mls qos 10g-only command shuts down the ports.

When you switch from 10g-only mode to normal mode, you must enter the no shutdown command on each of the 1-Gigabit Ethernet ports to resume QoS service on those ports.

In 10g-only mode, the 1-Gigabit Ethernet ports are visible, but they remain in an administratively down state.

Examples

The following example shows how to place the supervisor engine in the 10g-only mode:

Router# configure terminal

Router(config)# mls qos 10g-only

Related Commands

mls qos aggregate-policer

To define a named aggregate policer for use in policy maps, use the mls qos aggregate-policer command in global configuration mode. To delete a named aggregate policer, use the no form of this command.

mls qos aggregate-policer name rate-bps [normal-burst-bytes [maximum-burst-bytes | pir peak-rate-bps | action-type action]]

no mls qos aggregate-policer name

Syntax Description

Command Default

The defaults are as follows:

•conform-action is transmit.

•exceed-action is drop.

•violate-action is equal to the exceed-action.

•pir peak-rate-bps is equal to the normal (cir) rate.

Command Modes

Global configuration

Command History

Usage Guidelines

This policer can be shared by different policy map classes and on different interfaces. The Cisco 7600 series router supports up to 1023 aggregates and 1023 policing rules.

The mls qos aggregate-policer command allows you to configure an aggregate flow and a policing rule for that aggregate. When you enter the rate and burst parameters, the range for the average rate is 32 kbps to 10 Gbps (entered as 32000 and 10000000000) and the range for the burst size is 1 KB (entered as 1000) to 31.25 MB (entered as 31250000). Modifying an existing aggregate rate limit entry causes that entry to be modified in NVRAM and in the Cisco 7600 series router if that entry is currently being used.

Note Because of hardware granularity, the rate value is limited, so the burst that you configure may not be the value that is used.

Modifying an existing microflow or aggregate rate limit modifies that entry in NVRAM as well as in the Cisco 7600 series router if it is currently being used.

When you enter the aggregate policer name, follow these naming conventions:

•Maximum of 31 characters and may include a-z, A-Z, 0-9, the dash character (-), the underscore character (_), and the period character (.).

•Must start with an alphabetic character and must be unique across all ACLs of all types.

•Case sensitive.

•Cannot be a number.

•Must not be a keyword; keywords to avoid are all, default-action, map, help, and editbuffer.

Aggregate policing works independently on each DFC-equipped switching module and independently on the PFC2, which supports any non-DFC-equipped switching modules. Aggregate policing does not combine flow statistics from different DFC-equipped switching modules. You can display aggregate policing statistics for each DFC-equipped switching module, PFC2, and any non-DFC-equipped switching modules that are supported by the PFC2 by entering the show mls qos aggregate policer command.

Examples

The following example shows how to configure a QoS aggregate policer to allow a maximum of 100000 bits per second with a normal burst byte size of 10000, to set DSCP to 48 when these rates are not exceeded, and to drop packets when these rates are exceeded:

Router(config)# mls qos aggregate-policer micro-one 100000 10000 conform-action 
set-dscp-transmit 48 exceed-action drop

Related Commands

mls qos bridged

To enable the microflow policing for bridged traffic on Layer 3 LAN interfaces, use the mls qos bridged command in interface configuration mode. To disable microflow policing for bridged traffic, use the no form of this command.

mls qos bridged

no mls qos bridged

Syntax Description

This command has no arguments or keywords.

Command Default

Disabled

Command Modes

Interface configuration

Command History

Usage Guidelines

This command is supported on SVIs only.

On Cisco 7600 series routers that are configured with a Supervisor Engine 2, you must enable the mls qos bridged command on an SVI for the microflow policing of IPv4 multicast packets if the user policy is attached to an SVI.

Examples

This example shows how to enable the microflow policing for bridged traffic on a VLAN interface:

Router(config-if)# mls qos bridged

Related Commands

mls qos channel-consistency

To enable the quality of service (QoS)-port attribute checks on EtherChannel bundling, use the mls qos channel-consistency command in interface configuration mode. To disable the QoS-port attribute checks on EtherChannel bundling, use the no form of this command.

mls qos channel-consistency

no mls qos channel-consistency

Syntax Description

This command has no arguments or keywords.

Command Default

Enabled

Command Modes

Interface configuration

Command History

Usage Guidelines

The mls qos channel-consistency command is supported on port channels only.

Examples

This example shows how to enable the QoS-port attribute checks on the EtherChannel bundling:

Router(config-if)# mls qos channel-consistency

This example shows how to disable the QoS-port attribute checks on the EtherChannel bundling:

Router(config-if)# no mls qos channel-consistency

mls qos cos

To define the default multilayer switching (MLS) class of service (CoS) value of a port or to assign the default CoS value to all incoming packets on the port, use the mls qos cos command in interface configuration mode. To return to the default CoS setting, use the no form of this command.

Cisco 3660, 3845, 6500, 7200, 7400, and 7500 Series Routers

mls qos cos {cos-value | override}

no mls qos cos {cos-value | override}

Cisco 7600 Series Routers

mls qos cos cos-value

no mls qos cos cos-value

Syntax Description

Command Default

The defaults are as follows:

•Default CoS value (cos-value) value for a port is 0.

•CoS override is not configured.

Command Modes

Interface configuration

Command History

Usage Guidelines

Cisco 3660, 3845, 6500, 7200, 7400, and 7500 Series Routers

You can assign the default CoS and differentiated services code point (DSCP) value to all packets entering a port if the port has been configured by use of the override keyword.

Use the override keyword when all incoming packets on certain ports deserve a higher or lower priority than packets the enter from other ports. Even if a port was previously set to trust DSCP or CoS, this command overrides that trust state, and all the CoS values on the incoming packets are changed to the default CoS value that is configured with the mls qos cos command. If an incoming packet is tagged, the CoS value of the packet is modified at the ingress port. It is changed to the default CoS of that port.

Use the show mls qos interface privileged EXEC command to verify your settings.

Cisco 7600 Series Routers

CoS values are configurable on physical LAN ports only.

On Cisco 7600 series routers that are configured with a Supervisor Engine 2, the following restrictions apply:

•This command is not supported on any WAN interface on the Optical Service Modules (OSMs).

•This command is not supported on 4-port Gigabit Ethernet WAN ports.

Examples

Cisco 3660, 3845, 6500, 7200, 7400, and 7500 Series Routers

The following example shows how to assign 4 as the default port CoS:

Router(config)# interface gigabitethernet 0/1

Router(config-if)# mls qos trust cos

Router(config-if)# mls qos cos 4

The following example shows how to assign 4 as the default port CoS value for all packets the enter the port:

Router(config)# interface gigabitethernet0/1

Router(config-if)# mls qos cos 4

Router(config-if)# mls qos cos override

Cisco 7600 Series Routers

The following example shows how to configure the default QoS CoS value as 6:

Router(config)# interface gigabitethernet 0/1

Router(config-if)# mls qos cos 6

Related Commands

mls qos cos-mutation

To attach an ingress-class-of-service (CoS) mutation map to the interface, use the mls qos cos-mutation command in interface configuration mode. To remove the ingress-CoS mutation map from the interface, use the no form of this command.

mls qos cos-mutation cos-mutation-table-name

no mls qos cos-mutation

Syntax Description

Command Default

No ingress-CoS mutation table is defined.

Command Modes

Interface configuration

Command History

Usage Guidelines

This command is not supported on Cisco 7600 series routers that are configured with a Supervisor Engine 2.

Examples

This example shows how to attach the ingress-CoS mutation map named mutemap2:

Router(config-if)# mls qos cos-mutation mutemap2 

Related Commands

mls qos dscp-mutation

To attach an egress-differentiated-services-code-point (DSCP) mutation map to the interface, use the mls qos dscp-mutation command in interface configuration mode. To remove the egress-DSCP mutation map from the interface, use the no form of this command.

mls qos dscp-mutation dscp-mutation-table-name

no mls qos dscp-mutation

Syntax Description

Command Default

No table is defined.

Command Modes

Interface configuration

Command History

Usage Guidelines

This command is not supported on Cisco 7600 series routers that are configured with a Supervisor Engine 2.

Examples

This example shows how to attach the egress-DSCP mutation map named mutemap1:

Router(config-if)# mls qos dscp-mutation mutemap1 

Related Commands

mls qos exp-mutation

To attach an egress-EXP mutation map to the interface in the interface configuration command mode, use the mls qos exp-mutation command. Use the no form of this command to remove the egress-EXP mutation map from the interface.

mls qos exp-mutation exp-mutation-table-name

no mls qos exp-mutation

Syntax Description

Command Default

No table is defined.

Command Modes

Interface configuration

Command History

Usage Guidelines

This command is supported in PFC3BXL or PFC3B mode only.

This command is not supported on Cisco 7600 series routers that are configured with a Supervisor Engine 2.

Examples

This example shows how to attach the egress-exp mutation map named mutemap2:

Router(config-if)# mls qos exp-mutation mutemap2 

Router(config-if)#

Related Commands

mls qos loopback

To remove a router port from the Switched Virtual Interface (SVI) flood for VLANs that are carried through by the loopback cable, use the mls qos loopback command in interface configuration mode. To return to the default settings, use the no form of this command.

mls qos loopback

no mls qos loopback

Syntax Description

This command has no arguments or keywords.

Command Default

Disabled

Command Modes

Interface configuration

Command History

Usage Guidelines

With mls qos loopback applied at the interface, the packets are not forwarded to the destination.

Before you enter the mls qos loopback command, you must specify a MAC address for the Optical Services Modules (OSM) interface. The MAC address must be different from the LAN router MAC address that is used in PFC2 hardware switching.

Examples

This example shows how to prevent packets from being forwarded to the destination:

Router(config-if)# mls qos loopback 

mls qos map

To define the multilayer switching (MLS) class of service (CoS)-to-differentiated services code point (DSCP) map or DSCP-to-CoS map, use the mls qos map command in global configuration mode. To return to the default map, use the no form of this command.

mls qos map {cos-dscp dscp1...dscp8 | dscp-cos dscp-list to cos}

no mls qos map {cos-dscp | dscp-cos}

Syntax Description

Command Default

Table 12 shows the default CoS-to-DSCP map.

Table 13 shows the default DSCP-to-CoS map.

Command Modes

Global configuration (config)

Command History

Usage Guidelines

All of the CoS-to-DSCP and DSCP-to-CoS maps are globally defined. You apply all maps to all ports.

If you enter the mls qos trust cos command, the default CoS-to-DSCP map is applied.

If you enter the mls qos trust dscp command, the default DSCP-to-CoS map is applied.

After a default map is applied, you can define the CoS-to-DSCP or DSCP-to-CoS map by entering consecutive mls qos map commands.

If the mls qos trust dscp command is entered and a packet with an untrusted DSCP value is at an ingress port, the packet CoS value is set to 0.

Use the show mls qos maps privileged EXEC command to verify your settings.

Examples

The following example shows how to define the DSCP-to-CoS map. DSCP values 16, 18, 24, and 26 are mapped to CoS 1. DSCP values 0, 8, and 10 are mapped to CoS 0.

Router# configure terminal

Router(config)# mls qos map dscp-cos 16 18 24 26 to 1

Router(config)# mls qos map dscp-cos 0 8 10 to 0

The following example shows how to define the CoS-to-DSCP map. CoS values 0 to 7 are mapped to DSCP values 8, 8, 8, 8, 24, 32, 56, and 56.

Router# configure terminal

Router(config)# mls qos map cos-dscp 8 8 8 8 24 32 56 56

Related Commands

mls qos map cos-dscp

To define the ingress Class of Service (CoS)-to-differentiated services code point (DSCP) map for trusted interfaces, use the mls qos map cos-dscp command in global configuration mode. Use the no form of this command to remove a prior entry.

mls qos map cos-dscp dscp1...dscp8

no mls qos map cos-dscp

Syntax Description

Command Default

The default CoS-to-DSCP configuration is listed in Table 14.

Command Modes

Global configuration

Command History

Usage Guidelines

All of the CoS-to-DSCP and DSCP-to-CoS maps are globally defined. You apply all maps to all ports.

If you enter the mls qos trust cos command, the default CoS-to-DSCP map is applied.

If you enter the mls qos trust dscp command, the default DSCP-to-CoS map is applied.

After a default map is applied, you can define the CoS-to-DSCP or DSCP-to-CoS map by entering consecutive mls qos map commands.

If the mls qos trust dscp command is entered and a packet with an untrusted DSCP value is at an ingress port, the packet CoS value is set to 0.

Use the show mls qos maps privileged EXEC command to verify your settings.

Examples

The following example shows how to define the CoS-to-DSCP map. CoS values 0 to 7 are mapped to DSCP values 8, 8, 8, 8, 24, 32, 56, and 56.

Router# configure terminal

Router(config)# mls qos map cos-dscp 8 8 8 8 24 32 56 56

Related Commands

mls qos map cos-mutation

To map a class of service (CoS) value to a new CoS value for a packet, use the mls qos map cos-mutation command in the global configuration mode. To remove the map, use the no form of this command

mls qos map cos-mutation name mutated-cos1 mutated-cos2 mutated-cos3 mutated-cos4 mutated-cos5 mutated-cos6 mutated-cos7 mutated-cos8

no mls qos map cos-mutation name

Syntax Description

Command Default

If the CoS-to-CoS mutation map is not configured, the default CoS-to-CoS mutation mapping is listed in Table 15.

Command Modes

Global configuration

Command History

Usage Guidelines

This command is not supported on the Catalyst 6500 series switches and the Cisco 7600 series routers that are configured with a Supervisor Engine 2.

This command is supported on the Catalyst 6500 series switches and the Cisco 7600 series routers that are configured with the following modules only:

•WS-X6704-10GE

•WS-X6724-SFP

•WS-X6748-GE-TX

CoS mutation is not supported on non-802.1Q tunnel ports.

When you enter the mls qos map cos-mutation command, you are configuring the mutated-CoS values map to sequential ingress-CoS numbers. For example, by entering the mls qos map cos-mutation 2 3 4 5 6 7 0 1 command, you configure this map:

Separate the eight CoS values by a space.

After you define the map in global configuration mode, you can attach the map to a port.

If QoS is disabled, the port is not in a trust CoS mode, and the port is not in 802.1Q tunneling mode. The changes appear once you put the port into trust CoS mode and the port is configured as an 802.1Q tunnel port.

Release 12.2(17b)SXA and later releases support ingress-CoS mutation on 802.1Q tunnel ports and is on a per-port group basis only.

To avoid ingress-CoS mutation configuration failures, only create EtherChannels where all member ports support ingress-CoS mutation or where no member ports support ingress-CoS mutation. Do not create EtherChannels with mixed support for ingress-CoS mutation.

If you configure ingress-CoS mutation on a port that is a member of an EtherChannel, the ingress-CoS mutation is applied to the port-channel interface.

You can configure ingress-CoS mutation on port-channel interfaces.

Examples

This example shows how to define a CoS-to-CoS map:

Router(config)# mls qos map cos-mutation test-map 1 2 3 4 5 6 7 1

Related Commands

mls qos map dscp-cos

To define an egress differentiated services code point (DSCP)-to-class of service (CoS) map, use the mls qos map dscp-cos command in global configuration mode. To remove a prior entry, use the no form of this command.

mls qos map dscp-cos dscp-values to cos-values

no mls qos map dscp-cos

Syntax Description

Command Default

The default DSCP-to-CoS map is listed in Table 16.

Command Modes

Global configuration

Command History

Usage Guidelines

The DSCP-to-CoS map is used to map the final DSCP classification to a final CoS. This final map determines the output queue and threshold to which the packet is assigned. The CoS map is written into the Inter-Switch Link (ISL) header or 802.1Q tag of the transmitted packet on trunk interfaces and contains a table of 64 DSCP values and the corresponding CoS values. The Catalyst 6500 series switch and the Cisco 7600 series router have one map.

All of the CoS-to-DSCP and DSCP-to-CoS maps are globally defined. You apply all maps to all ports.

If you enter the mls qos trust cos command, the default CoS-to-DSCP map is applied.

If you enter the mls qos trust dscp command, the default DSCP-to-CoS map is applied.

After a default map is applied, you can define the CoS-to-DSCP or DSCP-to-CoS map by entering consecutive mls qos map commands.

If the mls qos trust dscp command is entered and a packet with an untrusted DSCP value is at an ingress port, the packet CoS value is set to 0.

Use the show mls qos maps privileged EXEC command to verify your settings.

Examples

The following example shows how to define the DSCP-to-CoS map. DSCP values 16, 18, 24, and 26 are mapped to CoS 1. DSCP values 0, 8, and 10 are mapped to CoS 0.

Router# configure terminal

Router(config)# mls qos map dscp-cos 16 18 24 26 to 1

Router(config)# mls qos map dscp-cos 0 8 10 to 0

Related Commands

mls qos map dscp-exp

To map the final differentiated services code point (DSCP) value to the final experimental (EXP) value, use the mls qos map dscp-exp command in global configuration mode. To remove a prior entry, use the no form of this command.

mls qos map dscp-exp dscp-values to exp-values

no mls qos map dscp-exp

Syntax Description

Command Default

The default DSCP-to-EXP map is listed in Table 17.

Command Modes

Global configuration

Command History

Usage Guidelines

This command is supported in PFC3BXL or PFC3B mode only.

The DSCP-to-EXP map is used to map the final DSCP value to a final EXP value. This final map determines the output queue and threshold to which the packet is assigned. The EXP map contains a table of 64 DSCP values and the corresponding EXP values. The Catalyst 6500 series switch and the Cisco 7600 series router have one map.

You can enter up to eight DSCP values separated by a space. You can enter up to eight EXP values separated by a space.

Examples

This example shows how to configure the final DSCP value to a final EXP value:

Router(config)# mls qos map dscp-exp 20 25 to 3

Related Commands

mls qos map dscp-mutation

To define a named differentiated services code point (DSCP) mutation map, use the mls qos map dscp-mutation command in global configuration mode. To return to the default mapping, use the no form of this command.

mls qos map dscp-mutation map-name input-dscp1 [input-dscp2 [input-dscp3 [input-dscp4 [input-dscp5 [input-dscp6 [input-dscp7 [input-dscp8]]]]]]] to output-dscp

no mls qos map dscp-mutation map-name

Syntax Description

Command Default

output-dscp equals input-dscp.

Command Modes

Global configuration

Command History

Usage Guidelines

This command is not supported on the Catalyst 6500 series switches and the Cisco 7600 series routers that are configured with a Supervisor Engine 2.

When configuring a named DSCP mutation map, note the following:

•You can enter up to eight input DSCP values that map to a mutated DSCP value.

•You can enter multiple commands to map additional DSCP values to a mutated DSCP value.

•You can enter a separate command for each mutated DSCP value.

You can configure 15 egress-DSCP mutation maps to mutate the internal DSCP value before it is written as the egress-DSCP value. You can attach egress-DSCP mutation maps to any interface that Policy Feature Card (PFC) QoS supports.

PFC QoS derives the egress-class-of-service (CoS) value from the internal DSCP value. If you configure egress-DSCP mutation, PFC QoS does not derive the egress-CoS value from the mutated DSCP value.

Examples

This example shows how to map DSCP 30 to mutated DSCP value 8:

Router(config)# mls qos map dscp-mutation mutemap1 30 to 8 

Related Commands

mls qos map exp-dscp

To define the ingress Experimental (EXP) value to the internal differentiated services code point (DSCP) map, use the mls qos map exp-dscp command in global configuration mode. To return to the default mapping, use the no form of this command.

mls qos map exp-dscp dscp-values

no mls qos map exp-dscp

Syntax Description

Command Default

The default EXP-to-DSCP map is listed in Table 18.

Command Modes

Global configuration

Command History

Usage Guidelines

This command is supported in PFC3BXL or PFC3B mode only.

The DSCP in these maps refers to the internal DSCP, not the packet DSCP.

The EXP-to-DSCP map is used to map the received EXP value to the internal DSCP map. This final map determines the output queue and threshold to which the packet is assigned. The EXP map contains a table of 64 DSCP values and the corresponding EXP values. The Catalyst 6500 series switch and the Cisco 7600 series router have one map.

You can enter up to eight DSCP values separated by a space.

Examples

This example shows how to configure the received EXP value to an internal DSCP value:

Router(config)# mls qos map exp-dscp 20 25 30 31 32 32 33 34

Related Commands

mls qos map exp-mutation

To map the Experimental (EXP) value of a packet to a new EXP value, use the mls qos map exp-mutation command in global configuration mode. To return to the default mapping, use the no form of this command.

mls qos map exp-mutation map-name mutated-exp1 mutated-exp2 mutated-exp3 mutated-exp4 mutated-exp5 mutated-exp6 mutated-exp7 mutated-exp8

no mls qos map exp-mutation map-name

Syntax Description

Command Default

If the EXP-to-EXP mutation map is not configured, the default EXP-to-EXP mutation mapping is listed in Table 19.

Command Modes

Global configuration

Command History

Usage Guidelines

This command is not supported on the Catalyst 6500 series switch and the Cisco 7600 series router that are configured with a Supervisor Engine 2.

This command is supported in PFC3BXL or PFC3B mode only.

When you enter the mls qos map exp-mutation command, you are configuring the mutated EXP values map to the sequential EXP numbers. For example, by entering the mls qos map exp-mutation 2 3 4 5 6 7 0 1 command, you configure the map as shown in Table 20 below:

Separate the eight EXP values by a space.

After you define the map in global configuration mode, you can attach the map to a port.

You can configure 15 ingress-EXP mutation maps to mutate the internal EXP value before it is written as the ingress-EXP value. You can attach ingress-EXP mutation maps to any interface that Policy Feature Card (PFC) quality of service (QoS) supports.

The PFC QoS derives the egress EXP value from the internal differentiated services code point (DSCP) value. If you configure ingress-EXP mutation, PFC QoS does not derive the ingress-EXP value from the mutated EXP value.

Examples

This example shows how to map the EXP value of a packet to a new EXP value:

Router(config)# mls qos map exp-mutation mutemap1 1 2 3 4 5 6 7 0

Related Commands

mls qos map ip-prec-dscp

To define an ingress-IP precedence-to-differentiated-services-code-point (DSCP) map for trusted interfaces, use the mls qos map ip-prec-dscp command in global configuration mode. To remove a prior entry, use the no form of this command.

mls qos map ip-prec-dscp dscp-values

no mls qos map ip-prec-dscp

Syntax Description

Command Default

The default IP precedence-to-DSCP configuration is listed in Table 21.

Command Modes

Global configuration

Command History

Usage Guidelines

Use the mls qos map ip-prec-dscp command to map the IP precedence of IP packets arriving on trusted interfaces (or flows) to a DSCP when the trust type is trust-ipprec.

You can enter up to eight DSCP values separated by a space.

This map is a table of eight precedence values (0 through 7) and their corresponding DSCP values. The Catalyst 6500 series switch and the Cisco 7600 series router have one map. The IP precedence values are as follows:

•network 7

•internet 6

•critical 5

•flash-override 4

•flash 3

•immediate 2

•priority 1

•routine 0

Examples

This example shows how to configure the ingress-IP precedence-to-DSCP mapping for trusted interfaces:

Router(config)# mls qos map ip-prec-dscp 20 30 1 43 63 12 13 8

Related Commands

mls qos map policed-dscp

To set the mapping of policed differentiated services code point (DSCP) values to marked-down DSCP values, use the mls qos map policed-dscp command in global configuration mode. To remove a prior entry, use the no form of this command.

mls qos map policed-dscp dscp-list to policed-dscp

no mls qos map policed-dscp

Catalyst 6500 Series Switches and Cisco 7600 Series Routers

mls qos map policed-dscp {normal-burst | max-burst} dscp1 [dscp2 [dscp3 [dscp4 [dscp5 [dscp6 [dscp7 [dscp8]]]]]]] to policed-dscp

no mls qos map policed-dscp

Syntax Description

Command Default

No marked-down values are configured.

Command Modes

Global configuration

Command History

Usage Guidelines

The DSCP-to-policed-DSCP map determines the marked-down DSCP value that is applied to out-of-profile flows. The Catalyst 6500 series switch and the Cisco 7600 series router have one map.

You can enter up to eight DSCP values separated by a space.

You can enter up to eight policed DSCP values separated by a space.

Note To avoid out-of-sequence packets, configure the DSCP-to-policed-DSCP map so that marked-down packets remain in the same queue as the in-profile traffic.

Examples

This example shows how to map multiple DSCPs to a single policed-DSCP value:

Router(config)# mls qos map policed-dscp 20 25 43 to 4

Related Commands

mls qos marking ignore port-trust

To mark packets even if the interface is trusted, use the mls qos marking ignore port-trust command in global configuration mode. To return to the default settings, use the no form of this command.

mls qos marking ignore port-trust

no mls qos marking ignore port-trust

Syntax Description

This command has no arguments or keywords.

Command Default

Port trust is enabled.

Command Modes

Global configuration

Command History

Usage Guidelines

Use the mls qos marking ignore port-trust command to mark packets even if the interface is trusted.

Examples

This example shows how to mark packets even if the interface is trusted:

mls qos marking ignore port-trust

This example shows how to re-enable port trust:

no mls qos marking ignore port-trust

Related Commands

mls qos marking statistics

To disable allocation of the policer-traffic class identification with set actions, use the mls qos marking statistics command in global configuration mode. To return to the default settings, use the no form of this command.

mls qos marking statistics

no mls qos marking statistics

Syntax Description

This command has no arguments or keywords.

Command Default

Enabled

Command Modes

Global configuration

Command History

Usage Guidelines

This command is not supported on Cisco 7600 series routers that are configured with a Supervisor Engine 2.

Use the show policy-map interface command to display policy-map statistics.

Examples

This example shows how to disable allocation of the policer-traffic class identification with set actions:

Router(config)# mls qos marking statistics

This example shows how to allow allocation of the policer-traffic class identification with set actions:

Router(config)# no mls qos marking statistics

Related Commands

mls qos mpls trust experimental

To set the trusted state of Multiprotocol Label Switching (MPLS) packets only, use the mls qos mpls trust experimental command in interface configuration mode. To set the trusted state of MPLS packets to untrusted, use the no form of this command.

mls qos mpls trust experimental

no mls qos mpls trust experimental

Syntax Description

This command has no arguments or keywords.

Command Default

With the trusted state enabled, the defaults are as follows:

•Untrusted—The packets are marked to 0 or by policy.

•trust-cos.

With the trusted state disabled, the defaults are as follows:

•trust-exp—The port or policy trust state is ignored.

•The packets are marked by policy.

Command Modes

Interface configuration (config-if)

Command History

Usage Guidelines

You can enter the mls qos mpls trust experimental command to treat MPLS packets as other Layer 2 packets for class of service (CoS) and egress queueing purposes (for example, to apply port or policy trust). All trusted cases (trust CoS/IP/Differentiated Services Code Point (DSCP)) are treated as trust-cos.

Class of Service (CoS) refers to three bits in either an ISL header or an 802.1Q header that are used to indicate the priority of the Ethernet frame as it passes through a switched network. The CoS bits in the 802.1Q header are commonly referred to as the 802.1p bits. To maintain QoS when a packet traverses both Layer 2 and Layer 3 domain, the ToS and CoS values can be mapped to each other.

Examples

This example shows how to set the trusted state of MPLS packets to trust-cos:

Router(config-if)# mls qos mpls trust experimental 

This example shows how to set the trusted state of MPLS packets to untrusted:

Router(config-if)# no mls qos mpls trust experimental 

Related Commands

mls qos police redirected

To turn on access control list (ACL)-redirected packet policing, use the mls qos police redirected command in global configuration mode. To turn off ACL-redirected packet policing, use the no form of this command.

mls qos police redirected

no mls qos police redirected

Syntax Description

This command has no arguments or keywords.

Command Default

Enabled

Command Modes

Global configuration

Command History

Usage Guidelines

This command is supported on PFC3BXL or PFC3B mode only. With Release 12.2(17b)SXA, enter the show platform earl-mode command to display the PFC3 mode.

This command is not supported on Cisco 7600 series routers that are configured with a Supervisor Engine 2.

Use the no mls qos police redirected command whenever you require NetFlow Data Export (NDE) accuracy (if you do not require QoS-redirected packets).

Examples

This example shows how to turn on the ACL-redirected packet policing:

Router(config)# mls qos police redirected

This example shows how to turn off the ACL-redirected packet policing:

Router(config)# no mls qos police redirected

Related Commands

mls qos police serial

To enable serial mode for ingress and egress policers on the PFC3C or PFC3CXL, use the mls qos police serial command in global configuration mode. To reset the policing mode to parallel, use the no form of the command.

mls qos police serial

no mls qos police serial

Syntax Description

This command has no arguments or keywords.

Command Default

This command is disabled by default.

Command Modes

Global configuration (config)

Command History

Usage Guidelines

You can use the mls qos police serial command to configure the PFC3C or PFC3CXL ingress and egress policers to operate independently of each other (in serial mode). Normally, ingress and egress policers operate in parallel mode, where action by one policer causes a corresponding action in the other. For example, if the egress policer drops a packet, the ingress policer does not count the packet either. In serial mode, however, action by one policer does not cause a corresponding action in the other.

Note This command does not affect marking using policers.

Examples

The following command example shows how to enable serial policing mode on the PFC3C or PFC3CXL:

Router(config)# mls qos police serial 

mls qos protocol

To define routing-protocol packet policing, use the mls qos protocol command in global configuration mode. To return to the default settings, use the no form of this command.

mls qos protocol protocol-name {pass-through | police rate [burst] | precedence value [police rate [burst]]}

no mls qos protocol protocol-name

Syntax Description

Command Default

The defaults are as follows:

•burst is 1000 bits per second.

•If quality of service (QoS) is enabled, the differentiated services code point (DSCP) value is rewritten to zero.

•If QoS is disabled, the port is in a pass-through mode (no marking or policing is applied).

Command Modes

Global configuration (config)

Command History

Usage Guidelines

This command does not support ARP, ISIS, or EIGRP on Cisco 7600 series routers that are configured with a Supervisor Engine 2.

If you enter the precedence value keyword and arguments without entering the police rate burst keyword and arguments, only the packets from an untrusted port are marked.

You can make the protocol packets avoid the per-interface policy maps by entering the police rate, pass-through, or precedence value keywords and arguments.

The mls qos protocol command allows you to define the routing-protocol packet policing as follows:

•When you specify the pass-through mode, the DSCP value does not change and is not policed.

•When you set the police rate, the DSCP value does not change and is policed.

•When you specify the precedence value, the DSCP value changes for the packets that come from an untrusted port, the class of service (CoS) value that is based on DSCP-to-CoS map changes, and the traffic is not policed.

•When you specify the precedence value and the police rate, the DSCP value changes, the CoS value that is based on DSCP-to-CoS map changes, and the DSCP value is policed. In this case, the DSCP value changes are based on the trust state of the port; the DSCP value is changed only for the packets that come from an untrusted port.

•If you do not enter a precedence value, the DSCP value is based on whether or not you have enabled multilayer switching (MLS) QoS as follows:

–If you enabled MLS QoS and the port is untrusted, the internal DSCP value is overwritten to zero.

–If you enabled MLS QoS and the port is trusted, then the incoming DSCP value is maintained.

You can make the protocol packets avoid policing completely if you choose the pass-through mode. If the police mode is chosen, the committed information rate (CIR) specified is the rate that is used to police all the specified protocol's packets, both entering or leaving the Cisco 7600 series router.

To protect the system by ARP broadcast, you can enter the mls qos protocol arp police bps command.

Examples

This example shows how to define the routing-protocol packet policing:

Router(config)# mls qos protocol arp police 43000

This example shows how to avoid policing completely:

Router(config)# mls qos protocol arp pass-through

This example shows how to define the IP-precedence value of the protocol packets to rewrite:

Router(config)# mls qos protocol bgp precedence 4

This example shows how to define the IP-precedence value of the protocol packets to rewrite and police the DSCP value:

Router(config)# mls qos protocol bgp precedence 4 police 32000 1200

Related Commands

mls qos queueing-only

To enable port-queueing mode, use the mls qos queueing-only command in global configuration mode. To disable the port-queueing mode, use the no form of this command.

mls qos queueing-only

no mls qos queueing-only

Syntax Description

This command has no arguments or keywords.

Command Default

Quality of service (QoS) is globally disabled.

Command Modes

Global configuration

Command History

Usage Guidelines

In port-queueing mode, Policy Feature Card (PFC) QoS (marking and policing) is disabled, and packet type of service (ToS) and class of service (CoS) are not changed by the PFC. All queueing on rcv and xmt is based on a QoS tag in the incoming packet, which is based on the incoming CoS.

For 802.1Q or Inter-Link Switch (ISL)-encapsulated port links, queueing is based on the packet 802.1Q or ISL CoS.

For router main interfaces or access ports, queueing is based on the configured per-port CoS (the default CoS is 0).

Examples

This example shows how to enable the port-queueing mode globally:

Router(config)# mls qos queueing-only

This example shows how to disable the port-queueing mode globally:

Router(config)# no mls qos queueing-only

Related Commands

mls qos queue-mode mode-dscp

To set the queuing mode to Differentiated Services Code Point (DSCP) on an interface, use the mls qos queue-mode mode-dscp command in interface configuration mode. To return to the default settings, use the no form of this command.

mls qos queue-mode mode-dscp

no mls qos queue-mode mode-dscp

Syntax Description

This command has no arguments or keywords.

Command Default

The queuing mode of an interfaces is class of service (CoS) mode.

Command Modes

Interface configuration (config-if)

Command History

Usage Guidelines

This command is supported on 10-Gigabit Ethernet ports only.

You should configure ports to trust DSCP only if they receive traffic that carries valid Layer 3 DSCP.

In Release 12.2(18)SXF5 and later releases, you can enable DSCP-based ingress queues and thresholds on WS-X6708-10GE ports to provide congestion avoidance.

In releases earlier than Release 12.2(18)SXF5, the ingress port queues and thresholds use only Layer 2 Class of Service (CoS), and Policy Feature Card (PFC) QoS does not implement ingress port congestion avoidance on ports configured to trust DSCP.

For traffic from trust DSCP ports, Policy Feature Card (PFC) QoS uses the received DSCP value as the initial internal DSCP value. PFC QoS does not mark any traffic on ingress ports configured to trust received DSCP.

Examples

This example shows how to set the queuing mode to DSCP on an interface:

mls qos queue-mode mode-dscp

Related Commands

mls qos rewrite ip dscp

To enable type of service (ToS)-to-differentiated services code point (DSCP) rewrite, use the mls qos rewrite ip dscp command in global configuration mode. To disable ToS-to-DSCP rewrite, use the no form of this command.

mls qos rewrite ip dscp [slot slot1,slot2,slot3...]

no mls qos rewrite ip dscp [slot slot1,slot2,slot3...]

Syntax Description

Command Default

ToS-to-DSCP rewrite is enabled.

Command Modes

Global configuration (config)

Command History

Usage Guidelines

This command is not supported on Cisco 7600 series routers that are configured with a Supervisor Engine 2.

If you disable ToS-to-DSCP rewrite, and QoS is enabled globally, the following occurs:

•Final ToS-to-DSCP rewrite is disabled, and the DSCP packet is preserved.

•Policing and marking function according to the QoS configuration.

•Marked and marked-down class of service (CoS) is used for queueing.

•In QoS disabled mode, both ToS and CoS are preserved.

The no mls qos rewrite ip dscp command is incompatible with Multiprotocol Label Switching (MPLS). The default mls qos rewrite ip dscp command must remain enabled in order for the PFC3BXL or PFC3B to assign the correct MPLS Experimental (EXP) value for the labels that it imposes. This restriction does not apply to PFC3C or PFC3CXL forward.

The mls qos rewrite ip dscp slot command can be used for disabling ToS-to-DSCP rewrite on supervisors or DFC linecards. Although the command will be accepted for non-DFC linecard slots, it does not come into effect unless a DFC linecard is inserted into that slot.

To disable rewrite on packets that are coming in on non-DFC linecards, disable the rewrite on the supervisor slots. Note that this disables the rewrite on packets that are coming in on all non-DFC linecards on the system.

Examples

The following example shows how to enable ToS-to-DSCP rewrite in slot 4:

Router(config)# mls qos rewrite ip dscp slot 4

The following example shows how to disable port-queueing mode globally:

Router(config)# no mls qos rewrite ip dscp

Related Commands

mls qos statistics-export (global configuration)

To enable quality of service (QoS)-statistics data export globally, use the mls qos statistics-export command in global configuration mode. To disable QoS-statistics data export globally, use the no form of this command.

mls qos statistics-export

no mls qos statistics-export

Syntax Description

This command has no arguments or keywords.

Command Default

Disabled

Command Modes

Global configuration

Command History

Usage Guidelines

You must enable data export globally to set up data export on your Cisco 7600 series router.

QoS-statistics data export is not supported on OSM interfaces.

For QoS-statistics data export to perform correctly, you should set the export-destination hostname or IP address and the User Datagram Port (UDP) number.

Examples

This example shows how to enable data export globally:

Router(config)# mls qos statistics-export

This example shows how to disable data export globally:

Router(config)# no mls qos statistics-export

Related Commands

mls qos statistics-export (interface configuration)

To enable per-port quality of service (QoS)-statistics data export, use the mls qos statistics-export command in interface configuration mode. To disable per-port QoS-statistics data export, use the no form of this command.

mls qos statistics-export

no mls qos statistics-export

Syntax Description

This command has no arguments or keywords.

Command Default

Disabled

Command Modes

Interface configuration

Command History

Usage Guidelines

QoS-statistics data export is not supported on OSM interfaces.

You must enable data export on the port and globally to set up data export on your Cisco 7600 series router.

For QoS-statistics data export to perform correctly, you should set the export-destination hostname or IP address and the User Datagram Port (UDP) number.

QoS-statistics data is exported using delimiter-separated fields. You can set the delimiter by entering the mls qos statistics-export delimiter command.

Port statistics are exported; port QoS statistics are not exported. For each data export-enabled port, the following information is exported:

•Type (1 denotes the type of port)

•Module/port

•In packets (cumulated hardware-counter values)

•In bytes (cumulated hardware-counter values)

•Out packets (cumulated hardware-counter values)

•Out bytes (cumulated hardware-counter values)

•Time stamp (time in seconds since January 1, 1970 UTC relative)

For example, if you have QoS-statistics data export that is enabled on FastEthernet4/5, the exported records could be (in this example, the delimiter is a | [pipe]) as follows:

|1|4/5|123|80|12500|6800|982361894|

Examples

This example shows how to enable QoS-statistics data export:

Router(config-if)# mls qos statistics-export 

This example shows how to disable QoS-statistics data export:

Router(config-if)# no mls qos statistics-export 

Related Commands

mls qos statistics-export aggregate-policer

To enable quality of service (QoS)-statistics data export on the named aggregate policer, use the mls qos statistics-export aggregate-policer command in global configuration mode. To disable QoS-statistics data export on the named aggregate policer, use the no form of this command.

mls qos statistics-export aggregate-policer policer-name

no mls qos statistics-export aggregate-policer policer-name

Syntax Description

Command Default

Disabled for all shared aggregate policers.

Command Modes

Global configuration

Command History

Usage Guidelines

QoS-statistics data export is not supported on Optical Services Modules (OSM) interfaces.

You must enable data export on the shared aggregate policer and globally to set up data export on your Cisco 7600 series router.

QoS-statistics data is exported using delimiter-separated fields. You can set the delimiter by entering the mls qos statistics-export delimiter command.

For each data export-enabled shared aggregate or named policer, statistics data per policer per EARL is exported. For each data export-enabled shared aggregate or named policer, the following information is exported:

•Type (3 denotes aggregate policer export type)

•Aggregate name

•Direction (in or out)

•Encoded Address Recognition Logic (EARL) identification

•Accepted packets (accumulated hardware-counter values)

•Exceeded normal-rate packets (accumulated hardware-counter values)

•Exceeded excess-rate packets (accumulated hardware-counter values)

•Time stamp (time in seconds since January 1, 1970 UTC relative)

If a shared aggregate policer is attached to policies in both directions, two records are exported (one in each direction). Each record will contain the same counter values for accepted packets, exceeded normal packet rates, and exceeded excess packet rates.

For example, if you have the following configuration:

•QoS-statistics data export that is enabled on the shared aggregate policer named "aggr_1"

•An EARL in the supervisor engine that is installed in slot 1

•An EARL on the Distributed Forwarding Card (DFC) that is installed in slot 3

the exported records could be (note that in this example, the delimiter is a | [pipe]) as follows:

|3|agg_1|in|1|45543|2345|982361894|

|3|agg_1|in|3|45543|2345|982361894|

Examples

This example shows how to enable per-shared aggregate or named-policer data export:

Router(config)# mls qos statistics-export aggregate-policer aggr1M 

Related Commands

mls qos statistics-export class-map

To enable quality of service (QoS)-statistics data export for a class map, use the mls qos statistics-export class-map command in global configuration mode. To disable QoS-statistics data export for a class map, use the no form of this command.

mls qos statistics-export class-map classmap-name

no mls qos statistics-export class-map classmap-name

Syntax Description

Command Default

Disabled

Command Modes

Global configuration

Command History

Usage Guidelines

QoS-statistics data export is not supported on OSM interfaces.

You must enable data export on the class map and globally to set up data export on your Cisco 7600 series router.

QoS-statistics data is exported using delimiter-separated fields. You can set the delimiter by entering the mls qos statistics-export delimiter command.

For each data export-enabled class map, statistics data per policer per interface is exported. If the interface is a physical interface, the following information is exported:

•Type (4 denotes class map physical export)

•Class-map name

•Direction (in or out)

•Module/port

•Accepted packets (accumulated hardware-counter values)

•Exceeded normal-rate packets (accumulated hardware-counter values)

•Exceeded excess-rate packets (accumulated hardware-counter values)

•Time stamp (time in seconds since January 1, 1970 UTC relative)

If the interface is a Cisco 7600 series router VLAN, the following information is exported:

•Type (5 denotes class-map VLAN export)

•Class-map name

•Direction (in or out)

•Encoded Address Recognition Logic (EARL) identification (slot number in which the EARL is installed)

•VLAN number

•Accepted packets (cumulated hardware-counter values)

•Exceeded normal-rate packets (cumulated hardware-counter values)

•Exceeded excess-rate packets (cumulated hardware-counter values)

•Time stamp (time in seconds since January 1, 1970 UTC relative)

If the interface is a Cisco 7600 series router port channel, the following information is exported:

•Type (6 denotes class-map port-channel export)

•Class-map name

•Direction (in or out)

•EARL identification (slot number in which the EARL is installed)

•Port-channel number

•Accepted packets (cumulated hardware-counter values)

•Exceeded normal-rate packets (cumulated hardware-counter values)

•Exceeded excess-rate packets (cumulated hardware-counter values)

•Time stamp (time in seconds since January 1, 1970 UTC relative)

For example, if you have the following configuration:

•QoS-statistics data export enabled on the class map named "class_1"

•An EARL in the supervisor engine that is installed in slot 1

•An EARL on the Distributed Forwarding Card (DFC) that is installed in slot 3

•The Cisco 7600 series router is in the policy map named "policy_1"

•policy_1 is attached to the following interfaces in the ingress direction:

–FastEthernet4/5

–VLAN 100

–Port-channel 24

The exported records could be (in this example, the delimiter is a | [pipe]) as follows:

|4|class_1|in|4/5|45543|2345|2345|982361894|

|5|class_1|in|1|100|44000|3554|36678|982361894|

|5|class_1|in|3|100|30234|1575|1575|982361894|

Examples

This example shows how to enable QoS-statistics data export for a class map:

Router(config)# mls qos statistics-export class-map class3 

Related Commands

mls qos statistics-export delimiter

To set the quality of service (QoS)-statistics data-export field delimiter, use the mls qos statistics-export delimiter command in global configuration mode. To return to the default settings, use the no form of this command.

mls qos statistics-export delimiter

no mls qos statistics-export delimiter

Syntax Description

This command has no arguments or keywords.

Command Default

The default delimiter is the pipe character (|).

Command Modes

Global configuration

Command History

Usage Guidelines

QoS-statistics data export is not supported on Optical Service Module (OSM) interfaces.

You must enable data export globally to set up data export on your Cisco 7600 series router.

Examples

This example shows how to set the QoS-statistics data-export field delimiter (a comma) and verify the configuration:

Router(config)# mls qos statistics-export delimiter , 

Related Commands

mls qos statistics-export destination

To configure the quality of service (QoS)-statistics data-export destination host and User Datagram Protocol (UDP) port number, use the mls qos statistics-export destination command in global configuration mode. To return to the default settings, use the no form of this command.

mls qos statistics-export destination {host-name | host-ip-address} {port port-number | syslog} [facility facility-name] [severity severity-value]

Syntax Description

Command Default

The default is none unless syslog is specified. If syslog is specified, the defaults are as follows:

•port is 514.

•facility is local6.

•severity is debug.

Command Modes

Global configuration

Command History

Usage Guidelines

QoS-statistics data export is not supported on Optical Service Module (OSM) interfaces.

Valid facility values are as follows:

•authorization—Security/authorization messages

•cron—Clock daemon

•daemon—System daemon

•kernel—Kernel messages

•local0—Local use 0

•local1—Local use 1

•local2—Local use 2

•local3—Local use 3

•local4—Local use 4

•local5—Local use 5

•local6—Local use 6

•local7—Local use 7

•lpr—Line printer subsystem

•mail—Mail system

•news—Network news subsystem

•syslog—Messages that are generated internally by syslogd

•user—User-level messages

•uucp—UNIX-to-UNIX Copy Program (UUCP) subsystem

Valid severity levels are as follows:

•alert—Action must be taken immediately

•critical—Critical conditions

•debug—Debug-level messages

•emergency—System is unusable

•error—Error conditions

•informational—Informational

•notice—Normal but significant conditions

•warning—Warning conditions

Examples

This example shows how to specify the destination host address and syslog as the UDP port number:

Router(config)# mls qos statistics-export destination 172.20.52.3 syslog 

Related Commands

mls qos statistics-export interval

To specify how often a port and/or aggregate-policer quality of service (QoS)-statistics data is read and exported, use the mls qos statistics-export interval command in global configuration mode. To return to the default settings, use the no form of this command.

mls qos statistics-export interval interval

no mls qos statistics-export interval

Syntax Description

Command Default

300 seconds

Command Modes

Global configuration

Command History

Usage Guidelines

QoS-statistics data export is not supported on Optical Services Module (OSM) interfaces.

The interval needs to be short enough to avoid counter wraparound with the activity in your configuration.

Caution Be careful when decreasing the interval because exporting QoS statistics imposes a noticeable load on the Cisco 7600 series router.

Examples

This example shows how to set the QoS-statistics data-export interval:

Router(config)# mls qos statistics-export interval 250 

Related Commands

mls qos supervisor 10g-only

To configure the Cisco 7600 RSP720-10GE to run QoS only on the 10GE uplink ports, use the mls qos supervisor 10g-only command in global configuration mode. Use the no form of the command to reconfigure the RSP to run QoS on all the uplink ports (10GE and 1GE).

mls qos supervisor 10g-only

no mls qos supervisor 10g-only

Syntax Description

This command has no arguments or keywords.

Defaults

This command is disabled by default.

Command Modes

Global configuration

Command History

Usage Guidelines

The RSP720-10GE has both 10GE and 1GE uplink ports. You can configure the RSP720-10GE to run QoS features on all uplink ports (mixed mode) or on 10GE ports only. The number of queues available for QoS depends on which mode is used:

•In mixed mode (10GE and 1GE ports), the default, only four queues are available for QoS.

The QoS port architecture for fixed mode for 1GE ports is (Rx/Tx): 2q8t/1p3q8t.

•In 10GE only mode, eight queues are available for QoS.

The QoS port architecture for 10GE only mode is as follows (Rx/Tx):

–8q8t/1p7q8t (CoS)

–16q8t/1p15q8t (DSCP)

–16q1t/1p15q1t (VLAN)

When you switch between mixed-mode QoS and 10GE only mode, service is temporarily lost on the RSP720-10GE uplinks. In addition, when you switch between modes, any existing QoS configuration on the uplinks is lost. You must reconfigure QoS.

When you switch from 10GE only to mixed-mode QoS, you must issue the no shutdown command on each of the three 1GE ports to resume QoS service on those ports.

In 10GE only mode, the 1GE ports are visible but they remain in an administratively down state.

Note To obtain more information on queues, use the show queueing interface command.

Examples

The following example shows how to configure the RSP720-10GE to run QoS on 10GE ports only:

Router(config)# mls qos supervisor 10g-only

The following ports will be shut to enable 10g-only mode:

Gix/1 Gix/2 Gix/3 

The following example shows how in a redundant setup (High Availability), the 1GE uplink ports on both supervisors are shut down even though the redundant links are not used:

Router(config)# mls qos supervisor 10g-only

The following ports will be shut to enable 10g-only mode:

Gi6/1 Gi6/2 Gi6/3 Gi5/1 Gi5/2 Gi5/3 

Related Commands

mls qos trust

To configure the multilayer switching (MLS) quality of service (QoS) port trust state and to classify traffic by examining the class of service (CoS) or differentiated services code point (DSCP) value, use the mls qos trust command in interface configuration mode. To return a port to its untrusted state, use the no form of this command.

mls qos trust [cos | device cisco-phone | dscp | ip-precedence ]

no mls qos trust

Syntax Description

Command Default

The defaults are as follows:

•If you enable global QoS, the port is not trusted.

•If no keyword is specified or the global QoS is disabled, the default is dscp.

Command Modes

Interface configuration (config-if)

Command History

Usage Guidelines

Packets that enter a QoS domain are classified at its edge. Because the packets are classified at the edge, the switch port within the QoS domain can be configured to a trusted state. It is not necessary to classify the packets at every switch within the domain. Use the mls qos trust command to set the trusted state of an interface and to indicate which fields of the packet are used to classify traffic.

When a port is configured with trust DSCP or trust IP precedence and the incoming packet is a non-IP packet, the CoS-to-DSCP map is used to derive the corresponding DSCP value from the CoS value. The CoS can be the packet CoS for trunk ports or the port default CoS for nontrunk ports.

If the DSCP is trusted, the DSCP field of the IP packet is not modified. However, it is still possible that the CoS value of the packet is modified (according to DSCP-to-CoS map).

If the CoS is trusted, the CoS field of the packet is not modified, but the DSCP can be modified (according to CoS-to-DSCP map) if the packet is an IP packet.

The trusted boundary with Cisco device verification feature, implemented with the device cisco-phone keywords, prevents security problems if users connect a non-phone device to a switch port that is configured to support a Cisco IP phone. You must globally enable CDP on the switch and on the port connected to the IP phone. If a Cisco IP phone is not detected, QoS does not apply any configured nondefault trust setting, which prevents misuse of a high-priority queue.

If you configure the trust setting for DSCP or IP precedence, the DSCP or IP precedence values in the incoming packets are trusted. If you configure the mls qos cos override interface configuration command on the switch port connected to the IP phone, the switch overrides the CoS of the incoming voice and data packets and assigns the default CoS value to them.

For an inter-QoS domain boundary, you can configure the port to the DSCP-trusted state and apply the DSCP-to-DSCP-mutation map if the DSCP values are different between the QoS domains.

Classification using a port trust state (for example, mls qos trust [cos | dscp | ip-precedence] and a policy map (for example, service-policy input policy-map-name) are mutually exclusive. The last one configured overwrites the previous configuration.

The following conditions apply to the mls qos trust command running on the Catalyst 6500 series switches or the Cisco 7600 series routers:

•The cos keyword is not supported for pos or atm interface types.

•The trust state does not apply to FlexWAN modules.

•The trust state does not apply to 1q4t LAN ports except for Gigabit Ethernet ports.

•Incoming queue drop thresholds are not implemented when you enter the mls qos trust cos command on 4-port Gigabit Ethernet WAN modules.

Note Use the set qos-group command to set the trust state on Catalyst 6500 series switch and Cisco 7600 series router Layer 2 WAN interfaces.

Examples

The following example shows how to set the trusted state of an interface to IP precedence:

Router(config-if)# mls qos trust ip-precedence

The following example shows how to configure CDP to detect a Cisco IP phone connected to the port:

Router(config-if)# mls qos trust device cisco-phone

Related Commands

mls qos trust extend

To configure the trust mode of the phone, use the mls qos trust extend command in interface configuration mode. To return to the default settings, use the no form of this command.

mls qos trust extend [cos value]

no mls qos trust extend

Syntax Description

Command Default

The default settings are as follows:

•Mode is untrusted.

•cos value is 0.

Command Modes

Interface configuration

Command History

Usage Guidelines

This command is not supported on WAN modules.

If you set the phone to trusted mode, all the packets from the PC are sent untouched directly through the phone to the Cisco 7600 series router. If you set the phone to untrusted mode, all the traffic coming from the PC are remarked with the configured CoS value before being sent to the Cisco 7600 series router.

Each time that you enter the mls qos trust extend command, the mode is changed. For example, if the mode was previously set to trusted, if you enter the command, the mode changes to untrusted. Enter the show queueing interface command to display the current trust mode.

Examples

This example shows how to set the phone that is attached to the switch port in trust mode:

Router(config-if)# interface fastethernet5/1

Router(config-if)# mls qos trust extend

This example shows how to change the mode to untrusted and set the remark CoS value to 3:

Router(config-if)# interface fastethernet5/1

Router(config-if)# mls qos trust extend cos 3

This example shows how to set the configuration to the default mode:

Router(config-if)# interface fastethernet5/1

Router(config-if)# no mls qos trust extend

Related Commands

mls qos tunnel gre input uniform-mode

To enable the original quality of service (QoS) marking of ingress packets to be copied into the differentiated services code point (DSCP) field of the ingress packet and the Generic Routing Encapsulation (GRE) header, use the mls qos tunnel gre input uniform-mode command in interface configuration mode. To disable the copying operation, use the no form of this command.

mls qos tunnel gre input uniform-mode

no mls qos tunnel gre input uniform-mode

Syntax Description

This command has no arguments or keywords.

Command Default

No marking operation is performed on the incoming packets or the GRE headers.

Command Modes

Interface configuration (config-if)

Command History

Usage Guidelines

This command is supported on Supervisor Engine 4/PFC3C systems only.

Enter the show mls qos command to verify the configuration.

Examples

The following example shows how to enable the original QoS marking of ingress packets to be copied into the DSCP field and copied in the GRE header:

Router(config-if)# mls qos tunnel gre input uniform-mode

Related Commands

mls qos vlan-based

To enable per-VLAN quality of service (QoS) for a Layer 2 interface, use the mls qos vlan-based command in interface configuration mode. To disable per-VLAN QoS for a Layer 2 interface, use the no form of this command.

mls qos vlan-based

no mls qos vlan-based

Syntax Description

This command has no arguments or keywords.

Command Default

Disabled

Command Modes

Interface configuration

Command History

Usage Guidelines

This command is supported on switch-port and port-channel interfaces only.

In VLAN-based mode, the policy map that is attached to the Layer 2 interface is ignored, and QoS is driven by the policy map that is attached to the corresponding VLAN interface.

You can configure per-VLAN QoS only on Layer 2 interfaces.

Note Layer 3 interfaces are always in interface-based mode. Layer 3 VLAN interfaces are always in VLAN-based mode.

Examples

This example shows how to enable per-VLAN QoS for a Layer 2 interface:

Router(config-if)# mls qos vlan-based

Related Commands

monitor pids

To configure the program identifiers (PIDs) to be monitored in the Media Delivery Index (MDI) flow, use the monitor pids command in the monitor metric mdi mode. To auto-learn the PIDs, use the no form of this command.

monitor pids pid1 [pid2] [pid3] [pid4] [pid5]

no monitor pids

Syntax Description

Command Default

No PIDs are configured.

Command Modes

(config-pmap-c-metric) #

Command History

Usage Guidelines

Use the monitor pids command to configure the PIDs to monitor in a MDI flow. By default, the first five PIDs in a new MDI flow stream are logged for monitoring. These PIDs can be video, audio or caption PIDs. However, monitoring PIDs for audio or caption data is not a priority for a customer implementing inline video monitoring, and is optional.

Examples

This example shows how to configure the PIDs:

router(config-pmap-c-metric)# monitor pids 4050 4678 8902

Related Commands

mpls experimental

To configure Multiprotocol Label Switching (MPLS) experimental (EXP) levels for a virtual circuit (VC) class that can be assigned to a VC bundle and thus applied to all VC members of that bundle, use the mpls experimental command in VC-class configuration mode. To remove the MPLS EXP levels from the VC class, use the no form of this command.

To configure the MPLS EXP levels for a VC member of a bundle, use the mpls experimental command in bundle-vc configuration mode. To remove the MPLS EXP levels from the VC, use the no form of this command.

mpls experimental [other | range]

no mpls experimental

Syntax Description

Defaults

Defaults to other, that is, any MPLS EXP levels in the range from 0 to 7 that are not explicitly configured.

Command Modes

VC-class configuration (for a VC class)
Bundle-vc configuration (for ATM VC bundle members)

Command History

Usage Guidelines

Assignment of MPLS EXP levels to VC bundle members allows you to create differentiated service because you can distribute the MPLS EXP levels over the different VC bundle members. You can map a single level or a range of levels to each discrete VC in the bundle, thereby enabling VCs in the bundle to carry packets marked with different levels. Alternatively, you can configure a VC with the mpls experimental other command to indicate that it can carry traffic marked with levels not specifically configured for it. Only one VC in the bundle can be configured with the mpls experimental other command to carry all levels not specified. This VC is considered the default one.

To use this command in VC-class configuration mode, enter the vc-class atm global configuration command before you enter this command. 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.

To use this command to configure an individual bundle member in bundle-VC configuration mode, first enter the bundle command to enact 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.

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

•VC configuration in bundle-VC mode

•Bundle configuration in bundle mode (with the effect of assigned VC class configuration)

•Subinterface configuration in subinterface mode

Note If you are using an ATM interface, you must configure all MPLS EXP levels (ranging from 0 to 7) for the bundle. For this configuration, Cisco recommends configuring one member of the bundle with the mpls experimental other command. The other keyword defaults to any MPLS EXP level in a range from 0 to 7 that is not explicitly configured.

Examples

The following example configures a class named control-class that includes an mpls experimental command that, when applied to a bundle, configures all VC members of that bundle to carry MPLS EXP level 7 traffic. Note that VC members of that bundle can be individually configured with the mpls experimental command at the bundle-vc level, which would supervene.

vc-class atm control-class

 mpls experimental 7

The following example configures permanent virtual circuit (PVC) 401, named control-class, to carry traffic with MPLS EXP levels in the range of 4 to 2, overriding the level mapping set for the VC through VC-class configuration:

pvc-bundle control-class 401

 mpls experimental 4-2

Related Commands