Multitopology Routing Configuration Guide, Cisco IOS Release 15SY
IS-IS MTR for the Multicast Address Family
IS-IS MTR for the Multicast Address Family
Last Updated: October 15, 2012
The IS-IS MTR for the Multicast Address Family feature provides Intermediate System-to-Intermediate System (IS-IS) support for multiple logical topologies over a single physical network. This module describes how to configure IS-IS for Multitopology Routing (MTR) for both unicast and multicast topologies.
Finding Feature Information
Your software release may not support all the features documented in this module. For the latest caveats and feature information, see Bug Search Tool and 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 module.
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.
Prerequisites for IS-IS MTR for the Multicast Address Family
Restrictions for IS-IS MTR for the Multicast Address Family
Information About IS-IS MTR for the Multicast Address Family
Routing Protocol Support for MTR
You must enable IP routing on the device for Multitopology Routing (MTR) to operate. MTR supports static and dynamic routing in Cisco software. You can enable dynamic routing per topology to support interdomain and intradomain routing. Route calculation and forwarding are independent for each topology. MTR support is integrated into Cisco software for the following protocols:
You apply the per-topology configuration in router address family configuration mode of the global routing process (router configuration mode). The address family and subaddress family are specified when the device enters address family configuration mode. You specify the topology name and topology ID by entering the topology command in address family configuration mode.
You configure each topology with a unique topology ID under the routing protocol. The topology ID is used to identify and group Network Layer Reachability Information (NLRI) for each topology in updates for a given protocol. In OSPF, EIGRP, and IS-IS, you enter the topology ID during the first configuration of the topology command for a class-specific topology. In BGP, you configure the topology ID by entering the bgp tid command under the topology configuration.
You can configure class-specific topologies with different metrics than the base topology. Interface metrics configured on the base topology can be inherited by the class-specific topology. Inheritance occurs if no explicit inheritance metric is configured in the class-specific topology.
You configure BGP support only in router configuration mode. You configure Interior Gateway Protocol (IGP) support in router configuration mode and in interface configuration mode.
By default, interfaces are not included in nonbase topologies. For routing protocol support for EIGRP, IS-IS, and OSPF, you must explicitly configure a nonbase topology on an interface. You can override the default behavior by using the all-interfaces command in address family topology configuration mode. The all-interfaces command causes the nonbase topology to be configured on all interfaces of the device that are part of the default address space or the virtual routing and forwarding (VRF) instance in which the topology is configured.
Interface Configuration Support for MTR
The configuration of a Multitopology Routing (MTR) topology in interface configuration mode allows you to enable or disable MTR on a per-interface basis. By default, a class-specific topology does not include any interfaces.
You can include or exclude individual interfaces by configuring the topology interface configuration command. You specify the address family and the topology (base or class-specific) when entering this command. The subaddress family can be specified. If no subaddress family is specified, the unicast subaddress family is used by default.
You can include globally all interfaces on a device in a topology by entering the all-interfaces command in routing topology configuration mode. Per-interface topology configuration applied with the topology command overrides global interface configuration.
The interface configuration support for MTR has these characteristics:
How to Configure IS-IS MTR for the Multicast Address Family
Activating an MTR Topology by Using IS-IS
Activating an MTR Topology in Interface Configuration Mode by Using IS-IS
Before You BeginSUMMARY STEPS
Define a topology globally before performing the per-interface topology configuration.
Monitoring Interface and Topology IP Traffic Statistics for MTR
Use any of the following commands in any order to monitor interface and topology IP traffic statistics for Multitopology Routing (MTR).
Configuration Examples for IS-IS MTR for the Multicast Address Family
Example: Activating an MTR Topology by Using IS-IS
The following example shows how to configure both the Multitopology Routing (MTR) topologies DATA and VIDEO and Intermediate System-to-Intermediate System (IS-IS) support for MTR. The DATA and VIDEO topologies are enabled on three IS-IS neighbors in a network.
global-address-family ipv4 topology DATA topology VOICE end interface Ethernet 0/0 ip address 192.168.128.2 255.255.255.0 ip router isis topology ipv4 DATA isis topology disable topology ipv4 VOICE end router isis net 33.3333.3333.3333.00 metric-style wide address-family ipv4 topology DATA tid 100 topology VOICE tid 200 end
global-address-family ipv4 topology DATA topology VOICE all-interfaces forward-base maximum routes 1000 warning-only shutdown end interface Ethernet 0/0 ip address 192.168.128.1 255.255.255.0 ip router isis topology ipv4 DATA isis topology disable topology ipv4 VOICE end interface Ethernet 1/0 ip address 192.168.130.1 255.255.255.0 ip router isis topology ipv4 DATA isis topology disable topology ipv4 VOICE end router isis net 32.3232.3232.3232.00 metric-style wide address-family ipv4 topology DATA tid 100 topology VOICE tid 200 end
global-address-family ipv4 topology DATA topology VOICE all-interfaces forward-base maximum routes 1000 warning-only shutdown end interface Ethernet 1/0 ip address 192.168.131.1 255.255.255.0 ip router isis topology ipv4 DATA isis topology disable topology ipv4 VOICE end router isis net 31.3131.3131.3131.00 metric-style wide address-family ipv4 topology DATA tid 100 topology VOICE tid 200 end
Entering the show isis neighbors detail command verifies topology translation with the IS-IS neighbor Device 1:
Device# show isis neighbors detail System Id Type Interface IP Address State Holdtime Circuit Id R1 L2 Et0/0 192.168.128.2 UP 28 R5.01 Area Address(es): 33 SNPA: aabb.cc00.1f00 State Changed: 00:07:05 LAN Priority: 64 Format: Phase V Remote TID: 100, 200 Local TID: 100, 200
Example: MTR IS-IS Topology in Interface Configuration Mode
The following example shows how to prevent the Intermediate System-to-Intermediate System (IS-IS) process from advertising interface Ethernet 1/0 as part of the DATA topology:
interface Ethernet 1/0 ip address 192.168.130.1 255.255.255.0 ip router isis topology ipv4 DATA isis topology disable topology ipv4 VOICE end
Standards and RFCs
Feature Information for IS-IS MTR for the Multicast Address Family
The 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.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: 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. (1110R)
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.
© 2012 Cisco Systems, Inc. All rights reserved.