Enabling MT for an IS-IS Process
Based on service requirements and the network plan, an IS-IS process can be associated with various topology instances so that multiple logical topologies are deployed in an IS-IS AS.
Context
You can associate an IS-IS process with IPv4 or IPv6 topology instances as required so that the SPF calculation can be performed for the topology instances in the IS-IS process. Then, configure parameters, you can such as the interface cost and protocol priority for the topology instances.
The configuration in an IS-IS topology instance view takes effect only on the topology instance. Therefore, you can configure different features and parameters for different topology instances as required.
Procedure
- Run system-view
The system view is displayed.
- Run ip topology topology-name
An IPv4 topology is created.
- Run ipv6 topology topology-name
An IPv6 topology is created.
- Run isis [ process-id ]
The IS-IS view is displayed.
- Run cost-style { wide | wide-compatible }
The cost style of packets sent and received by the router is set to wide or wide-compatible.
Go to Step 6 or Step 7 as required.- If the router supports only IPv4 services, go to Step 6.
- If the router supports only IPv6 services, go to Step 7.
- If the router supports both IPv4 and IPv6 services, perform the following steps.
- Run topology topology-name [ topology-id { multicast | topology-id } ]
The IS-IS process is associated with a specified IPv4 topology instance, and the IS-IS IPv4 topology view is displayed.
- Run ipv6 topology topology-name [ topology-id { multicast | topology-id } ]
The IS-IS process is associated with a specified IPv6 topology instance, and the IPv6 topology view is displayed.
- (Optional) Configure IS-IS features for topology instances using the following commands:
To set the priority of IS-IS, run the preference command.
To enable an IS-IS device to generate a default route, run the default-route-advertise command.
To enable an IS-IS device to import routes from other routing protocols in the IS-IS view, run the import-route command.
To control IS-IS route leaking from a Level-1 area to a Level-2 area, run the import-route isis level-1 into level-2 command.
To control IS-IS route leaking from a Level-2 area to a Level-1 area, run the import-route isis level-2 into level-1 command.
- Run commit
The configuration is committed.