The isis command starts the IS-IS process and the specified VPN instance.
The undo isis command cancels the specified IS-IS process.
By default, IS-IS is not enabled for the system.
| Parameter | Description | Value |
|---|---|---|
| process-id | Specifies the process ID. | The value is an integer ranging from 1 to 65535. By default, it is 1. |
| vpn-instance vpn-instance-name | Specifies the name of the VPN instance. The VPN instance name indicates a common VPN or the VPN created for a virtual system. | The value is a string of 1 to 31 case-sensitive characters, spaces not supported. When double quotation marks are used around the string, spaces are allowed in the string. |
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 routers 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 router, 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.
# Start an IS-IS routing process 1 whose system is ID 0000.0000.0002 and the area ID 01.0001.
<sysname> system-view
[sysname] isis 1
[sysname-isis-1] network-entity 01.0001.0000.0000.0002.00
# Bind IS-IS process 2 to the VPN instance named vpn1.
<sysname> system-view
[sysname] isis 2 vpn-instance vpn1