Enabling IPv4 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 unicast or multicast topology instances as required so that the SPF calculation can be performed for the topology instances in the IS-IS process. Then, you can configure parameters, 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 instance is configured.
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 5 or Step 6 as required.
- If the router supports only unicast services, go to Step 5.
- If the router supports only multicast services, go to Step 6.
- If the router supports both unicast and multicast services, perform the following steps.
Run topology topology-name topology-id mt-id
The IS-IS process is associated with a specified unicast topology instance, and the IS-IS unicast topology instance view is displayed.
Run topology topology-name topology-id multicast
The IS-IS process is associated with a specified multicast topology instance, and the IS-IS multicast topology instance view is displayed.
(Optional) Configure IS-IS parameters for IPv4 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.
- To enable IS-IS summarization, run the summary command.
- To configure a link cost for all interfaces of a specified IS-IS process, run the circuit-cost { cost | maximum } [ level-1 | level-2 ] command.
- To enable IS-IS to automatically calculate the interface cost according to the interface bandwidth, run the auto-cost enable [ compatible ] command.
- To set a bandwidth reference value used for automatic interface cost calculation, run the bandwidth-reference value command.
- To set the maximum number of equal-cost routes for load balancing, run the maximum load-balancing number command.
Run commit
The configuration is committed.