-
Catalyst 6500 Series Software Configuration Guide, 8.7
-
Catalyst 6500 Series Switch Software Configuration Guide (Full-book PDF)
-
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 aCEF
-
Configuring MSFC IOS Features
-
Acronyms
-
Table Of Contents
Configuring CEF for PFC2 and PFC3A
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 CEF for PFC2/PFC3A
Understanding the Forwarding Decisions
Understanding the Adjacency Table
Partially and Completely Switched Multicast Flows
Understanding the NetFlow Statistics
Default CEF for PFC2/PFC3A Configuration
CEF for PFC2/PFC3A Configuration Guidelines and Restrictions
Configuring CEF for PFC2/PFC3A on the Switch
Displaying the Layer 3-Switching Entries on the Supervisor Engine
Configuring CEF on MSFC2/MSFC3
Configuring IP Multicast on MSFC2/MSFC3
Enabling IP Multicast Routing Globally
Enabling IP PIM on an MSFC2/MSFC3 Interface
Configuring the IP MMLS Global Threshold
Enabling IP MMLS on MSFC2/MSFC3 Interfaces
Displaying IP Multicast Information
Displaying IP Multicast Information on MSFC2/MSFC3
Displaying the IP Multicast Information on the Supervisor Engine
Configuring the NetFlow Statistics on the Switch
Specifying NetFlow Table Entry Creation on a Per-Interface Basis
Specifying the NetFlow Table Entry Aging-Time Value
Specifying the NetFlow Table IP Entry Fast Aging Time and Packet Threshold Values
Setting the Minimum Statistics Flow Mask
Excluding the IP Protocol Entries from the NetFlow Table
Displaying the NetFlow Statistics
Clearing the NetFlow IP and IPX Statistics
Clearing All the NetFlow Statistics
Clearing the NetFlow IP Statistics
Clearing the NetFlow IPX Statistics
Clearing the NetFlow Statistics Totals
Displaying the NetFlow Statistics Debug Information
Configuring the MLS IP-Directed Broadcasts on the Switch
Configuring CEF for PFC2 and PFC3A
This chapter describes how to configure Cisco Express Forwarding (CEF) for Policy Feature Card 2 (PFC2) and PFC3A on the Catalyst 6500 series switches.
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).
CEF for PFC3A provides IP unicast Layer 3 switching and IP multicast Layer 3 switching for Supervisor Engine 720, PFC3A, and Multilayer Switch Feature Card 3 (MSFC3).
Note
With Supervisor Engine 720 (MSFC3), IPX routing is done through the software.
Note
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
Note
Layer 3 switching allows a switch, instead of a router, to forward the IP and IPX unicast traffic and the IP multicast traffic between the VLANs. Layer 3 switching is implemented in the hardware and provides wire-speed interVLAN forwarding on the switch, rather than on MSFC2/MSFC3. Layer 3 switching requires minimal support from MSFC2/MSFC3. MSFC2/MSFC3 routes any traffic that cannot be Layer 3 switched.
Note
Layer 3 switching on Catalyst 6500 series switches provides flow statistics that you can use to identify the traffic characteristics for administration, planning, and troubleshooting. Layer 3 switching uses NetFlow Data Export (NDE) to export the flow statistics. See Chapter 16, "Configuring NDE" for more information about NDE.
Note
Understanding Layer 3-Switched Packet Rewrite
Note
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 that is based on information learned from MSFC2/MSFC3 so that the packets appear to have been routed by MSFC2/MSFC3.
Note
The packet rewrite alters these five fields:
•
•
•
•
•
Note
If Source A and Destination B are on different VLANs and Source A sends a packet to MSFC2/MSFC3 to be routed to Destination B, the switch recognizes that the packet was sent to the Layer 2 (MAC) address of MSFC2/MSFC3.
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 MSFC2/MSFC3. 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/MSFC3 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/MSFC3 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/MSFC3 MAC
Group G1 IP
Source A IP
n-1
calculation2
Understanding CEF for PFC2/PFC3A
Note
These sections describe CEF for PFC2:
•
•
•
CEF for PFC2/PFC3A 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 MSFC2 in support of CEF for PFC2.
Supervisor Engine 720, PFC3A, and MSFC3 provide Layer 3 switching with CEF for PFC3A. CEF for PFC3A is permanently enabled on Supervisor Engine 720. Cisco IOS CEF is permanently enabled on MSFC3 in support of CEF for PFC3A.
CEF for PFC2/PFC3A works with CEF (for unicast traffic) and PIM (for multicast traffic) on MSFC2/MSFC3 to support IP, IP multicast, and IPX traffic. CEF and PIM on MSFC2/MSFC3 are enhanced to support CEF for PFC2/PFC3A. CEF for PFC2/PFC3A generates flow statistics for Layer 3-switched traffic that can be displayed at the CLI or used for NDE.
CEF for PFC2/PFC3A 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/PFC3A sends all packets that match an incomplete FIB entry (one where the MAC address has not been resolved) to MSFC2/MSFC3 to be routed until MSFC2/MSFC3 resolves the MAC address.
Note
Note
Understanding the Forwarding Decisions
CEF for PFC2/PFC3A provides Layer 3 switching that is based on the following:
•
•
•
Enter the show mls entry command to display information about the entries that are used to make forwarding decisions. CEF for PFC2/PFC3A 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 that is contained in the unicast and multicast routing tables on MSFC2/MSFC3. When routing or topology changes occur in the network, the unicast and multicast routing tables on MSFC2/MSFC3 are updated and those changes are reflected in the FIB. The FIB maintains next-hop address information that is based on the information in the routing tables on MSFC2/MSFC3. The FIB supports 256,000 entries, which includes 16,000 IP multicast entries (128,000 IP multicast entries on MSFC3). With reverse path forwarding (RPF) check enabled, the number of IP entries doubles (with Supervisor Engine 720, the number of IP entries remain the same).
FIB lookup uses the following criteria:
•
•
•
•
Note
In switches with redundant supervisor engines and MSFC2s/MSFC3s, the designated MSFC2/MSFC3 supports the FIB on the active Supervisor Engine 2 or Supervisor Engine 720. The routing protocols on the nondesignated MSFC2/MSFC3 send information to the routing protocols on the designated MSFC2/MSFC3.
Enter the show mls entry cef command to display the following:
•
•
•
•
•
•
•
Console> (enable) show mls entry cefMod 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.0 255.255.255.25515 receive 127.0.0.52 255.255.255.25515 receive 127.255.255.255 255.255.255.25515 receive 10.1.1.2 255.255.255.25515 receive 10.1.1.0 255.255.255.25515 receive 10.1.1.255 255.255.255.25515 receive 10.10.1.1 255.255.255.25515 receive 10.10.0.0 255.255.255.255...Console> (enable)Enter the show mls command to display a Layer 3 switching summary:
Console> (enable) show mlsTotal packets switched = 35254Total bytes switched = 2256256Total routes = 120569Total number of Netflow entries = 120000IP statistics flows aging time = 50 secondsLong-duration flows aging time = 320 secondsIP statistics flows fast aging time = 0 seconds, packet threshold = 0IP Current flow mask is Full-Vlan flowNetflow Data Export version: 7Netflow Data Export disabledNetflow Data Export port/host is not configured.Total packets exported = 0Destination Ifindex export is enabledSource Ifindex export is enabledRate limiting is turned off, packets are bridged to routerLoad balancing hash is based on source and destination IP addresses and universcPer-prefix Stats for ALL FIB entries is EnabledConsole> (enable)Understanding the Adjacency Table
For each FIB entry, CEF for PFC2/PFC3A stores Layer 2 information from the designated MSFC2/MSFC3 for adjacent nodes in the adjacency table. Adjacent nodes are nodes that are directly connected at Layer 2. To forward traffic, CEF for PFC2/PFC3A 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 256,000 adjacency table entries. CEF for PFC3A supports 1,000,000 adjacency table entries. Only half of the adjacency table entries provide statistics.
Table 13-1 lists the adjacency types.
Enter the show mls entry cef adjacency command to display the following:
•
•
•
•
•
•
•
Console> (enable) show mls entry cef adjacencyMod: 15Destination-IP: 140.140.1.5 Destination-Mask: 255.255.255.255FIB-Type: resolvedAdjType NextHop-IP NextHop-Mac Vlan Encp Tx-Packets Tx-Octets-------- --------------- ----------------- ---- ---- ------------ -------------connect 140.140.1.5 00-00-d0-00-00-05 140 ARPA 0 0Mod: 15Destination-IP: 150.150.1.5 Destination-Mask: 255.255.255.255FIB-Type: resolvedAdjType NextHop-IP NextHop-Mac Vlan Encp Tx-Packets Tx-Octets-------- --------------- ----------------- ---- ---- ------------ -------------connect 150.150.1.5 00-00-e0-00-00-05 150 ARPA 0 0Mod: 15Destination-IP: 153.153.1.5 Destination-Mask: 255.255.255.255FIB-Type: resolvedAdjType NextHop-IP NextHop-Mac Vlan Encp Tx-Packets Tx-Octets-------- --------------- ----------------- ---- ---- ------------ -------------connect 153.153.1.5 00-00-e3-00-00-05 153 ARPA 0 0...Console> (enable)Enter the clear mls entry cef adjacency command to clear the CEF adjacency information:
Console> (enable) clear mls entry cef adjacencyAdjacency statistics has been cleared.Console> (enable)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 MSFC2/MSFC3 and is software switched for any interface that is not Layer 3 switched.
Note
PFC2/PFC3A prevents multicast traffic in flows that are completely Layer 3 switched from reaching MSFC2/MSFC3, reducing the load on MSFC2/MSFC3. 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 MSFC2/MSFC3, the multicast packet is dropped, because it is switched by the PFC2/PFC3A.
For all completely Layer 3-switched flows, PFC2/PFC3A periodically sends multicast packet and byte count statistics to MSFC2/MSFC3, because MSFC2/MSFC3 cannot record multicast statistics for completely switched flows, which it never sees. MSFC2/MSFC3 uses the statistics to update the corresponding multicast routing table entries and reset the appropriate expiration timers.
CEF for PFC2/PFC3A 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, PFC2/PFC3A 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, 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 the NetFlow Statistics
Note
These sections describe NetFlow statistics:
NetFlow Statistics Overview
CEF for PFC2/PFC3A 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 support unicast and multicast flows as follows:
•
–
–
–
•
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 the NetFlow table entries that are 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 the NetFlow table entries are created. CEF for PFC2 supports only one flow mask (the most specific one) for all statistics. If NetFlow 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 (this applies to the PFC2/MSFC2 only).
When the flow mask changes, the entire NetFlow table is purged. When CEF for PFC2/PFC3A 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 6500 Series Switch Command Reference publication for more information).
Default CEF for PFC2/PFC3A Configuration
Table 13-2 shows the default CEF for PFC2/PFC3A configuration.
CEF for PFC2/PFC3A Configuration Guidelines and Restrictions
Note
This section describes the guidelines and restrictions for configuring CEF for PFC2/PFC3A:
•
Note
•
•
•
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/PFC3A does not provide Layer 3 switching for an IP multicast flow in the following cases:
•
Note
•
Note
•
•
•
•
Configuring CEF for PFC2/PFC3A on the Switch
These sections describe how to configure CEF for PFC2/PFC3A:
•
•
•
•
•
Note
Displaying the Layer 3-Switching Entries on the Supervisor Engine
CEF for PFC2/PFC3A is permanently enabled on Supervisor Engine 2 with PFC2 and MSFC2 and on Supervisor Engine 720 with PFC3A and MSFC3. No configuration is required.
To display all the Layer 3-switching entries on the supervisor engine, perform this task:
Display Layer 3-switching information.
show mls entry [pbr-route] [cef] | [netflow-route] [qos]
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). Enter the show mls entry pbr-route command to display only the PBR entries. Enter the show mls entry qos command to display only the QoS entries.
Configuring CEF on MSFC2/MSFC3
CEF is permanently enabled on MSFC2/MSFC3. No configuration is required to support CEF for PFC2/PFC3A.
Note
Specifying CEF Maximum Routes
Note
To specify the maximum number of routes that can be programmed in the FIB TCAM for a protocol, use the set mls cef maximum-routes {ip | ip-multicast} routes command. The syntax is as follows:
•
•
•
Follow these guidelines when specifying the maximum number of routes that can be programmed in the FIB TCAM:
•
•
This command has the following characteristics:
•
•
•
•
Note
Note
Note
To specify the maximum number of routes that can be programmed in the FIB TCAM for a protocol, perform these tasks in privileged mode:
This example shows how to specify the maximum number of routes for IP unicast:
Console> (enable) set mls cef maximum-routes ip 220Configuration change will take effect after next reboot.Console> (enable) show mls cef maximum-routesCurrent:IPv4 :192k (default)IPv4 multicast : 32k (default)User configured:(effective after reboot)IPv4 :220kIPv4 multicast : 16k (adjusted default)Console> (enable)Configuring IP Multicast on MSFC2/MSFC3
These sections describe how to configure MSFC2/MSFC3 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 MSFC2/MSFC3 before you can enable PIM on MSFC2/MSFC3 interfaces.
To enable IP multicast routing globally on MSFC2/MSFC3, 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/MSFC3 Interface
You must enable PIM on MSFC2/MSFC3 interfaces before IP multicast will function on those interfaces.
To enable IP PIM on an MSFC2/MSFC3 interface, perform this task in interface configuration mode:
Enable IP PIM on an MSFC2/MSFC3 interface.
Router(config-if)# ip pim {dense-mode | sparse-mode | sparse-dense-mode}
This example shows how to enable PIM on an MSFC2/MSFC3 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/MSFC3 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 MSFC2/MSFC3. 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 MSFC2/MSFC3 Interfaces
IP MMLS is enabled by default on the MSFC2/MSFC3 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
