Feature configuration

The user first configures a locator for use in IS-IS IPv6 unicast multi-topology. Use the following CLI syntax to configure a locator for use in IS-IS IPv6 unicast multi-topology:

classic CLI

configure
+--router
   +--isis <isis-instance>
      +--segment-routing-v6
        +---no adj-sid-hold    
        |   adj-sid-hold <seconds>
        +---locator <name>
        |   no locator <name>
        |   +---level {1|2}    
        |   |   +---metric <metric>
        |   |   |   no metric
        |   +---level-capability {level-1|level-2|level-1/2}
        |   |   no level-capability
        |   +---multi-topology [mt0] [mt2]
        |   |   no multi-topology    
        |   +---no tag
        |   |   tag <tag>
        +---shutdown
        |   no shutdown

MD-CLI

configure
+--router
   +--isis <isis-instance>
      +--segment-routing-v6
         +-- adj-sid-hold <seconds>
         +--admin-state (enable|disable)
         +--locator <locator-name> 
            +--level-capability <level-1|level-2|level-1/2>
            +--level <1|2>
               +--metric <metric>
            +--tag <tag>
        +---multi-topology [mt0] [mt2]

The user can enable one or more SRv6 local locators in a specific IS-IS instance. Each locator can be enabled in a single topology of an IS-IS instance, topology 0 (MT0) or topology 2 (MT2). By default, a locator name added to an IS-IS instance is enabled in MT0. A local locator can be used in multiple IS-IS instances and can be assigned to at most one IPv6 topology independently within each IS-IS instance.

Note: To enable processing of local and remote IPv6 prefixes and SRv6 locators in MT0 and MT2, use the admin-state enable MD-CLI command in the configure router isis segment-routing-v6 context. The user must also enable IPv6 routing in MT0 (using the isis ipv6-routing native command), in MT2 (using the isis multi-topology ipv6-unicast command), or in both to enable SRv6 forwarding in the MT0, MT2, or both topologies.