-
Catalyst 6500 Series Software Configuration Guide, 6.3 and 6.4
-
Product Overview
-
Command-Line Interfaces
-
Configuring the Switch IP Address and Default Gateway
-
Configuring Ethernet, Fast Ethernet, and Gigabit Ethernet Switching
-
Configuring Ethernet VLAN Trunks
-
Configuring EtherChannel
-
Configuring IEEE 802.1Q Tunneling
-
Configuring Spanning Tree
-
Configuring Spanning Tree PortFast, UplinkFast, BackboneFast, and Loop Guard
-
Configuring VTP
-
Configuring VLANs
-
Configuring InterVLAN Routing
-
Configuring CEF for PFC2
-
Configuring MLS
-
Configuring NDE
-
Configuring Access Control
-
Configuring GVRP
-
Configuring Dynamic Port VLAN Membership with VMPS
-
Checking Port Status and Connectivity
-
Administering the Switch
-
Configuring Switch Access Using AAA
-
Configuring 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 NTP
-
Configuring Broadcast Suppression
-
Configuring Layer 3 Protocol Filtering
-
Configuring the IP Permit List
-
Configuring Port Security
-
Configuring SNMP
-
Configuring RMON
-
Configuring SPAN and RSPAN
-
Using Switch TopN Reports
-
Configuring Multicast Services
-
Configuring QoS
-
Configuring a VoIP Network
-
Configuring ASLB
-
Configuring the Switch Fabric Modules
-
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
Understanding Forwarding Decisions
Understanding the Adjacency Table
Partially and Completely Switched Multicast Flows
Understanding NetFlow Statistics
Default CEF for PFC2 Configuration
CEF for PFC2 Configuration Guidelines and Restrictions
Displaying Layer 3-Switching Entries on the Supervisor Engine
Configuring IP Multicast on the MSFC2
Enabling IP Multicast Routing Globally
Enabling IP PIM on an MSFC2 Interface
Configuring the IP MMLS Global Threshold
Enabling IP MMLS on MSFC Interfaces
Displaying IP Multicast Information
Displaying IP Multicast Information on the MSFC2
Displaying IP Multicast Information on the Supervisor Engine
Configuring NetFlow Statistics
Specifying the NetFlow Table Entry Aging-Time Value
Specifying NetFlow Table IP Entry Fast Aging Time and Packet Threshold Values
Setting the Minimum Statistics Flow Mask
Excluding IP Protocol Entries from the NetFlow Table
Clearing NetFlow IP and IPX Statistics
Clearing All NetFlow Statistics
Clearing NetFlow IP Statistics
Clearing NetFlow IPX Statistics
Clearing NetFlow Statistics Totals
Displaying NetFlow Statistics Debug Information
Configuring CEF for PFC2
This chapter describes how to configure Cisco Express Forwarding (CEF) for Policy Feature Card 2 (PFC2). CEF for PFC2 provides IP and Internetwork Packet Exchange (IPX) unicast Layer 3 switching and IP multicast Layer 3 switching for Supervisor Engine 2, PFC2, and Multilayer Switch Feature Card 2 (MSFC2).
Note
For complete information on the syntax and usage information for the supervisor engine commands used in this chapter, refer to the Catalyst 6000 Family Command Reference publication.
This chapter consists of these sections:
•
•
•
•
Note
Note
http://www.cisco.com/univercd/cc/td/doc/product/lan/cat5000/rel_5_2/layer3/index.htm.
Understanding How Layer 3 Switching Works
These sections describe Layer 3 switching with PFC2:
•
•
Layer 3 Switching Overview
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 hardware and provides wire-speed interVLAN forwarding on the switch, rather than on the MSFC2. Layer 3 switching requires minimal support from the MSFC2. The MSFC2 routes any traffic that cannot be Layer 3 switched.
Note
Layer 3 switching on Catalyst 6000 family switches provides flow 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 "Configuring NDE").
Note
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 MSFC2 so that the packets appear to have been routed by the MSFC2.
Note
Packet rewrite alters five fields:
•
•
•
•
•
Note
If Source A and Destination B are on different VLANs and Source A sends a packet to the MSFC2 to be routed to Destination B, the switch recognizes that the packet was sent to the Layer 2 (MAC) address of the MSFC2.
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 MSFC2. The Layer 3 addresses remain the same.
In IP unicast and IP multicast traffic, the switch decrements the Layer 3 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
MSFC2 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
MSFC2 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
MSFC2 MAC
Group G1 IP
Source A IP
n-1
calculation2
Understanding CEF for PFC2
These sections describe CEF for PFC2:
•
•
•
CEF for PFC2 Overview
Supervisor Engine 2, PFC2, and MSFC2 provide Layer 3 switching with CEF for PFC2. CEF for PFC2 is permanently enabled on Supervisor Engine 2. Cisco IOS CEF is permanently enabled on the MSFC2 in support of CEF for PFC2.
CEF for PFC2 works with CEF (for unicast traffic) and PIM (for multicast traffic) on the MSFC2 to support IP, IP multicast, and IPX traffic. CEF and PIM on the MSFC2 are enhanced to support CEF for PFC2. CEF for PFC2 generates flow statistics for Layer 3-switched traffic that can be displayed at the CLI or used for NDE.
CEF for PFC2 provides Layer 3 switching for all packets that match a complete forwarding information base (FIB) entry (see the "Understanding the FIB" section). CEF for PFC2 sends all packets that match an incomplete FIB entry (one where the MAC address has not been resolved) to the MSFC2 to be routed until the MSFC2 resolves the MAC address.
Note
Note
Enter the show mls cef command to display a Layer 3 switching summary:
Console> (enable) show mls cefTotal L3 packets switched: 0Total L3 octets switched: 0Total route entries: 18IP route entries: 15IPX route entries: 3IPM route entries: 0IP load sharing entries: 0IPX load sharing entries: 0Forwarding entries: 4Bridge entries: 12Drop entries: 2Understanding Forwarding Decisions
CEF for PFC2 provides Layer 3 switching based on:
•
•
•
Enter the show mls entry command to display information about the entries used to make forwarding decisions. CEF for PFC2 makes a forwarding decision for each packet and sends the rewrite information for each packet to the egress port, where the rewrite occurs when the packet is transmitted from the switch.
Understanding the FIB
The FIB resides in a separate TCAM. The adjacency table is stored separately in DRAM. The NetFlow table is stored separately in DRAM. The FIB, the adjacency table, and the NetFlow table do not compete with any other features for storage space.
The FIB is conceptually similar to a routing table. It maintains a mirror image of the forwarding information contained in the unicast and multicast routing tables on the MSFC2. When routing or topology changes occur in the network, the unicast and multicast routing tables on the MSFC2 are updated and those changes are reflected in the FIB. The FIB maintains next-hop address information based on the information in the routing tables on the MSFC2. The FIB supports 256K entries, which includes 16K IP multicast entries. With reverse path forwarding (RPF) check enabled, the number of IP entries doubles.
FIB lookup uses the following criteria:
•
•
•
•
Note
In switches with redundant supervisor engines and MSFC2s, the designated MSFC2 supports the FIB on the active Supervisor Engine 2. The routing protocols on the nondesignated MSFC2 send information to the routing protocols on the designated MSFC2.
Enter the show mls entry cef command to display:
•
•
•
•
•
•
•
Understanding the Adjacency Table
For each FIB entry, CEF for PFC2 stores Layer 2 information from the designated MSFC2 for adjacent nodes in the adjacency table. Adjacent nodes are nodes that are directly connected at Layer 2. To forward traffic, CEF for PFC2 selects a route from a FIB entry, which points to an adjacency entry, and uses the Layer 2 header for the adjacent node in the adjacency table entry to rewrite the packet during Layer 3 switching. CEF for PFC2 supports 256K adjacency table entries.
Table 13-1 lists the adjacency types.
Enter the show mls entry cef adjacency command to display:
•
•
•
•
•
•
•
Partially and Completely Switched Multicast Flows
Some flows might be partially Layer 3 switched instead of completely Layer 3 switched in these situations:
•
•
•
•
•
•
Note
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.
Note
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 viewpoint 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 multicast packet and byte count statistics to the MSFC, because the MSFC cannot record multicast statistics for completely switched flows, which it never sees. The MSFC uses the statistics to update the corresponding multicast routing table entries and reset the appropriate expiration timers.
CEF for PFC2 Examples
Figure 13-1 shows a simple IP CEF 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, the PFC2 uses the information in the FIB and adjacency table to forward packets from Host A to Host C.
Figure 13-1 IP CEF Example Topology
Figure 13-2 shows a simple IPX CEF 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, the PFC2 uses the information in the FIB and adjacency table to forward packets from Host A to Host C.
Figure 13-2 IPX CEF Example Topology
Understanding NetFlow Statistics
These sections describe NetFlow statistics:
NetFlow Statistics Overview
CEF for PFC2 generates flow statistics for Layer 3-switched traffic, which are stored in the NetFlow table. NetFlow statistics can be displayed with show commands and are also available to NetFlow Data Export (NDE).
Note
NetFlow statistics supports unicast and multicast flows:
•
–
–
–
•
NetFlow Table Entry Aging
The state and identity of flows are maintained while packet traffic is active; when traffic for a flow ceases, the entry ages out. You can configure the aging time for NetFlow table entries kept in the NetFlow table. 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.
Flow Masks
Flow masks determine how NetFlow table entries are created. CEF for PFC2 supports only one flow mask (the most specific one) for all statistics. If CEF for PFC2 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 flow mask changes, the entire NetFlow table is purged. When CEF for PFC2 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 statistics flow masks are as follows:
•
•
•
•
•
Enter the show mls statistics entry command to display the contents of the NetFlow table and the current flow mask. Use the keyword options to display information for specific traffic (refer to the Catalyst 6000 Family Command Reference publication for more information).
Default CEF for PFC2 Configuration
Table 13-2 shows the default CEF for PFC2 configuration.
CEF for PFC2 Configuration Guidelines and Restrictions
Follow these guidelines and restrictions when configuring CEF for PFC2:
•
Note
•
•
–
Ethernet V2.0 (ARPA)
802.3 with 802.2 with 1 byte control (SAP1)
802.3 with 802.2 and SNAP–
Ethernet V2.0 (ARPA)
802.3 (raw)
802.2 with 1 byte control (SAP1)
SNAP
Note
–
CEF for PFC2 does not provide Layer 3 switching for an IP multicast flow in the following cases:
•
Note
•
Note
•
•
•
•
Configuring CEF for PFC2
These sections describe how to configure CEF for PFC2:
•
•
•
Note
Displaying Layer 3-Switching Entries on the Supervisor Engine
CEF for PFC2 is permanently enabled on Supervisor Engine 2 with the PFC2 and the MSFC2. No configuration is required.
To display all the Layer 3-switching entries on the supervisor engine, perform this task:
This example shows how to display the Layer 3-switching entries:
Console> (enable) show mls entryMod FIB-Type Destination-IP Destination-Mask NextHop-IP Weight--- --------- --------------- ---------------- --------------- ------15 receive 0.0.0.0 255.255.255.25515 receive 255.255.255.255 255.255.255.25515 receive 127.0.0.12 255.255.255.25516 receive 127.0.0.0 255.255.255.25516 receive 127.255.255.255 255.255.255.25515 resolved 127.0.0.11 255.255.255.255 127.0.0.11 115 receive 21.2.0.4 255.255.255.25516 receive 21.0.0.0 255.255.255.25516 receive 21.255.255.255 255.255.255.25515 receive 44.0.0.1 255.255.255.25516 receive 44.0.0.0 255.255.255.25516 receive 44.255.255.255 255.255.255.25515 receive 42.0.0.1 255.255.255.25516 receive 42.0.0.0 255.255.255.25516 receive 42.255.255.255 255.255.255.25515 receive 43.0.0.99 255.255.255.25515 receive 43.0.0.0 255.255.255.25515 receive 43.255.255.255 255.255.255.25515 receive 192.20.20.20 255.255.255.25516 receive 21.2.0.5 255.255.255.25516 receive 42.0.0.20 255.255.255.25515 connected 43.0.0.0 255.0.0.015 drop 224.0.0.0 240.0.0.015 wildcard 0.0.0.0 0.0.0.0Mod FIB-Type Dest-IPX-net NextHop-IPX Weight--- --------- ------------ ------------------------- ------15 connected 2115 connected 4415 connected 4215 resolved 450 42.0050.3EA9.ABFD 115 resolved 480 42.0050.3EA9.ABFD 115 wildcard 0Destination-IP Source-IP Prot DstPrt SrcPrt Destination-Mac Vlan EDst Stat-Pkts Stat-Bytes Uptime Age TcpDltSeq TcpDltAck--------------- --------------- ----- ------ ------ ----------------- ---- ---- ---------- ----------- -------- -------- --------- ---------0.0.0.5 0.0.0.5 5 204 104 cc-cc-cc-cc-cc-cc 5 ARPA 0 0 01:03:18 01:00:51 cccccccc cccccccc0.0.0.2 0.0.0.2 2 201 101 cc-cc-cc-cc-cc-cc 2 ARPA 0 0 01:03:21 01:00:51 cccccccc cccccccc0.0.0.4 0.0.0.4 4 203 X cc-cc-cc-cc-cc-cc 4 ARPA 0 0 01:03:19 01:00:51 cccccccc cccccccc0.0.0.1 0.0.0.1 ICMP 200 100 cc-cc-cc-cc-cc-cc 1 ARPA 0 0 01:03:25 01:00:52 cccccccc cccccccc0.0.0.3 0.0.0.3 3 202 102 cc-cc-cc-cc-cc-cc 3 ARPA 0 0 01:03:20 01:00:52 cccccccc cccccccc0.0.0.6 0.0.0.6 TCP 205 105 cc-cc-cc-cc-cc-cc 6 ARPA 0 0 01:03:18 01:00:52 cccccccc ccccccccConsole> (enable)Enter the show mls entry cef command to display only the FIB entries. Enter the show mls entry netflow-route command to display only the entries from the TCP intercept feature and reflexive access control lists (ACLs).
Configuring CEF on the MSFC2
CEF is permanently enabled on the MSFC2. No configuration is required to support CEF for PFC2.
Note
Configuring IP Multicast on the MSFC2
These sections describe how to configure the MSFC2 for IP multicast:
•
•
•
•
Note
http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121cgcr/ip_c/ipcprt3/index.htm
Enabling IP Multicast Routing Globally
You must enable IP multicast routing globally on the MSFC2 before you can enable PIM on MSFC interfaces.
To enable IP multicast routing globally on the MSFC2, 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 an MSFC2 Interface
You must enable PIM on MSFC2 interfaces before IP multicast will function on those interfaces.
To enable IP PIM on an MSFC2 interface, perform this task in interface configuration mode:
Enable IP PIM on an MSFC2 interface.
Router(config-if)# ip pim {dense-mode | sparse-mode | sparse-dense-mode}
This example shows how to enable PIM on an MSFC2 interface using the default mode (sparse-dense-mode):
Router(config-if)# ip pimRouter(config-if)#This example shows how to enable PIM sparse mode on an MSFC2 interface:
Router(config-if)# ip pim sparse-modeRouter(config-if)#Configuring the IP MMLS Global Threshold
You can configure a global multicast rate threshold, specified in packets per second, below which all multicast traffic is routed by the MSFC. This prevents 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 Multicast Information
These sections describe how to display IP multicast information:
•
•
Displaying IP Multicast Information on the MSFC2
These sections describe displaying IP multicast information on the MSFC2:
•
•
•
•
Displaying IP MMLS Interface Information
The show ip pim interface count command displays the IP MMLS enable state on MSFC IP PIM interfaces and the number of packets received and sent on the interface.
The show ip interface command displays the IP MMLS enable state on an MSFC interface.
To display 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 MSFC2.
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:
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, HDisplaying IP Multicast Details
The show mls ip multicast command displays detailed information about IP MMLS.
To display detailed MMLS information on the MSFC, perform one of these tasks:
This example shows how to display 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 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
Table 13-3 describes IP MMLS-related debug troubleshooting commands.
Table 13-3 IP MMLS Debug Commands
[no] debug mls ip multicast group group_id group_mask
Configures filtering that applies to all other multicast debugging commands.
[no] debug mls ip multicast events
Displays IP MMLS events.
[no] debug mls ip multicast errors
Turns on debug messages for 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 IP MMLS messages.
[no] debug mdss error
Turns on MDSS1 error messages.
[no] debug mdss events
Turns on MDSS-related events.
[no] debug mdss all
Turns on all MDSS messages.
1 MDSS = Multicast Distributed Switching Services
Using Debug Commands on the SCP
Table 13-4 describes the Serial Control Protocol (SCP)-related debug commands to troubleshoot the SCP that runs over the Ethernet out-of-band channel (EOBC).
