
Figure 62. ISO Address Format
Multi-Topology IS-IS
Multi-topology IS-IS (MT IS-IS) allows you to create multiple IS-IS topologies on a single router with separate databases. Use this
feature to place a virtual physical topology into logical routing domains, which can each support different routing and security
policies.
All routers on a LAN or point-to-point must have at least one common supported topology when operating in Multi-Topology IS-IS
mode. If IPv4 is the common supported topology between those two routers, adjacency can be formed. All topologies must share
the same set of L1-L2 boundaries.
You must implement a wide metric-style globally on the autonomous system (AS) to run multi-topology IS-IS for IPv6 because the
Type, Length, Value (TLVs) used to advertise IPv6 information in link-state packets (LSPs) are defined to use only extended metrics.
The multi-topology ID is shown in the first octet of the IS-IS packet. Certain MT topologies are assigned to serve predetermined
purposes:
•
MT ID #0: Equivalent to the “standard” topology.
•
MT ID #1: Reserved for IPv4 in-band management purposes.
•
MT ID #2: Reserved for IPv6 routing topology.
•
MT ID #3: Reserved for IPv4 multicast routing topology.
•
MT ID #4: Reserved for IPv6 multicast routing topology.
•
MT ID #5: Reserved for IPv6 in-band management purposes.
Transition Mode
All routers in the area or domain must use the same type of IPv6 support, either single-topology or multi-topology. A router operating
in multi-topology mode does not recognize the ability of the single-topology mode router to support IPv6 traffic, which leads to holes
in the IPv6 topology.
While in Transition mode, both types of TLVs (single-topology and multi-topology) are sent in LSPs for all configured IPv6 addresses,
but the router continues to operate in single-topology mode (that is, the topological restrictions of the single-topology mode remain
in effect). Transition mode stops after all routers in the area or domain have been upgraded to support multi-topology IPv6. After all
routers in the area or domain are operating in multi-topology IPv6 mode, the topological restrictions of single-topology mode are no
longer in effect.
Interface Support
MT IS-IS is supported on physical Ethernet interfaces, physical synchronous optical network technologies (SONET) interfaces, port-
channel interfaces (static and dynamic using LACP), and virtual local area network (VLAN) interfaces.
Adjacencies
Adjacencies on point-to-point interfaces are formed as usual, where IS-IS routers do not implement MT extensions.
If a local router does not participate in certain MTs, it does not advertise those MT IDs in its IS-IS hellos (IIHs) and so does not
include that neighbor within its LSPs. If an MT ID is not detected in the remote side’s IIHs, the local router does not include that
Intermediate System to Intermediate System
447
Содержание S4048-ON
Страница 1: ...Dell Configuration Guide for the S4048 ON System 9 9 0 0 ...
Страница 146: ...Figure 14 BFD Three Way Handshake State Changes 146 Bidirectional Forwarding Detection BFD ...
Страница 477: ...Figure 68 Inspecting Configuration of LAG 10 on ALPHA Link Aggregation Control Protocol LACP 477 ...
Страница 480: ...Figure 70 Inspecting a LAG Port on BRAVO Using the show interface Command 480 Link Aggregation Control Protocol LACP ...
Страница 481: ...Figure 71 Inspecting LAG 10 Using the show interfaces port channel Command Link Aggregation Control Protocol LACP 481 ...
Страница 522: ...Figure 87 Configuring Interfaces for MSDP 522 Multicast Source Discovery Protocol MSDP ...
Страница 523: ...Figure 88 Configuring OSPF and BGP for MSDP Multicast Source Discovery Protocol MSDP 523 ...
Страница 524: ...Figure 89 Configuring PIM in Multiple Routing Domains 524 Multicast Source Discovery Protocol MSDP ...
Страница 528: ...Figure 91 MSDP Default Peer Scenario 1 528 Multicast Source Discovery Protocol MSDP ...
Страница 529: ...Figure 92 MSDP Default Peer Scenario 2 Multicast Source Discovery Protocol MSDP 529 ...
Страница 530: ...Figure 93 MSDP Default Peer Scenario 3 530 Multicast Source Discovery Protocol MSDP ...
Страница 633: ...Policy based Routing PBR 633 ...
Страница 777: ...Figure 119 Single and Double Tag TPID Match Service Provider Bridging 777 ...
Страница 778: ...Figure 120 Single and Double Tag First byte TPID Match 778 Service Provider Bridging ...