The isis command starts an IS-IS process and a specified VPN instance, and displays the IS-IS view.
The undo isis command deletes a specified IS-IS process.
By default, no IS-IS instance exists on the network.| Parameter | Description | Value |
|---|---|---|
| process-id | Specifies an IS-IS process ID. | The value is an integer that ranges from 1 to 65535. |
| vpn-instance vpn-instance-name | Specifies the name of a VPN instance. | The value must be an existing VPN instance name. |
Usage Scenario
Before you configure IS-IS functions and interface-related features, run the isis command to create an IS-IS process and enable IS-IS on the interface.
On a large-scale network, if a large number of switches run IS-IS, there will be a huge number routes, increasing maintenance costs, slowing down route convergence, and affecting network stability. To resolve the problem, you can run the isis process-id command to start multi-processes to reduce the number of routes to be maintained.
In addition, to ensure that different services are forwarded properly on the network, you can run the isis vpn-instance vpn-instance-name command to start multiple IS-IS processes on one device to isolate these services.
Follow-up Procedure
After the isis command is used to enable an IS-IS process, run the network-entity command to set a NET for the switch, and run the isis enable command to enable IS-IS on each interface that needs to run IS-IS. You can start IS-IS only when these configurations are completed.
Precautions
One IS-IS process can be bound to only one VPN instance. Multiple IS-IS interfaces can be bound to one VPN instance.
If a VPN instance is deleted, the IS-IS process bound to the VPN instance is deleted.
When creating an IS-IS process, bind it to a VPN instance. An existing IS-IS process cannot be bound to any VPN instance.