To reduce the interface count and configuration workload required by multiple conventional IS-IS processes, you can configure IS-IS multi-instance processes. A conventional IS-IS process and multiple IS-IS multi-instance processes can be configured on the same interface.
On IS-IS networks, multiple IS-IS processes need to be used to isolate different access rings. To close the access rings, the IS-IS processes on all access rings need to be enabled. In this case, you need to enable different IGP processes on one interface. This reduces the interface count and configuration workload of the access rings.
The system view is displayed.
An IS-IS process is created, and its view is displayed.
process-id specifies the ID of an IS-IS process. If process-id is not specified, 1 is used as the IS-IS process ID. To associate an IS-IS process with a VPN instance, run the isis process-id vpn-instance vpn-instance-name command.
The IS-IS process is configured as an IS-IS multi-instance process.
Return to the system view.
The interface view is displayed.
The configuration is committed.
For details on how to configure other functions for an IS-IS process, see Creating an IPv4 IS-IS process or Creating an IPv6 IS-IS process.
After configuring an IS-IS multi-instance process, check the configurations.
Run the display isis interface interface-type interface-number [ verbose ] command to check information about the IS-IS interface. The command output shows more than one IS-IS process on the interface.