Enabling MT for an IPv6 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

  1. Run system-view

    The system view is displayed.

  2. Run ipv6 topology topology-name

    An IPv6 topology instance is configured.

  3. Run isis [ process-id ]

    The IS-IS view is displayed.

  4. 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.

  5. Run ipv6 topology topology-name topology-id topology-id

    The IS-IS process is associated with a specified unicast topology instance, and the IS-IS IPv6 unicast topology view is displayed.

  6. Run ipv6 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.

  7. (Optional) Configure IS-IS features for IPv6 topology instances using the following commands:

  8. Run commit

    The configuration is committed.

Copyright © Huawei Technologies Co., Ltd.
Copyright © Huawei Technologies Co., Ltd.
Next topic >