MTR Support for Multicast
|
|||||||||||||||
Contents
MTR Support for MulticastLast Updated: July 23, 2010
The MTR Support for Multicast feature provides Multitopology Routing (MTR) support for multicast and allows you to control the path of multicast traffic in the network. This module describes how to configure MTR support for multicast. Finding Feature InformationYour software release may not support all the features documented in this module. For the latest feature information and caveats, see the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the Feature Information Table at the end of this document. Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required. Information About MTR Support for MulticastMulticast Topology Support for MTRCisco IOS software supports legacy (pre-MTR) IP multicast behavior by default. MTR support for IP multicast must be explicitly enabled. Legacy IP multicast uses reverse path forwarding on routes in the unicast RIB (base unicast topology) to build multicast distribution trees (MDTs). MTR introduces a multicast topology that is completely independent from the unicast topology. MTR integration with multicast allows the user to control the path of multicast traffic in the network. The multicast topology maintains separate routing and forwarding tables. The following list summarizes MTR multicast support that is integrated into Cisco IOS software:
As in pre-MTR software, you enable multicast support by configuring the ip multicast-routing command in global configuration mode. You enable MTR support for multicast by configuring the ip multicast rpf multitopology command. The global-address-family command is entered with the IPv4 address family and multicast subaddress family. You then enter thetopology command with the base keyword, and global topology configuration parameters are applied in this mode. For detailed steps, see the Configuring a Multicast Topology for MTR section. How to Configure MTR Support for MulticastConfiguring a Multicast Topology for MTR
DETAILED STEPS Configuration Examples for MTR Support for MulticastExample Route Replication ConfigurationThe following example shows how to enable multicast support for MTR and to configure a separate multicast topology: ip multicast-routing ip multicast rpf multitopology ! global-address-family ipv4 multicast topology base end The following example shows how to configure the multicast topology to replicate OSPF routes from the VOICE topology. The routes are filtered through the BLUE route map before they are installed in the multicast routing table. ip multicast-routing ip multicast rpf multitopology ! access-list 1 permit 192.168.1.0 0.0.0.255 ! route-map BLUE match ip address 1 exit ! global-address-family ipv4 multicast topology base route-replicate from unicast topology VOICE ospf route-map BLUE Example Using a Unicast RIB for Multicast RPF ConfigurationThe following example shows how to configure the multicast topology to perform RPF calculations on routes in the VIDEO topology RIB to build multicast distribution trees: ip multicast-routing ip multicast rpf multitopology ! global-address-family ipv4 multicast topology base use-topology unicast VIDEO end Example Multicast VerificationThe following example shows that the multicast topology is configured to replicate routes from the RIB of the VOICE topology:
Router# show topology detail
Topology: base
Address-family: ipv4
Associated VPN VRF is default
Topology state is UP
Associated interfaces:
Ethernet0/0, operation state: UP
Ethernet0/1, operation state: DOWN
Ethernet0/2, operation state: DOWN
Ethernet0/3, operation state: DOWN
Loopback0, operation state: UP
Topology: VIDEO
Address-family: ipv4
Associated VPN VRF is default
Topology state is UP
Topology fallback is enabled
Topology maximum route limit 1000, warning limit 90% (900)
Associated interfaces:
Topology: VOICE
Address-family: ipv4
Associated VPN VRF is default
Topology state is UP
Topology is enabled on all interfaces
Associated interfaces:
Ethernet0/0, operation state: UP
Ethernet0/1, operation state: DOWN
Ethernet0/2, operation state: DOWN
Ethernet0/3, operation state: DOWN
Loopback0, operation state: UP
Topology: base
Address-family: ipv4 multicast
Associated VPN VRF is default
Topology state is DOWN
Multicast multi-topology mode is enabled.
Route Replication Enabled:
from unicast topology VOICE all route-map BLUE
Associated interfaces:
Additional ReferencesRelated DocumentsTechnical Assistance
Feature Information for MTR Support for MulticastThe following table provides release information about the feature or features described in this module. This table lists only the software release that introduced support for a given feature in a given software release train. Unless noted otherwise, subsequent releases of that software release train also support that feature. Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.
Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at www.cisco.com/go/trademarks. Third party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1005R) Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental. © 2007-2012 Cisco Systems, Inc. All rights reserved.
|
|||||||||||||||