|
|
This chapter describes how to configure IP Multilayer Switching (MLS) on the Catalyst 6000 family switches.
This chapter consists of these sections:
These sections provide an overview of IP MLS and describe how IP MLS works:
For detailed MLS overview and configuration information, refer to the Cisco IOS Switching Services Configuration Guide.
IP MLS provides high-performance hardware-based Layer 3 switching for Catalyst 6000 family LAN switches. IP MLS switches unicast IP data packet flows between IP subnets using advanced application-specific integrated circuit (ASIC) switching hardware, offloading processor-intensive packet routing from network routers.
The packet forwarding function is moved onto Layer 3 switches whenever a complete switched path exists between two hosts. Standard routing protocols, such as Open Shortest Path First (OSPF), Enhanced Interior Gateway Routing Protocol (EIGRP), Routing Information Protocol (RIP), and Intermediate System-to-Intermediate System (IS-IS), are used for route determination.
In addition, IP MLS provides traffic statistics you can use to identify traffic characteristics for administration, planning, and troubleshooting. IP MLS uses NetFlow Data Export (NDE) to export flow statistics.
Layer 3 protocols, such as IP and Internetwork Packet Exchange (IPX), are connectionless---they deliver every packet independently of every other packet. However, actual network traffic consists of many end-to-end conversations, or flows, between users or applications.
A flow is a unidirectional sequence of packets between a particular source and destination that share the same protocol and transport-layer information. Communication from a client to a server and from the server to the client are separate flows. For example, Telnet traffic transferred from a particular source to a particular destination comprises a separate flow from File Transfer Protocol (FTP) packets between the same source and destination.
Flows are based only on Layer 3 addresses, which allow IP traffic from multiple users or applications to a particular destination to be carried on a single flow if only the destination IP address is used to identify a flow.
An MLS cache entry is created for the initial packet of each flow. Upon receipt of a packet that does not match any flow currently in the MLS cache, a new IP MLS entry is created.
The state and identity of the flow are maintained while packet traffic is active; when traffic for a flow ceases, the entry ages out. You can configure the aging time for MLS entries kept in the MLS cache. If an entry is not used for the specified period of time, the entry ages out and statistics for that flow can be exported to a flow collector application.
The maximum MLS cache size is 128K entries. However, an MLS cache larger than 32K entries increases the probability that a flow will not be switched by the PFC and will get forwarded to the Catalyst 6000 family switch.
The PFC uses flow masks to determine how MLS entries are created. This section describe how the flow mask modes work.
The PFC supports only one flow mask (the most specific one) for all Multilayer Switch Feature Cards (MSFCs) that are Layer 3 switched by that PFC. If the PFC detects different flow masks from different MSFCs for which it is performing Layer 3 switching, it changes its flow mask to the most specific flow mask detected.
When the PFC flow mask changes, the entire MLS cache is purged. When a PFC exports cached entries, flow records are created based on the current flow mask. Depending on the current flow mask, some fields in the flow record might not have values. Unsupported fields are filled with a zero (0).
The three flow masks for IP MLS are as follows:
The flow mask mode you chose impacts the screen output of the show mls ip command.
In destination mode, the destination IP address of the switched flows are displayed, along with the packet rewrite information: rewritten destination MAC, rewritten VLAN, and egress interface.
When a packet is Layer 3 switched from a source host to a destination host, the PFC performs a packet rewrite based on information learned from the MSFC and stored in the MLS cache.
If Host A and Host B are on different VLANs and Host A sends a packet to the MSFC to be routed to Host B, the PFC recognizes that the packet was sent to the MAC address of the MSFC. The PFC checks the MLS cache and finds the entry matching the flow in question.
When the PFC receives the packet, it is (conceptually) formatted as follows:
| Frame Header | IP Header | Payload | |||||
|---|---|---|---|---|---|---|---|
Destination | Source | Destination | Source | TTL | Checksum | Data | Checksum |
MSFC MAC | Host A MAC | Host B IP | Host A IP | n | calculation1 | ||
The PFC rewrites the Layer 2 frame header, changing the destination MAC address to the MAC address of Host B and the source MAC address to the MAC address of the MSFC (these MAC addresses are stored in the MLS cache entry for this flow). The Layer 3 IP addresses remain the same, but the IP header Time to Live (TTL) is decremented and the checksum is recomputed. The PFC rewrites the switched Layer 3 packets so that they appear to have been routed by a router.
The PFC forwards the rewritten packet to Host B's VLAN (the destination VLAN is stored in the MLS cache entry) and Host B receives the packet.
After the PFC performs the packet rewrite, the packet is (conceptually) formatted as follows:
| Frame Header | IP Header | Payload | |||||
|---|---|---|---|---|---|---|---|
Destination | Source | Destination | Source | TTL | Checksum | Data | Checksum |
Host B MAC | MSFC MAC | Host B IP | Host A IP | n-1 | calculation2 | ||
Figure 12-1 shows a simple IP MLS network topology. In this example, Host A is on the Sales VLAN (IP subnet 171.59.1.0), Host B is on the Marketing VLAN (IP subnet 171.59.3.0), and Host C is on the Engineering VLAN (IP subnet 171.59.2.0).
When Host A initiates an HTTP file transfer to Host C, an MLS entry for this flow is created (this entry is the second item in the MLS cache shown in Figure 12-1). The PFC stores the MAC addresses of the MSFC and Host C in the MLS entry when the MSFC forwards the first packet from Host A through the switch to Host C. The PFC uses this information to rewrite subsequent packets from Host A to Host C.
Table 12-1 shows the default IP MLS configuration.
| Feature | Default Value |
|---|---|
IP MLS enable state | Enabled |
IP MLS aging time | 256 seconds |
IP MLS fast aging time | 32 seconds |
IP MLS fast aging-time packet threshold | 100 packets |
IP MLS long aging time | 900 seconds |
This section describes configuration guidelines that apply when configuring IP MLS. Enabling certain IP processes on an interface will affect IP MLS on the interface. Table 12-2 shows the affected commands and the resulting behavior:
| Command | Behavior |
|---|---|
Router# clear ip route | Clear all MLS cache entries for all switches performing Layer 3 switching for this MSFC. |
Router(config)# ip routing | The no form purges all MLS cache entries and disables IP MLS on this MSFC. |
Router(config)# ip security (all forms of this command) | Disable IP MLS on the interface. |
These sections describe how to configure the MSFC for IP MLS:
MLS route processor shortcuts for IP are enabled by default.
To reenable the IP MLS on the route processor, perform this task:
| Command | Purpose |
|---|---|
Router(config)# mls rp [ip {input-acl | route-map}| nde-address ip_address] | Enable MLS route processor shortcuts for IP. |
This example shows how to enable the MLS route processor for IP on the switch:
Router(config)# mls rp ip ip multi-layer switching is already enabled Router(config)#
To verify the IP MLS route process configuration, perform this task:
| Command | Purpose |
|---|---|
Router# show mls rp | Display the IP MLS route process configuration. |
This example shows how to display the IP MLS route process configuration of the switch:
Router# show mls rp ip multilayer switching is globally enabled ipx multilayer switching is globally disabled ipx mls inbound acl override is globally disabled mls id is 0040.0bd0.29e0 mls ip address 172.20.52.18 mls ip flow mask is destination mls ipx flow mask is unknown number of domains configured for mls 0 Router#
IP MLS is enabled globally by default but can be disabled and enabled on a specified interface.
To disable IP MLS on a specific Catalyst 6000 family switch interface, perform this task:
| Step | Command | Purpose | ||
|---|---|---|---|---|
| Router(config)# interface | Select the Ethernet interface to be configured. | ||
| Router(config-if)# no mls ip | Remove a Catalyst 6000 family switch interface from IP MLS. |
This example shows how to disable IP MLS for Fast Ethernet interface 5/5:
Router(config)# interface fastethernet 5/5 Router(config-if)# no mls ip Router(config-if)#
To enable IP MLS on a specific Catalyst 6000 family switch interface, perform this task:
| Step | Command | Purpose | ||
|---|---|---|---|---|
| Router(config)# interface | Select the Ethernet interface to be configured. | ||
| Router(config-if)# mls ip | Specify a Catalyst 6000 family switch interface for IP MLS. |
This example shows how to enable IP MLS fast Ethernet interface 5/5:
Router(config)# interface fastethernet 5/5 Router(config-if)# mls ip Router(config-if)#
To display the IP MLS configuration on a router interface, perform this task:
| Command | Purpose |
|---|---|
Router# show [ip [interface type number] | nde] | Display IP MLS configuration for an interface. |
This example shows how to display interface MLS information for Fast Ethernet interface 5/4:
Router# show ip interface fastethernet 5/4 FastEthernet5/4 is up, line protocol is up Internet address is 172.20.52.106/29 Broadcast address is 255.255.255.255 Address determined by non-volatile memory MTU is 1500 bytes Helper address is not set Directed broadcast forwarding is disabled Multicast reserved groups joined: 224.0.0.10 Outgoing access list is not set Inbound access list is not set Proxy ARP is enabled Security level is default Split horizon is enabled ICMP redirects are always sent ICMP unreachables are always sent ICMP mask replies are never sent IP fast switching is enabled IP fast switching on the same interface is disabled IP Flow switching is disabled IP CEF switching is enabled IP Fast switching turbo vector IP Normal CEF switching turbo vector IP multicast fast switching is enabled IP multicast distributed fast switching is disabled Router Discovery is disabled IP output packet accounting is disabled IP access violation accounting is disabled TCP/IP header compression is disabled RTP/IP header compression is disabled Probe proxy name replies are disabled Policy routing is disabled Network address translation is disabled WCCP Redirect outbound is disabled WCCP Redirect exclude is disabled BGP Policy Mapping is disabled IP multicast multilayer switching is disabled IP mls switching is enabled Router#
The IP MLS aging time applies to all MLS cache entries. The aging-time value is applied directly to destination mode aging. The mls aging time value is divided by two to derive the source-to-destination mode aging time, and divided by eight to find the full-flow aging time. The default mls aging time value is 256 seconds.
You can configure the normal aging time in the range of 32 to 4092 seconds in 8-second increments. Any aging-time value that is not a multiple of 8 seconds is adjusted to the closest multiple of 8 seconds. For example, a value of 65 is adjusted to 64 and a value of 127 is adjusted to 128.
Other events might cause MLS entries to be purged, such as routing changes or a change in link state (PFC link is down).
To keep the MLS cache size below 32K entries, enable the following parameters after the mls aging command:
A typical cache entry that is removed is the entry for flows to and from a Domain Name Server (DNS) or TFTP server; the entry might never be used again after it is created. Detecting and aging out these entries saves space in the MLS cache for other data traffic.
If you need to enable IP MLS fast aging time, initially set the value to 128 seconds. If the size of the MLS cache continues to grow over 32K entries, decrease the setting until the cache size stays below 32K. If the cache continues to grow over 32K entries, decrease the normal IP MLS aging time.
To specify the MLS aging time, perform this task:
| Command | Purpose |
|---|---|
Router(config)# mls aging {fast [threshold {1-128} | time {1-128}] | long 64-900 | normal 32-4092} | Specify the MLS aging time for an MLS cache entry. |
This example displays how to specify the MLS aging time on the Catalyst 6000 family switch:
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# mls aging fast threshold 64 time 30
To display the MLS aging-time configuration for the Catalyst 6000 family switch, perform this task:
| Command | Purpose |
|---|---|
Router# show mls aging | Display the MLS aging-time configuration. |
This example shows how to display the MLS aging-time configuration on the switch:
Router# show mls aging
enable timeout packet threshold
------ ------- ----------------
normal aging false 300 N/A
fast aging false 32 100
long aging false 900 N/A
Router#
You can set the minimum granularity of the flow mask for the MLS cache on the PFC. The actual flow mask used will be at least of the granularity specified by this command. For information on how the different flow masks work, see the "Flow Masks" section.
For example, if you do not configure access lists on any MSFC, then the IP MLS flow mask on the PFC is destination-ip by default. However, you can force the PFC to use the source-destination-ip flow mask by setting the minimum IP MLS flow mask using the mls flow destination-source command. If an extended access list is configured on the MSFC, then the flow mask is changed to ip-flow, which is a more granular flow mask than the configured source-destination-ip flow mask.
 | Caution The mls flow destination-source command purges all existing shortcuts in the MLS cache and affects the number of active shortcuts on the PFC. Exercise care when using this command. |
To set the minimum IP MLS flow mask, perform this task:
| Command | Purpose |
|---|---|
Router(config)# mls flow [ip {destination | destination-source | full}] | Set the minimum IP MLS flow mask for the protocol. |
This example shows how to set the minimum IP MLS flow mask on the Catalyst 6000 family switch:
Router(config)# mls flow ip destination Router(config)#
To display the MLS flow mask configuration for the Catalyst 6000 family switch, perform this task:
| Command | Purpose |
|---|---|
Router# show mls rp | Display the flow mask configuration. |
This example shows how to display the MLS flow mask configuration of the Catalyst 6000 family switch:
Router# show mls rp ip multilayer switching is globally enabled ipx multilayer switching is globally disabled ipx mls inbound acl override is globally disabled mls id is 0040.0bd0.29e0 mls ip address 172.20.52.34 mls ip flow mask is source-destination mls ipx flow mask is unknown number of domains configured for mls 1 vlan domain name: -null- current ip flow mask: source-destination ip current/next global purge: false/false ip current/next purge count: 0/0 current ipx flow mask: destination ipx current/next global purge: false/false ipx current/next purge count: 0/0 current sequence number: 3907649016 current/maximum retry count: 0/10 current domain state: no-change domain uptime: 00:34:42 keepalive timer expires in 11 seconds retry timer not running change timer not running fcp subblock count = 1 (Information Deleted)
These sections describe the commands used to display IP MLS configuration and statistics for the switch and the various interfaces:
The show mls rp command displays MLS details. Displays include:
To display the IP MLS information for the entire switch, perform this task:
| Command | Purpose |
|---|---|
Router# show mls rp | Display MLS details for the switch and all interfaces. |
This example shows how to display the IP MLS information for the switch and all interfaces:
Router# show mls rp
multilayer switching is globally enabled
mls id is 00e0.fefc.6000
mls ip address 10.20.26.64
mls flow mask is ip-flow
vlan domain name: WBU
current flow mask: ip-flow
current sequence number: 80709115
current/maximum retry count: 0/10
current domain state: no-change
current/next global purge: false/false
current/next purge count: 0/0
domain uptime: 13:03:19
keepalive timer expires in 9 seconds
retry timer not running
change timer not running
fcp subblock count = 7
1 management interface(s) currently defined:
vlan 1 on Vlan1
7 mac-vlan(s) configured for multi-layer switching:
mac 00e0.fefc.6000
vlan id(s)
1 10 91 92 93 95 100
router currently aware of following 1 switch(es):
switch id 0010.1192.b5ff
Router#
To display MLS information for a specific interface, perform this task:
| Command | Purpose |
|---|---|
Router# show mls rp [interface] | Display MLS details for a specific interface. |
This example shows how to display the MLS details for the interface VLAN 10:
Router# show mls rp interface vlan 10 mls active on Vlan10, domain WBU Router#
To display MLS interfaces for a VTP domain, perform this task:
| Command | Purpose |
|---|---|
Router# show mls rp vtp-domain domain-name | Display MLS interfaces for a specific VTP domain. |
This example shows how to display the MLS interfaces for the VTP domain WBU:
Router# show mls rp vtp-domain WBU
vlan domain name: WBU
current flow mask: ip-flow
current sequence number: 80709115
current/maximum retry count: 0/10
current domain state: no-change
current/next global purge: false/false
current/next purge count: 0/0
domain uptime: 13:07:36
keepalive timer expires in 8 seconds
retry timer not running
change timer not running
fcp subblock count = 7
1 management interface(s) currently defined:
vlan 1 on Vlan1
7 mac-vlan(s) configured for multi-layer switching:
mac 00e0.fefc.6000
vlan id(s)
1 10 91 92 93 95 100
router currently aware of following 1 switch(es):
switch id 0010.1192.b5ff
Router#
The show mls ip interface command displays MLS interface configuration details. The output of the command includes:
To display detailed MLS interface status information on the Catalyst 6000 family switch, perform this task:
| Command | Purpose |
|---|---|
Router# show mls [ip [interface] | nde] | Display MLS details for an interface. |
This example shows how to display IP MLS information for Fast Ethernet interface 5/5:
Router# show mls ip interface fastethernet 5/5 DstIP SrcIP DstVlan-DstMAC Pkts Bytes ----------------------------------------------------------------------- 172.20.52.124 0.0.0.0 5 : 00e0.1e9b.31ff 846 34747 Number of Entries Found = 1 Router#
These sections describe how to display IP MLS cache entries on the switch:
The show mls command displays IP MLS information and MSFC-specific information.
To display IP MLS information and MSFC-specific information on the switch, perform this task:
| Command | Purpose |
|---|---|
Router# show mls ip [any | destination ip_address | detail | flow [tcp | udp] | interface type number | macd destination_mac_address | macs source_mac_address | multicast | slot 1-8 | source ip_address] | Display the IP MLS information and MSFC-specific information. |
This example shows how to display IP MLS information and MSFC-specific information on the switch:
Router# show mls ip DstIP SrcIP DstVlan-DstMAC Pkts Bytes ----------------------------------------------------------------------- SrcDstPorts SrcDstEncap Age LastSeen -------------------------------------- 172.20.52.122 0.0.0.0 5 : 00e0.4fac.b3ff 155 6290 5 /9 ,5 /9 ARPA,ARPA 661 15:09:32 Number of Entries Found = 1 Router#
To display MLS entries for a specific destination IP address, perform this task:
| Command | Purpose |
|---|---|
Router# show mls ip destination ip_address [any | detail | flow [tcp | udp] | interface type number | macd destination_mac_address | macs source_mac_address | multicast | slot 1-8 | source ip_address] | Display the IP MLS cache entries for a specific IP destination address. |
This example shows how to display MLS entries for a specific destination IP address:
Router# show mls ip destination 127.1.1.1 DstIP/SrcIP Prot/SrcPt/DstPt DstMAC/DstVlan Pkts Bytes ----------- ---------------- -------------- ---- ----- 127.1.1.1/127.1.1.1 udp/ 0040.0bd0.29fc/4095 92 111C 127.1.1.1/0.0.0.0 0040.0bd0.29fc/4095 0 0 Number of Entries Found = 2 Router#
To display MLS entries for a specific source IP address, perform this task
| Command | Purpose |
|---|---|
Router# show mls ip source ip_address [any | destination ip_address | detail | flow [tcp | udp] | interface type number | macd destination_mac_address | macs source_mac_address | multicast | slot 1-8] | Display the IP MLS source cache entries for a specific IP source address. |
This example shows how to display MLS entries for a specific source IP address:
Router# show mls ip source 172.20.52.122 any DstIP SrcIP DstVlan-DstMAC Pkts Bytes ----------------------------------------------------------------------- SrcDstPorts SrcDstEncap Age LastSeen -------------------------------------- 172.20.52.122 0.0.0.0 5 : 00e0.4fac.b3ff 157 6370 5 /9 ,5 /9 ARPA,ARPA 901 15:15:30 Number of Entries Found = 1 Router#
The show mls ip flow command displays MLS entries for a specific IP flow. The protocol argument can be tcp or udp.
To display MLS cache entries for a specific IP flow (when the switch flow mask mode is IP-flow), perform this task:
| Command | Purpose |
|---|---|
Router# show mls ip flow [tcp [any | detail | interface type number | macd destination_mac_address | macs source_mac_address] | udp [any | detail | interface type number | macd destination_mac_address | macs source_mac_address]] | Display the IP MLS cache entries for a specific IP flow. |
This example shows how to display MLS cache entries for a specific IP flow:
Router# show mls ip flow tcp detail
IP Destination IP Source Vlan Xtag L3-protocol Encapsulation RW-Vlan
--------------+---------------+----+----+-----------+-------------+-------+
RW-MACSource RW-MACDestination Bytes Packets Age Last Seen
--------------+-----------------+------------+------------+-----+---------+
QoS Police Count Threshold Leak Drop Bucket Use-Tbl Use-Enable
-----------+------------+---------+-----------+----+-------+-------+----------+
Number of Entries Found = 0
Router#
The clear mls ip command removes specific MLS cache entries on the switch. If none of the following parameters are entered, all IP Layer 3 entries in the table are cleared:
The flow keyword specifies the following additional flow information:
To clear an IP MLS cache entry, perform this task:
| Command | Purpose |
|---|---|
Router# clear mls [exclude protocol [all port 1-96 | [tcp port 1-96 | udp port 1-96]] | ip [any | destination ip_address | flow [tcp [any | interface | macd | macs] | udp [any | interface | macd | macs]] | interface type number | macd dest_mac_address | macs source_mac_address | multicast | slot 1-8 | source]] | Clear MLS cache entries. |
This example shows how to clear MLS cache entries with destination IP address 172.20.26.22:
Router# clear mls ip destination 172.20.26.22 Router#
This example shows how to clear MLS cache entries with destination IP address 172.20.26.22, source 172.20.22.113, and flow TCP port 23:
Router# clear mls ip destination 172.20.26.22 source 172.20.22.113 flow tcp 23 Router#
To display the MLS entries and confirm they have been cleared see the "Displaying IP MLS Information" section.
These sections describe how to display the MLS IP contention table and statistics.
The show mls table-contention command displays the flow contention level for the switch. The table contention level (TCL) is indicated with a number ranging from 0 (normal) to 3 (maximum). When reaching levels 1 through 3, accelerated aging starts, and begins to age out entries at a rate suitable to reduce the current contention rate. The detailed option displays the breakdown of contention between different flows.
To show the MLS contention table and VLAN statistics for the switch, perform this task:
| Command | Purpose |
|---|---|
Router# show mls table-contention [detailed | summary] | Display the MLS contention table. |
This example shows how to display the MLS contention table for the switch:
Router# show mls table-contention detailed Detailed Table Contention Level Information =========================================== Layer 3 ------- L3 Contention Level: 0 Page Hits Requiring 1 Lookup = 10 Page Hits Requiring 2 Lookups = 0 Page Hits Requiring 3 Lookups = 0 Page Hits Requiring 4 Lookups = 0 Page Hits Requiring 5 Lookups = 0 Page Hits Requiring 6 Lookups = 0 Page Hits Requiring 7 Lookups = 0 Page Hits Requiring 8 Lookups = 0 Page Misses = 0 Router#
The show mls vlan-statistics command displays VLAN-based statistics for MLS cache entries. Specifying a VLAN identifier results in a display with only the shortcuts for that VLAN. If you specify a slot, only the information about that specific slot is shown; otherwise, all entries are displayed.
To display the MLS VLAN statistics for the switch, perform this task:
| Command | Purpose |
|---|---|
Router# show mls vlan-statistics 1-1024 | Display the MLS VLAN statistics. |
This example shows how to display the VLAN statistics for VLAN 1 for every slot in the switch:
Router# show mls vlan-statistics 1 Slot 0 ======= Vlan 1 Statistics Information: ------------------------------- 65280 Layer 2 Packets Bridged, 0 Bytes 65280 Layer 3 Packets Input, 0 Bytes 65280 Layer 3 Packets Output, 0 Bytes Slot 1 ======= Vlan 1 Statistics Information: ------------------------------- 65280 Layer 2 Packets Bridged, 0 Bytes 65280 Layer 3 Packets Input, 0 Bytes 65280 Layer 3 Packets Output, 0 Bytes Slot 2 ======= Vlan 1 Statistics Information: ------------------------------- 65280 Layer 2 Packets Bridged, 0 Bytes 65280 Layer 3 Packets Input, 0 Bytes 65280 Layer 3 Packets Output, 0 Bytes Slot 3 ======= (Information Deleted) Router#
This section provides some of the debugging commands you can use to troubleshoot the IP MLS configuration and operation. This section includes the following:
Table 12-3 describes IP MLS-related debugging commands that you can use to troubleshoot IP MLS problems on the Catalyst 6000 family switch.
| Command | Description |
[no] debugging l3-mgr events | Display Layer 3 manager-related events |
[no] debugging l3-mgr packets | Display Layer 3 manager packets |
[no] debugging l3-mgr global | Display bugtrace of ip global purge events |
[no] debugging l3-mgr all | Turn on all Layer 3 manager debugging messages |
Table 12-3 describes IP MLS debugging commands that you can use to troubleshoot IP MLS problems when using the MSFC as an external router for a Catalyst 6000 family switch.
To configure the IP MLS-related debugging commands that you can use to troubleshoot IP MLS problems when using the MSFC as an external router for a Catalyst 6000 family switch, perform this task:
| Command | Purpose |
|---|---|
Router(config)# debugging mls {ip {all | error | events | messages | multicast} | rp {all | error| events | ip | locator | packets | verbose}} | Configure IP-MLS debugging. |
This example shows how to configure all IP debugging on the Catalyst 6000 family switch:
Router# debugging mls ip all mls ip all debugging is on Router#
To stop IP MLS debugging, perform one of these tasks:
| Command | Purpose |
|---|---|
Router(config)# no debug mls {all | ip {all | error | events | messages | multicast}| rp {all | error| events | ip | locator | packets | verbose}}
| Disable debugging on the Catalyst 6000 family switch using the no keyword. |
Router(config)# undebug mls {all | ip {all | error | events | messages | multicast} | rp {all | error| events | ip | locator | packets | verbose}}
| Disable debugging on the Catalyst 6000 family switch using the undebug keyword. |
This example shows how to stop all IP MLS debugging on the Catalyst 6000 family switch:
Router# undebug all All possible debugging has been turned off Router#
Posted: Mon Jan 3 14:39:16 PST 2000
Copyright 1989-1999©Cisco Systems Inc.