Catalyst Supervisor Engine 32 PISA IOS Command Reference, 12.2ZY

mls flow

To configure the flow mask for NDE, use the mls flow command. To restore the flow mask to the default, use the no form of this command.

mls flow {{ip | ipv6} {destination | destination-source | full | interface-destination-source | interface-full | source}}

no mls flow {ip | ipv6}

Syntax Description

Command Default

The NDE flow mask is null.

Command Modes

Global configuration (config)

Command History

Usage Guidelines

This command collects statistics for the supervisor engine.

Examples

This example shows how to set the minimum flow mask for an extended access list for MLS IP:

Router(config)# mls flow ip full

Router(config)#

Related Commands

mls ip

To enable MLS IP for the internal router on the interface, use the mls ip command. To disable MLS IP on the interface, use the no form of this command.

mls ip

no mls ip

Syntax Description

This command has no arguments or keywords.

Command Default

Multicast is disabled.

Command Modes

Interface configuration

Command History

Examples

This example shows how to enable shortcuts for MLS IP:

Router(config-if)# mls ip 

Router(config-if)# 

Related Commands

mls ip acl port expand

To enable ACL-specific features for Layer 4, use the mls ip acl port expand command. To disable the ACL-specific Layer 4 features, use the no form of this command.

mls ip acl port expand

no mls ip acl port expand

Syntax Description

This command has no arguments or keywords.

Command Default

This command has no default settings.

Command Modes

Global configuration (config)

Command History

Examples

This example shows how to enable the expansion of ACL logical operations on Layer 4 ports:

Router(config)# mls ip acl port expand

Router(config)# 

mls ip cef accounting per-prefix

To enable MLS per-prefix accounting, use the mls ip cef accounting per-prefix command. To disable MLS per-prefix accounting, use the no form of this command

mls ip cef accounting per-prefix prefix-entry prefix-entry-mask [instance-name]

no mls ip cef accounting per-prefix

Syntax Description

Command Default

This command has no default settings.

Command Modes

Global configuration (config)

Command History

Usage Guidelines

Per-prefix accounting collects the adjacency counters used by the prefix. When the prefix is used for accounting, the adjacency cannot be shared with other prefixes. You can use per-prefix accounting to account for the packets sent to a specific destination.

Examples

This example shows how to enable MLS per-prefix accounting:

Router(config)# mls ip cef accounting per-prefix 172.20.52.18 255.255.255.255

Router(config)#

This example shows how to disable MLS per-prefix accounting:

Router(config)# no mls ip cef accounting per-prefix 

Router(config)#

Related Commands

mls ip cef load-sharing

To configure the CEF load balancing, use the mls ip cef load-sharing command. To return to the default settings, use the no form of this command.

mls ip cef load-sharing [full [exclude-port {destination | source}]] [simple]

no mls ip cef load-sharing

Syntax Description

Command Default

Source and destination IP address and universal identification

Command Modes

Global configuration (config)

Command History

Usage Guidelines

The mls ip cef load-sharing command affects the IPv4, the IPv6, and the MPLS forwardings.

The mls ip cef load-sharing command is structured as follows:

•mls ip cef load-sharing full—Uses Layer 3 and Layer 4 information with multiple adjacencies.

•mls ip cef load-sharing full simple—Uses Layer 3 and Layer 4 information without multiple adjacencies.

•mls ip cef load-sharing simple—Uses Layer 3 information without multiple adjacencies.

For additional guidelines, refer to the Catalyst Supervisor Engine 32 PISA Cisco IOS Software Configuration Guide—Release 12.2ZY.

Examples

This example shows how to set load balancing to include Layer 3 and Layer 4 ports with multiple adjacencies:

Router(config)# mls ip cef load-sharing full

Router(config)#

This example shows how to set load balancing to exclude the destination Layer 4 ports and source and destination IP addresses (Layer 3) from the load-balancing algorithm:

Router(config)# mls ip cef load-sharing full exclude-port destination

Router(config)# 

This example shows how to set load balancing to exclude the source Layer 4 ports and source and destination IP addresses (Layer 3) from the load-balancing algorithm:

Router(config)# mls ip cef load-sharing full exclude-port source

Router(config)# 

This example shows how to return to the default setting:

Router(config)# no mls ip cef load-sharing

Router(config)#

Related Commands

mls ip cef rate-limit

To rate-limit CEF-punted data packets, use the mls ip cef rate-limit command. To disable the rate-limited CEF-punted data packets, use the no form of this command.

mls ip cef rate-limit pps

no mls ip cef rate-limit

Syntax Description

Command Default

No rate limit is configured.

Command Modes

Global configuration (config)

Command History

Usage Guidelines

Certain denial-of-service attacks target the route processing engines of routers. Certain packets that cannot be forwarded by the PFC are directed to the PISA for processing. Denial-of-service attacks can overload the route processing engine and cause routing instability when running dynamic routing protocols. You can use the mls ip cef rate-limit command to limit the amount of traffic that is sent to the PISA to prevent denial-of-service attacks against the route processing engine.

This command rate limits all CEF-punted data packets including the following:

•Data packets going to the local interface IP address

•Data packets requiring ARP

Setting the rate to a low value could impact the packets that are destined to the IP addresses of the local interfaces and the packets that require ARP. You should use this command to limit these packets to a normal rate and to avoid abnormal incoming rates.

For additional guidelines, refer to the Catalyst Supervisor Engine 32 PISA Cisco IOS Software Configuration Guide—Release 12.2ZY.

Examples

This example shows how to enable and set rate limiting:

Router(config)# mls ip cef rate-limit 50000

Router(config)# 

Related Commands

mls ip cef rpf hw-enable-rpf-acl

To enable hardware uRPF for packets matching the deny ace when uRPF with ACL is enabled, use the mls ip cef rpf hw-enable-rpf-acl command. To disable hardware uRPF when RPF and ACL are enabled, use the no form of this command.

mls ip cef rpf hw-enable-rpf-acl

no mls ip cef rpf hw-enable-rpf-acl

Syntax Description

This command has no arguments or keywords.

Command Default

This command has no default settings.

Command Modes

Global configuration (config)

Command History

Usage Guidelines

If you do not enter the mls ip cef rpf hw-enable-rpf-acl command, when the uRPF with ACL is specified, packets that are permitted by the uRPF ACL are forwarded in hardware and the denied packets are sent to the PISA for the uRPF check. This command enables hardware forwarding with the uRPF check for the packets that are denied by the uRPF ACL. However in this case packets permitted by uRPF ACL are sent to the PISA for forwarding.

uRPF is not supported on PVLAN host ports.

Examples

This example shows how to enable hardware uRPF when RPF and ACL are enabled:

Router(config)# mls ip cef rpf hw-enable-rpf-acl

Router(config)# 

This example shows how to disable hardware uRPF when RPF and ACL are enabled:

Router(config)# no mls ip cef rpf hw-enable-rpf-acl

Router(config)# 

Related Commands

mls ip cef rpf interface-group

To define an interface group in the RPF-VLAN table, use the mls ip cef rpf interface-group command. To delete the interface group, use the no form of this command.

mls ip cef rpf interface-group group-number interface1 interface2 interface3 [...]

no mls ip cef rpf interface-group group-number interface1 interface2 interface3 [...]

Syntax Description

Command Default

No groups are configured.

Command Modes

Global configuration (config)

Command History

Usage Guidelines

A single interface group contains three to six interfaces. You can configure up to four interface groups. For each interface group, the first four entries are installed in the hardware RPF-VLAN table.

Enter the interface as interface-typemod/port.

Separate each interface entry with a space. You do not have to include a space between the interface-type and the mod/port arguments. See the "Examples" section for a sample entry.

Examples

This example shows how to define an interface group:

Router(config)# mls ip cef rpf interface-group 0 F2/1 F2/2 F2/3 F2/4 F2/5 F2/6

Router(config)# 

mls ip cef rpf multipath

To configure the RPF modes, use the mls ip cef rpf multipath command. To return to the default settings, use the no form of this command.

mls ip cef rpf multipath {interface-group | punt | pass}

Syntax Description

Command Default

punt

Command Modes

Global configuration (config)

Command History

Usage Guidelines

The interface-group mode is similar to the pass mode but utilizes the RPF_VLAN global table for the RPF check. Packets from other multiple path prefixes always pass the RPF check.

You enter the mls ip cef rpf multipath interface-group command to define an RPF_VLAN table interface group. One interface group contains from three to six interfaces, and you can configure up to four interface groups. For each interface group, the first four entries are installed in the hardware RPF_VLAN table. For the prefix that has more than three multiple paths, and all paths except two are part of that interface group, the FIB entry of that prefix uses this RPF_VLAN entry.

Examples

This example shows how to redirect the RPF-failed packets to the route processor for multiple path prefix support:

Router(config)# mls ip cef rpf multipath interface-group

Router(config)# 

Related Commands

mls ip delete-threshold

To delete the configured ACL thresholds, use the mls ip delete-threshold command.

mls ip delete-threshold acl-num

Syntax Description

Command Default

This command has no default settings.

Command Default

Global configuration (config)

Command History

Usage Guidelines

The mls ip delete-threshold command is active only when you enable the mls ip reflexive ndr-entry tcam command.

Examples

This example shows how to delete an ACL threshold:

Router(config)# mls ip delete-threshold 223

Router(config)#  

Related Commands

mls ip directed-broadcast

To enable the hardware switching of the IP-directed broadcasts, use the mls ip directed-broadcast command. To return to the default settings, use the no form of this command.

mls ip directed-broadcast {exclude-router | include-router}

no mls ip directed-broadcast

Syntax Description

Command Modes

Disabled

Command Default

Interface configuration

Command History

Usage Guidelines

The exclude-router and include-router keywords both support hardware switching, but exclude-router does not send a copy of the hardware-switched packets to the router. If you enter the include-router keyword, the router does not forward the IP-directed broadcast packet again.

In the default mode, IP-directed broadcast packets are not forwarded in the hardware; they are handled at the process level by the PISA. The PISA decision to forward or not forward the packet is dependent on the ip directed-broadcast command configuration.

There is no interaction between the ip directed-broadcast command and the mls ip directed-broadcast command. The ip directed-broadcast command involves software forwarding, and the mls ip directed-broadcast command involves hardware forwarding.

MLS IP-directed broadcast supports a secondary interface address.

Any packets that hit the CPU are not forwarded unless you add the ip directed-broadcast command to the same interface.

You can configure the MLS IP-directed broadcasts on a port-channel interface but not on the physical interfaces on the port-channel interface. If you want to add a physical interface to a port-channel group, the physical interface cannot have the MLS IP-directed broadcast configuration. You have to first remove the configuration manually and then add the physical interface to the channel group. If a physical interface is already part of a channel group, the CLI will not accept the mls ip directed-broadcast configuration command on that physical interface.

Examples

This example shows how to forward the IP-directed broadcast packet in the hardware to all hosts in the VLAN with the exception of the router:

Router(config-if)# mls ip directed-broadcast exclude-router

Router(config-if)# 

This example shows how to forward the IP-directed broadcast packet in the hardware to all hosts in the VLAN:

Router(config-if)# mls ip directed-broadcast include-router

Router(config-if)# 

Related Commands

mls ip inspect

To permit traffic through any ACLs that would deny the traffic through other interfaces, use the mls ip inspect command. To return to the default settings, use the no form of this command.

mls ip inspect acl-name

no mls ip inspect acl-name

Syntax Description

Command Modes

Disabled

Command Default

Global configuration (config)

Command History

Usage Guidelines

On a Catalyst 6500 series switch, when interfaces are configured to deny traffic, the CBAC permits traffic to flow bidirectionally only through the interface that is configured with the ip inspect command.

Examples

This example shows how to permit the traffic through a specific ACL (named deny_ftp_c):

Router(config)# mls ip inspect deny_ftp_c 

Router(config)# 

Related Commands

mls ip install-threshold

To install the configured ACL thresholds, use the mls ip install-threshold command.

mls ip install-threshold acl-num

Syntax Description

Command Modes

This command has no default settings.

Command Default

Global configuration (config)

Command History

Usage Guidelines

The mls ip install-threshold command is active only when you enable the mls ip reflexive ndr-entry tcam command.

Examples

This example shows how to install an ACL threshold:

Router(config)# mls ip install-threshold 123

Router(config)#  

Related Commands

mls ip multicast (global configuration mode)

To enable MLS IP and configure the hardware switching globally, use the mls ip multicast command. To disable MLS IP, use the no form of this command.

mls ip multicast [capability]

mls ip multicast [vrf name] [connected | egress local | mfd | refresh-state | shared-tree-mfd | threshold ppsec]

no mls ip multicast [vrf]

Syntax Description

Command Modes

The defaults are as follows:

•Multicast is disabled.

•Hardware switching is allowed for all eligible multicast routes.

•connected is enabled.

•egress local is disabled.

•mfd is enabled.

•refresh-state is enabled.

•shared-tree-mfd is enabled.

Command Default

Global configuration (config)

Command History

Usage Guidelines

Note After you enter the mls ip multicast egress local command, you must perform a system reset for the configuration to take effect.

When entering the mls ip multicast egress local command, ensure that IPv6 multicast is not enabled. Since the egress multicast replication performance enhancement feature cannot separately turn on or turn off IPv4 and IPv6, you cannot have IPv4 and IPv6 multicast enabled when this feature is turned on.

These optional keywords are supported:

•threshold

•connected

•refresh-state

•shared-tree-mfd

•mfd

The threshold ppsec optional keyword and argument do not impact flows that are already populated in the hardware cache.

The expiration time refresh is updated when flow statistics are received from the Catalyst 6500 series switch (indicating that the traffic is received from the RPF interface).

Examples

This example shows how to enable the MLS IP shortcuts:

Router(config)# mls ip multicast

Router(config)# 

This example shows how to enable the hardware switching on a specific multicast route:

Router(config)# mls ip multicast vrf test1

Router(config)# 

This example shows how to export the information about egress capability from the switch processor to the route processor:

Router(config)# mls ip multicast capability

Router(config)# 

This example shows how to populate the multicast expansion table with local Layer 3-routed interfaces:

Router(config)# mls ip multicast egress local

Router(config)# 

Related Commands

mls ip multicast (interface configuration mode)

To enable MLS IP shortcuts on the interface, use the mls ip multicast command. To disable MLS IP shortcuts on the interface, use the no form of this command.

mls ip multicast

no mls ip multicast

Syntax Description

This command has no arguments or keywords.

Command Modes

Multicast is disabled.

Command Default

Interface configuration

Command History

Examples

This example shows how to enable the MLS IP shortcuts:

Router(config-if)# mls ip multicast

Router(config-if)# 

Related Commands

mls ip multicast bidir gm-scan-interval

To set the RPF scan interval for the Bidir rendezvous point, use the mls ip multicast bidir gm-scan-interval command. To disable the RPF scan interval for the Bidir rendezvous point, use the no form of this command.

mls ip multicast bidir gm-scan-interval interval

no mls ip multicast bidir gm-scan-interval

Syntax Description

Command Modes

10 seconds

Command Modes

Global configuration (config)

Command History

Usage Guidelines

When you set the RPF scan interval for the Bidir rendezvous point, you set the time that the periodic scan timer updates the RPF in the DF table for all Bidir rendezvous points in the hardware.

Examples

This example shows how to set the RPF scan interval for the Bidir rendezvous point:

Router(config)# mls ip multicast bidir gm-scan-interval 30

Router(config)# 

Related Commands

mls ip multicast connected

To enable the downloading of directly connected subnets globally, use the mls ip multicast connected command. To disable the downloading of directly connected subnets globally, use the no form of this command.

mls ip multicast connected

no mls ip multicast connected

Syntax Description

This command has no arguments or keywords.

Command Modes

Disabled

Command Modes

Global configuration (config)

Command History

Usage Guidelines

Do not create directly connected subnets for the following cases:

•To make more room available in the FIB TCAM

•The switch is the first-hop router for a source

•The entries are for Bidir, SSM, and DM mode groups

In these cases, if you enable the downloading of directly connected subnets, the directly connected source hits the MMLS (*,G) entry and is switched using the MMLS (*,G) entry. The registers are not sent to the route processor (in the case of PIM-SM), and the (S,G) state is not created on the first hop (in the case of PIM-DM).

The subnet entry is installed in the TCAM entries with a shorter mask to catch directly connected sources before they hit such entries. You can punt traffic from directly connected sources to the PISA. Once the PISA sees this traffic, it can install an MMLS (S,G) entry for this source, which gets installed before the subnet entry in the TCAM. New packets from this source are now switched with the (S,G) entry.

Examples

This example shows how to enable the downloading of directly connected subnets:

Router(config)# mls ip multicast connected

Router(config)# 

Related Commands

mls ip multicast consistency-check

To enable and configure the hardware-shortcut consistency checker, use the mls ip multicast consistency-check command. To disable the consistency checkers, use the no form of this command.

mls ip multicast consistency-check [{settle-time seconds} | {type scan-mroute [count count-number] | {settle-time seconds}} | {period seconds}]

no mls ip multicast consistency-check

Syntax Description

Command Default

The defaults are as follows:

•Consistency check is enabled.

•count count-number is 20.

•period seconds is 2 seconds.

•settle-time seconds is 60 seconds.

Command Modes

Global configuration (config)

Command History

Usage Guidelines

The oif entry is the outgoing interface of a multicast {*,G} or {source, group} flow.

The consistency checker scans the mroute table and assures that the multicast-hardware entries are consistent with the mroute table. Whenever an inconsistency is detected, the inconsistency is automatically corrected.

To display the inconsistency error, use the show mls ip multicast consistency-check command.

Examples

This example shows how to enable the hardware-shortcut consistency checker:

Router (config)# mls ip multicast consistency-check

Router (config)# 

This example shows how to enable the hardware-shortcut consistency checker and configure the scan check of the mroute table:

Router (config)# mls ip multicast consistency-check type scan-mroute count 20 period 35

Router (config)# 

This example shows how to enable the hardware-shortcut consistency checker and specify the period between scans:

Router (config)# mls ip multicast consistency-check type scan-mroute period 35

Router (config)# 

Related Commands

mls ip multicast flow-stat-timer

To set the time interval between two consecutive batches of flow-statistics messages from the switch processor to the route processor, use the mls ip multicast flow-stat-timer command. To return to the default settings, use the no form of this command.

mls ip multicast flow-stat-timer num

no mls ip multicast flow-stat-timer

Syntax Description

Command Default

25 seconds

Command Modes

Global configuration (config)

Command History

Examples

This example shows how to configure the time interval between two consecutive batches of flow-statistics messages from the switch processor to the route processor:

Router (config)# mls ip multicast flow-stat-timer 10 

Router (config)#

Related Commands

mls ip multicast replication-mode

To enable and specify the replication mode, use the mls ip multicast replication-mode command. To restore the system to automatic detection mode, use the no form of this command.

mls ip multicast replication-mode {egress | ingress}

no mls ip multicast replication-mode {egress | ingress}

Syntax Description

Command Default

ingress

Command Modes

Global configuration (config)

Command History

Usage Guidelines

The Supervisor Engine 32 PISA does not support the egress keyword.

Note During the change from egress- to ingress-replication mode, traffic interruptions may occur because the shortcuts are purged and reinstalled. To avoid interruptions in traffic forwarding, enter the mls ip multicast replication-mode ingress command.

If you enter the no mls ip multicast replication-mode ingress command, only the forced-ingress mode resets

Examples

This example shows how to enable the ingress-replication mode:

Router (config)# mls ip multicast replication-mode ingress

Router (config)#

Related Commands

mls ip multicast sso

To configure the SSO parameters, use the mls ip multicast sso command. To return to the default settings, use the no form of this command.

mls ip multicast sso {{convergence-time time} | {leak interval} | {leak percentage}}

Syntax Description

Command Default

The defaults are as follows:

•convergence-time time—20 seconds

•leak interval—60 seconds

•leak percentage—10 percent

Command Modes

Global configuration (config)

Command History

Examples

This example shows how to set the maximum time to wait for protocol convergence:

Router (config)# mls ip multicast sso convergence-time 300

Router (config)# 

This example shows how to set the packet-leak interval:

Router (config)# mls ip multicast sso leak 200

Router (config)# 

This example shows how to set the packet-leak percentage:

Router (config)# mls ip multicast sso leak 55

Router (config)# 

Related Commands

mls ip multicast stub

To enable the support for non-RPF traffic drops for PIM sparse-mode stub networks, use the mls ip multicast stub command. To disable support for non-RPF traffic drops for PIM sparse-mode stub networks, use the no form of this command.

mls ip multicast stub

no mls ip multicast stub

Syntax Description

This command has no arguments or keywords.

Command Default

Multicast is disabled.

Command Modes

Interface configuration

Command History

Usage Guidelines

The mls ip multicast stub command, creates the following filters on a routed interface or a VLAN:

•Permits IP packets from all addresses that are connected to the interface to any IP destination. An address is connected to the interface if it is within the IP address prefixes configured through the ip address addr mask [secondary] command.

This filter is meant to permit unicast and multicast packets from directly connected sources.

•Permits IP multicast packets from any source address to multicast group prefixes 224.0.0.0/24 and 224.0.1.0/24.

This filter allows packets to be sent from any source address to well-known multicast addresses; 224.0.0.0/24 is used by protocols such as PIM, OSPF, EIGRP, or NTP. Addresses in 224.0.1.0/24 are used by protocols such as AutoRP (224.0.1.39, 224.0.1.40).

•Denies any other IP multicast packets.

This deny filter is meant to inhibit any multicast packets from nondirectly connected sources and is applied to the packets received on this interface or VLAN.

The permit IP multicast packets and the deny any other IP multicast packets filters are the same for all interface or VLANs to which you configure the mls ip multicast stub command. The permit IP packets from all addresses that are connected to the interface to any IP destination filter is different for each interface or VLAN.

Examples

This example shows how to enable the support for the non-RPF traffic drops for the PIM sparse-mode stub networks:

Router(config-if)# mls ip multicast stub

Router(config-if)# 

Related Commands

mls ip multicast threshold

To configure a threshold rate for installing hardware shortcuts, use the mls ip multicast threshold command. To deconfigure the threshold, use the no form of this command.

mls ip multicast threshold ppsec

no mls ip multicast threshold

Syntax Description

Command Default

This command has no default settings.

Command Modes

Global configuration (config)

Command History

Usage Guidelines

Use this command to prevent creation of MLS entries for short-lived multicast flows such as join requests.

If multicast traffic drops below the configured multicast rate threshold, all multicast traffic is routed by the PISA.

This command does not affect already installed routes. For example, if you enter this command and the shortcuts are already installed, the shortcuts are not removed if they are disqualified. To apply the threshold to existing routes, clear the route and let it reestablish.

Examples

This example shows how to configure the IP MLS threshold to 10 packets per second:

Router (config)# mls ip multicast threshold 10 

Router (config)# 

Related Commands

mls ip nat netflow-frag-l4-zero

To zero out the Layer 4 information in the NetFlow lookup table for fragmented packets, use the mls ip nat netflow-frag-l4-zero command.

mls ip nat netflow-frag-l4-zero

Syntax Description

This command has no arguments or keywords.

Command Default

This command has no default settings.

Command Modes

Global configuration (config)

Command History

Usage Guidelines

This command is supported in PFC3BXL or PFC3B mode only.

Use the mls ip nat netflow-frag-l4-zero command to prevent matching the first fragment to the NetFlow shortcut (normal operation) that is sent to the software. The next fragments that are sent to the software are translated based on the Layer 4 port information from the first fragment. The translation based on the Layer 4 port information from the first fragment occurs because there are no fragment bits for matching in the NetFlow key.

When there is a large feature configuration on an interface that requires a large number of ACL TCAM entries/masks that are programmed in TCAM, if the interface is configured as a NAT-inside interface, the feature configuration may not fit in the ACL TCAM and the traffic on the interface may get switched in the software.

Examples

This example shows how to zero out the Layer 4 information in the NetFlow lookup table for fragmented packets:

Router (config)# mls ip nat netflow-frag-l4-zero

Router (config)# 

mls ip pbr

To enable the MLS support for policy-routed packets, use the mls ip pbr command. To disable the MLS support for policy-routed packets, use the no form of this command.

mls ip pbr [null0]

no mls ip pbr

Syntax Description

Command Default

MLS support for policy-routed packets is disabled.

Command Modes

Global configuration (config)

Command History

Usage Guidelines

Note Do not enable PBR and SLB on the same interface; PBR-based packets are not forwarded correctly.

When you enable the hardware-policy routing by entering the mls ip pbr command, all policy routing occurs in the hardware and is applied to all interfaces, regardless of which interface was configured for policy routing.

Use the null0 keyword when you have routed traffic only to enable the hardware support for the set interface null0 in the route maps.

Examples

This example shows how to enable the MLS support for policy-routed packets:

Router(config)# mls ip pbr

Router(config)#

Related Commands

mls ip reflexive ndr-entry tcam

To enable the shortcuts in TCAM for the reflexive TCP/UDP entries when installed by the NDR, use the mls ip reflexive ndr-entry tcam command. To disable the shortcuts in TCAM for the reflexive TCP/UDP entries when installed by the NDR, use the no form of this command.

mls ip reflexive ndr-entry tcam

no mls ip reflexive ndr-entry tcam

Syntax Description

This command has no arguments or keywords.

Command Default

Disabled

Command Modes

Global configuration (config)

Command History

Usage Guidelines

When you enter the mls ip reflexive ndr-entry tcam command, the reflexive ACL dynamic entries are installed in TCAM instead of in NetFlow.

Examples

This example shows how to enable the shortcuts in TCAM for the reflexive TCP/UDP entries when installed by the NDR:

Router(config)# mls ip reflexive ndr-entry tcam

Router(config)#

This example shows how to disable the shortcuts in TCAM for the reflexive TCP/UDP entries when installed by the NDR:

Router(config)# no mls ip reflexive ndr-entry tcam

Router(config)#

Related Commands

mls ipv6 acl compress address unicast

To turn on the compression of IPv6 addresses, use the mls ipv6 acl compress address unicast command. To turn off the compression of IPv6 addresses, use the no form of this command.

mls ipv6 acl compress address unicast

no mls ipv6 acl compress address unicast

Syntax Description

This command has no arguments or keywords.

Command Default

Disabled

Command Modes

Global configuration (config)

Command History

Usage Guidelines

Caution Do not enable the compression mode if you have noncompressible address types in your network. A list of compressible address types and the address compression methosd are listed in Table 2-15.

Examples

This example shows how to turn on the compression of the noncompressible IPv6 addresses:

Router(config)# mls ipv6 acl compress address unicast

Router(config)#

This example shows how to turn off the compression of the noncompressible IPv6 addresses:

Router(config)# no mls ipv6 acl compress address unicast

Router(config)#

Related Commands

mls ipv6 acl source

To deny all IPv6 packets from a source-specific address, use the mls ipv6 acl source command. To accept all IPv6 packets from a source-specific address, use the no form of this command.

mls ipv6 acl source {loopback | multicast}

no mls ipv6 acl source {loopback | multicast}

Syntax Description

Command Default

Disabled

Command Modes

Global configuration (config)

Command History

Examples

This example shows how to deny all IPv6 packets with a source loopback address:

Router(config)# mls ipv6 acl source loopback

Router(config)#

This example shows how to deny all IPv6 packets with a source multicast address:

Router(config)# no mls ipv6 acl source multicast

Router(config)#

Related Commands

mls mpls (recirculation)

To enable MPLS recirculation, use the mls mpls command. To disable MPLS recirculation, use the no form of this command.

mls mpls {recir-agg | tunnel-recir}

no mls mpls {recir-agg | tunnel-recir}

Syntax Description

Command Default

Disabled

Command Modes

Global configuration (config)

Command History

Usage Guidelines

If you do not enable tunnel-MPLS recirculation, the IPv4 and IPv4-tunneled packets that need to be labeled (for example, the packets that are encapsulated with an MPLS header) will be corrupted when they are transmitted from the Catalyst 6500 series switch.

Use the show erm statistics command to display the FIB TCAM exception status for IPv4, IPv6, and MPLS protocols.

Examples

This example shows how to enable the aggregated-label MPLS recirculation:

Router(config)# mls mpls recir-agg

Router(config)#

This example shows how to enable the tunnel-MPLS recirculation:

Router(config)# mls mpls tunnel-recir

Router(config)#

This example shows how to disable the aggregated-label MPLS recirculation:

Router(config)# no mls mpls recir-agg

Router(config)#

This example shows how to disable the tunnel-MPLS recirculation:

Router(config)# no mls mpls tunnel-recir

Router(config)#

Related Commands

mls mpls (guaranteed bandwidth traffic engineering)

To configure the guaranteed bandwidth traffic engineering flow parameters globally, use the mls mpls command. To return to the default settings, use the no form of this command.

mls mpls {{gb-te-burst burst} | {gb-te-cir-ratio ratio} | {gb-te-dscp dscp-value [markdown]} | {gb-te-enable [global-pool]}}

no mls mpls {{gb-te-burst burst} | {gb-te-cir-ratio ratio} | {gb-te-dscp dscp-value [markdown]} | {gb-te-enable [global-pool]}}

Syntax Description

Command Default

The default settings are as follows:

•burst is 1000 milliseconds.

•ratio is 1 percent.

•dscp-value is 40.

Command Modes

Global configuration (config)

Command History

Usage Guidelines

Use the mls qos map dscp-exp command to reset the Exp value of the MPLS packet when the out-label gets swapped.

If you do not enable tunnel-MPLS recirculation, the IPv4 and IPv4-tunneled packets that need to be labeled (for example, the packets that are encapsulated with an MPLS header) will be corrupted when they are transmitted from the Catalyst 6500 series switch.

Use the show erm statistics command to display the FIB TCAM exception status for IPv4, IPv6, and MPLS protocols.

Examples

This example shows how to specify the burst duration for the guaranteed bandwidth traffic engineering flows:

Router(config)# mls mpls gb-te-burst 2000

Router(config)#

This example shows how to specify the ratio for CIR policing:

Router(config)# mls mpls gb-te-ratio 30

Router(config)#

This example shows how to specify the DSCP map for the guaranteed bandwidth traffic engineering flows and to drop the nonconforming flows:

Router(config)# mls mpls gb-te-dscp 25 markdown

Router(config)#

This example shows how to enable the guaranteed bandwidth traffic engineering flow policing:

Router(config)# mls mpls gb-te-enable

Router(config)#

Related Commands

mls nde flow

To specify the filter options for NDE, use the mls nde flow command. To clear the NDE flow filter and reset the filter to the default settings, use the no form of this command.

mls nde flow {include | exclude} {{dest-port port-num} | {destination ip-addr ip-mask} | {protocol {tcp | udp}} | {source ip-addr ip-mask} | {src-port port-num}}

no mls nde flow {include | exclude}

Syntax Description

Command Default

The defaults are as follows:

•All expired flows are imported.

•Interface export is disabled (no mls nde interface).

Command Modes

Global configuration (config)

Command History

Usage Guidelines

The mls nde flow command adds filtering to the NDE. The expired flows matching the specified criteria are exported. These values are stored in NVRAM and do not clear when NDE is disabled. If any option is not specified in this command, it is treated as a wildcard. The NDE filter in NVRAM does not clear when you disable NDE.

Only one filter can be active at a time. If you do not enter the exclude or include keyword, the filter is assumed to be an inclusion filter.

The include and exclude filters are stored in NVRAM and are not removed if you disable NDE.

ip-addr maskbits is the simplified long subnet address format. The mask bits specify the number of bits of the network masks. For example, 172.25.2.1/22 indicates a 22-bit subnet address. The ip-addr is a full host address, such as 193.22.253.1/22.

Examples

This example shows how to specify an interface flow filter so that only expired flows to destination port 23 are exported (assuming that the flow mask is set to ip-flow):

Router(config)# mls nde flow include dest-port 23

Router(config)#

Related Commands

mls nde interface

To populate the additional fields in the NDE packets, use the mls nde interface command. To disable the population of the additional fields, use the no form of this command.

mls nde interface

no mls nde interface

Syntax Description

This command has no arguments or keywords.

Command Default

Enabled

Command Modes

Interface configuration

Command History

Usage Guidelines

You can configure NDE to populate the following additional fields in the NDE packets:

•Egress interface SNMP index

•Source-autonomous system number

•Destination-autonomous system number

•IP address of the next-hop router

The ingress-interface SNMP index is always populated if the flow mask is interface-full or interface-src-dst.

For detailed information, refer to the "Configuring NDE" chapter of the Catalyst Supervisor Engine 32 PISA Cisco IOS Software Configuration Guide—Release 12.2ZY.

Examples

This example shows how to populate the additional fields in the NDE packets:

Router(config)# mls nde interface

Router(config)#

This example shows how to disable the population of the additional fields:

Router(config)# no mls nde interface

Router(config)#

Related Commands

mls nde sender

To enable MLS NDE export, use the mls nde sender command. To disable MLS NDE export, use the no form of this command.

mls nde sender [version version]

no mls nde sender

Syntax Description

Command Default

The defaults are as follows:

•MLS NDE export is disabled.

•version is 7.

Command Modes

Global configuration (config)

Command History

Examples

This example shows how to enable MLS NDE export:

Router(config)# mls nde sender

Router(config)#

This example shows how to disable MLS NDE export:

Router(config)# no mls nde sender

Router(config)#

Related Commands

mls netflow

To enable NetFlow to gather the statistics, use the mls netflow command. To disable NetFlow from gathering the statistics, use the no form of this command.

mls netflow

no mls netflow

Syntax Description

Command Default

Enabled

Command Modes

Global configuration (config)

Command History

Usage Guidelines

NetFlow gathers the statistics from traffic that flows through the Catalyst 6500 series switch and stores the statistics in the NetFlow table. You can gather the statistics globally based on a protocol or optionally per interface.

If you are not using NDE or the Cisco IOS features that use the hardware NetFlow table (micro-flow QoS, WCCP, TCP Intercept, or Reflexive ACLs), you may safely disable the use and maintenance of the hardware NetFlow table using the no mls netflow command in global configuration mode.

Examples

This example shows how to gather the statistics:

Router(config)# mls netflow

Router(config)#

This example shows how to disable NetFlow from gathering the statistics:

Router(config)# no mls netflow

Disabling MLS netflow entry creation.

Router(config)# 

Related Commands

mls netflow maximum-flows

To configure the maximum flow allocation in the NetFlow table, use the mls netflow maximum-flows command. To return to the default settings, use the no form of this command.

mls netflow maximum-flows [maximum-flows]

no mls netflow maximum-flows

Syntax Description

Command Default

128

Command Modes

Global configuration (config)

Command History

Usage Guidelines

The value that you specify for the maximum number of flows is that value times 1000. For example, if you enter 32, you specify that 32,000 is the maximum number of permitted flows.

Examples

This example shows how to configure the maximum flow allocation in the NetFlow table:

Router(config)# mls netflow maximum-flows 96

Router(config)#

This example shows how to return to the default setting:

Router(config)# no mls netflow maximum-flows

Router(config)# 

Related Commands

mls netflow sampling

To enable the sampled NetFlow on an interface, use the mls netflow sampling command. To disable the sampled NetFlow, use the no form of this command.

mls netflow sampling

no mls netflow sampling

Syntax Description

This command has no arguments or keywords.

Command Default

Disabled

Command Modes

Interface configuration

Command History

Usage Guidelines

To enable sampling, you must enter the mls sampling command and the mls netflow sampling command on the appropriate interfaces. If you do not enter the mls netflow sampling command, NDE will not export flows.

Depending on the current flow mask, the sampled NetFlow can be global or per interface. For Interface-Full and Interface-Src-Dest flow masks, the sampled NetFlow is enabled on a per-interface basis. For all the other flow masks, the sampled NetFlow is always global and turned on/off for all interfaces.

Enter the mls sampling command to enable the sampled NetFlow globally.

Examples

This example shows how to enable the sampled NetFlow on an interface:

Router(config-if)# mls netflow sampling

Router(config-if)#

This example shows how to disable the sampled NetFlow on an interface:

Router(config-if)# no mls netflow sampling

Router(config-if)#

Related Commands

mls netflow usage notify

To monitor the NetFlow table usage on the switch processor, use the mls netflow usage notify command. To return to the default settings, use the no form of this command.

mls netflow usage notify {threshold interval}

no mls netflow usage notify

Syntax Description

Command Default

Disabled

Command Modes

Global configuration (config)

Command History

Usage Guidelines

If the NetFlow table usage monitoring is enabled and the NetFlow table usage exceeds the percentage threshold, a warning message is displayed.

NetFlow gathers statistics from traffic that flows through the Catalyst 6500 series switch and stores the statistics in the NetFlow table. You can gather statistics globally based on a protocol or optionally per interface.

If you are not using NDE or the Cisco IOS features that use the hardware NetFlow table (micro-flow QoS, WCCP, TCP Intercept, or Reflexive ACLs), you may safely disable the use and maintenance of the hardware NetFlow table using the no mls netflow command in global configuration mode.

Examples

This example shows how to configure the monitoring of the NetFlow table usage on the switch processor:

Router(config)# mls netflow usage notify 80 300

Router(config)#

Related Commands

mls qos (global configuration mode)

To enable the QoS functionality globally, use the mls qos command. 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, PFC QoS (marking and policing) is disabled, and packet ToS and 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 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 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 Catalyst 6500 series switch:

Router(config)# no mls qos

Router(config)#

Related Commands

mls qos (interface configuration mode)

To enable the QoS functionality on an interface, use the mls qos command. 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

Command History

Usage Guidelines

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

Router(config-if)#

Related Commands

mls qos aggregate-policer

To define a named aggregate policer for use in policy maps, use the mls qos aggregate-policer command. This policer can be shared by different policy map classes and on different interfaces. To delete a named aggregate policer, use the no form of this command.

mls qos aggregate-policer name rate-bps

mls qos aggregate-policer name rate-bps burst-bytes maximum-burst-bytes

mls qos aggregate-policer name rate-bps [{conform-action {drop [exceed-action action]}} | {set-dscp-transmit [new-dscp]} | {set-prec-transmit [new-precedence]} | {transmit [{exceed-action action} | {violate-action action]}}

mls qos aggregate-policer aggregate-name rate-bps {pir peak-rate-bps [{conform-action {drop [exceed-action action]}} | {set-dscp-transmit [new-dscp]} | {set-prec-transmit [new-precedence]} | {transmit [{exceed-action action}} | {violate-action action}]]}

no mls qos aggregate-policer name

Syntax Description

Command Default

The defaults are as follows:

•extended-burst-bytes is equal to burst-bytes.

•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 (config)

Command History

Usage Guidelines

Valid values for action are as follows:

•drop—Drops the packet

•policed-dscp-transmit—Changes the DSCP per the policed-DSCP map and sends it

•transmit—Transmits the package

The Catalyst 6500 series switch 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 4 Gbps (entered as 32000 and 4000000000) and the range for the burst size is 1 KB (entered as 1000) to 512 MB (entered as 512000000). Modifying an existing aggregate rate limit entry causes that entry to be modified in NVRAM and in the Catalyst 6500 series switch if that entry is currently being used.

Note Due to 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 and in the Catalyst 6500 series switch 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

Examples

This 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, set DSCP to 48 when these rates are not exceeded, and drop packets when these rates are exceeded:

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

Router(config)#

Related Commands

mls qos bridged

To enable the microflow policing for bridged traffic on Layer 3 LAN interfaces, use the mls qos bridged command. 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.

Examples

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

Router(config-if)# mls qos bridged

Router(config-if)#

Related Commands

mls qos channel-consistency

To enable the QoS-port attribute checks on EtherChannel bundling, use the mls qos channel-consistency command. 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

Router(config-if)#

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

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

Router(config-if)#

mls qos cos

To define the default CoS value for an interface, use the mls qos cos command. To remove a prior entry, use the no form of this command.

mls qos cos cos-value

no mls qos cos cos-value

Syntax Description

Command Default

The defaults are as follows:

•cos-value is 0.

•CoS override is not configured.

Command Default

Interface configuration

Command History

Usage Guidelines

CoS values are configurable on physical LAN ports only.

Examples

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

Router(config-if)# mls qos cos 6

Router(config-if)#

Related Commands

mls qos cos-mutation

To attach an ingress-CoS mutation map to the interface, use the mls qos cos-mutation command. 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 Modes

No table is defined.

Command Default

Interface configuration

Command History

Examples

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

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

Router(config-if)#

Related Commands

mls qos dscp-mutation

To attach an egress-DSCP mutation map to the interface, use the mls qos dscp-mutation command. 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 Modes

No table is defined.

Command Default

Interface configuration

Command History

Examples

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

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

Router(config-if)#

Related Commands

mls qos exp-mutation

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

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

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 SVI flood for VLANs that are carried through by the loopback cable, use the mls qos loopback command. 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 Default

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

Router (config-if)#

mls qos map cos-dscp

To define the ingress CoS-to-DSCP map for trusted interfaces, use the mls qos map cos-dscp command. To remove a prior entry, use the no form of this command.

mls qos map cos-dscp values

no mls qos map cos-dscp

Syntax Description

Command Modes

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

Command Default

Global configuration (config)

Command History

Usage Guidelines

The CoS-to-DSCP map is used to map the CoS of packets arriving on trusted interfaces (or flows) to a DSCP where the trust type is trust-cos. This map is a table of eight CoS values (0 through 7) and their corresponding DSCP values. The Catalyst 6500 series switch has one map.

Examples

This example shows how to configure the ingress CoS-to-DSCP map for trusted interfaces:

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

Router(config)# 

Related Commands

mls qos map cos-mutation

To map a packet's CoS to a new CoS value, use the mls qos map cos-mutation command. 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 Modes

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

Command Default

Global configuration (config)

Command History

Usage Guidelines

This command is supported on Catalyst 6500 series switches 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.

Support for 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 5 4 3 to 1 

Router(config)#

Related Commands

mls qos map dscp-cos

To define an egress DSCP-to-CoS map, use the mls qos map dscp-cos command. 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 Modes

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

Command Default

Global configuration (config)

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 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 has one map.

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

Examples

This example shows how to configure the egress DSCP-to-CoS map for trusted interfaces:

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

Router(config)#

Related Commands

mls qos map dscp-exp

To define the final DSCP classification to the final EXP value, use the mls qos map dscp-exp command. 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 Modes

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

Command Default

Global configuration (config)

Command History

Usage Guidelines

The DSCP-to-EXP map is used to map the final DSCP classification to a final EXP. 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 has 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 classification to a final EXP value:

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

Router(config)#

Related Commands

mls qos map dscp-mutation

To define a named DSCP mutation map, use the mls qos map dscp-mutation command. 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 (config)

Command History

Usage Guidelines

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 PFC QoS supports.

PFC QoS derives the egress-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 

Router(config)#

Related Commands

mls qos map exp-dscp

To define the ingress EXP value to the internal DSCP map, use the mls qos map exp-dscp command. To return to the default mappings, 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 2-20.

Command Modes

Global configuration (config)

Command History

Usage Guidelines

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

Router(config)#

Related Commands

mls qos map exp-mutation

To map a packet's EXP to a new EXP value, use the mls qos map exp-mutation command. To return to the default mappings, 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 2-21.