-
Catalyst 6500 Series Software Configuration Guide, 8.7
-
Index
-
Preface
-
Product Overview
-
Command-Line Interfaces
-
Configuring the Switch IP Address and Default Gateway
-
Configuring Ethernet, Fast Ethernet, Gigabit Ethernet, and 10-Gigabit Ethernet Switching
-
Configuring Ethernet VLAN Trunks
-
Configuring EtherChannel
-
Configuring IEEE 802.1Q Tunneling and Layer 2 Protocol Tunneling
-
Configuring Spanning Tree
-
Configuring Spanning Tree PortFast, UplinkFast, BackboneFast, and Loop Guard
-
Configuring VTP
-
Configuring VLANs
-
Configuring InterVLAN Routing
-
Configuring CEF for PFC2/PFC3
-
Configuring MLS
-
Configuring Access Control
-
Configuring NDE
-
Configuring GVRP
-
Configuring MVRP
-
Configuring Dynamic Port VLAN Membership with VMPS
-
Checking Status and Connectivity
-
Configuring Online Diagnostics
-
Administering the Switch
-
Configuring Redundancy
-
Configuring NSF with SSO MSFC Redundancy
-
Modifying the Switch Boot Configuration
-
Working with the Flash File System
-
Working with System Software Images
-
Working with Configuration Files
-
Configuring System Message Logging
-
Configuring DNS
-
Configuring CDP
-
Configuring UDLD
-
Configuring DHCP Snooping and IP Source Guard
-
Configuring NTP
-
Configuring Broadcast Suppression
-
Configuring Layer 3 Protocol Filtering
-
Configuring the IP Permit List
-
Configuring Port Security
-
Configuring Switch Access Using AAA
-
Configuring 802.1x Authentication
-
Configuring MAC Authentication Bypass
-
Configuring Web-Based Proxy Authentication
-
Tracking Host Aging
-
Configuring Network Admission Control
-
Configuring Unicast Flood Blocking
-
Configuring SNMP
-
Configuring RMON
-
Configuring SPAN, RSPAN and the Mini Protocol Analyzer
-
Using Switch TopN Reports
-
Configuring Multicast Services
-
Configuring QoS
-
Configuring Automatic QoS
-
Configuring ASLB
-
Configuring the Switch Fabric Module
-
Configuring a VoIP Network
-
Configuring MSFC IOS Features
-
Acronyms
-
Table Of Contents
Understanding How Layer 3 Switching Works
Understanding Layer 3-Switched Packet Rewrite
Understanding IP Unicast Rewrite
Understanding IPX Unicast Rewrite
Understanding IP Multicast Rewrite
Partially and Completely Switched Multicast Flows
Configuration Guidelines and Restrictions
Maximum Transmission Unit Size
Restrictions on Using IP Routing Commands with IP MLS Enabled
IP MMLS Supervisor Engine Guidelines and Restrictions
IP MMLS MSFC Configuration Restrictions
IPX MLS Interaction with Other Features
IPX MLS and Maximum Transmission Unit Size
Configuring Unicast MLS on the MSFC
Disabling and Enabling Unicast MLS on an MSFC Interface
Displaying MLS Information on the MSFC
Using Debug Commands on the MSFC
Using Debug Commands on the SCP
Configuring MLS on Supervisor Engine 1
Specifying the MLS Aging-Time Value
Specifying IP MLS Long-Duration Aging Time, Fast Aging Time, and Packet Threshold Values
Setting the Minimum IP MLS Flow Mask
Displaying CAM Entries on the Supervisor Engine
Displaying IP MLS Cache Entries
Clearing IPX MLS Cache Entries
Displaying MLS Debug Information
Configuring IP MMLS on the MSFC
Displaying Global IP MMLS Information on the Supervisor Engine
Configuring MLS
This chapter describes how to configure Multilayer Switching (MLS) for the Catalyst 6500 series switches. MLS provides IP and Internetwork Packet Exchange (IPX) unicast Layer 3 switching and IP multicast Layer 3 switching with Supervisor Engine 1, the Policy Feature Card (PFC), and the Multilayer Switch Feature Card (MSFC) or MSFC2.
Note
For complete information on the syntax and usage information for the supervisor engine commands that are used in this chapter, refer to the Catalyst 6500 Series Switch Command Reference publication.
This chapter consists of these sections:
•
•
Note
Note
Understanding How Layer 3 Switching Works
Layer 3 switching allows the switch, instead of a router, to forward IP and IPX unicast traffic and IP multicast traffic between VLANs. Layer 3 switching is implemented in the hardware and provides wire-speed interVLAN forwarding on the switch, rather than on the MSFC. Layer 3 switching requires minimal support from the MSFC. The MSFC routes any traffic that cannot be Layer 3 switched.
Note
Layer 3 switching on Catalyst 6500 series switches provides traffic statistics that you can use to identify traffic characteristics for administration, planning, and troubleshooting. Layer 3 switching uses NetFlow Data Export (NDE) to export flow statistics (for more information about NDE, see Chapter 16, "Configuring NDE").
These sections describe Layer 3 switching and MLS on the Catalyst 6500 series switches:
•
Understanding Layer 3-Switched Packet Rewrite
When a packet is Layer 3 switched from a source in one VLAN to a destination in another VLAN, the switch performs a packet rewrite at the egress port based on information learned from the MSFC so that the packets appear to have been routed by the MSFC.
Note
The packet rewrite alters these five fields:
•
•
•
•
•
If Source A and Destination B are on different VLANs and Source A sends a packet to the MSFC to be routed to Destination B, the switch recognizes that the packet was sent to the Layer 2 (MAC) address of the MSFC.
To perform Layer 3 switching, the switch rewrites the Layer 2 frame header, changing the Layer 2 destination address to the Layer 2 address of Destination B and the Layer 2 source address to the Layer 2 address of the MSFC. The Layer 3 addresses remain the same.
In IP unicast and IP multicast traffic, the switch decrements the Layer 3 Time to Live (TTL) value by 1 and recomputes the Layer 3 packet checksum. In IPX traffic, the switch increments the Layer 3 Transport Control value by 1 and recomputes the Layer 3 packet checksum. The switch recomputes the Layer 2 frame checksum and forwards (or for multicast packets, replicates as necessary) the rewritten packet to Destination B's VLAN.
These sections describe how the packets are rewritten:
•
•
•
Understanding IP Unicast Rewrite
Received IP unicast packets are (conceptually) formatted as follows:
Destination
Source
Destination
Source
TTL
Checksum
MSFC MAC
Source A MAC
Destination B IP
Source A IP
n
calculation1
After the switch rewrites an IP unicast packet, it is (conceptually) formatted as follows:
Destination
Source
Destination
Source
TTL
Checksum
Destination B MAC
MSFC MAC
Destination B IP
Source A IP
n-1
calculation2
Understanding IPX Unicast Rewrite
Received IPX packets are (conceptually) formatted as follows:
After the switch rewrites an IPX packet, it is (conceptually) formatted as follows:
Understanding IP Multicast Rewrite
Received IP multicast packets are (conceptually) formatted as follows:
Destination
Source
Destination
Source
TTL
Checksum
Group G1 MAC1
Source A MAC
Group G1 IP
Source A IP
n
calculation1
1 In this example, Destination B is a member of Group G1.
After the switch rewrites an IP multicast packet, it is (conceptually) formatted as follows:
Destination
Source
Destination
Source
TTL
Checksum
Group G1 MAC
MSFC MAC
Group G1 IP
Source A IP
n-1
calculation2
Understanding MLS
Note
Supervisor Engine 1, PFC, and MSFC or MSFC2 provide Layer 3 switching with MLS. Layer 3 switching with MLS identifies flows on the switch after the first packet has been routed by the MSFC and transfers the process of forwarding the remaining traffic in the flow to the switch, which reduces the load on the MSFC.
These sections describe MLS:
•
Understanding MLS Flows
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.
MLS supports unicast and multicast flows:
•
–
–
–
•
For example, communication from a client to a server and from the server to the client are separate flows. The Telnet traffic that is 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.
Note
Understanding the MLS Cache
These sections describe the MLS cache:
MLS Cache
The PFC maintains a Layer 3 switching table called the MLS cache for the Layer 3-switched flows. The cache also includes the entries for the traffic statistics that are updated simultaneously with the switching of packets. After the PFC creates an MLS cache entry, the packets that are 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 the active flows.
Unicast Traffic
For unicast traffic, the PFC creates an MLS cache entry for the initial routed packet of each unicast flow. Upon receipt of a routed packet that does not match any unicast flow currently in the MLS cache, the PFC creates a new MLS entry.
Multicast Traffic
For multicast traffic, the PFC populates the MLS cache using information that is learned from the MSFC. Whenever the MSFC receives traffic for a new multicast flow, it updates its multicast routing table and forwards the new information to the PFC. In addition, if an entry in the multicast routing table ages out, the MSFC deletes the entry and forwards the updated information to the PFC.
For each multicast flow cache entry, the PFC maintains a list of outgoing interfaces for the destination IP multicast group. The PFC uses this list to identify the VLANs on which traffic to a given multicast flow should be replicated.
These Cisco IOS commands affect the multicast MLS cache entries on the switch:
•
•
MLS Cache Aging
The state and identity of flows are maintained while the packet traffic is active; when the traffic for a flow ceases, the entry ages out. You can configure the aging time for the MLS entries that are kept in the MLS cache. If an entry is not used for the specified period of time, the entry ages out and the statistics for that flow can be exported to a flow collector application.
MLS Cache Size
The maximum MLS cache size is 128,000 entries. The MLS cache is shared by all MLS processes on the switch (IP MLS, IP MMLS, and IPX MLS). An MLS cache that is larger than 32,000 entries increases the probability that a flow will not be Layer 3 switched but will be forwarded to the MSFC.
Understanding Flow Masks
The PFC uses flow masks to determine how the MLS entries are created.
These sections describe the flow mask modes:
•
•
•
Flow Mask Modes—Prior to Software Release 8.5(1)
The PFC supports only one flow mask (the most specific one) for all MSFCs that are Layer 3 switched by that PFC. If the PFC detects different flow masks from the 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 the cached entries, the 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. The unsupported fields are filled with a zero (0).
The MLS flow masks are as follows:
•
•
•
•
•
Flow Mask Modes—Software Release 8.5(1) and Later Releases
With software release 8.5(1) and later releases, the multiple flow mask feature is supported on Supervisor Engine 720. This feature results in some changes to the NetFlow Data Export (NDE) functionality.
A new value for the flow mask is null. Enter the set mls flow null command to set the flow mask to null (null is the new default flow mask). When the flow mask is set to null and no feature is driving a more specific flow mask, all the flows will match to the same null flow. The counters for the null flow are incremented each time a flow hits the null flow. When the flow masks are null and no other feature is driving a flow mask, when you enter the show mls statistics entry command, the command output displays the null flow as follows (in the example, flows are not being exported because NDE is disabled):
Console> (enable) show mls statistics entryFlowmask set to Null. Please set the flowmask to see the flowsLast UsedDestination IP Source IP Prot DstPrt SrcPrt Vlan Stat-Pkts Stat-Bytes---------------- --------------- ----- ------ ------ ----- --------- ------------ - - - - N/A 728915 33530090Console> (enable)To enable flow creation, specify the flow mask by entering the set mls flow {destination | destination-source | null | full} command and specify a keyword other than the null keyword. If NDE is enabled when the null flow mask is configured, NDE will not export any flows. An example is as follows:
Console> (enable) set mls nde enableNetflow export enabledConsole> (enable) 2005 Sep 18 18:04:43 %MLS-5-FLOWMASK_NULL:IP Flowmask set to Null:Flows will not be exportedConversely, if NDE is enabled and you set the flow mask to null, the following message displays:
Console> (enable) set mls flow null2000 Sep 18 18:04:02 %MLS-5-FLOWMASK_NULL:IP Flowmask set to Null:Flows will not be exportedConsole> (enable)When you upgrade from software release 8.4(x) to software release 8.5(1) and later releases, note the following:
•
–
–
•
–
–
–
Because multiple flow masks can now coexist on the switch, the show mls statistics entry command displays only the relevant fields per flow. Depending on the flow mask that is used to create a particular flow, the relevant fields are zeroed out. NDE is used by the flow collector software. NDE assumes that all flows are created with the same flow mask. Due to this restriction, NDE cannot be enabled with certain features requiring conflicting flow masks. One specific case is hardware-accelerated NAT. NDE and hardware-accelerated NAT are mutually exclusive.
Software release 8.5(1) introduces hardware acceleration for some MSFC features. When upgrading from software release 8.4(x) to software release 8.5(1), there are no issues with MSFC features that were already configured and running. In addition to NAT, such features as reflexive ACLs and Context Based Access Control (CBAC) can work in the hardware if there is no flow mask conflict. A feature will work in the hardware unless the feature needs a flow mask that is in conflict with another feature such as an NDE or QoS microflow policer.
Hardware acceleration is also introduced in software release 8.5(1) for WCCP and TCP intercept. These MSFC features can coexist with NDE if there is no flow mask conflict. The ACL manager attempts to merge the flow mask requirements of different features. The basic idea is to allocate a new flow mask only for a strict flow mask requirement that is incompatible with already allocated flow masks. NDE does not have a strict flow mask requirement, so the flow mask for NDE can be moved up.
To use the hardware acceleration functionality for NAT, if a flow mask has been configured for NDE (enter the show mls command to display flow masks), perform these steps:
Step 1
Step 2
NDE will fail if any of the following events occur:
•
•
Conversely, once NDE is successfully configured, NAT cannot be configured to work in the hardware and two different features with conflicting flow mask requirements cannot be configured on the switch.
Software release 8.5(1) introduces the show mls flowmask command that displays the flow masks used by the various features on the switch.
These examples show the output with various configurations when no features are configured on the MSFC:
Console> show mls flowmaskNetflow Data Export is enabledNDE Flowmask is configured to use at least Null flowmaskConsole>Console> show mls flowmaskNetflow Data Export is enabled and is using Full flowmaskNDE Flowmask is configured to use at least Full flowmaskConsole>Console> show mls flowmaskNetflow Data Export is disabledNDE Flowmask is configured to use at least Full flowmaskConsole>This example shows the output when NAT is configured on the MSFC:
Console> show mls flowmaskThe MSFC features are using NotVlanFullFlow and VlanFullFlowOnly flow mask on vlan(s)10-11,50-51,90-91.Netflow Data Export is disabledNDE Flowmask is configured to at least the Null flowmaskConsole>These examples show the output with various configurations when the reflexive ACL feature is configured on the MSFC:
Console> show mls flowmaskThe MSFC features are using VlanFullFlowOnly flow mask on vlan(s) 13.Netflow Data Export is disabledNDE Flowmask is configured to use at least Null flowmaskConsole>Console> show mls flowmaskThe MSFC features are using VlanFullFlowOnly flow mask on vlan(s) 13.Netflow Data Export is enabled and is using Full-Vlan flowmaskNDE Flowmask is configured to use at least Full-Vlan flowmaskConsole>Flow Mask Modes and show mls entry Command Outputs
With the destination-ip flow mask, the source IP, protocol, and source and destination port fields show the details of the last packet that was Layer 3 switched using the MLS cache entry.
This example shows how the show mls entry command output appears in destination-ip mode:
Console> (enable) show mls entry ip shortDestination-IP Source-IP Prot DstPrt SrcPrt Destination-Mac Vlan--------------- --------------- ----- ------ ------ ----------------- ----ESrc EDst SPort DPort Stat-Pkts Stat-Byte Uptime Age---- ---- ----- ----- --------- ------------ -------- --------171.69.200.234 - - - - 00-60-70-6c-fc-22 4ARPA SNAP 5/8 11/1 3152 347854 09:01:19 09:08:20171.69.1.133 - - - - 00-60-70-6c-fc-23 2SNAP ARPA 5/8 1/1 2345 123456 09:03:32 09:08:12Total Entries: 2* indicates TCP flow has endedConsole> (enable)
Note
With the source-destination-ip flow mask, the protocol, source port, and destination port fields display the details of the last packet that was Layer 3 switched using the MLS cache entry.
This example shows how the show mls entry command output appears in source-destination-ip mode:
Console> (enable) show mls entry ip shortDestination-IP Source-IP Prot DstPrt SrcPrt Destination-Mac Vlan--------------- --------------- ----- ------ ------ ----------------- ----ESrc EDst SPort DPort Stat-Pkts Stat-Byte Uptime Age---- ---- ----- ----- --------- ------------ -------- --------171.69.200.234 171.69.192.41 - - - 00-60-70-6c-fc-22 4ARPA SNAP 5/8 11/1 3152 347854 09:01:19 09:08:20171.69.1.133 171.69.192.42 - - - 00-60-70-6c-fc-23 2SNAP ARPA 5/8 1/1 2345 123456 09:03:32 09:08:12Total Entries: 2* indicates TCP flow has endedConsole> (enable)With the full-flow flow mask, because a separate MLS entry is created for every ip flow, the details are shown for each flow.
This example shows how the show mls entry command output appears in full flow mode:
Console> (enable) show mls entry ip shortDestination-IP Source-IP Prot DstPrt SrcPrt Destination-Mac Vlan--------------- --------------- ----- ------ ------ ----------------- ----ESrc EDst SPort DPort Stat-Pkts Stat-Byte Uptime Age---- ---- ----- ----- --------- ------------ -------- --------171.69.200.234 171.69.192.41 TCP* 6000 59181 00-60-70-6c-fc-22 4ARPA SNAP 5/8 11/1 3152 347854 09:01:19 09:08:20171.69.1.133 171.69.192.42 UDP 2049 41636 00-60-70-6c-fc-23 2SNAP ARPA 5/8 1/1 2345 123456 09:03:32 09:08:12Total Entries: 2* indicates TCP flow has endedConsole> (enable)Partially and Completely Switched Multicast Flows
Some flows might be partially Layer 3 switched instead of completely Layer 3 switched in these situations:
•
•
•
•
•
•
•
For partially switched flows, all multicast traffic belonging to the flow reaches the MSFC and is software switched for any interface that is not Layer 3 switched.
The PFC prevents multicast traffic in flows that are completely Layer 3 switched from reaching the MSFC, reducing the load on the MSFC. The show ip mroute and show mls ip multicast commands identify completely Layer 3-switched flows with the text string "RPF-MFD." Multicast Fast Drop (MFD) indicates that from the perspective of the MSFC, the multicast packet is dropped because it is switched by the PFC.
For all completely Layer 3-switched flows, the PFC periodically sends the multicast packet and byte count statistics to the MSFC, because the MSFC cannot record the multicast statistics for completely switched flows, which it never sees. The MSFC uses the statistics to update the corresponding multicast routing table entries and to reset the appropriate expiration timers.
MLS Examples
Figure 14-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 14-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 the subsequent packets from Host A to Host C.
Figure 14-1 IP MLS Example Topology
Figure 14-2 shows a simple 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 B, an IPX MLS entry for this flow is created (this entry is the first item in the table shown in Figure 14-1). The PFC stores the MAC addresses of the MSFC and Host B in the IPX MLS entry when the MSFC forwards the first packet from Host A through the switch to Host B. The PFC uses this information to rewrite the subsequent packets from Host A to Host B.
Similarly, a separate IPX MLS entry is created in the MLS cache for the traffic from Host A to Host C, and for the traffic from Host C 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 the trunk links.
Figure 14-2 IPX MLS Example Topology
Default MLS Configuration
Table 14-1 shows the default IP MLS configuration.
Table 14-2 shows the default IP MMLS switch configuration.
Table 14-2 Default IP MMLS Supervisor Engine Configuration
Multicast services (IGMP snooping or GMRP)
Disabled
IP MMLS
Enabled
Table 14-3 shows the default IP MMLS MSFC configuration.
Table 14-4 shows the default IPX MLS configuration.
Table 14-4 Default IPX MLS Configuration
IPX MLS enable state
Enabled
IPX MLS aging time
256 seconds
Configuration Guidelines and Restrictions
These sections describe the configuration guidelines and restrictions for IP MLS, IP MMLS, and IPX MLS:
IP MLS
These sections describe the IP MLS configuration guidelines:
•
•
Maximum Transmission Unit Size
The default maximum transmission unit (MTU) for IP MLS is 1500. To change the MTU on an IP MLS-enabled interface, enter the ip mtu mtu command.
Restrictions on Using IP Routing Commands with IP MLS Enabled
Enabling certain IP processes on an interface will affect IP MLS on the interface. Table 14-5 shows the affected commands and the resulting behavior.
IP MMLS
These sections describe the IP MMLS configuration guidelines:
•
•
IP MMLS Supervisor Engine Guidelines and Restrictions
This section describes the guidelines and restrictions for configuring Supervisor Engine 1 for IP MMLS:
•
•
•
•
•
•
•
IP MMLS MSFC Configuration Restrictions
IP MMLS does not perform multilayer switching for an IP multicast flow in these situations:
•
224.0.0.* through 239.0.0.*
224.128.0.* through 239.128.0.*
Note
•
Note
•
•
•
•
•
Unsupported IP MMLS Features
If you enable IP MMLS, the IP accounting for the interface will not reflect accurate values.
IPX MLS
These sections describe the configuration guidelines that apply when configuring IPX MLS:
•
•
IPX MLS Interaction with Other Features
Other Cisco IOS software features affect IPX MLS as follows:
•
•
IPX MLS and Maximum Transmission Unit Size
In IPX, the two end points of communication negotiate the maximum transmission unit (MTU) to be used. The MTU size is limited by the media type.
Configuring MLS
These sections describe how to configure MLS:
•
•
Configuring Unicast MLS on the MSFC
These sections describe how to configure MLS on the MSFC:
•
•
•
•
For information on configuring routing on the MSFC, see Chapter 12, "Configuring InterVLAN Routing." For information on configuring unicast Layer 3 switching on Supervisor Engine 1, see the "Configuring MLS on Supervisor Engine 1" section.
Note
Disabling and Enabling Unicast MLS on an MSFC Interface
Unicast MLS for IP and IPX is enabled globally by default, but can be disabled and enabled on a specified interface.
To disable unicast IP or IPX MLS on a specific MSFC interface, perform one of these tasks:
This example shows how to disable IP MLS on an MSFC interface:
Router(config)# interface vlan 100Router(config-if)# no mls ipRouter(config-if)#This example shows how to disable IPX MLS on an MSFC interface:
Router(config)# interface vlan 100Router(config-if)# no mls ipxRouter(config-if)#
Note
To enable unicast IP or IPX MLS on a specific MSFC interface, perform this task:
Step 1
Specify an MSFC interface.
Router(config)# interface vlan-id
Step 2
Enable IP or IPX MLS on an MSFC interface.
Router(config-if)# mls ip
or
Router(config-if)# mls ipx
This example shows how to enable IP MLS on an MSFC interface:
Router(config)# interface vlan 100Router(config-if)# mls ipRouter(config-if)#This example shows how to enable IPX MLS on an MSFC interface:
Router(config)# interface vlan 100Router(config-if)# mls ipxRouter(config-if)#Displaying MLS Information on the MSFC
The show mls status command displays the MLS details. To display the MLS information on the MSFC, perform this task:
This example shows how to display the MLS status on the MSFC:
Router# show mls statusMLS global configuration status:global mls ip: enabledglobal mls ipx: enabledglobal mls ip multicast: disabledcurrent ip flowmask for unicast: destination onlycurrent ipx flowmask for unicast: destination onlyRouter#Using Debug Commands on the MSFC
Table 14-6 describes the MLS-related debug commands that you can use to troubleshoot the MLS problems on the MSFC.
Table 14-7 describes the MLS-related debug commands that you can use to troubleshoot the MLS problems when using the MSFC as an external router for a Catalyst 5000 family switch.
Using Debug Commands on the SCP
Table 14-8 describes the Serial Control Protocol (SCP)-related debug commands to troubleshoot the SCP that runs over the Ethernet out-of-band channel (EOBC).
Configuring MLS on Supervisor Engine 1
MLS is enabled by default on Catalyst 6500 series switches. You only need to configure Supervisor Engine 1 in these circumstances:
•
•
These sections describe how to configure MLS on Supervisor Engine 1:
•
•
•
•
•
•
•
For information on configuring the VLANs on the switch, see Chapter 11, "Configuring VLANs." For information on configuring MLS on the MSFC, see the "Configuring Unicast MLS on the MSFC" section.
Note
Note
Specifying the MLS Aging-Time Value
The MLS aging time for each protocol (IP and IPX) applies to all protocol-specific MLS cache entries. Any MLS entry that has not been used for agingtime seconds is aged out. The default is 256 seconds.
You can configure the aging time in the range of 8 to 2032 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.
Note
To specify the MLS aging time for both IP and IPX, perform this task in privileged mode:
This example shows how to specify the MLS aging time:
Console> (enable) set mls agingtime 512Multilayer switching agingtime IP and IPX set to 512Console> (enable)To specify the IP MLS aging time, perform this task in privileged mode:
This example shows how to specify the IP MLS aging time:
Console> (enable) set mls agingtime ip 512Multilayer switching aging time IP set to 512Console> (enable)To specify the IPX MLS aging time, perform this task in privileged mode:
Specify the IPX MLS aging time for an MLS cache entry.
set mls agingtime ipx [agingtime]
This example shows how to specify the IPX MLS aging time:
Console> (enable) set mls agingtime ipx 512Multilayer switching aging time IPX set to 512Console> (enable)Specifying IP MLS Long-Duration Aging Time, Fast Aging Time, and Packet Threshold Values
Note
To keep the MLS cache size below 32,000 entries, enable IP MLS fast aging time. The IP MLS fast aging time applies to the MLS entries that have no more than pkt_threshold packets that are switched within fastagingtime seconds after they are created. 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 the other data traffic.
The default fastagingtime value is 0 (no fast aging). You can configure the fastagingtime value to 32, 64, 96, or 128 seconds. Any fastagingtime value that is not configured exactly as the indicated values is adjusted to the closest one. You can configure the pkt_threshold value to 0, 1, 3, 7, 15, 31, or 63 packets.
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 32,000 entries, decrease the setting until the cache size stays below 32,000. If the cache continues to grow over 32,000 entries, decrease the normal IP MLS aging time.
The typical values for fastagingtime and pkt_threshold are 32 seconds and 0 packets (no packets are switched within 32 seconds after the entry is created).
To specify the IP MLS fast aging time and packet threshold, perform this task in privileged mode:
Specify the IP MLS fast aging time and packet threshold for an MLS cache entry.
set mls agingtime fast [fastagingtime] [pkt_threshold]
This example shows how to set the IP MLS fast aging time to 32 seconds with a packet threshold of 0 packets:
Console> (enable) set mls agingtime fast 32 0Multilayer switching fast aging time set to 32 seconds for entries with no more than 0 packets switched.Console> (enable)To specify that an active flow gets aged out, perform this task in privileged mode:
This example shows how to force an active flow to age out. You can specify the aging time of the active flow in the range of 64 to 1920 seconds in increments of 64.
Console> (enable) set mls agingtime long-duration 128Multilayer switching agingtime set to 128 seconds for long duration flowsConsole> (enable)Setting the Minimum IP MLS Flow Mask
You can set the minimum granularity of the flow mask for the MLS cache on the PFC. The actual flow mask that is used will be at least of the granularity that is specified by this command. For information on how the different flow masks work, see the "Understanding Flow Masks" section.
For example, if you do not configure the 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 set mls flow destination-source command.
Caution
To set the minimum IP MLS flow mask, perform this task in privileged mode:
Set the minimum IP MLS flow mask.
set mls flow {destination | destination-source | null | full}
This example shows how to set the minimum IP MLS flow mask to destination-source-ip:
Console> (enable) set mls flow destination-sourceConfigured IP flow mask is set to destination-source flow.Console> (enable)Displaying CAM Entries on the Supervisor Engine
The show cam command displays the content-addressable memory (CAM) entries that are associated with a specific MAC address. If the MAC address belongs to an MSFC, an "R" is appended to the MAC address.
If you specify a VLAN number, only those CAM entries that correspond to that VLAN number are displayed. If a VLAN is not specified, the entries for all the VLANs are displayed.
To display the CAM entries, perform this task:
This example shows how to display the CAM entries:
Console> show cam msfcVLAN Destination MAC Destination-Ports or VCs Xtag Status---- ------------------ ------------------------------ ---- ------194 00-e0-f9-d1-2c-00R 7/1 2 H193 00-00-0c-07-ac-c1R 7/1 2 H193 00-00-0c-07-ac-5dR 7/1 2 H202 00-00-0c-07-ac-caR 7/1 2 H204 00-e0-f9-d1-2c-00R 7/1 2 H195 00-e0-f9-d1-2c-00R 7/1 2 H192 00-00-0c-07-ac-c0R 7/1 2 H192 00-e0-f9-d1-2c-00R 7/1 2 H204 00-00-0c-07-ac-ccR 7/1 2 H202 00-e0-f9-d1-2c-00R 7/1 2 H194 00-00-0c-07-ac-5eR 7/1 2 H196 00-e0-f9-d1-2c-00R 7/1 2 H194 00-00-0c-07-ac-c2R 7/1 2 H193 00-e0-f9-d1-2c-00R 7/1 2 HTotal Matching CAM Entries Displayed = 14Console>This example shows how to display the CAM entries for a specified VLAN:
Console> show cam msfc 192VLAN Destination MAC Destination-Ports or VCs Xtag Status---- ------------------ ------------------------------ ---- ------192 00-00-0c-07-ac-c0R 7/1 2 H192 00-e0-f9-d1-2c-00R 7/1 2 HConsole>Displaying MLS Information
The show mls command displays protocol-specific MLS information and MSFC-specific information.
To display protocol-specific MLS information and MSFC-specific information, perform this task:
Display general IP or IPX MLS information and MSFC-specific information for all MSFCs.
show mls {ip | ipx} [mod1 ]
1 The mod keyword specifies the module number of the MSFC; either 15 (if the MSFC is installed on Supervisor Engine 1 in slot 1) or 16 (if the MSFC is installed on Supervisor Engine 1 in slot 2).
This example shows how to display IP MLS information and MSFC-specific information:
Console> (enable) show mls ipTotal Active MLS entries = 0Total packets switched = 0IP Multilayer switching enabledIP Multilayer switching aging time = 256 secondsIP Multilayer switching fast aging time = 0 seconds, packet threshold = 0IP Flow mask: Full FlowConfigured flow mask is Destination flowActive IP MLS entries = 0Netflow Data Export version: 8Netflow Data Export disabledNetflow Data Export port/host is not configuredTotal packets exported = 0MSFC ID Module XTAG MAC Vlans--------------- ------ ---- ----------------- --------------------52.0.03 15 1 01-10-29-8a-0c-00 1,10,123,434,121222,666,959Console> (enable)This example shows how to display IPX MLS information:
Console> (enable) show mls ipxIPX Multilayer switching aging time = 256 secondsIPX flow mask is Destination flowIPX max hop is 15Active IPX MLS entries = 356IPX MSFC ID Module XTAG MAC Vlans--------------- ------ ---- ----------------- ----------------22.1.0.56 15 1 00-10-07-38-29-18 2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,66,7700-d0-d3-9c-e3-f4 2500-10-07-38-29-18 26,11100-d0-d3-9c-e3-f4 11222.1.0.58 16 2 00-10-07-38-22-22 2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,2000-d0-d3-33-17-8c 2500-10-07-38-22-22 26,66,77,88,99,11100-d0-d3-33-17-8c 112Console> (enable)Displaying IP MLS Cache Entries
These sections describe how to display the MLS cache entries on Supervisor Engine 1:
•
•
•
•
•
•
Note
Displaying All MLS Entries
To display all the MLS entries (IP and IPX), perform this task in privileged mode:
This example shows how to display all the MLS entries (IP and IPX):
Console> (enable) show mls entry shortDestination-IP Source-IP Prot DstPrt SrcPrt Destination-Mac Vlan--------------- --------------- ----- ------ ------ ----------------- ----ESrc EDst SPort DPort Stat-Pkts Stat-Bytes Created LastUsed---- ---- ----- ----- ---------- ------------ -------- --------171.69.200.234 171.69.192.41 TCP* 6000 59181 00-60-70-6c-fc-22 4ARPA SNAP 5/8 11/1 3152 347854 09:01:19 09:08:20171.69.1.133 171.69.192.42 UDP 2049 41636 00-60-70-6c-fc-23 2SNAP ARPA 5/8 1/1 2345 1234567 09:03:32 09:08:12171.69.1.133 171.69.192.42 UDP 2049 41636 00-60-70-6c-fc-23 2SNAP ARPA 5/8 1/1 2345 1234567 09:03:32 09:08:12171.69.1.133 171.69.192.42 UDP 2049 41636 00-60-70-6c-fc-23 2SNAP ARPA 5/8 1/1 2345 1234567 09:03:32 09:08:12171.69.1.133 171.69.192.42 UDP 2049 41636 00-60-70-6c-fc-23 2SNAP ARPA 5/8 1/1 2345 1234567 09:03:32 09:08:12Total IP entries: 5* indicates TCP flow has ended.Destination-IPX Source-IPX-net Destination-Mac Vlan PortStat-Pkts Stat-Bytes------------------------- -------------- ----------------- ---- -------------- -----------BABE.0000.0000.0001 - 00-a0-c9-0a-89-1d 211 13/3730230 1510775201.00A0.2451.7423 - 00-a0-24-51-74-23 201 14/3330256 31795084501.0000.3100.0501 - 31-00-05-01-00-00 501 9/3712121 323232401.0000.0000.0401 - 00-00-04-01-00-00 401 3/14633 38676Total IPX entries: 4Console>Displaying MLS Entries for a Specific IP Destination Address
To display the MLS entries for a specific destination IP address, perform this task in privileged mode:
Display the MLS entries for the specified destination IP address.
show mls entry ip destination [ip_addr]
This example shows how to display the MLS entries for a specific destination IP address:
Console> (enable) show mls entry ip destination 172.20.22.14/24Destination-IP Source-IP Prot DstPrt SrcPrt Destination-Mac VlanEDst ESrc DPort SPort Stat-Pkts Stat-Bytes Uptime Age--------------- --------------- ----- ------ ------ ----------------- -------- ---- ------ ------ ---------- ----------- -------- --------MSFC 172.20.25.1 (Module 15):172.20.22.14 - - - - 00-60-70-6c-fc-22 4ARPA ARPA 5/39 5/40 115 5290 00:12:20 00:00:04MSFC 172.20.27.1 (Module 16):Total entries:1Console> (enable)Displaying IPX MLS Entries for a Specific IPX Destination Address
To display the IPX MLS entries for a specific destination IPX address, perform this task in privileged mode:
Display the IPX MLS entries for a specific destination IPX address (net_address.node_address).
show mls entry ipx destination ipx_addr
This example shows how to display the IPX MLS entries for a specific destination IPX address:
Console> (enable) show mls entry ipx destination 3E.0010.298a.0c00Destination IPX Source IPX net Destination Mac Vlan Port------------------------- -------------- ----------------- ---- -----MSFC 22.1.0.56 (Module 15):3E.0010.298a.0c00 13 00-00-00-00-00-09 26 4/7Console> (enable)Displaying MLS Entries for a Specific IP Source Address
To display the MLS entries for a specific source IP address, perform this task in privileged mode:
Display the MLS entries for the specified source IP address.
show mls entry ip source [ip_addr]
This example shows how to display the MLS entries for a specific source IP address:
Console> (enable) show mls entry ip source 10.0.2.15Destination-IP Source-IP Prot DstPrt SrcPrt Destination-Mac VlanEDst ESrc DPort SPort Stat-Pkts Stat-Bytes Uptime Age--------------- --------------- ----- ------ ------ ----------------- -------- ---- ------ ------ ---------- ----------- -------- --------MSFC 172.20.25.1 (Module 15):172.20.22.14 10.0.2.15 TCP Telnet 37819 00-e0-4f-15-49-ff 51ARPA ARPA 5/39 5/40 115 5290 00:12:20 00:00:04MSFC 172.20.27.1 (Module 16):Total entries:1Console> (enable)Displaying MLS Entries for a Specific IP Flow
The show mls entry ip flow command displays the MLS entries for a specific IP flow. The protocol argument can be tcp, udp, icmp, or a decimal number for other protocol families. The src_port and dst_port arguments specify the protocol ports if the protocol is TCP or User Datagram Protocol (UDP). A value of zero (0) for src_port, dst_port, or protocol is treated as a wildcard and all entries are displayed (unspecified options are treated as wildcards). If the protocol selected is not TCP or UDP, set the src_port and dst_prt to 0 or no flows will display.
To display the MLS entries for a specific IP flow (when the flow mask mode is full flow), perform this task in privileged mode:
Display the MLS entries for a specific IP flow (when the flow mask mode is full flow).
show mls entry ip flow [protocol src_port dst_port]
This example shows how to display the MLS entries for a specific IP flow:
Console> (enable) show mls entry ip flow tcp 23 37819Destination IP Source IP Port DstPrt SrcPrt Destination Mac Vlan Port--------------- --------------- ---- ------ ------ ----------------- ---- -----MSFC 51.0.0.3:10.0.2.15 51.0.0.2 TCP 37819 Telnet 08-00-20-7a-07-75 10 3/1Console> (enable)Displaying IPX MLS Entries for a Specific MSFC
To display the IPX MLS entries for a specific MSFC, perform this task in privileged mode:
Display the IPX MLS entries for a specific MSFC.
show mls entry ipx mod1
1 The mod keyword specifies the module number of the MSFC; either 15 (if the MSFC is installed on Supervisor Engine 1 in slot 1) or 16 (if the MSFC is installed on Supervisor Engine 1 in slot 2).
This example shows how to display the IPX MLS entries for a specific MSFC:
Console> (enable) show mls entry ipx 15Destination-IPX Destination-Mac Vlan EDst ESrc Port Stat-PktsStat-Bytes Uptime Age------------------------- ----------------- ---- ---- ---- ----- --------------------- -------- --------MSFC 22.1.0.56 (Module 15):11.0000.0000.2B10 00-00-00-00-2b-10 11 ARPA ARPA - 7869361974 00:15:52 00:00:0011.0000.0000.A810 00-00-00-00-a8-10 11 ARPA ARPA - 3934180964 00:15:52 00:00:0011.0000.0000.3210 00-00-00-00-32-10 11 ARPA ARPA - 7871362066 00:15:52 00:00:0011.0000.0000.B110 00-00-00-00-b1-10 11 ARPA ARPA - 3935181010 00:15:52 00:00:0011.0000.0000.1910 00-00-00-00-19-10 11 ARPA ARPA - 7873362158 00:15:52 00:00:0011.0000.0000.9A10 00-00-00-00-9a-10 11 ARPA ARPA - 3936181056 00:15:52 00:00:0011.0000.0000.0010 00-00-00-00-00-10 11 ARPA ARPA 3/11 7875362250 00:15:52 00:00:0011.0000.0000.8310 00-00-00-00-83-10 11 ARPA ARPA - 3937181102 00:15:52 00:00:0010.0000.0000.0109 00-00-00-00-01-09 10 ARPA ARPA 3/10 963644432744 00:15:52 00:00:0011.0000.0000.4F10 00-00-00-00-4f-10 11 ARPA ARPA - 7877362342 00:15:53 00:00:0011.0000.0000.CC10 00-00-00-00-cc-10 11 ARPA ARPA - 3938181148 00:15:53 00:00:0011.0000.0000.5610 00-00-00-00-56-10 11 ARPA ARPA - 7879362434 00:15:53 00:00:0011.0000.0000.D510 00-00-00-00-d5-10 11 ARPA ARPA - 3939181194 00:15:53 00:00:0011.0000.0000.7D10 00-00-00-00-7d-10 11 ARPA ARPA - 3940181240 00:15:53 00:00:0011.0000.0000.FE10 00-00-00-00-fe-10 11 ARPA ARPA - 3941181286 00:15:53 00:00:0011.0000.0000.6410 00-00-00-00-64-10 11 ARPA ARPA - 7883362618 00:15:53 00:00:0011.0000.0000.E710 00-00-00-00-e7-10 11 ARPA ARPA - 3941181286 00:15:53 00:00:0011.0000.0000.6010 00-00-00-00-60-10 11 ARPA ARPA - 7885362710 00:15:53 00:00:0011.0000.0000.E310 00-00-00-00-e3-10 11 ARPA ARPA - 3942181332 00:15:53 00:00:0011.0000.0000.7910 00-00-00-00-79-10 11 ARPA ARPA - 3943181378 00:15:54 00:00:00Console> (enable)Displaying MLS Entries for Bridged-Flow Statistics
To display the MLS entries for the bridged-flow statistics, perform this task in privileged mode:
This example shows how to display the MLS entries for the bridged-flow statistics:
Console> (enable) show mls entryDestination-IP Source-IP Prot DstPrt SrcPrt Destination-Mac Vlan EDst ESrc DPort SPort Stat-Pkts Stat-Bytes Uptime Age--------------- --------------- ----- ------ ------ ----------------- ---- ---- ---- --------- --------- ---------- ----------- -------- --------224.0.0.5 21.2.0.22 - 0 0 00-00-00-00-00-00 0 ARPA ARPA - 5/11 20 1280 00:03:14 00:00:04224.0.0.13 1.1.1.2 - 0 0 00-00-00-00-00-00 0 ARPA ARPA - 5/11 7 210 00:03:02 00:00:02255.255.255.255 - - 0 0 ff-ff-ff-ff-ff-ff 21 ARPA ARPA - 5/11 28 2996 00:03:10 00:00:0210.6.62.195 - - 0 0 00-00-00-00-00-02 20 ARPA ARPA - 5/5 291494 13408724 00:03:16 00:00:00Destination-IPX Destination-Mac Vlan EDst ESrc Port Stat-Pkts Stat-Bytes Uptime Age------------------------- ----------------- ---- ---- ---- ----- ---------- ----------- -------- --------Total entries displayed:2Clearing MLS Cache Entries
The clear mls entry command removes specific MLS cache entries. The all keyword clears all the MLS entries. The destination and source keywords specify the source and destination IP addresses. The destination and source ip_addr_spec can be a full IP address or a subnet address in the format ip_subnet_addr, ip_addr/subnet_mask, or ip_addr/subnet_mask_bits.
The flow keyword specifies the following additional flow information:
•
•
To clear an MLS entry, perform this task in privileged mode:
Clear an MLS entry.
clear mls entry ip [destination ip_addr_spec] [source ip_addr_spec] [flow protocol src_port dst_port] [all]
This example shows how to clear the MLS entries with destination IP address 172.20.26.22:
Console> (enable) clear mls entry ip destination 172.20.26.22MLS IP entry clearedConsole> (enable)This example shows how to clear the MLS entries with destination IP address 172.20.22.113, TCP source port 1652, and TCP destination port 23:
Console> (enable) clear mls entry destination 172.20.26.22 source 172.20.22.113 flow tcp 1652 23MLS IP entry clearedConsole> (enable)Clearing IPX MLS Cache Entries
The clear mls entry ipx command removes specific IPX MLS cache entries. The destination and source keywords specify the source and destination IPX addresses. The all keyword clears all the MLS entries.
Displaying IP MLS Statistics
These sections describe how to display the IP MLS statistics:
•
•
Displaying IP MLS Statistics by Protocol
The show mls statistics protocol command displays the IP MLS statistics by protocol (such as Telnet, FTP, and WWW). The protocol keyword functions only if the flow mask mode is full flow. Enter the show mls command to see the current flow mask.
To display the IP MLS statistics by protocol, perform this task in privileged mode:
Display the IP MLS statistics by protocol (only if IP MLS is in full flow mode).
show mls statistics protocol
This example shows how to display the IP MLS statistics by protocol:
Console> (enable) show mls statistics protocolProtocol TotalFlows TotalPackets Total Bytes------- ---------- -------------- ------------Telnet 900 630 4298FTP 688 2190 3105WWW 389 42679 623686SMTP 802 4966 92873X 142 2487 36870DNS 1580 52 1046Others 82 1 73Total 6583 53005 801951Console> (enable)Displaying Statistics for MLS Cache Entries
The show mls statistics entry command displays the IP MLS statistics for the MLS cache entries. Specify the destination IP address, source IP address, protocol, and source and destination ports to see the specific MLS cache entries.
A value of zero (0) for src_port or dst_port is treated as a wildcard, and all the statistics are displayed (the unspecified options are treated as wildcards). If the protocol specified is not TCP or UDP, set the src_port and dst_prt to 0 or no statistics will display.
To display the statistics for the MLS cache entries, perform this task in privileged mode:
This example shows how to display the statistics for a particular MLS cache entry:
Console> show mls statistics entry ip destination 172.20.22.14Last UsedDestination IP Source IP Prot DstPrt SrcPrt Stat-Pkts Stat-Bytes--------------- --------------- ---- ------ ------ --------- -----------MSFC 127.0.0.12:172.20.22.14 172.20.25.10 6 50648 80 3152 347854Console>Clearing MLS Statistics
The clear mls statistics command clears the following statistics:
•
•
To clear the IP MLS statistics, perform this task in privileged mode:
This example shows how to clear the IP MLS statistics:
Console> (enable) clear mls statisticsAll mls statistics cleared.Console> (enable)Displaying MLS Debug Information
The show mls debug command displays MLS debug information that you can send to your technical support representative for analysis if necessary.
To display the MLS debug information, perform this task:
Display the MLS debug information that you can send to your technical support representative.
show mls debug
Note
Configuring IP MMLS
These sections describe how to configure IP MMLS:
•
•
Configuring IP MMLS on the MSFC
These sections describe how to configure the MSFC for IP MMLS:
•
•
•
•
•
•
•
•
•
Note
Note
Note
http://www.cisco.com/en/US/docs/ios/12_1/iproute/configuration/guide/ip_c.html
Enabling IP Multicast Routing Globally
You must enable IP multicast routing globally on the MSFC before you can enable IP MMLS on the MSFC interfaces.
To enable IP multicast routing globally on the MSFC, perform this task in global configuration mode:
This example shows how to enable IP multicast routing globally:
Router(config)# ip multicast-routingRouter(config)#Enabling IP PIM on MSFC Interfaces
You must enable IP PIM on the MSFC interfaces before IP MMLS will function on those interfaces.
To enable IP PIM on an interface, perform this task:
Enable IP PIM on an MSFC interface.
Router(config-if)# ip pim {dense-mode | sparse-mode | sparse-dense-mode}
This example shows how to enable IP PIM on an interface using the default mode (sparse-dense-mode):
Router(config-if)# ip pimRouter(config-if)#This example shows how to enable IP PIM sparse mode on an interface:
Router(config-if)# ip pim sparse-modeRouter(config-if)#Configuring the IP MMLS Global Threshold
You can configure a global multicast rate threshold, which is specified in packets per second, below which all (S,G) multicast traffic is routed by the MSFC. Entering the command prevents the creation of MLS entries for short-lived multicast flows (such as join requests).
Note
To configure the IP MMLS threshold, perform this task:
This example shows how to configure the IP MMLS threshold to 10 packets per second:
Router(config)# mls ip multicast threshold 10Router(config)#Use the no keyword to deconfigure the threshold.
Enabling IP MMLS on MSFC Interfaces
IP MMLS is enabled by default on the MSFC interface when you enable IP PIM on the interface. Perform this task only if you disabled IP MMLS on the interface and you want to reenable it.
Note
To enable IP MMLS on an MSFC interface, perform this task:
This example shows how to enable IP MMLS on an MSFC interface:
Router(config-if)# mls ip multicastRouter(config-if)#Use the no keyword to disable IP MMLS on an MSFC interface.
Displaying IP MMLS Interface Information
The show ip pim interface count command displays the IP MMLS enable state on the MSFC IP PIM interfaces and the number of packets that are received and sent on the interface.
The show ip interface command displays the IP MMLS enable state on an MSFC interface.
To display the IP MMLS information for an IP PIM MSFC interface, perform one of these tasks:
Display IP MMLS interface information.
Router# show ip pim interface [type number] count
Display the IP MMLS interface enable state.
Router# show ip interface
Displaying the IP Multicast Routing Table
The show ip mroute command displays the IP multicast routing table on the MSFC.
To display the IP multicast routing table, perform this task:
Display the IP multicast routing table.
Router# show ip mroute [group[source]] | [summary] | [count] | [active kbps]
This example shows how to display the IP multicast routing table for 239.252.1.1:
Router# show ip mroute 239.252.1.1IP Multicast Routing TableFlags:D - Dense, S - Sparse, C - Connected, L - Local, P - PrunedR - RP-bit set, F - Register flag, T - SPT-bit set, J - Join SPTM - MSDP created entry, X - Proxy Join Timer RunningA - Advertised via MSDPOutgoing interface flags:H - Hardware switchedTimers:Uptime/ExpiresInterface state:Interface, Next-Hop or VCD, State/Mode(*, 239.252.1.1), 04:04:59/00:02:59, RP 80.0.0.2, flags:SJIncoming interface:Vlan800, RPF nbr 80.0.0.2Outgoing interface list:Vlan10, Forward/Dense, 01:29:57/00:00:00, H(22.0.0.10, 239.252.1.1), 00:00:19/00:02:41, flags:JTIncoming interface:Vlan800, RPF nbr 80.0.0.2, RPF-MFDOutgoing interface list:Vlan10, Forward/Dense, 00:00:19/00:00:00, HMonitoring IP MMLS on the MSFC
The show mls ip multicast command displays detailed information about IP MMLS.
To display the detailed IP MMLS information on the MSFC, perform one of these tasks:
This example shows how to display the IP MMLS statistics on the MSFC:
Router# show mls ip multicast statisticsMLS Multicast configuration and state:Router Mac:0050.0f2d.9bfd, Router IP:1.12.123.234MLS multicast operating state:ACTIVEMaximum number of allowed outstanding messages:1Maximum size reached from feQ:1Feature Notification sent:5Feature Notification Ack received:4Unsolicited Feature Notification received:0MSM sent:33MSM ACK received:33Delete notifications received:1Flow Statistics messages received:248MLS Multicast statistics:Flow install Ack:9Flow install Nack:0Flow update Ack:2Flow update Nack:0Flow delete Ack:0Complete flow install Ack:10Complete flow install Nack:0Complete flow delete Ack:1Input VLAN delete Ack:4Output VLAN delete Ack:0Group delete sent:0Group delete Ack:0Global delete sent:7Global delete Ack:7L2 entry not found error:0Generic error :3LTL entry not found error:0MET entry not found error:0L3 entry exists error :0Hash collision error :0L3 entry not found error:0Complete flow exists error :0This example shows how to display information on a specific IP MMLS entry on the MSFC:
Router# show mls ip multicast 224.1.1.1Multicast hardware switched flows:(1.1.13.1, 224.1.1.1) Incoming interface: Vlan13, Packets switched: 61590Hardware switched outgoing interfaces: Vlan20 Vlan9RFD-MFD installed: Vlan13(1.1.9.3, 224.1.1.1) Incoming interface: Vlan9, Packets switched: 0Hardware switched outgoing interfaces: Vlan20RFD-MFD installed: Vlan9(1.1.12.1, 224.1.1.1) Incoming interface: Vlan12, Packets switched: 62010Hardware switched outgoing interfaces: Vlan20 Vlan9RFD-MFD installed: Vlan12(1.1.12.3, 224.1.1.1) Incoming interface: Vlan12, Packets switched: 61980Hardware switched outgoing interfaces: Vlan20 Vlan9RFD-MFD installed: Vlan12(1.1.11.1, 224.1.1.1) Incoming interface: Vlan11, Packets switched: 62430Hardware switched outgoing interfaces: Vlan20 Vlan9RFD-MFD installed: Vlan11(1.1.11.3, 224.1.1.1) Incoming interface: Vlan11, Packets switched: 62430Hardware switched outgoing interfaces: Vlan20 Vlan9RFD-MFD installed: Vlan11Total hardware switched installed: 6Router#This example shows how to display a summary of the IP MMLS information on the MSFC:
Router# show mls ip multicast summary7 MMLS entries using 560 bytes of memoryNumber of partial hardware-switched flows:2Number of complete hardware-switched flows:5Router#Using Debug Commands on the IP MMLS MSFC
Table 14-9 describes the IP MMLS-related debug troubleshooting commands.
Table 14-9 IP MMLS Debug Commands
[no] debug mls ip multicast group group_id group_mask
Configures filtering that applies to all the other multicast debugging commands.
[no] debug mls ip multicast events
Displays the IP MMLS events.
[no] debug mls ip multicast errors
Turns on the debug messages for the multicast MLS-related errors.
[no] debug mls ip multicast messages
Displays IP MMLS messages from/to the hardware switching engine.
[no] debug mls ip multicast all
Turns on all the IP MMLS messages.
[no] debug mdss error
Turns on the MDSS1 error messages.
[no] debug mdss events
Turns on the MDSS-related events.
[no] debug mdss all
Turns on all the MDSS messages.
1 MDSS = Multicast Distributed Switching Services
Using Debug Commands on the SCP
Table 14-10 describes the Serial Control Protocol (SCP)-related debug commands to troubleshoot the SCP that runs over the Ethernet out-of-band channel (EOBC).
Displaying Global IP MMLS Information on the Supervisor Engine
These sections describe how to configure IP MMLS on Supervisor Engine 1:
•
•
Note
Note
Displaying IP MMLS Configuration Information
The show mls multicast command displays the global IP MMLS configuration information and the state of the participating MSFCs.
To display the global IP MMLS configuration information, perform this task:
This example shows how to display the global IP MMLS configuration information:
Console> (enable) show mls multicastAdmin Status: EnabledOperational Status: ActiveConfigured flow mask is {Destination-source-vlan flow}Active Entries = 10Router include list :1.1.9.254 (Active)1.1.5.252 (Active)Console> (enable)Displaying IP MMLS Statistics
The show mls multicast statistics command displays the IP MMLS statistics for the multicast MSFCs.
To display the IP MMLS statistics for the multicast MSFCs, perform this task:
This example shows how to display the IP MMLS statistics for the multicast MSFCs:
Console (enable) show mls multicast statisticsRouter IP Router Name Router MAC-------------------------------------------------------1.1.9.254 ? 00-50-0f-06-3c-a0Transmit:Delete Notifications: 23Acknowledgements: 92Flow Statistics: 56Receive:Open Connection Requests: 1Keep Alive Messages: 72Shortcut Messages: 19Shortcut Install TLV: 8Selective Delete TLV: 4Group Delete TLV: 0Update TLV: 3Input VLAN Delete TLV: 0Output VLAN Delete TLV: 0Global Delete TLV: 0MFD Install TLV: 7MFD Delete TLV: 0Router IP Router Name Router MAC-------------------------------------------------------1.1.5.252 ? 00-10-29-8d-88-01Transmit:Delete Notifications: 22Acknowledgements: 75Flow Statistics: 22Receive:Open Connection Requests: 1Keep Alive Messages: 68Shortcut Messages: 6Shortcut Install TLV: 4Selective Delete TLV: 2Group Delete TLV: 0Update TLV: 0Input VLAN Delete TLV: 0Output VLAN Delete TLV: 0Global Delete TLV: 0MFD Install TLV: 4MFD Delete TLV: 0Console (enable)Clearing IP MMLS Statistics
The clear mls multicast statistics command clears the IP MMLS statistics for all the participating MSFCs.
To clear the IP MMLS statistics, perform this task in privileged mode:
This example shows how to clear the IP MMLS statistics:
Console> (enable) clear mls multicast statisticsAll statistics for the MLS routers in include list are cleared.Console> (enable)Displaying IP MMLS Entries
The show mls multicast entry command displays information about the multicast flows that are handled by the PFC. You can display the entries that are based on any combination of the participating MSFC, the VLAN, the multicast group address, or the multicast traffic source.
To display information about the IP MMLS entries, perform this task in privileged mode:
Display information about the IP MMLS entries.
show mls multicast entry [[[mod] [vlan vlan_id] [group ip_addr] [source ip_addr]] | [all]]
This example shows how to display all the IP MMLS entries:
Console> (enable) show mls multicast entry allRouter IP Dest IP Source IP Pkts Bytes InVlan OutVlans--------------- --------------- --------------- ---------- ----------- ------- --------1.1.5.252 224.1.1.1 1.1.11.1 15870 2761380 201.1.9.254 224.1.1.1 1.1.12.3 473220 82340280 121.1.5.252 224.1.1.1 1.1.12.3 15759 2742066 201.1.9.254 224.1.1.1 1.1.11.1 473670 82418580 111.1.5.252 224.1.1.1 1.1.11.3 15810 2750940 201.1.9.254 224.1.1.1 1.1.12.1 473220 82340280 121.1.5.252 224.1.1.1 1.1.13.1 15840 2756160 201.1.9.254 224.1.1.1 1.1.13.1 472770 82261980 131.1.5.252 224.1.1.1 1.1.12.1 15840 2756160 201.1.9.254 224.1.1.1 1.1.11.3 473667 82418058 11Total Entries: 10Console> (enable)This example shows how to display the IP MMLS entries for a specific MSFC:
Console> (enable) show mls multicast entry 15Router IP Dest IP Source IP Pkts Bytes InVlan OutVlans--------------- --------------- --------------- ---------- ----------- ------- --------1.1.5.252 224.1.1.1 1.1.11.1 15870 2761380 201.1.5.252 224.1.1.1 1.1.12.3 15759 2742066 201.1.5.252 224.1.1.1 1.1.11.3 15810 2750940 201.1.5.252 224.1.1.1 1.1.13.1 15840 2756160 201.1.5.252 224.1.1.1 1.1.12.1 15840 2756160 20Total Entries: 5Console> (enable)This example shows how to display the IP MMLS entries for a specific multicast group address:
Console> (enable) show mls multicast entry group 226.0.1.3 shortRouter IP Dest IP Source IP InVlan Pkts Bytes OutVlans-------------- ----------- ------------ ------ ------ --------- ---------171.69.2.1 226.0.1.3 172.2.3.8 20 171 23512 10,201,22,45171.69.2.1 226.0.1.3 172.3.4.9 12 25 3120 8,20Total Entries: 2Console> (enable)This example shows how to display the IP MMLS entries for a specific MSFC and a specific multicast source address:
Console> (enable) show mls multicast entry 15 1.1.5.252 source 1.1.11.1 shortRouter IP Dest IP Source IP Pkts BytesInVlan OutVlans--------------- --------------- --------------- ---------- -------------------------- ----------172.20.49.159 224.1.1.6 1.1.40.4 368 5777640 23,25172.20.49.159 224.1.1.71 1.1.22.2 99 6514222 30,37172.20.49.159 224.1.1.8 1.1.22.2 396 23562022 13,19Console> (enable)
