|
|
This chapter describes how to configure Internetwork Packet Exchange (IPX) Multilayer Switching (MLS) on the Catalyst 6000 family switch.
This chapter consists of these sections:
These sections provide an overview of MLS and describe how MLS works:
For detailed MLS overview and configuration information, refer to the Cisco IOS Switching Services Configuration Guide.
IPX MLS provides high-performance hardware-based Layer 3 switching for Catalyst 6000 family LAN switches. IPX MLS switches unicast IPX data packet flows between networks 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 partial or complete switched path exists between two hosts. Packets that do not have a partial or complete switched path to reach their destinations are still forwarded by routers. Standard routing protocols, such as Routing Information Protocol (RIP), Enhanced Interior Gateway Protocol (EIGRP), and NetWare Link Services Protocol (NLSP), are used for route determination.
Layer 3 protocols, such as IP and 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 network-layer information. Communication from a client to a server and from the server to the client are separate flows.
Flows are based only on Layer 3 addresses, which allow IPX traffic from multiple users or applications to a particular destination to be carried on a single flow if only the destination IPX address is used to identify a flow.
The Policy Feature Card (PFC) maintains a Layer 3 switching table (MLS cache) for the Layer 3-switched flows. The cache includes entries for traffic statistics that are updated in tandem with the switching of packets. After the MLS cache is created, packets identified as belonging to an existing flow can be Layer 3 switched based on the cached information. The MLS cache maintains flow information for all active flows.
An IPX 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 IPX 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 IPX 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 mask modes to determine how IPX MLS entries are created. The flow mask mode is based on the access lists configured on the IPX MLS router interfaces.
These sections 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. 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 the PFC exports cached entries, flow records are created based on the current flow mask mode. Depending on the current mode, some fields in the flow record might not have values. Unsupported fields are filled with a dash (-).
The flow mask modes for IPX MLS are as follows:
This section describes how the flow mask mode impacts the screen output of the show mls ipx command.
In destination mode, the destination IPX 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 | Encap | IPX Header | Payload | |||||
|---|---|---|---|---|---|---|---|---|
Destination | Source | Length | Checksum/ IPX Length/ Transport Control1 | Packet Type | Destination Net/Node/ Socket | Source Net/Node/ Socket | Data | Pad/FCS |
MSFC MAC | Host A MAC |
|
| Host B IPX | Host A IPX |
|
| |
| 1Transport Control counts the number of times this packet has been routed. If this number is greater than the maximum (the default is 16), then the packet is dropped. |
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 IPX MLS cache entry for this flow). The Layer 3 IPX addresses remain the same. 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 saved in the IPX 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 | Encap | IPX Header | Payload | |||||
|---|---|---|---|---|---|---|---|---|
Destination | Source | Length | Checksum/ IPX Length/ Transport Control | Packet Type | Destination Net/Node/ Socket | Source Net/Node/ Socket | Data | Pad/FCS |
Host B MAC | MSFC MAC |
|
| Host B IPX | Host A IPX |
|
| |
Figure 14-1 displays a conceptual IPX MLS network topology. In this example, Host A is on the Sales VLAN (IPX address 01.Aa), Host B is on the Marketing VLAN (IPX address 03.Bb), and Host C is on the Engineering VLAN (IPX address 02.Cc).
When Host A initiates a file transfer to Host C, an IPX MLS entry for this flow is created (this entry is the second item in the table shown in Figure 14-1). The PFC stores the MAC addresses of the MSFC and Host C in the IPX 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 Station A to Station C.
Similarly, a separate IPX MLS entry is created in the MLS cache for the traffic from Host A to Host B, and for the traffic from Host B to Host A. The destination VLAN is stored as part of each IPX MLS entry so that the correct VLAN identifier is used when encapsulating traffic on trunk links.
Table 14-1 displays the default IPX MLS configuration.
| Feature | Default Value |
|---|---|
IPX MLS enable state | Disabled |
IPX MLS aging time | 256 seconds |
IPX MLS fast aging time | 32 seconds |
IPX MLS fast aging-time packet threshold | 100 packets |
IPX MLS long aging time | 900 seconds |
These sections describe configuration guidelines that apply when configuring IPX MLS:
Other IOS software features affect IPX MLS as follows:
This section describes configuration guidelines that apply when configuring IPX MLS. Enabling certain IPX processes on an interface will affect IPX MLS on the interface. Table 14-2 shows the affected commands and the resulting behavior.
| Command | Behavior |
|---|---|
Router# clear ipx route | Clears all IPX MLS cache entries for all switches performing Layer 3 switching for this MSFC. |
Router(config)# ipx routing | The no form purges all MLS cache entries and disables IPX MLS on this MSFC. |
Router(config)# ipx security1 | Disables IPX MLS on the interface. |
| 1All forms of this command |
In IPX, the two end points of communication negotiate the maximum transmission unit (MTU) to be used. MTU size is limited by media type.
These sections describe how to configure the MSFC for IPX MLS. Depending upon your configuration, you might not have to perform all the steps in the procedure.
These sections describe how to configure the MSFC for IPX MLS:
After you perform the steps in this section to configure the MSFC, see the "Configuring IPX MLS on the Switch" section.
For information on configuring IP MLS on the switch, see the "Configuring IPX MLS on the Switch" section.
MLS route processor shortcuts for IPX are disabled by default on the switch.
To enable the MLS route processor for IPX, perform this task:
| Command | Purpose |
|---|---|
Router(config)# mls rp [ipx {input-acl} | nde-address ip_address] | Enable MLS route processing shortcuts for IPX. |
This example displays how to enable the MLS route processor for IPX on the switch:
Router(config)# mls rp ipx Router(config)#
When you disable MLS on the MSFC, IPX MLS is automatically disabled on the switch. All existing IPX MLS cache entries are purged.
To disable IPX MLS on the MSFC, use the no form of the mls rp ipx command described previously.
To display the IPX MLS route process configuration for the switch, perform this task:
| Command | Purpose |
|---|---|
Router# show mls rp | Display the IPX MLS route process configuration. |
This example shows how to display the IPX MLS route process configuration of the switch:
Router# show mls rp ip multilayer switching is globally enabled ipx multilayer switching is globally enabled 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 destination number of domains configured for mls 0 Router#
To enable IPX 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 ipx | Specify a Catalyst 6000 family switch interface for IPX MLS. |
This example shows how to enable IPX MLS for Fast Ethernet interface 5/5:
Router(config)# interface fastethernet 5/5 Router(config-if)# mls ipx Router(config-if)#
To disable IPX 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 ipx | Remove a Catalyst 6000 family switch interface from IPX MLS. |
This example shows how to disable IPX MLS for Fast Ethernet interface 5/5:
Router(config)# interface fastethernet 5/5 Router(config-if)# no mls ipx Router(config-if)#
To display the interface IPX MLS configuration, perform this task:
| Command | Purpose |
|---|---|
Router# show [ipx [interface type number] | nde] | Display MLS details for an interface. |
This example shows how to display interface IPX MLS information for interface VLAN 200:
Router# show ipx interface vlan 200 Vlan200 is up, line protocol is up IPX address is 2.0050.3e8d.6400, NOVELL-ETHER [up] Delay of this IPX network, in ticks is 1 throughput 0 link delay 0 IPXWAN processing not enabled on this interface. IPX SAP update interval is 60 seconds IPX type 20 propagation packet forwarding is disabled Incoming access list is not set Outgoing access list is not set IPX helper access list is not set SAP GGS output filter list is not set SAP GNS processing enabled, delay 0 ms, output filter list is not set SAP Input filter list is not set SAP Output filter list is not set SAP Router filter list is not set Input filter list is not set Output filter list is not set Router filter list is not set Netbios Input host access list is not set Netbios Input bytes access list is not set Netbios Output host access list is not set Netbios Output bytes access list is not set Updates each 60 seconds aging multiples RIP: 3 SAP: 3 SAP interpacket delay is 55 ms, maximum size is 480 bytes RIP interpacket delay is 55 ms, maximum size is 432 bytes RIP response delay is not set IPX accounting is disabled IPX fast switching is configured (enabled) RIP packets received 0, RIP packets sent 1, 0 Throttled RIP specific requests received 0, RIP specific replies sent 0 RIP general requests received 0, 0 ignored, RIP general replies sent 0 SAP packets received 0, SAP packets sent 1, 0 Throttled SAP GNS packets received 0, SAP GNS replies sent 0 SAP GGS packets received 0, 0 ignored, SAP GGS replies sent 0 IPX mls switching is enabled Router#
You only need to configure the switch in these circumstances:
These sections describe how to configure IPX MLS on the switch:
For information on configuring VLANs on the switch, see "Configuring Layer 2 Ethernet Interfaces." For information on configuring IPX MLS on the Catalyst 6000 family switch, see the "Configuring IPX MLS on the MSFC" section.
The IPX 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 IPX 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 IPX MLS aging time.
To configure the IPX MLS aging time, perform this task:
| Command | Purpose |
|---|---|
Router(config)# mls aging {fast | Configure the IPX MLS aging time for an MLS cache entry. |
This example shows how to configure 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 IPX 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 IPX 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 IPX 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 IPX MLS flow mask using the set 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 This 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 IPX MLS flow mask, perform this task:
| Command | Purpose |
|---|---|
Router(config)# mls flow ipx {destination | destination-source} | Specify the minimum IPX MLS flow mask for the protocol. |
This example displays how to set the minimum IPX MLS flow mask on the Catalyst 6000 family switch:
Router(config)# mls flow ipx destination Router(config)#
To display the IPX 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 displays 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)
This section describes the commands used to display IPX MLS configuration and statistics for the switch and the various interfaces and is separated into the following:
The show mls rp ipx command displays IPX MLS details. The output of the show mls rp ipx command includes:
To display detailed MLS IPX information on the switch, perform this task:
| Command | Purpose |
|---|---|
Router# show mls rp ipx [interface] | Display details for all IPX MLS interfaces. |
This example shows how to display details about all IPX MLS interfaces on the switch:
Router# show mls rp ipx
ipx multilayer switching is globally enabled
ipx mls inbound acl override is globally disabled
mls id is 0090.6dfc.5800
mls ip address 22.1.0.55
mls ipx flow mask is destination
number of domains configured for mls 1
vlan domain name: WBU
current ipx flow mask: destination
ipx current/next global purge: false/false
ipx current/next purge count: 0/0
current sequence number: 590678296
current/maximum retry count: 0/10
current domain state: no-change
domain uptime: 1d13h
keepalive timer expires in 0 seconds
retry timer not running
change timer not running
1 management interface(s) currently defined:
vlan 2 on Vlan2
18 mac-vlan(s) enabled for ipx multi-layer switching:
mac 0010.0738.2917
vlan id(s)
2 3 4 5 6 7 8 9 10 11 12
13 14 15 66 77 88 99
router currently aware of following 1 switch(es):
switch id 0010.141f.6fff
Router#
This example shows how to display IPX MLS information about a specific interface (in this case, interface vlan 10):
Router# show mls rp interface vlan 10 ipx mls active on Vlan10, domain WBU Router#
This example shows how to show detailed information about IPX MLS interfaces in a specific VTP domain:
Router# show mls rp vtp-domain WBU
vlan domain name: WBU
current ip flow mask: 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: 590678296
current/maximum retry count: 0/10
current domain state: no-change
domain uptime: 1d14h
keepalive timer expires in 3 seconds
retry timer not running
change timer not running
fcp subblock count = 20
1 management interface(s) currently defined:
vlan 2 on Vlan2
20 mac-vlan(s) configured for multi-layer switching
17 mac-vlan(s) enabled for ip multi-layer switching:
mac 0010.0738.2917
vlan id(s)
2 3 4 5 6 7 8 9 10 12 13
14 15 88 99
mac 0090.6dfc.5800
vlan id(s)
20 21
18 mac-vlan(s) enabled for ipx multi-layer switching:
mac 0010.0738.2917
vlan id(s)
2 3 4 5 6 7 8 9 10 11 12
13 14 15 66 77 88 99
router currently aware of following 1 switch(es):
switch id 0010.141f.6fff
Router#
The show mls ipx command displays IPX shortcut cache entries. You can specify the following parameters to focus the information displayed:
To display all IPX MLS entries on the switch, perform this task:
| Command | Purpose |
|---|---|
Router# show mls ipx [destination ipx_network_address | interface [ethernet slot/interface |fastethernet slot/interface | gigabitethernet slot/interface] | macd destination_mac_address | macs source_mac_address | slot 1-8 | source ipx_network_address]] | Display various IPX MLS cache entries. |
These sections provide examples of how to display specific IPX MLS cache entries on the switch:
To display all IPX MLS cache entries on the switch, perform this task:
| Command | Purpose |
|---|---|
Router# show mls ipx | Display all IPX MLS entries. |
This example shows how to display all IPX MLS entries on the switch:
Router# show mls ipx DstNet-DstNode SrcNet DstVlan-DstMac Pkts Bytes ----------------------------------------------------------------------- SrcDstPorts SrcDstEncap Age LastSeen ---------------------------------------- Number of Entries Found = 0 Router#
To display IPX MLS cache entries for a specific destination IPX address, perform this task:
| Command | Purpose |
|---|---|
Router# show mls ipx [destination ipx_addr] | Display IPX MLS entries for a specific destination address (net_address.node_address). |
This example shows how to display IPX MLS entries for a specific destination address:
Router# show mls ipx destination 1.2.2.2 DstNet-DstNode SrcNet DstVlan-DstMac Pkts Bytes ----------------------------------------------------------------------- SrcDstPorts SrcDstEncap Age LastSeen ---------------------------------------- Number of Entries Found = 0 Router#
To display IPX MLS cache entries for a specific source network address, perform this task:
| Command | Purpose |
|---|---|
Router# show mls ipx source ipx_address | Display IPX MLS entries for a specific source network address (net_address). |
This example shows how to display IPX MLS entries for a specific source IPX address:
Router# show mls ipx source 1.2.2.2 DstNet-DstNode SrcNet DstVlan-DstMac Pkts Bytes ----------------------------------------------------------------------- SrcDstPorts SrcDstEncap Age LastSeen ---------------------------------------- Number of Entries Found = 0 Router#
To display IPX MLS entries for a specific interface, perform this task:
| Command | Purpose |
|---|---|
Router# show mls ipx interface [ethernet slot/interface |fastethernet slot/interface | gigabitethernet slot/interface] | Display IPX MLS cache entries for a specific interface. |
This example shows how to display IPX MLS entries for IPX Fast Ethernet interface 5/4:
Router# show mls ipx interface fastethernet 5/4 DstNet-DstNode SrcNet DstVlan-DstMac Pkts Bytes ----------------------------------------------------------------------- SrcDstPorts SrcDstEncap Age LastSeen ---------------------------------------- Number of Entries Found = 0 Router#
To display IPX MLS entries for a specific MAC destination or source address, perform this task:
| Command | Purpose |
|---|---|
Router# show mls ipx [macd destination_address | macs source_address] | Display IPX MLS cache entries for a specific destination or source MAC address. |
This example shows how to display IPX MLS entries for a specific MAC destination address:
Router# show mls ipx macd aaaa.bbbb.bbbb DstNet-DstNode SrcNet DstVlan-DstMac Pkts Bytes ----------------------------------------------------------------------- SrcDstPorts SrcDstEncap Age LastSeen ---------------------------------------- Number of Entries Found = 0 Router#
Clear IPX shortcut entries in the Layer 3 table based on the entered criteria. The clear mls ipx command clears shortcut entries in the Layer 3 tables matching configured parameters. If none of the following parameters are entered, all IPX Layer 3 entries in the table are cleared:
The flow keyword specifies the following additional flow information:
To clear the IPX MLS statistics, perform this task:
| Command | Purpose |
|---|---|
Router# clear mls ipx [exclude protocol [all port 1-96 | tcp port 1-96 | udp port 1-96] | [destination [hostname | ip-address] interface type | macd destination_mac_address | macs source_mac_address | slot 1-8]] | Clear the IPX MLS statistics. |
This example shows how to clear the MLS cache entries in the Layer 3 table IPX interface, Fast Ethernet interface 5/5:
Router# clear mls ipx interface fastethernet 5/5 Router#
To display the MLS entries and confirm they have been cleared, see the "Displaying IPX MLS Information" section.
These sections describe how to display the IPX MLS 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, which 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 IPX MLS contention table. |
This example displays the IPX 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 IPX 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 slot is shown; otherwise, all entries are displayed.
To display the IPX MLS VLAN statistics for the switch, perform this task:
| Command | Purpose |
|---|---|
Router# show mls vlan-statistics 1-1024 | Display the IPX MLS VLAN statistics. |
This example displays 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 ======= 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 4 ======= 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 5 (Information Deleted)
This section provides debug commands to troubleshoot the IPX MLS configuration and operation:
Table 14-3 describes IPX MLS-related debug commands that you can use to troubleshoot IPX MLS problems.
| Command | Description |
[no] debug l3-mgr events | Display Layer 3 manager-related events |
[no] debug l3-mgr packets | Display Layer 3 manager packets |
[no] debug l3-mgr global | Display bugtrace of ip global purge events |
[no] debug l3-mgr all | Turn on all Layer 3 manager debugging messages |
Table 14-4 describes IPX MLS-related debug commands that you can use to troubleshoot IPX MLS problems when using the MSFC as an external router for a Catalyst 6000 family switch.
| Command | Description |
|---|---|
[no] debug mls ipx | Turn on IPX-related events for MLS, including route purging and changes of access lists and flow masks |
[no] debug mls locator | Identify which switch is switching a particular flow by using MLS explorer packets |
[no] debug mls all | Turn on all MLS debugging events |
Table 14-5 describes IPX MLS-related debug commands that you can use to troubleshoot IPX MLS problems on the Catalyst 6000 family switch.
| Command | Description |
[no] debug l3-mgr events | Display Layer 3 manager-related events |
[no] debug l3-mgr packets | Display Layer 3 manager packets |
[no] debug l3-mgr global | Display bugtrace of ip global purge events |
[no] debug l3-mgr all | Turn on all Layer 3 manager debugging messages |
To configure the IPX MLS-related debug commands that you can use to troubleshoot IPX MLS problems when using the MSFC as an external router for a Catalyst 6000 family switch, perform this task:
| Command | Purpose |
|---|---|
Router(config)# debug mls {ipx | Configure IPX MLS debugging. |
This example displays how to configure all IPX and IP debugging on the Catalyst 6000 family switch:
Router# debug mls ip all mls ip all debugging is on Router#
Table 14-6 describes the Serial Control Protocol (SCP)-related debug commands to troubleshoot the SCP that runs over the Ethernet out-of-band channel (EOBC).
| Command | Description |
[no] debug scp async | Display trace for async data in and out of the SCP system |
[no] debug scp data | Display packet data trace |
[no] debug scp errors | Display errors and warnings in SCP |
[no] debug scp packets | Display packet data in and out of the SCP system |
[no] debug scp timeouts | Report timeouts |
[no] debug scp all | Turn on all SCP debugging messages |
To stop IPX MLS debugging, perform one of these tasks:
| Command | Purpose |
|---|---|
Router(config)# no debug mls {all | ipx {all | error | events | messages} | rp {all | error| events | ipx | locator | packets | verbose}}
| Disable MLS debugging using the no keyword. |
Router(config)# undebug mls {all | ipx {all | error | events | messages} | rp {all | error| events | ipx | locator | packets | verbose}}
| Disable MLS debugging. |
This example shows how to stop all debugging on the Catalyst 6000 family switch:
Router# undebug all All possible debugging has been turned off Router#
Posted: Mon Jan 3 14:44:07 PST 2000
Copyright 1989-1999©Cisco Systems Inc.