Feedback
Table Of Contents
Configuring IPv4 Multicast Layer 3 Switching
Understanding IPv4 Multicast Layer 3 Switching
IPv4 Multicast Layer 3 Switching Overview
Multicast Layer 3 Switching Cache
Layer 3-Switched Multicast Packet Rewrite
Partially and Completely Switched Flows
Filtering of RPF Failures for Stub Networks
Rate Limiting of RPF Failure Traffic
Understanding IPv4 Bidirectional PIM
Default IPv4 Multicast Layer 3 Switching Configuration
IPv4 Multicast Layer 3 Switching Configuration Guidelines and Restrictions
Configuring IPv4 Multicast Layer 3 Switching
Source-Specific Multicast with IGMPv3, IGMP v3lite, and URD
Enabling IPv4 Multicast Routing Globally
Enabling IPv4 PIM on Layer 3 Interfaces
Enabling IP Multicast Layer 3 Switching Globally
Enabling IP Multicast Layer 3 Switching on Layer 3 Interfaces
Configuring the Replication Mode
Enabling Local Egress Replication
Configuring the Layer 3 Switching Global Threshold
Enabling Installation of Directly Connected Subnets
Specifying the Flow Statistics Message Interval
Enabling Shortcut-Consistency Checking
Configuring ACL-Based Filtering of RPF Failures
Displaying RPF Failure Rate-Limiting Information
Configuring Multicast Boundary
Displaying IPv4 Multicast Layer 3 Hardware Switching Summary
Displaying the IPv4 Multicast Routing Table
Displaying IPv4 Multicast Layer 3 Switching Statistics
Configuring IPv4 Bidirectional PIM
Enabling IPv4 Bidirectional PIM Globally
Configuring the Rendezvous Point for IPv4 Bidirectional PIM Groups
Setting the IPv4 Bidirectional PIM Scan Interval
Displaying IPv4 Bidirectional PIM Information
Clearing IPv4 Multicast Layer 3 Switching Statistics
Configuring IPv4 Multicast Layer 3 Switching
This chapter describes how to configure IPv4 multicast Layer 3 switching in Cisco IOS Software Release 12.2SX.
Note
For complete syntax and usage information for the commands used in this chapter, see these publications:
•
http://www.cisco.com/en/US/docs/ios/mcl/122sx_mcl.html
•
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122cgcr/index.htm
This chapter consists of these sections:
•
•
•
•
•
•
Understanding IPv4 Multicast Layer 3 Switching
These sections describe how IPv4 multicast Layer 3 switching works:
•
•
•
•
•
IPv4 Multicast Layer 3 Switching Overview
The Policy Feature Card (PFC) provides Layer 3 switching for IP multicast flows using the hardware replication table and hardware Cisco Express Forwarding (CEF), which uses the forwarding information base (FIB) and the adjacency table on the PFC. In systems with Distributed Forwarding Cards (DFCs), IP multicast flows are Layer 3 switched locally using Multicast Distributed Hardware Switching (MDHS). MDHS uses local hardware CEF and replication tables on each DFC to perform Layer 3 switching and rate limiting of reverse path forwarding (RPF) failures locally on each DFC-equipped switching module.
The PFC and the DFCs support hardware switching of (*,G) state flows. The PFC and the DFCs support rate limiting of non-RPF traffic.
Multicast Layer 3 switching forwards IP multicast data packet flows between IP subnets using advanced application-specific integrated circuit (ASIC) switching hardware, which offloads processor-intensive multicast forwarding and replication from network routers.
Layer 3 flows that cannot be hardware switched are still forwarded in the software by routers. Protocol Independent Multicast (PIM) is used for route determination.
The PFC and the DFCs all use the Layer 2 multicast forwarding table to determine on which ports Layer 2 multicast traffic should be forwarded (if any). The multicast forwarding table entries are populated in conjunction with Internet Group Management Protocol (IGMP) snooping (see Chapter 32, "Configuring IGMP Snooping and MVR for IPv4 Multicast Traffic").
Multicast Layer 3 Switching Cache
This section describes how the PFC and the DFCs maintain Layer 3 switching information in hardware tables.
The PFC and DFC populate the (S,G) or (*,G) flows in the hardware FIB table with the appropriate masks; for example, (S/32, G/32) and (*/0, G/32). The RPF interface and the adjacency pointer information is also stored in each entry. The adjacency table contains the rewrite and a pointer to the replication entries. If a flow matches a FIB entry, the RPF check compares the incoming interface/VLAN with the entry. A mismatch is an RPF failure, which can be rate limited if this feature is enabled.
The route processor (RP) updates its multicast routing table and forwards the new information to the PFC whenever it receives traffic for a new flow. In addition, if an entry in the multicast routing table on the RP ages out, the RP deletes the entry and forwards the updated information to the PFC. In systems with DFCs, flows are populated symmetrically on all DFCs and on the PFC.
The Layer 3 switching cache contains flow information for all active Layer 3-switched flows. After the switching cache is populated, multicast packets identified as belonging to an existing flow can be Layer 3 switched based on the cache entry for that flow. For each cache entry, the PFC maintains a list of outgoing interfaces for the IP multicast group. From this list, the PFC determines onto which VLANs traffic from a given multicast flow should be replicated.
These commands affect the Layer 3 switching cache entries:
•
•
•
Layer 3-Switched Multicast Packet Rewrite
When a multicast packet is Layer 3 switched from a multicast source to a destination multicast group, the PFC and the DFCs perform a packet rewrite that is based on information learned from the RP and stored in the adjacency table.
For example, Server A sends a multicast packet addressed to IP multicast group G1. If there are members of group G1 on VLANs other than the source VLAN, the PFC must perform a packet rewrite when it replicates the traffic to the other VLANs (the switch also bridges the packet in the source VLAN).
When the PFC receives the multicast packet, it is (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.
The PFC rewrites the packet as follows:
•
•
The result is a rewritten IP multicast packet that appears to have been routed. The PFC replicates the rewritten packet onto the appropriate destination VLANs, where it is forwarded to members of IP multicast group G1.
After the PFC performs the packet rewrite, the packet is (conceptually) formatted as follows:
Destination
Source
Destination
Source
TTL
Checksum
Group G1 MAC
RP MAC
Group G1 IP
Source A IP
n-1
calculation2
Partially and Completely Switched Flows
When at least one outgoing Layer 3 interface for a given flow is multilayer switched and at least one outgoing interface is not multilayer switched, that flow is considered partially switched. When a partially switched flow is created, all multicast traffic belonging to that flow still reaches the RP and is forwarded by software on those outgoing interfaces that are not multilayer switched.
These sections describe partially and completely switched flow:
Partially Switched Flows
A flow might be partially switched instead of completely switched in these situations:
•
•
•
•
•
•
•
•
(S,G) flows are partially switched instead of completely switched in these situations:
•
•
(*,G) flows are partially switched instead of completely switched in these situations:
•
•
–
–
–
•
•
Completely Switched Flows
When all the outgoing interfaces for a given flow are Layer 3 switched, and none of the above situations apply to the flow, that flow is considered completely switched. When a completely switched flow is created, the PFC prevents multicast traffic bridged on the source VLAN for that flow from reaching the RP interface in that VLAN, freeing the RP of the forwarding and replication load for that flow.
One consequence of a completely switched flow is that multicast statistics on a per-packet basis for that flow cannot be recorded. Therefore, the PFC periodically sends multicast packet and byte count statistics for all completely switched flows to the RP. The RP updates the corresponding multicast routing table entry and resets the expiration timer for that multicast route.
Note
Non-RPF Traffic Processing
These sections describe non-RPF traffic processing:
•
•
Non-RPF Traffic Overview
In a redundant configuration where multiple routers connect to the same LAN segment, only one router forwards the multicast traffic from the source to the receivers on the outgoing interfaces (see Figure 31-1). In this kind of topology, only the PIM designated router (PIM DR) forwards the data in the common VLAN, but the non-PIM DR receives the forwarded multicast traffic. The redundant router (non-PIM DR) must drop this traffic because it has arrived on the wrong interface and fails the RPF check. Traffic that fails the RPF check is called non-RPF traffic.
The PFC hardware processes non-RPF traffic by filtering (dropping) or rate limiting the non-RPF traffic.
Figure 31-1 Redundant Multicast Router Configuration in a Stub Network
Filtering of RPF Failures for Stub Networks
The PFC and the DFCs support ACL-based filtering of RPF failures for sparse mode stub networks. When you enable the ACL-based method of filtering RPF failures by entering the mls ip multicast stub command on the redundant router, the following ACLs automatically download to the PFC and are applied to the interface you specify:
access-list 100 permit ip A.B.C.0 0.0.0.255 anyaccess-list 100 permit ip A.B.D.0 0.0.0.255 anyaccess-list 100 permit ip any 224.0.0.0 0.0.0.255access-list 100 permit ip any 224.0.1.0 0.0.0.255access-list 100 deny ip any 224.0.0.0 15.255.255.255The ACLs filter RPF failures and drop them in hardware so that they are not forwarded to the router.
Use the ACL-based method of filtering RPF failures only in sparse mode stub networks where there are no downstream routers. For dense mode groups, RPF failure packets have to be seen on the router for the PIM assert mechanism to function properly. Use CEF-based or NetFlow-based rate limiting to limit the rate of RPF failures in dense mode networks and sparse mode transit networks.
For information on configuring ACL-based filtering of RPF failures, see the "Configuring ACL-Based Filtering of RPF Failures" section.
Rate Limiting of RPF Failure Traffic
When you enable rate limiting of packets that fail the RPF check (non-RPF packets), most non-RPF packets are dropped in hardware. According to the multicast protocol specification, the router needs to receive the non-RPF packets for the PIM assert mechanism to function properly, so all non-RPF packets cannot be dropped in hardware.
When a non-RPF packet is received, a NetFlow entry is created for each non-RPF flow.
When the first non-RPF packet arrives, the PFC bridges the packet to the RP and to any bridged ports and creates a NetFlow entry that contains source, group, and ingress interface information, after which the NetFlow entry handles all packets for that source and group, sending packets only to bridged ports and not to the RP.
To support the PIM assert mechanism, the PFC periodically forwards a percentage of the non-RPF flow packets to the RP.
The first packets for directly connected sources in PIM sparse mode are also rate-limited and are processed by the CPU.
Rate limiting of RPF failures is enabled by default.
Multicast Boundary
The multicast boundary feature allows you to configure an administrative boundary for multicast group addresses. By restricting the flow of multicast data packets, you can reuse the same multicast group address in different administrative domains.
You configure the multicast boundary on an interface. A multicast data packet is blocked from flowing across the interface if the packet's multicast group address matches the access control list (ACL) associated with the multicast boundary feature.
Multicast boundary ACLs can be processed in hardware by the Policy Feature Card (PFC), a Distributed Forwarding Card (DFC), or in software by the RP. The multicast boundary ACLs are programmed to match the destination address of the packet. These ACLs are applied to traffic on the interface in both directions (input and output).
To support multicast boundary ACLs in hardware, the switch creates new ACL TCAM entries or modifies existing ACL TCAM entries (if other ACL-based features are active on the interface). To verify TCAM resource utilization, enter the show tcam counts ip command.
If you configure the filter-autorp keyword, the administrative boundary also examines auto-RP discovery and announcement messages and removes any auto-RP group range announcements from the auto-RP packets that are denied by the boundary ACL.
Understanding IPv4 Bidirectional PIM
The PFC3 supports hardware forwarding of IPv4 bidirectional PIM groups. To support IPv4 bidirectional PIM groups, the PFC3 implements a new mode called designated forwarder (DF) mode. The designated forwarder is the router elected to forward packets to and from a segment for a IPv4 bidirectional PIM group. In DF mode, the switch accepts packets from the RPF and from the DF interfaces.
When the switch is forwarding IPv4 bidirectional PIM groups, the RPF interface is always included in the outgoing interface list of (*,G) entry, and the DF interfaces are included depending on IGMP/PIM joins.
If the route to the RP becomes unavailable, the group is changed to dense mode. Should the RPF link to the RP become unavailable, the IPv4 bidirectional PIM flow is removed from the hardware FIB.
For information on configuring IPv4 bidirectional PIM, see the "Configuring IPv4 Bidirectional PIM" section.
Default IPv4 Multicast Layer 3 Switching Configuration
Table 31-1 shows the default IP multicast Layer 3 switching configuration.
Internet Group Management Protocol (IGMP) snooping is enabled by default on all VLAN interfaces. If you disable IGMP snooping on an interface, multicast Layer 3 flows are still switched by the hardware. Bridging of the flow on an interface with IGMP snooping disabled causes flooding to all forwarding interfaces of the VLAN. For details on configuring IGMP snooping, see Chapter 32, "Configuring IGMP Snooping and MVR for IPv4 Multicast Traffic."
IPv4 Multicast Layer 3 Switching Configuration Guidelines and Restrictions
These sections describe IP Multicast Layer 3 switching configuration restrictions:
Restrictions
IP multicast Layer 3 switching is not provided for an IP multicast flow in the following situations:
•
Note
•
•
•
•
•
•
•
•
•
Unsupported Features
If you enable IP multicast Layer 3 switching, IP accounting for Layer 3 interfaces does not report accurate values. The show ip accounting command is not supported.
Configuring IPv4 Multicast Layer 3 Switching
These sections describe how to configure IP multicast Layer 3 switching:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Note
Source-Specific Multicast with IGMPv3, IGMP v3lite, and URD
For complete information and procedures about source-specific multicast with IGMPv3, IGMP v3lite, and URL Rendezvous Directory (URD), see this URL:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122cgcr/fipr_c/ipcpt3/1cfssm.htm
Enabling IPv4 Multicast Routing Globally
You must enable IP multicast routing globally before you can enable IP multicast Layer 3 switching on Layer 3 interfaces.
For complete information and procedures, see these publications:
•
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122cgcr/fipr_c/ipcprt2/index.htm
•
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122cgcr/fipras_r/index.htm
To enable IP multicast routing globally, perform this task:
Router(config)# ip multicast-routing
Enables IP multicast routing globally.
Router(config)# no ip multicast-routing
Disables IP multicast routing globally.
This example shows how to enable multicast routing globally:
Router(config)# ip multicast-routingRouter(config)#Enabling IPv4 PIM on Layer 3 Interfaces
You must enable PIM on the Layer 3 interfaces before IP multicast Layer 3 switching functions on those interfaces.
To enable IP PIM on a Layer 3 interface, perform this task:
Step 1
Router(config)# interface {{vlan vlan_ID} | {type1 slot/port}}
Selects an interface to configure.
Step 2
Router(config-if)# ip pim {dense-mode | sparse-mode | sparse-dense-mode}
Enables IP PIM on a Layer 3 interface.
Router(config-if)# no ip pim [dense-mode | sparse-mode | sparse-dense-mode]
Disables IP PIM on a Layer 3 interface.
1 type = fastethernet, gigabitethernet, or tengigabitethernet
This example shows how to enable PIM on an interface using the default mode (sparse-dense-mode):
Router(config-if)# ip pimThis example shows how to enable PIM sparse mode on an interface:
Router(config-if)# ip pim sparse-modeEnabling IP Multicast Layer 3 Switching Globally
To enable hardware switching of multicast routes globally on your system, perform this task:
Step 1
Router(config)# mls ip multicast
Globally enables hardware switching of multicast routes.
Step 2
Router# show mls ip multicast
Displays MLS IP multicast configuration.
This example shows how to globally enable hardware switching of multicast routes:
Router(config)# mls ip multicastRouter(config)#Enabling IP Multicast Layer 3 Switching on Layer 3 Interfaces
IP multicast Layer 3 switching is enabled by default on the Layer 3 interface when you enable PIM on the interface. Perform this task only if you disabled IP multicast Layer 3 switching on the interface and you want to reenable it.
PIM can be enabled on any Layer 3 interface, including VLAN interfaces.
Note
To enable IP multicast Layer 3 switching on a Layer 3 interface, perform this task:
Step 1
Router(config)# interface {{vlan vlan_ID} | {type1 slot/port}}
Selects an interface to configure.
Step 2
Router(config-if)# mls ip multicast
Enables IP multicast Layer 3 switching on a Layer 3 interface.
Step 3
Router(config-if)# no mls ip multicast
Disables IP multicast Layer 3 switching on a Layer 3 interface.
1 type = fastethernet, gigabitethernet, or tengigabitethernet
This example shows how to enable IP multicast Layer 3 switching on a Layer 3 interface:
Router(config-if)# mls ip multicastRouter(config-if)#Configuring the Replication Mode
Note
The Supervisor Engine 720 and Supervisor Engine 720-10GE support the egress keyword. Support for the egress keyword is called "Multicast Enhancement - Replication Mode Detection" in the release notes and Feature Navigator.
By default, the switch automatically detects the replication mode based on the switching modules installed in the system. If all switching modules are capable of egress replication, the switch uses egress-replication mode. If the switch detects switching modules that are not capable of egress replication, the replication mode automatically changes to ingress replication. You can override this action by entering the mls ip multicast replication-mode egress command so that the switch continues to work in egress-replication mode even if there are fabric-enabled modules installed that do not support egress replication. You can also configure the switch to operate only in ingress-replication mode.
If the switch is functioning in automatic detection mode, and you install a switching module that cannot perform egress replication, the following occurs:
•
•
•
If the switch is functioning in forced egress mode, a system log is created that will display the presence of modules that are not capable of egress replication mode.
Note
Note
During a change from egress- to ingress-replication mode, traffic interruptions may occur because the shortcuts will be purged and reinstalled. To avoid interruptions in traffic forwarding, enter the mls ip multicast replication-mode ingress command in global configuration mode. This command forces the system to operate in ingress-replication mode.
The no form of the mls ip multicast replication-mode ingress command restores the system to automatic detection mode.
To enable IP multicast Layer 3 switching, perform this task:
This example shows how to enable the replication mode:
Router (config)# mls ip multicast replication-mode egressRouter# show mlp ip multicast capabilityCurrent mode of replication is IngressConfigured replication mode is EgressSlot Multicast replication capability2 Egress3 Egress4 Ingress5 Egress6 EgressRouter# show mls ip multicast summary4 MMLS entries using 656 bytes of memoryNumber of partial hardware-switched flows:2Number of complete hardware-switched flows:2Directly connected subnet entry install is enabledCurrent mode of replication is IngressAuto-detection of replication mode is enabledConsistency checker is enabledRouter (config)#Enabling Local Egress Replication
Note
With a Supervisor Engine 720 or Supervisor Engine 720-10GE, you can unconditionally enable local egress replication. This feature is called "Multicast enhancement - egress replication performance improvement" in the release notes and Feature Navigator.
DFC-equipped modules with dual switch-fabric connections host two packet replication engines, one per fabric connection. Each replication engine is responsible for forwarding packets to and from the interfaces associated with the switch-fabric connections. The interfaces that are associated with a switch-fabric connection are considered to be "local" from the perspective of the packet replication engine.
You can prevent redundant replication of multicast packets across the switch-fabric connection by entering a command that instructs the two replication engines on these modules to forward packets only to local interfaces which are associated with the switch-fabric connection that the replication engine supports.
When you enable this feature, the multicast expansion table (MET) for each replication engine is populated with the local Layer 3 interfaces only. This action prevents replication for interfaces that are not supported by the replication engine (nonlocal interfaces) and increases replication performance.
Local egress replication is supported with the following software configuration and hardware:
•
•
•
The local egress replication feature is not supported for the following internal VLANs:
•
•
•
•
•
Note
To enable local egress replication, perform this task:
This example shows how to enable local egress replication:
Router (config)# mls ip multicast egress localRouter (config)# exitRouter # reloadRouter # show mls ip multicast capability Current mode of replication is Ingress Configured replication mode is Egress Egress Local is EnabledSlot Multicast replication capability Egress Local 2 Egress No 3 Egress Yes 4 Ingress No 5 Egress No 6 Egress NoConfiguring the Layer 3 Switching Global Threshold
You can configure a global multicast rate threshold (specified in packets per second) below which all multicast traffic is routed by the RP. This configuration prevents creation of switching cache entries for low-rate Layer 3 flows.
Note
To configure the Layer 3 switching threshold, perform this task:
Router(config)# mls ip multicast threshold ppsec
Configures the IP MMLS threshold.
Router(config)# no mls ip multicast threshold
Reverts to the default IP MMLS threshold.
This example shows how to configure the Layer 3 switching threshold to 10 packets per second:
Router(config)# mls ip multicast threshold 10Router(config)#Enabling Installation of Directly Connected Subnets
In PIM sparse mode, a first-hop router that is the designated router for the interface may need to encapsulate the source traffic in a PIM register message and unicast it to the rendezvous point. To prevent new sources for the group from being learned in the routing table, the (*,G) flows should remain as completely hardware-switched flows. When (subnet/mask, 224/4) entries are installed in the hardware, the FIB allows both (*,G) flows to remain completely hardware-switched flows, and new, directly connected sources to be learned correctly. The installation of directly connected subnets is enabled globally by default. One (subnet/mask, 224/4) is installed per PIM-enabled interface.
To view FIB entries, enter the show mls ip multicast connected command.
To enable installation of directly connected subnets, perform this task:
This example shows how to enable installation of directly connected subnets:
Router(config)# mls ip multicast connectedRouter(config)#Specifying the Flow Statistics Message Interval
By default, the switch processor (SP) forwards flow statistics messages to the route processor (RP) every 25 seconds. The messages are forwarded in batches, and each batch of messages contains statistics for 25 percent of all flows. If you leave the interval at the default of 25 seconds, it will take 100 seconds to forward statistics for all flows to the RP.
To specify how often flow statistics messages forwarded from the SP to the RP, perform this task:
This example shows how to configure the SP to forward flow statistics messages to the RP every 10 seconds:
Router(config)# mls ip multicast flow-stat-timer 10Router(config)#Enabling Shortcut-Consistency Checking
When you enable the shortcut-consistency checking feature, the multicast route table and the multicast-hardware entries are checked for consistency, and any inconsistencies are corrected. You can view inconsistencies by entering the show mls ip multicast consistency-check command.
If consistency checking is enabled, the multicast route table will be scanned every two seconds and a full scan is completed within 4 minutes.
To enable shortcut-consistency checking, perform this task:
Router(config)# mls ip multicast consistency-check
Enables shortcut-consistency checking.
Router(config)# no mls ip multicast consistency-check num
Restores the default.
This example shows how to enable the hardware shortcut-consistency checker:
Router (config)# mls ip multicast consistency-checkRouter (config)#Configuring ACL-Based Filtering of RPF Failures
When you configure ACL-based filtering of RPF failures, ACLs that filter RPF failures in hardware are downloaded to the hardware-based ACL engine and applied on the interface you specify.
To enable ACL-based filtering of RPF failures on an interface, perform this task:
Step 1
Router(config)# interface {{vlan vlan_ID} | {type1 slot/port} | {port-channel number}}
Selects an interface to configure.
Step 2
Router(config-if)# mls ip multicast stub
Enables ACL-based filtering of RPF failures on an interface.
Router(config-if)# no mls ip multicast stub
Disables ACL-based filtering of RPF failures on an interface.
1 type = fastethernet, gigabitethernet, or tengigabitethernet
Displaying RPF Failure Rate-Limiting Information
To display RPF failure rate-limiting information, perform this task:
Router# show mls ip multicast summary
Displays RPF failure rate-limiting information.
This example shows how to display RPF failure rate-limiting information:
Router# show mls ip multicast summary10004 MMLS entries using 1280464 bytes of memoryNumber of partial hardware-switched flows:4Number of complete hardware-switched flows:10000Router#Configuring Multicast Boundary
To configure a multicast boundary, perform this task:
Step 1
Router(config)# interface {{vlan vlan_ID} | {type1 slot/port} | {port-channel number}}
Selects an interface to configure.
Step 2
Router(config-if)# ip multicast boundary access_list [filter-autorp]
Enables an administratively scoped boundary on an interface.
•
•
Router(config-if)# no ip multicast boundary
Disables the multicast boundary for this interface.
1 type = fastethernet, gigabitethernet, or tengigabitethernet
Note
The following example sets up a multicast boundary for all administratively scoped addresses:
Router (config)# access-list 1 deny 239.0.0.0 0.255.255.255Router (config)# access-list 1 permit 224.0.0.0 15.255.255.255Router (config)# interface gigabitethernet 5/2Router (config-if)# ip multicast boundary 1Displaying IPv4 Multicast Layer 3 Hardware Switching Summary
Note
The show ip pim interface count command displays the IP multicast Layer 3 switching enable state on IP PIM interfaces and the number of packets received and sent on the interface.
To display IP multicast Layer 3 switching information for an IP PIM Layer 3 interface, perform one of these tasks:
Router# show ip pim interface [{{vlan vlan_ID} | {type1 slot/port} | {port-channel number}}] count
Displays IP multicast Layer 3 switching enable state information for all RP IP PIM Layer 3 interfaces.
Router# show ip interface
Displays the IP multicast Layer 3 switching enable state on the Layer 3 interfaces.
1 type = fastethernet, gigabitethernet, or tengigabitethernet
These examples show how to display the IP PIM configuration of the interfaces:
Router# show ip pim interface countState:* - Fast Switched, D - Distributed Fast SwitchedH - Hardware Switching EnabledAddress Interface FS Mpackets In/Out10.15.1.20 GigabitEthernet4/8 * H 952/423713077010.20.1.7 GigabitEthernet4/9 * H 1385673757/3410.25.1.7 GigabitEthernet4/10* H 0/3410.11.1.30 FastEthernet6/26 * H 0/010.37.1.1 FastEthernet6/37 * H 0/01.22.33.44 FastEthernet6/47 * H 514/68The "*" flag indicates that this interface can be fast switched and the "H" flag indicates that this interface is hardware switched. The "In" flag indicates the number of multicast packet bytes that have been received on the interface. The "Out" flag indicates the number of multicast packet bytes that have been forwarded from this interface.
Router# show ip mroute countIP Multicast Statistics56 routes using 28552 bytes of memory13 groups, 3.30 average sources per groupForwarding Counts:Pkt Count/Pkts per second/Avg Pkt Size/Kilobits per secondOther counts:Total/RPF failed/Other drops(OIF-null, rate-limit etc)Group:224.2.136.89, Source count:1, Group pkt count:29051Source:132.206.72.28/32, Forwarding:29051/-278/1186/0, Other:85724/8/56665Router#
Note
This example shows how to display the IP multicast Layer 3 switching configuration of interface VLAN 10:
Router# show ip interface vlan 10Vlan10 is up, line protocol is upInternet address is 10.0.0.6/8Broadcast address is 255.255.255.255Address determined by non-volatile memoryMTU is 1500 bytesHelper address is not setDirected broadcast forwarding is disabledMulticast reserved groups joined: 224.0.0.1 224.0.0.2 224.0.0.13 224.0.0.10Outgoing access list is not setInbound access list is not setProxy ARP is enabledSecurity level is defaultSplit horizon is enabledICMP redirects are always sentICMP unreachables are never sentICMP mask replies are never sentIP fast switching is enabledIP fast switching on the same interface is disabledIP Flow switching is disabledIP CEF switching is enabledIP Fast switching turbo vectorIP Normal CEF switching turbo vectorIP multicast fast switching is enabledIP multicast distributed fast switching is disabledIP route-cache flags are Fast, CEFRouter Discovery is disabledIP output packet accounting is disabledIP access violation accounting is disabledTCP/IP header compression is disabledRTP/IP header compression is disabledProbe proxy name replies are disabledPolicy routing is disabledNetwork address translation is disabledWCCP Redirect outbound is disabledWCCP Redirect exclude is disabledBGP Policy Mapping is disabledIP multicast multilayer switching is enabledIP mls switching is enabledRouter#This example shows how to display the IP multicast Layer 3 switching configuration of Gigabit Ethernet interface 1/2:
Router# show interfaces gigabitEthernet 1/2GigabitEthernet1/2 is up, line protocol is up (connected)Hardware is C6k 1000Mb 802.3, address is 0001.c9db.2441 (bia 0001.c9db.2441)MTU 1500 bytes, BW 1000000 Kbit, DLY 10 usec,Last clearing of "show interface" counters 00:05:13....Input queue: 0/2000/0/0 (size/max/drops/flushes); Total output drops: 0Queueing strategy: fifoOutput queue :0/40 (size/max)5 minute input rate 10000 bits/sec, 1 packets/sec5 minute output rate 0 bits/sec, 0 packets/sec284 packets input, 113104 bytes, 0 no bufferReceived 284 broadcasts (284 multicast)0 runts, 41 giants, 0 throttles41 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored0 input packets with dribble condition detected198 packets output, 14732 bytes, 0 underruns0 output errors, 0 collisions, 0 interface resets0 babbles, 0 late collision, 0 deferred0 lost carrier, 0 no carrier0 output buffer failures, 0 output buffers swapped outRouter#Displaying the IPv4 Multicast Routing Table
The show ip mroute command displays the IP multicast routing table.
To display the IP multicast routing table, perform this task:
Router# show ip mroute partical-sc [hostname | group_number]
Displays the IP multicast routing table and the hardware-switched interfaces.
This example shows how to display the IP multicast routing table:
Router# show ip mroute 230.13.13.1IP Multicast Routing TableFlags:D - Dense, S - Sparse, s - SSM Group, C - Connected, L - Local,P - Pruned, R - RP-bit set, F - Register flag, T - SPT-bit set,J - Join SPT, M - MSDP created entry, X - Proxy Join Timer RunningA - Advertised via MSDP, U - URD, I - Received Source Specific HostReportOutgoing interface flags:H - Hardware switchedTimers:Uptime/ExpiresInterface state:Interface, Next-Hop or VCD, State/Mode(*, 230.13.13.1), 00:16:41/00:00:00, RP 10.15.1.20, flags:SJCIncoming interface:GigabitEthernet4/8, RPF nbr 10.15.1.20Outgoing interface list:GigabitEthernet4/9, Forward/Sparse-Dense, 00:16:41/00:00:00, H(*, 230.13.13.2), 00:16:41/00:00:00, RP 10.15.1.20, flags:SJCIncoming interface:GigabitEthernet4/8, RPF nbr 10.15.1.20, RPF-MFDOutgoing interface list:GigabitEthernet4/9, Forward/Sparse-Dense, 00:16:41/00:00:00, H(10.20.1.15, 230.13.13.1), 00:14:31/00:01:40, flags:CJTIncoming interface:GigabitEthernet4/8, RPF nbr 10.15.1.20, RPF-MFDOutgoing interface list:GigabitEthernet4/9, Forward/Sparse-Dense, 00:14:31/00:00:00, H(132.206.72.28, 224.2.136.89), 00:14:31/00:01:40, flags:CJTIncoming interface:GigabitEthernet4/8, RPF nbr 10.15.1.20, RPF-MFDOutgoing interface list:NullRouter#
Note
Displaying IPv4 Multicast Layer 3 Switching Statistics
The show mls ip multicast command displays detailed information about IP multicast Layer 3 switching.
To display detailed IP multicast Layer 3 switching information, perform one of these tasks:
Router# show mls ip multicast group ip_address [interface type slot/port | statistics]
Displays IP multicast Layer 3 switching group information.
Router# show mls ip multicast interface {{vlan vlan_ID} | {type1 slot/port} | {port-channel number}} [statistics | summary]
Displays IP multicast Layer 3 switching details for all interfaces.
Router# show mls ip multicast source ip_address [interface {{vlan vlan_ID} | {type1 slot/port} | {port-channel number}} | statistics]
Displays IP multicast Layer 3 switching source information.
Router# show mls ip multicast summary
Displays a summary of IP multicast Layer 3 switching information.
Router# show mls ip multicast statistics
Displays IP multicast Layer 3 switching statistics.
1 type = fastethernet, gigabitethernet, or tengigabitethernet
This example shows how to display information on a specific IP multicast Layer 3 switching entry:
Router# show mls ip multicast group 10.1.0.11Multicast hardware switched flows:Total shortcut installed: 0This example shows how to display IP multicast group information:
Router# show mls ip multicast group 230.13.13.1 source 10.20.1.15Multicast hardware switched flows:(10.20.1.15, 230.13.13.1) Incoming interface:Gi4/8, Packets switched:0Hardware switched outgoing interfaces:Gi4/9RPF-MFD installedTotal hardware switched flows :1Router#This example shows how to display IP multicast Layer 3 switching information for VLAN 10:
Router# show mls ip multicast interface vlan 10Multicast hardware switched flows:(10.1.0.15, 224.2.2.15) Incoming interface: Vlan10, Packets switched: 0Hardware switched outgoing interfaces:MFD installed: Vlan10(10.1.0.19, 224.2.2.19) Incoming interface: Vlan10, Packets switched: 1970Hardware switched outgoing interfaces:MFD installed: Vlan10(10.1.0.11, 224.2.2.11) Incoming interface: Vlan10, Packets switched: 0Hardware switched outgoing interfaces:MFD installed: Vlan10(10.1.0.10, 224.2.2.10) Incoming interface: Vlan10, Packets switched: 2744Hardware switched outgoing interfaces:MFD installed: Vlan10(10.1.0.17, 224.2.2.17) Incoming interface: Vlan10, Packets switched: 3340Hardware switched outgoing interfaces:MFD installed: Vlan10(10.1.0.13, 224.2.2.13) Incoming interface: Vlan10, Packets switched: 0Hardware switched outgoing interfaces:This example shows how to display the IP multicast Layer 3 switching statistics:
Router# show mls ip multicast statisticsMLS Multicast Operation Status:MLS Multicast configuration and state:Router Mac: 00e0.b0ff.7b00, Router IP: 33.0.33.24MLS multicast operating state: ACTIVEShortcut Request Queue size 4Maximum number of allowed outstanding messages: 1Maximum size reached from feQ: 3096Feature Notification sent: 1Feature Notification Ack received: 1Unsolicited Feature Notification received: 0MSM sent: 205170MSM ACK received: 205170Delete notifications received: 0Flow Statistics messages received: 35211MLS Multicast statistics:Flow install Ack: 996508Flow install Nack: 1Flow update Ack: 1415959Flow update Nack: 0Flow delete Ack: 774953Complete flow install Ack: 958469Router#Configuring IPv4 Bidirectional PIM
These sections describe how to configure IPv4 bidirectional protocol independent multicast (PIM):
•
•
•
•
Enabling IPv4 Bidirectional PIM Globally
To enable IPv4 bidirectional PIM, perform this task:
This example shows how to enable IPv4 bidirectional PIM on the switch:
Router(config)# ip pim bidir-enableRouter(config)#Configuring the Rendezvous Point for IPv4 Bidirectional PIM Groups
To statically configure the rendezvous point for an IPv4 bidirectional PIM group, perform this task:
This example shows how to configure a static rendezvous point for an IPv4 bidirectional PIM group:
Router(config)# ip pim rp-address 10.0.0.1 10 bidir overrideRouter(config)# access-list 10 permit 224.1.0.0 0.0.255.255Router(config)# ip pim send-rp-announce Loopback0 scope 16 group-list c21-rp-list-0 bidirRouter(config)# ip access-list standard c21-rp-list-0 permit 230.31.31.1 0.0.255.255Setting the IPv4 Bidirectional PIM Scan Interval
You can specify the interval between the IPv4 bidirectional PIM RP Reverse Path Forwarding (RPF) scans.
To set the IPv4 bidirectional PIM RP RPF scan interval, perform this task:
This example shows how to set the IPv4 bidirectional PIM RP RPF scan interval:
Router(config)# mls ip multicast bidir gm-scan-interval 30Router(config)#Displaying IPv4 Bidirectional PIM Information
To display IPv4 bidirectional PIM information, perform one of these tasks:
This example shows how to display information about the PIM group and rendezvous point mappings:
Router# show ip pim rp mappingPIM Group-to-RP MappingsThis system is an RP (Auto-RP)This system is an RP-mapping agentGroup(s) 230.31.0.0/16RP 60.0.0.60 (?), v2v1, bidirInfo source:60.0.0.60 (?), elected via Auto-RPUptime:00:03:47, expires:00:02:11RP 50.0.0.50 (?), v2v1, bidirInfo source:50.0.0.50 (?), via Auto-RPUptime:00:03:04, expires:00:02:55RP 40.0.0.40 (?), v2v1, bidirInfo source:40.0.0.40 (?), via Auto-RPUptime:00:04:19, expires:00:02:38This example shows how to display information in the IP multicast routing table that is related to IPv4 bidirectional PIM:
Router# show ip mroute bidirectional(*, 225.1.3.0), 00:00:02/00:02:57, RP 3.3.3.3, flags:BCBidir-Upstream:GigabitEthernet2/1, RPF nbr 10.53.1.7, RPF-MFDOutgoing interface list:GigabitEthernet2/1, Bidir-Upstream/Sparse-Dense, 00:00:02/00:00:00,HVlan30, Forward/Sparse-Dense, 00:00:02/00:02:57, H(*, 225.1.2.0), 00:00:04/00:02:55, RP 3.3.3.3, flags:BCBidir-Upstream:GigabitEthernet2/1, RPF nbr 10.53.1.7, RPF-MFDOutgoing interface list:GigabitEthernet2/1, Bidir-Upstream/Sparse-Dense, 00:00:04/00:00:00,HVlan30, Forward/Sparse-Dense, 00:00:04/00:02:55, H(*, 225.1.4.1), 00:00:00/00:02:59, RP 3.3.3.3, flags:BCBidir-Upstream:GigabitEthernet2/1, RPF nbr 10.53.1.7, RPF-MFDOutgoing interface list:GigabitEthernet2/1, Bidir-Upstream/Sparse-Dense, 00:00:00/00:00:00,HVlan30, Forward/Sparse-Dense, 00:00:00/00:02:59, HThis example show how to display information related to a specific multicast route. In the output below, the arrow in the margin points to information about a partical short cut:
Router# show ip mroute 239.1.1.2 4.4.4.4IP Multicast Routing TableFlags:D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected,L - Local, P - Pruned, R - RP-bit set, F - Register flag,T - SPT-bit set, J - Join SPT, M - MSDP created entry,X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,U - URD, I - Received Source Specific Host Report, Z - Multicast TunnelY - Joined MDT-data group, y - Sending to MDT-data groupOutgoing interface flags:H - Hardware switchedTimers:Uptime/ExpiresInterface state:Interface, Next-Hop or VCD, State/Mode(4.4.4.4, 239.1.1.2), 1d02h/00:03:20, flags:FTZIncoming interface:Loopback0, RPF nbr 0.0.0.0, Partial-SCOutgoing interface list:Vlan10, Forward/Sparse-Dense, 1d02h/00:02:39 (ttl-threshold 5)This example shows how to display the entries for a specific multicast group address:
Router# show mls ip multicast group 230.31.31.1Multicast hardware switched flows:(*, 230.31.31.1) Incoming interface:Vlan611, Packets switched:1778Hardware switched outgoing interfaces:Vlan131 Vlan151 Vlan415 Gi4/16 Vlan611RPF-MFD installedThis example shows how to display PIM group to active rendezvous points mappings:
Router# show mls ip multicast rp-mappingState:H - Hardware Switched, I - Install Pending, D - Delete Pending, Z - ZombieRP Address State RPF DF-count GM-count60.0.0.60 H Vl611 4 1This example shows how to display information based on the group/mask ranges in the RP mapping cache:
Router# show mls ip multicast rp-mapping gm-cacheState:H - Hardware Switched, I - Install Pending, D - Delete Pending,Z - ZombieRP Address State Group Mask State Packet/Byte-count60.0.0.60 H 230.31.0.0 255.255.0.0 H 100/6400This example shows how to display information about specific MLS IP multicasting groups:
Router# show mls ip multicast rp-mapping df-cacheState:H - Hardware Switched, I - Install Pending, D - Delete Pending, Z - ZombieRP Address State DF State60.0.0.60 H Vl131 H60.0.0.60 H Vl151 H60.0.0.60 H Vl415 H60.0.0.60 H Gi4/16 HUsing IPv4 Debug Commands
Table 31-2 describes IPv4 multicast Layer 3 switching debug commands that you can use to troubleshoot IP multicast Layer 3 switching problems.
Table 31-2 IP Multicast Layer 3 Switching Debug Commands
[no] debug mls ip multicast events
Displays IP multicast Layer 3 switching events.
[no] debug mls ip multicast errors
Turns on debug messages for multicast MLS-related errors.
[no] debug mls ip multicast group group_id group_mask
Turns on debugging for a subset of flows.
[no] debug mls ip multicast messages
Displays IP multicast Layer 3 switching messages from and to hardware switching engine.
[no] debug mls ip multicast all
Turns on all IP multicast Layer 3 switching messages.
[no] debug mdss errors
Turns on MDSS1 error messages.
[no] debug mdss events
Displays MDSS-related events for debugging.
[no] debug mdss events mroute-bidir
Displays IPv4 bidirectional PIM MDSS events for debugging.
[no] debug mdss all
Displays all MDSS messages.
[no] debug ip pim df ip_address
Displays the DF election for a given rendezvous point for debug purposes.
1 MDSS = Multicast Distributed Switching Services
Clearing IPv4 Multicast Layer 3 Switching Statistics
To clear IP multicast Layer 3 switching statistics, perform this task:
Router# clear mls ip multicast statistics
Clears IP multicast Layer 3 switching statistics.
This example shows how to clear IP multicast Layer 3 switching statistics:
Router# clear mls ip multicast statisticsThe show mls multicast statistics command displays a variety of information about the multicast flows being handled by the PFC. You can display entries based on any combination of the participating RP, the VLAN, the multicast group address, or the multicast traffic source. For an example of the show mls ip multicast statistics command, see the "Displaying IPv4 Multicast Layer 3 Switching Statistics" section.
