- Table of Contents
-
- 05-Layer 3—IP Routing Command Reference
- 00-Preface
- 01-Basic IP routing commands
- 02-Static routing commands
- 03-RIP commands
- 04-OSPF commands
- 05-IS-IS commands
- 06-BGP commands
- 07-Policy-based routing commands
- 08-IPv6 static routing commands
- 09-RIPng commands
- 10-OSPFv3 commands
- 11-IPv6 policy-based routing commands
- 12-Routing policy commands
- Related Documents
-
| Title | Size | Download |
|---|---|---|
| 05-IS-IS commands | 721.19 KB |
display isis event-log graceful-restart
display isis event-log non-stop-routing
display isis graceful-restart status
display isis interface hello-sent
display isis non-stop-routing status
display isis peer hello-received
domain-authentication send-only
fast-reroute remote-lfa maximum-cost
fast-reroute remote-lfa prefix-list
fast-reroute remote-lfa tunnel ldp
import-route isis level-1 into level-2
import-route isis level-2 into level-1
import-route isisv6 level-1 into level-2
import-route isisv6 level-2 into level-1
isis fast-reroute lfa-backup exclude
isis fast-reroute remote-lfa disable
isis ipv6 fast-reroute lfa-backup exclude
isis ipv6 primary-path-detect bfd
isis peer hold-max-cost duration
isis troubleshooting max-number
reset isis event-log graceful-restart
reset isis event-log non-stop-routing
IS-IS commands
address-family ipv4
Use address-family ipv4 to create the IS-IS IPv4 address family and enter its view.
Use undo address-family ipv4 to delete the IS-IS IPv4 address family and all configurations in the view.
Syntax
address-family ipv4 [ unicast ]
undo address-family ipv4 [ unicast ]
Default
No IS-IS IPv4 address family exists.
Views
IS-IS view
Predefined user roles
network-admin
Parameters
unicast: Specifies the unicast address family (the default).
Examples
# Create the IS-IS IPv4 address family and enter its view.
<Sysname> system-view
[Sysname] isis 100
[Sysname-isis-100] address-family ipv4
[Sysname-isis-100-ipv4]
address-family ipv6
Use address-family ipv6 to create the IS-IS IPv6 address family and enter its view.
Use undo address-family ipv6 to remove the IS-IS IPv6 address family and all configurations in the view.
Syntax
address-family ipv6 [ unicast ]
undo address-family ipv6 [ unicast ]
Default
No IS-IS IPv6 address family exists.
Views
IS-IS view
Predefined user roles
network-admin
Parameters
unicast: Specifies the unicast address family (the default).
Usage guidelines
This command enables IPv6 for an IS-IS process.
Examples
# Create the IS-IS IPv6 address family and enter its view.
<Sysname> system-view
[Sysname] isis 100
[Sysname-isis-100] address-family ipv6
[Sysname-isis-100-ipv6]
area-authentication send-only
Use area-authentication send-only to configure IS-IS not to check the authentication information in the received Level-1 packets, including LSPs, CSNPs, and PSNPs.
Use undo area-authentication send-only to restore the default.
Syntax
area-authentication send-only
undo area-authentication send-only
Default
When area authentication mode and key are configured, a Level-1 or Level-1-2 router checks the authentication information in the received packets.
Views
IS-IS view
Predefined user roles
network-admin
Usage guidelines
When area authentication mode and key are configured, a Level-1 or Level-1-2 router adds the key in the specified mode into transmitted Level-1 packets (including LSPs, CSNPs, and PSNPs). It also checks the key in the received Level-1 packets.
To prevent packet exchange failure in case of an authentication key change, configure IS-IS not to check the authentication information in the received packets.
Examples
# Configure IS-IS not to check the authentication information in the received packets.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] area-authentication send-only
Related commands
area-authentication-mode
domain-authentication send-only
isis authentication send-only
area-authentication-mode
Use area-authentication-mode to specify an area authentication mode and a key.
Use undo area-authentication-mode to restore the default.
Syntax
area-authentication-mode { { gca key-id { hmac-sha-1 | hmac-sha-224 | hmac-sha-256 | hmac-sha-384 | hmac-sha-512 } [ nonstandard ] | md5 | simple } { cipher | plain } string | keychain keychain-name } [ ip | osi ]
undo area-authentication-mode
Default
No area authentication mode or key is configured.
Views
IS-IS view
Predefined user roles
network-admin
Parameters
gca: Specifies the Generic Cryptographic Authentication (GCA) mode.
key-id: Uniquely identifies an SA in the range of 1 to 65535. The sender inserts the Key ID into the authentication TLV, and the receiver authenticates the packet by using the SA that is selected based on the Key ID.
hmac-sha-1: Specifies the HMAC-SHA-1 algorithm.
hmac-sha-224: Specifies the HMAC-SHA-224 algorithm.
hmac-sha-256: Specifies the HMAC-SHA-256 algorithm.
hmac-sha-384: Specifies the HMAC-SHA-384 algorithm.
hmac-sha-512: Specifies the HMAC-SHA-512 algorithm.
nonstandard: Specifies the nonstandard GCA mode.
md5: Specifies the MD5 authentication mode.
simple: Specifies the simple authentication mode.
cipher: Specifies a key in encrypted form.
plain: Specifies a key in plaintext form. For security purposes, the key specified in plaintext form will be stored in encrypted form.
string: Specifies the key. Its plaintext form is a case-sensitive string of 1 to 16 characters. Its encrypted form is a case-sensitive string of 33 to 53 characters.
keychain: Specifies the keychain authentication mode.
keychain-name: Specifies a keychain by its name, a case-sensitive string of 1 to 63 characters.
ip: Checks IP-related fields in LSPs.
osi: Checks OSI-related fields in LSPs.
Area authentication enables IS-IS to discard routes from untrusted routers.
The key in the specified mode is inserted into all outbound Level-1 packets (LSP, CSNP, and PSNP) and is used to authenticate inbound Level-1 packets.
The keychain authentication mode supports only the HMAC-MD5 algorithm.
· Before IS-IS sends a Level-1 packet, it uses the valid send key obtained from the keychain to authenticate the packet. If no valid send key exists or the valid send key does not use the HMAC-MD5 algorithm, the authentication fails and the packet does not contain authentication information.
· After IS-IS receives a Level-1 packet, it uses a valid accept key obtained from the keychain to authenticate the packet. If no valid accept key exists or all valid accept keys fail to authenticate the packet, the authentication fails and the packet is discarded.
Routers in an area must have the same authentication mode and key.
If neither ip nor osi is specified, OSI-related fields are checked.
When you specify the GCA mode, follow these guidelines:
· If you do not specify the nonstandard keyword, the device can communicate only with devices that use the GCA mode.
· If you specify the nonstandard keyword, the device can communicate only with devices that use the nonstandard GCA mode.
Examples
# Set the area authentication mode to simple, and set the plaintext key to 123456.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] area-authentication-mode simple plain 123456
Related commands
area-authentication send-only
domain-authentication-mode
isis authentication-mode
auto-cost enable
Use auto-cost enable to enable automatic link cost calculation.
Use undo auto-cost enable to disable automatic link cost calculation.
Syntax
auto-cost enable
undo auto-cost enable
Default
Automatic link cost calculation is disabled.
Views
IS-IS view
IS-IS IPv6 unicast address family view
Predefined user roles
network-admin
Usage guidelines
After automatic link cost calculation is enabled, the link cost is automatically calculated based on the bandwidth reference value of an interface. When the cost-style is wide or wide-compatible, the cost value of an interface is calculated by using the following formula: Cost = (Reference bandwidth value / Link bandwidth) × 10. For other cost styles, Table 1 applies.
Table 1 Automatic cost calculation scheme for cost styles other than wide and wide-compatible
|
Interface bandwidth |
Cost |
|
≤10 Mbps |
60 |
|
≤100 Mbps |
50 |
|
≤155 Mbps |
40 |
|
≤622 Mbps |
30 |
|
≤2500 Mbps |
20 |
|
>2500 Mbps |
10 |
Examples
# Enable automatic link cost calculation for IS-IS process 1.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] auto-cost enable
Related commands
bandwidth-reference
cost-style
isis cost
isis ipv6 cost
bandwidth-reference
Use bandwidth-reference to set the bandwidth reference value for automatic link cost calculation.
Use undo bandwidth-reference to restore the default.
Syntax
bandwidth-reference value
undo bandwidth-reference
Default
The bandwidth reference value is 100 Mbps.
Views
IS-IS view
IS-IS IPv6 unicast address family view
Predefined user roles
network-admin
Parameters
value: Specifies the bandwidth reference value in the range of 1 to 2147483648 Mbps.
Examples
# Set the bandwidth reference of IS-IS process 1 to 200 Mbps.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] bandwidth-reference 200
Related commands
auto-cost enable
isis cost
circuit-cost
Use circuit-cost to set a global IS-IS link cost.
Use undo circuit-cost to remove the configuration.
Syntax
circuit-cost cost-value [ level-1 | level-2 ]
undo circuit-cost [ level-1 | level-2 ]
Default
No global link cost is configured.
Views
IS-IS view
IS-IS IPv6 unicast address family view
Predefined user roles
network-admin
Parameters
cost-value: Specifies the link cost value. The value range varies by cost style.
· For styles narrow, narrow-compatible, and compatible, the cost value is in the range of 0 to 63.
· For styles wide and wide-compatible, the cost value is in the range of 0 to 16777215.
level-1: Applies the link cost to Level-1.
level-2: Applies the link cost to Level-2.
Usage guidelines
If no level is specified, the specified cost applies to both Level-1 and Level-2.
Examples
# Set the global Level-1 link cost to 11 for IS-IS process 1.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] circuit-cost 11 level-1
Related commands
cost-style
isis cost
cost-style
Use cost-style to set a cost style.
Use undo cost-style to restore the default.
Syntax
cost-style { narrow | wide | wide-compatible | { compatible | narrow-compatible } [ relax-spf-limit ] }
undo cost-style
Default
The IS-IS cost style is narrow.
Views
Predefined user roles
network-admin
Parameters
narrow: Receives and sends only narrow cost style packets. The narrow cost is in the range of 0 to 63.
wide: Receives and sends only wide cost style packets. The wide cost is in the range of 0 to 16777215.
compatible: Receives and sends both wide and narrow cost style packets.
narrow-compatible: Receives both narrow and wide cost style packets, but sends only narrow cost style packets.
wide-compatible: Receives both narrow and wide cost style packets, but sends only wide cost style packets.
relax-spf-limit: Allows receiving routes with a cost greater than 1023. If you do not specify this keyword, routes with a cost bigger than 1023 will be discarded. This keyword is available only when compatible or narrow-compatible is used.
Examples
# Configure the router to send only narrow cost style packets, but receive both narrow and wide cost style packets.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] cost-style narrow-compatible
Related commands
circuit-cost
isis cost
default-route-advertise
Use default-route-advertise to advertise a default route of 0.0.0.0/0.
Use undo default-route-advertise to restore the default.
Syntax
default-route-advertise [ avoid-learning | [ level-1 | level-1-2 | level-2 ] | route-policy route-policy-name | tag tag ] *
undo default-route-advertise
Default
Default route advertisement is disabled.
Views
IS-IS IPv4 unicast address family view
IS-IS IPv6 unicast address family view
Predefined user roles
network-admin
Parameters
avoid-learning: Avoids learning the default route received in LSPs or generated by using the ATT bit to avoid routing loops.
level-1: Advertises a Level-1 default route.
level-1-2: Advertises both Level-1 and Level-2 default routes.
level-2: Advertises a Level-2 default route.
route-policy route-policy-name: Specifies a routing policy by its name, a case-sensitive string of 1 to 63 characters.
tag tag: Specifies the tag value for the default route, in the range of 1 to 4294967295.
Usage guidelines
If no level is specified, a Level-2 default route is advertised.
The Level-1 default route is advertised to other routers in the same area, and the Level-2 default route is advertised to all the Level-2 and Level-1-2 routers.
You can use a routing policy to specify a level for the default route. The apply isis level-1 command in routing policy view can generate a Level-1 default route. The apply isis level-2 command in routing policy view can generate a Level-2 default route. The apply isis level-1-2 command in routing policy view can generate both a Level-1 default route and Level-2 default route.
The tag value specified in the routing policy takes precedence over the tag value specified in this command.
Examples
# Configure IS-IS process 1 to advertise a Level-2 default route.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] address-family ipv4
[Sysname-isis-1-ipv4] default-route-advertise
display isis
Use display isis to display configuration information for an IS-IS process.
Syntax
display isis [ process-id ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
process-id: Specifies a process by its ID in the range of 1 to 65535. If you do not specify this argument, the command displays configuration information for all IS-IS processes.
Examples
# Display IS-IS configuration information.
<Sysname> display isis
IS-IS(1) Protocol Information
Instance identifier : 10
Network entity : 10.0000.0000.0001.00
IS level : level-1-2
Cost style : Wide
Isolation : Disabled
Fast reroute : Disabled
Fast-reroute TI-LFA
level-1 : Disabled
level-2 : Disabled
Microloop-avoidance
level-1 : Disabled
level-2 : Disabled
Microloop-avoidance RIB-update-delay
level-1 : 5000
level-2 : 5000
Fast-reroute remote-LFA
level-1 : Enabled
level-2 : Enabled
Preference : 15
LSP length receive : 1497
LSP length originate
level-1 : 1497
level-2 : 1497
Maximum imported routes : 1000
Timers
LSP-max-age : 1200
LSP-refresh : 900
SPF intervals : 5 50 200
IPv6 enabled
Multi-topology : Standard
Fast reroute : Disabled
Preference : 15
Maximum imported routes : 1000
SPF intervals : 5 50 200
Link tag inheritance : Disabled
Segment routing
MPLS : Disabled
Adjacency : Disabled
Global block : 16000 24000
Level-1 tunnel count : 0
Level-2 tunnel count : 0
Local block : 15000 15999
Table 2 Command output
|
Field |
Description |
|
Instance identifier |
Multi-instance process ID. |
|
Network entity |
Network entity name. |
|
IS level |
IS-IS routing level. |
|
Cost style |
Cost style. |
|
Isolation |
Whether IS-IS isolation is enabled. This field is available in Release 6522 and later. |
|
Fast reroute |
IS-IS FRR status: · Disabled—IS-IS FRR is disabled. · LFA—IS-IS FRR automatically calculates a backup next hop for non-ECMP routes. · Route-policy—IS-IS FRR specifies a backup next hop by using a routing policy. · LFA ecmp-shared—IS-IS FRR automatically calculates a backup next hop for all routes, including ECMP routes. ECMP routes share one backup next hop. |
|
Fast-reroute TI-LFA |
This field is not supported in the current software version. Topology independent LFA (TI-LFA) FRR status: Disabled or Enabled. |
|
Microloop-avoidance |
This field is not supported in the current software version. Microloop avoidance status: Disabled or Enabled. |
|
Microloop-avoidance RIB-update-delay |
This field is not supported in the current software version. Microloop avoidance delay timer. |
|
Fast-reroute remote-LFA |
Remote LFA FRR status: Disabled or Enabled. |
|
Preference |
IS-IS route preference. |
|
LSP length receive |
Maximum LSP that can be received. |
|
LSP length originate |
Maximum LSP that can be generated. |
|
Maximum imported routes |
Maximum number of redistributed Level-1/Level-2 IPv4/IPv6 routes. |
|
Timers |
Timers: · LSP-max-age—Maximum life period of LSPs. · LSP-refresh—Refresh interval of LSPs. · SPF intervals—Interval between SPF calculations. |
|
IPv6 enabled |
IPv6 is enabled. |
|
Multi-topology |
IPv6 unicast topology mode: · Standard—IPv6 unicast topology standard mode. · Compatible—IPv6 unicast topology compatible mode. |
|
Link tag inheritance |
Whether IPv6 IS-IS link tag inheritance is enabled. This field is not supported in the current software version. |
|
Segment routing |
This field is not supported in the current software version. Segment routing is supported. · MPLS: MPLS SR status. · Adjacency: Adjacency label allocation status. · Global block: SRGB range. · Level-1 tunnel count: Number of SR tunnels in Level-1 areas. · Level-2 tunnel count: Number of SR tunnels in the Level-2 area. · Local block: Minimum and maximum label values of the SRLB. |
display isis event-log graceful-restart
Use display isis event-log graceful-restart to display IS-IS GR log information.
Syntax
display isis event-log graceful-restart slot slot-number
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
slot slot-number: Specifies an IRF member device by its ID.
Examples
# Display IS-IS GR log information for the specified slot.
<Sysname> display isis event-log graceful-restart slot 1
IS-IS loginfo :
Sep 18 08:48:24 2019 slot 1 Process 1 enter GR restarting phase(Initialization).
Sep 18 08:48:24 2019 slot 1 Process 1 enter GR phase (LSDB synchronization).
Sep 18 08:48:24 2019 slot 1 Process 1 enter GR phase (TE tunnel prepare).
Sep 18 08:48:24 2019 slot 1 Process 1 enter GR phase (First SPF computation).
Sep 18 08:48:25 2019 slot 1 Process 1 enter GR phase (Redistribution).
Sep 18 08:48:25 2019 slot 1 Process 1 enter GR phase (Second SPF computation).
Sep 18 08:48:25 2019 slot 1 Process 1 enter GR phase (LSP stability).
Sep 18 08:48:25 2019 slot 1 Process 1 enter GR phase (LSP generation).
Sep 18 08:48:25 2019 slot 1 Process 1 enter GR phase (Finish).
Sep 18 08:48:25 2019 slot 1 Process 1 GR complete.
Table 3 Command output
|
Field |
Description |
|
GR phase |
GR phase: · Initialization. · LSDB synchronization. · TE tunnel prepare—Preparing for TE tunnel computation. This value is not supported in the current software version. · First SPF computation. · Redistribution. · Second SPF computation. · LSP stability—Ready to generate LSPs. · LSP generation. · Finish. |
display isis event-log hello
Use display isis event-log hello to display IS-IS log information about received or sent hello packets.
Syntax
display isis event-log hello { peer-change | received-abnormal | received-dropped | sent-abnormal | sent-failed } [ process-id ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
peer-change: Specifies log information for hello packets received or sent during neighbor state change.
received-abnormal: Specifies log information for abnormally received hello packets, which were received at intervals greater than or equal to 0.5 times the holdtime. The holdtime is the number of missed hello packets multiplied by the hello interval.
received-dropped: Specifies log information for received hello packets that were dropped.
sent-abnormal: Specifies log information for abnormally sent hello packets, which were sent at intervals greater than or equal to 1.5 times the hello interval.
sent-failed: Specifies log information for hello packets that failed to be sent.
process-id: Specifies an IS-IS process by its ID in the range of 1 to 65535. If you do not specify this argument, the command displays IS-IS log information for all processes.
Examples
# Display log information for hello packets received or sent during neighbor state changes.
<Sysname> display isis event-log hello peer-change
Hello logs for IS-IS(1)
-----------------------
Interface: Vlan10; NbrSystemID: 0000.0000.0002
Level-2 peer Up->Down at 2021-07-20 15:10:10:207
First 3 hello packets sent:
2021-10-21 11:34:33:311, succeeded
2021-10-21 11:34:33:323, succeeded
2021-10-21 11:34:41:057, succeeded
Last 3 hello packets sent:
2021-10-21 15:09:44:106, succeeded
2021-10-21 15:09:54:075, succeeded
2021-10-21 15:10:03:203, succeeded
First 3 hello packets received:
2021-10-21 11:34:33:321
2021-10-21 11:34:33:978
2021-10-21 11:34:43:524
Last 3 hello packets received:
2021-10-21 15:10:01:063
2021-10-21 15:10:04:370
2021-10-21 15:10:07:851
Interface: Vlan10; NbrSystemID: 0000.0000.0002
Level-1 peer Up->Down at 2021-10-21 15:10:10:206
First 3 hello packets sent:
2021-10-21 11:34:33:310, succeeded
2021-10-21 11:34:33:320, succeeded
2021-10-21 11:34:42:845, succeeded
Last 3 hello packets sent:
2021-10-21 15:09:50:074, succeeded
2021-10-21 15:09:57:643, succeeded
2021-10-21 15:10:05:665, succeeded
First 3 hello packets received:
2021-10-21 11:34:33:313
2021-10-21 11:34:35:738
2021-10-21 11:34:44:346
Last 3 hello packets received:
2021-10-21 15:10:01:062
2021-10-21 15:10:04:370
2021-10-21 15:10:07:847
Table 4 Command output
|
Field |
Description |
|
Interface |
Interface that sent or received the hello packets. |
|
NbrSystemID |
System ID of the neighbor. |
|
First 3 hello packets sent |
Time and result (succeeded or failed) for sending the first three hello packets. For a packet that failed to be sent, an error code is displayed in the errno field. |
|
Last 3 hello packets sent |
Time and result (succeeded or failed) for sending the last three hello packets before neighbor state change. For a packet that failed to be sent, an error code is displayed in the errno field. |
|
First 3 hello packets received |
Time when the first three hello packets were received. |
|
Last 3 hello packets received |
Time when the last three hello packets were received before neighbor state change. |
# Display log information about hello packets that failed to be sent.
<Sysname> display isis event-log hello sent-failed
Hello logs for IS-IS(1)
---------------------------
Date: 2021-10-21 Time: 14:51:20:121 Interface: Vlan10
PDU type: L1 hello; errno: 132
Date: 2021-10-21 Time: 14:51:20:121 Interface: Vlan10
PDU type: L2 hello; errno: 132
Date: 2021-10-21 Time: 11:20:20:116 Interface: Vlan12
PDU type: P2P hello; errno: 132
Table 5 Command output
|
Field |
Description |
|
Date |
Date for the hello packet sending failure, in the format of YYYY-MM-DD. YYYY represents the year, MM represents the month, and DD represents the day. |
|
Time |
Time for the hello packet sending failure, in the format of hh:mm:ss:xxx. hh represents the hours, mm represents the minutes, and ss represents the seconds, and xxx represents the milliseconds. |
|
Interface |
Interface that sent the hello packet. |
|
PDU type |
Type of the hello packet that failed to be sent. |
|
errno |
Error code for the hello packet sending failure. |
# Display log information for abnormally sent hello packets.
<Sysname> display isis event-log hello sent-abnormal
Hello logs for IS-IS(1)
---------------------------
Date: 2021-10-21 Time: 11:21:12:121 Interface: Vlan10
PDU type: L1 hello, last one sent: 2021-10-21 11:20:51:916
Date: 2021-10-21 Time: 11:56:21:312 Interface: Vlan12
PDU type: P2P hello, last one sent: 2021-10-21 11:56:02:691
Table 6 Command output
|
Field |
Description |
|
Date |
Date when the hello packet was sent, in the format of YYYY-MM-DD. YYYY represents the year, MM represents the month, and DD represents the day. |
|
Time |
Time when the hello packet was sent, in the format of hh:mm:ss:xxx. hh represents the hours, mm represents the minutes, and ss represents the seconds, and xxx represents the milliseconds. |
|
Interface |
Interface that sent the hello packet. |
|
PDU type |
Type of the hello packet. |
|
last one sent |
Time when the last hello packet was sent before the hello packet was sent. |
# Display log information about received hello packets that were dropped.
<Sysname> display isis event-log hello received-dropped
Hello logs for IS-IS(1)
---------------------------
Date: 2021-10-21 Time: 14:51:22:791 Interface: Vlan10
PDU type: L1 hello, NbrSystemID: 0000.0000.0001
Drop reason: Excessive area addresses
Date: 2021-10-21 Time: 14:51:20:121 Interface: Vlan12
PDU type: P2P hello, NbrSystemID: 0000.0000.0003
Drop reason: Duplicate system ID
|
Field |
Description |
|
Date |
Date when the received hello packet was dropped, in the format of YYYY-MM-DD. YYYY represents the year, MM represents the month, and DD represents the day. |
|
Time |
Time when the received hello packet was dropped, in the format of hh:mm:ss:xxx. hh represents the hours, mm represents the minutes, and ss represents the seconds, and xxx represents the milliseconds. |
|
Interface |
Interface that received the hello packet. |
|
PDU type |
Packet type. |
|
NbrSystemID |
System ID of the neighbor. |
|
Drop reason |
Reason for dropping the hello packet: · Bad packet length. · Bad header length. · Jumbo packet. · Bad protocol description. · Bad protocol ID. · Bad protocol version. · Unknown packet type. · Bad max area count. · Bad system ID length. · Bad circuit type. · Bad auth TLV. · Bad area address TLV. · Auth failure. · Excessive area addresses. · Bad NBR TLV. · Excessive auth TLVs. · Excessive IF Addr TLVs. · Excessive IF addresses. · Bad IF address TLV. · Duplicate system ID. · Bad TLV length. · Bad IP address. · Duplicate IP address. · Mismatched area address. · Mismatched protocol. · Mismatched network type. · Bad IPv6 address TLV. · Bad IPv6 address. · Duplicate IPv6 address. · Bad MT ID TLV. · SNPA conflict (LAN). · Excessive NBR SNPAs (LAN). · Mismatched level (LAN). · Bad 3-Way option TLV (P2P). · No common MT ID (P2P). · Bad circuit ID (P2P). · Bad BFD TLV. · Bad global IPv6 address TLV. · Bad multi instance TLV. |
# Display log information about abnormally received hello packets.
<Sysname> display isis event-log hello received-abnormal
Hello logs for IS-IS(1)
---------------------------
Date: 2021-10-21 Time: 10:12:22:121 Interface: Vlan10
PDU type: L1 hello, NbrSystemID: 0000.0000.0001
Last one received: 2021-10-21 10:12:01:212
Date: 2021-10-21 Time: 14:51:20:121 Interface: Vlan10
PDU type: L1 hello, NbrSystemID: 0000.0000.0001
Last one received: 2021-10-21 14:51:05:113
Table 8 Command output
|
Field |
Description |
|
Date |
Date when the hello packet was received, in the format of YYYY-MM-DD. YYYY represents the year, MM represents the month, and DD represents the day. |
|
Time |
Time when the hello packet was received, in the format of hh:mm:ss:xxx. hh represents the hours, mm represents the minutes, and ss represents the seconds, and xxx represents the milliseconds. |
|
Interface |
Interface that received the hello packet. |
|
PDU type |
Packet type. |
|
NbrSystemID |
System ID of the neighbor. |
|
Last one received |
Time when the last hello packet was received before the hello packet was received. |
Related commands
reset isis event-log hello
display isis event-log lsp
Use display isis event-log lsp to display IS-IS LSP log information.
Syntax
display isis event-log lsp { purged | refreshed } [ level-1 | level-2 ] [ process-id ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
purged: Displays log information about purged LSPs.
refreshed: Displays log information about refreshed LSPs, including generated and received LSPs.
level-1: Displays Level-1 LSP log information.
level-2: Displays Level-2 LSP log information.
process-id: Specifies a process by its ID in the range of 1 to 65535. If you do not specify this argument, the command displays LSP log information for all IS-IS processes.
Usage guidelines
If you do not specify a level, the command displays both Level-1 and Level-2 LSP log information.
Examples
# Displays log information about purged LSPs.
<Sysname> display isis event-log lsp purged
LSP log for IS-IS(1)
--------------------
Level-1 LSP log
---------------
Date Time LSP ID Seq Num Event
--------------------------------------------------------------------------------
2019-07-31 10:19:48 1111.1111.1111.01-00 0x00000001 Generated LSP purge packet
2019-07-31 10:19:48 1111.1111.1111.01-00 0x00000001 Received LSP purge packet
2019-07-31 10:15:29 2222.2222.2222.01-00 0x00000005 Generated LSP purge packet
Level-2 LSP log
---------------
Date Time LSP ID Seq Num Event
--------------------------------------------------------------------------------
2019-07-31 10:19:48 1111.1111.1111.01-00 0x00000001 Generated LSP purge packet
2019-07-31 10:19:48 1111.1111.1111.01-00 0x00000001 Received LSP purge packet
2019-07-31 10:15:29 2222.2222.2222.01-00 0x00000005 Generated LSP purge packet
# Displays log information about refreshed LSPs.
<Sysname> display isis event-log lsp refreshed
LSP log for IS-IS(1)
--------------------
Level-1 LSP log
---------------
Date Time LSP ID Seq Num Event
--------------------------------------------------------------------------------
2019-06-06 17:18:48 0000.0000.0012.00-00 0x00000038 Received LSP
2019-06-06 17:18:48 0000.0000.0011.00-00 0x00000042 Received LSP
2019-06-06 17:18:48 0000.0000.0012.00-00 0x00000039 Generated LSP
2019-06-06 17:18:48 0000.0000.0012.00-00 0x00000038 Received LSP
2019-06-06 17:18:48 0000.0000.0011.00-00 0x00000042 Received LSP
2019-06-06 17:18:48 0000.0000.0012.00-00 0x00000002 Generated LSP
2019-06-06 17:18:48 0000.0000.0011.01-00 0x00000032 Received LSP
2019-06-06 17:18:48 0000.0000.0011.02-00 0x00000035 Received LSP
2019-06-06 17:18:48 0000.0000.0011.01-00 0x00000032 Received LSP
2019-06-06 17:18:48 0000.0000.0011.02-00 0x00000035 Received LSP
2019-06-06 17:18:47 0000.0000.0012.00-00 0x00000001 Generated LSP
Level-2 LSP log
---------------
Date Time LSPID Seq Num Event
--------------------------------------------------------------------------------
2019-06-06 17:18:48 0000.0000.0012.00-00 0x00000002 Generated LSP
2019-06-06 17:18:47 0000.0000.0012.00-00 0x00000001 Generated LSP
Table 9 Command output
|
Field |
Description |
|
Date |
Date of the LSP change. |
|
Time |
Time of the LSP change. |
|
LSPID |
LSP ID. |
|
Seq Num |
LSP sequence number. |
|
Event |
LSP change event: · Received LSP. · Received LSP purge packet. · Generated LSP. · Generated LSP purge packet. |
Related commands
reset isis event-log lsp
display isis event-log non-stop-routing
Use display isis event-log non-stop-routing to display IS-IS NSR log information.
Syntax
display isis event-log non-stop-routing slot slot-number
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
slot slot-number: Specifies an IRF member device by its ID.
Examples
# Display IS-IS NSR log information for the specified slot.
<Sysname> display isis event-log non-stop-routing slot 1
IS-IS loginfo :
Sep 18 10:20:44 2019 slot 1 Enter HA Block status
Sep 18 10:20:44 2019 slot 1 Exit HA Block status
Sep 18 10:24:00 2019 slot 1 Process 100 enter NSR phase (Initialization).
Sep 18 10:24:00 2019 slot 1 Process 100 enter NSR phase (Smooth).
Sep 18 10:24:00 2019 slot 1 Process 100 enter NSR phase (TE tunnel prepare).
Sep 18 10:24:00 2019 slot 1 Process 100 enter NSR phase (First SPF computation).
Sep 18 10:24:00 2019 slot 1 Process 100 enter NSR phase (Redistribution).
Sep 18 10:24:00 2019 slot 1 Process 100 enter NSR phase (Second SPF computation).
Sep 18 10:24:00 2019 slot 1 Process 100 enter NSR phase (LSP stability).
Sep 18 10:24:00 2019 slot 1 Process 100 enter NSR phase (LSP generation).
Sep 18 10:24:00 2019 slot 1 Process 100 enter NSR phase (Finish).
Sep 18 10:24:00 2019 slot 1 Process 100 NSR complete.
Table 10 Command output
|
Field |
Description |
|
NSR phase |
NSR phase: · Initialization. · Smooth. · TE tunnel prepare—Preparing for TE tunnel computation. This value is not supported in the current software version. · First SPF computation. · Redistribution. · Second SPF computation. · LSP stability—Ready to generate LSPs. · LSP generation. · Finish. |
display isis event-log peer
Use display isis event-log peer to display neighbor state change log information.
Syntax
display isis event-log peer [ process-id ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
process-id: Specifies a process by its ID in the range of 1 to 65535. If you do not specify this argument, the command displays neighbor state change log information for all IS-IS processes.
Examples
# Display neighbor state change log information for IS-IS process 1.
<Sysname> display isis event-log peer 1
Peer Log for IS-IS(1)
---------------------
Date Time NbrSystemId Type Reason Interface
--------------------------------------------------------------------------------
2021-10-21 15:10:10 0000.0000.0002 L2 CircuitDown Vlan10
2021-10-21 15:10:10 0000.0000.0002 L1 CircuitDown Vlan10
Table 11 Command output
|
Field |
Description |
|
Date |
Date when the neighbor state changed, in the format of YYYY-MM-DD. YYYY represents the year, MM represents the month, and DD represents the day. |
|
Time |
Time when the neighbor state changed, in the format of hh:mm:ss:xxx. hh represents the hours, mm represents the minutes, and ss represents the seconds, and xxx represents the milliseconds. |
|
NbrSystemId |
System ID of the neighbor. |
|
Type |
Link type: · L1—Level-1 link. · L2—Level-2 link. · L1L2—Level-1-2 link. |
|
Reason |
Reason why the neighbor state changed: · ProcessReset. · ProcessResetGR. · ProcessLevelChange. · ProcessDeleted. · ProcessStopped. · LSPSequenceExceed. · AreaDeleted. · PeerReset. · HoldtimeExried. · BFDDown. · BFDAdminDown. · BFDLocalCfgChange. · BFDRemoteCfgChange. · IPv6TopoloyModeChange. · WaitDeleteBFDTLVTimeout. · CircuitIPv4Down. · CircuitIPv6Down. · PeerIPv4Disabled. · PeerIPv6Disabled. · CircuitDown. · CircuitDelete. · CircuitSilent. · CircuitTypeMismatch. · CircuitParamChange. · CircuitLevelChange. · CircuitIPv4Disabled. · CircuitIPv6Disabled. · IPv4AddressDelete. · IPv6AddressDelete. · IIHProtocloMismatch. · IIHAreaMismatch. · IIHCircuitTypeMismatch. · IIHNoSNPA. · IIHNoLocalSNPA. · SNPAConflict. · GRDown. · SystemIdChanged. · CircuitIdChanged. · ExtendedCircuitIdChanged. · ThreeWayStateDown. |
|
Interface |
Local interface connected to the neighbor. |
Related commands
reset isis event-log peer
display isis event-log spf
Use display isis event-log spf to display IS-IS route calculation log information.
Syntax
display isis event-log spf [ ipv4 | ipv6 ] [ [ level-1 | level-2 ] | verbose ] * [ process-id ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
ipv4: Displays IPv4 IS-IS route calculation log information.
ipv6: Displays IPv6 IS-IS route calculation log information.
level-1: Displays Level-1 route calculation log information.
level-2: Displays Level-2 route calculation log information.
verbose: Displays detailed route calculation log information. If you do not specify this keyword, the command displays brief route calculation log information.
process-id: Specifies a process by its ID in the range of 1 to 65535. If you do not specify this argument, the command displays route calculation log information for all IS-IS processes.
Usage guidelines
If you do not specify the ipv4 or ipv6 keyword, the command displays IPv4 IS-IS route calculation log information for the public network.
If you do not specify a level, the command displays both Level-1 and Level-2 route calculation log information.
Examples
# Display brief IS-IS route calculation log information.
<Sysname> display isis event-log spf
SPF Log for IS-IS(1)
--------------------
Level-1 SPF Log
---------------
Date Time Duration Count Trigger event
-------------------------------------------------------------------------------
2019-12-07 11:11:45 0.003 2 LDP label changed
2019-12-07 11:11:10 0 2 Remote LFA configuration changed
2019-12-07 11:10:45 0 4 Interface metric changed
2019-12-07 09:26:40 0 4 LSP updated
2019-12-07 09:26:28 0 2 DIS changed
2019-12-07 09:26:21 0.001 2 LSP updated
2019-12-07 09:26:07 0.001 3 Direct route changed
Level-2 SPF Log
---------------
Date Time Duration Count Trigger event
-------------------------------------------------------------------------------
2019-12-07 11:11:45 0.003 2 LDP label changed
2019-12-07 11:11:10 0 2 Remote LFA configuration changed
2019-12-07 11:10:45 0 4 Interface metric changed
2019-12-07 09:26:40 0 4 LSP updated
2019-12-07 09:26:28 0 2 DIS changed
2019-12-07 09:26:21 0 2 LSP updated
2019-12-07 09:26:07 0 3 Direct route changed
# Display detailed IS-IS route calculation log information.
<Sysname> display isis event-log spf verbose
SPF Log for IS-IS(1)
--------------------
Level-1 SPF Log
---------------
Log date : 2019-09-07 11:10:45
Log key : 5
Trigger count : 4
Trigger event : Interface metric changed
SPF details :
Phase Duration Description
TE tunnel ADJ 0 TE SPF nodes: 0
Topology 0 SPF nodes: 3
BSPF 0 Candidate NBRs: 1
TI/R-LFA prepare 0 TI/R-LFA links: 0, TI/R-LFA nodes: 0
Link PSPF 0
Link PQ 0
Node PSPF 0
Node PQ 0
LFA 0 LFA SPF nodes: 1
Area 0 Area addresses: 1
PRC 0 Add: 0 modify: 1 delete: 0
Last 10 routes:
1.1.1.0/24
Route summary 0 Summary route nodes: 0
Total 0
Log date : 2019-09-07 09:26:40
Log key : 4
Trigger count : 4
Trigger event : LSP updated
SPF details :
Phase Duration Description
TE tunnel ADJ 0 TE SPF nodes: 0
Topology 0 SPF nodes: 3
BSPF 0 Candidate NBRs: 1
TI/R-LFA prepare 0 TI/R-LFA links: 0, TI/R-LFA nodes: 0
Link PSPF 0
Link PQ 0
Node PSPF 0
Node PQ 0
LFA 0 LFA SPF nodes: 1
Area 0 Area addresses: 1
PRC 0 Add: 0 modify: 0 delete: 0
Route summary 0 Summary route nodes: 0
Total 0
Log date : 2019-09-07 09:26:28
Log key : 3
Trigger count : 2
Trigger event : DIS changed
SPF details :
Phase Duration Description
TE tunnel ADJ 0 TE SPF nodes: 0
Topology 0 SPF links changed: 1
BSPF 0 Candidate NBRs: 0
TI/R-LFA prepare 0 TI/R-LFA links: 0, TI/R-LFA nodes: 0
Link PSPF 0
Link PQ 0
Node PSPF 0
Node PQ 0
LFA 0 LFA SPF nodes: 0
Area 0 Area addresses: 0
PRC 0 Add: 0 modify: 0 delete: 0
Route summary 0 Summary route nodes: 0
Total 0
Log date : 2019-09-07 09:26:21
Log key : 2
Trigger count : 2
Trigger event : LSP updated
SPF details :
Phase Duration Description
TE tunnel ADJ 0 TE SPF nodes: 0
Topology 0 SPF nodes: 0
BSPF 0 Candidate NBRs: 0
TI/R-LFA prepare 0 TI/R-LFA links: 0, TI/R-LFA nodes: 0
Link PSPF 0
Link PQ 0
Node PSPF 0
Node PQ 0
LFA 0 LFA SPF nodes: 0
Area 0 Area addresses: 1
PRC 0.001 Add: 0 modify: 0 delete: 0
Route summary 0 Summary route nodes: 0
Total 0.001
Log date : 2019-09-07 09:26:07
Log key : 1
Trigger count : 3
Trigger event : Direct route changed
SPF details :
Phase Duration Description
TE tunnel ADJ 0 TE SPF nodes: 0
Topology 0 SPF nodes: 0
BSPF 0 Candidate NBRs: 0
TI/R-LFA prepare 0 TI/R-LFA links: 0, TI/R-LFA nodes: 0
Link PSPF 0
Link PQ 0
Node PSPF 0
Node PQ 0
LFA 0 LFA SPF nodes: 0
Area 0 Area addresses: 1
PRC 0.001 Add: 1 modify: 0 delete: 0
Last 10 routes:
1.1.1.0/24
Route summary 0 Summary route nodes: 0
Total 0.001
Level-2 SPF Log
---------------
Log date : 2019-09-07 11:10:45
Log key : 5
Trigger count : 4
Trigger event : Interface metric changed
SPF details :
Phase Duration Description
TE tunnel ADJ 0 TE SPF nodes: 0
Topology 0 SPF nodes: 3
BSPF 0 Candidate NBRs: 1
TI/R-LFA prepare 0 TI/R-LFA links: 0, TI/R-LFA nodes: 0
Link PSPF 0
Link PQ 0
Node PSPF 0
Node PQ 0
LFA 0 LFA SPF nodes: 1
Area 0 Area addresses: 1
PRC 0 Add: 0 modify: 0 delete: 0
Route summary 0 Summary route nodes: 0
Total 0
Log date : 2019-09-07 09:26:40
Log key : 4
Trigger count : 4
Trigger event : LSP updated
SPF details :
Phase Duration Description
TE tunnel ADJ 0 TE SPF nodes: 0
Topology 0 SPF nodes: 3
BSPF 0 Candidate NBRs: 1
TI/R-LFA prepare 0 TI/R-LFA links: 0, TI/R-LFA nodes: 0
Link PSPF 0
Link PQ 0
Node PSPF 0
Node PQ 0
LFA 0 LFA SPF nodes: 1
Area 0 Area addresses: 1
PRC 0 Add: 0 modify: 0 delete: 0
Route summary 0 Summary route nodes: 0
Total 0
Log date : 2019-09-07 09:26:28
Log key : 3
Trigger count : 2
Trigger event : DIS changed
SPF details :
Phase Duration Description
TE tunnel ADJ 0 TE SPF nodes: 0
Topology 0 SPF links changed: 1
BSPF 0 Candidate NBRs: 0
TI/R-LFA prepare 0 TI/R-LFA links: 0, TI/R-LFA nodes: 0
Link PSPF 0
Link PQ 0
Node PSPF 0
Node PQ 0
LFA 0 LFA SPF nodes: 0
Area 0 Area addresses: 0
PRC 0 Add: 0 modify: 0 delete: 0
Route summary 0 Summary route nodes: 0
Total 0
Log date : 2019-09-07 09:26:21
Log key : 2
Trigger count : 2
Trigger event : LSP updated
SPF details :
Phase Duration Description
TE tunnel ADJ 0 TE SPF nodes: 0
Topology 0 SPF nodes: 0
BSPF 0 Candidate NBRs: 0
TI/R-LFA prepare 0 TI/R-LFA links: 0, TI/R-LFA nodes: 0
Link PSPF 0
Link PQ 0
Node PSPF 0
Node PQ 0
LFA 0 LFA SPF nodes: 0
Area 0 Area addresses: 1
PRC 0 Add: 0 modify: 0 delete: 0
Route summary 0 Summary route nodes: 0
Total 0
Log date : 2019-09-07 09:26:07
Log key : 1
Trigger count : 3
Trigger event : Direct route changed
SPF details :
Phase Duration Description
TE tunnel ADJ 0 TE SPF nodes: 0
Topology 0 SPF nodes: 0
BSPF 0 Candidate NBRs: 0
TI/R-LFA prepare 0 TI/R-LFA links: 0, TI/R-LFA nodes: 0
Link PSPF 0
Link PQ 0
Node PSPF 0
Node PQ 0
LFA 0 LFA SPF nodes: 0
Area 0 Area addresses: 1
PRC 0 Add: 0 modify: 0 delete: 0
Route summary 0 Summary route nodes: 0
Total 0
Table 12 Command output
|
Field |
Description |
|
Date |
Start date of route calculation. |
|
Time |
Start time of route calculation. |
|
Duration |
Route calculation duration in seconds. The value is accurate to six decimal places. |
|
Count |
Number of events that trigger the current route calculation. |
|
Trigger event |
Type of the most recent event that triggers route calculation: · NextHop changed. · DIS changed. · Interface metric changed. · SPF link changed. · Default route changed. · Summary route changed. · IPv6 mode changed. · FRR configuration changed. · Prefix priority configuration changed. · Route preference changed. · ISPF configuration changed. · Import filter policy changed. · ECMP configuration changed. · PIC configuration changed. · Route leakage configuration changed. · NSR over. · Entered overload state. · Exited overload state. · Area address changed. · Route policy changed. · Redistributed route updated. · LSP updated. · MT disabled. · MT enabled. · RIB smooth. · Remote LFA configuration changed. · LDP label changed. |
|
Log date |
Generation time of the route calculation logs. |
|
Log key |
Route calculation log key. |
|
Trigger count |
Number of events that trigger the current route calculation. |
|
SPF details |
Detailed information about the route calculation phases. |
|
Phase |
Route calculation phase: · TE tunnel ADJ—TE tunnel adjacency calculation. This value is not supported in the current software version. · Topology—Topology calculation. · BSPF—Backup SPF calculation. · TI/R-LFA prepare—TI-LFA/Remote LFA calculation preparation. TI-LFA is not supported in the current software version. · Link PSPF—SPF calculation after PSPF convergence for link protection. This value is not supported in the current software version. · Link PQ—P space and Q space calculation for link protection. This value is not supported in the current software version. · Node PSPF—SPF calculation after PSPF convergence for node protection. This value is not supported in the current software version. · Node PQ—P space and Q space calculation for node protection. This value is not supported in the current software version. · LFA—LFA calculation. · Area—Area calculation. · PRC—Prefix calculation. · Route summary—Route summarization calculation. |
|
Description |
Route calculation phase description: · TE SPF nodes—Number of SPF nodes for TE tunnel adjacency calculation. This value is not supported in the current software version. · SPF nodes—Number of SPF nodes for topology calculation. · Candidate NBRs—Number of candidate neighbors. · TI/R-LFA links—Number of TI-LFA/remote LFA protected links. TI-LFA is not supported in the current software version. · TI/R-LFA nodes—Number of TI-LFA/remote LFA protected nodes. TI-LFA is not supported in the current software version. · LFA SPF nodes—Number of SPF nodes for LFA calculation. · Area addresses—Number of area addresses. · Add, modify, and delete—Prefix calculation summary. · Last 10 routes—10 routes that are most recently calculated. · Summary route nodes—Number of summarized routes. |
|
Total |
Total duration time of all route calculation phases. |
# Display brief IPv6 IS-IS route calculation log information.
<Sysname> display isis event-log spf ipv6
SPF Log for IS-IS(1)
--------------------
Level-1 SPF Log
---------------
Date Time Duration Count Trigger event
-------------------------------------------------------------------------------
2019-09-07 11:10:45 0 4 Interface metric changed
2019-09-07 09:26:40 0 4 LSP updated
2019-09-07 09:26:28 0 2 DIS changed
2019-09-07 09:26:21 0.001 2 LSP updated
2019-09-07 09:26:07 0.001 3 Direct route changed
Level-2 SPF Log
---------------
Date Time Duration Count Trigger event
-------------------------------------------------------------------------------
2019-09-07 11:10:45 0 4 Interface metric changed
2019-09-07 09:26:40 0 4 LSP updated
2019-09-07 09:26:28 0 2 DIS changed
2019-09-07 09:26:21 0 2 LSP updated
2019-09-07 09:26:07 0 3 Direct route changed
# Display detailed IPv6 IS-IS route calculation log information.
<Sysname> display isis event-log spf ipv6 verbose
SPF Log for IS-IS(1)
--------------------
Level-1 SPF Log
---------------
Log date : 2019-09-07 02:18:09
Log key : 10
Trigger count : 2
Trigger event : LSP updated
SPF details :
Phase Duration Description
TE tunnel ADJ 0 TE SPF nodes: 0
Topology 0 SPF nodes: 0
BSPF 0 Candidate NBRs: 0
TI-LFA prepare 0 TI-LFA links: 0, TI-LFA nodes: 0
Link PSPF 0
Link PQ 0
Node PSPF 0
Node PQ 0
LFA 0 LFA SPF nodes: 0
Area 0 Area addresses: 0
PRC 0 Add: 0 modify: 0 delete: 0
Route summary 0 Summary route nodes: 0
Total 0
Log date : 2019-09-07 02:18:09
Log key : 9
Trigger count : 2
Trigger event : NextHop changed
SPF details :
Phase Duration Description
TE tunnel ADJ 0 TE SPF nodes: 0
Topology 0.003 SPF nodes: 3
BSPF 0 Candidate NBRs: 0
TI-LFA prepare 0 TI-LFA links: 0, TI-LFA nodes: 0
Link PSPF 0
Link PQ 0
Node PSPF 0
Node PQ 0
LFA 0 LFA SPF nodes: 0
Area 0 Area addresses: 1
PRC 0 Add: 0 modify: 0 delete: 0
Route summary 0 Summary route nodes: 0
Total 0.003
Log date : 2019-01-01 02:17:40
Log key : 8
Trigger count : 2
Trigger event : Logic interface changed
SPF details :
Phase Duration Description
TE tunnel ADJ 0 TE SPF nodes: 0
Topology 0 SPF nodes: 0
BSPF 0 Candidate NBRs: 0
TI-LFA prepare 0 TI-LFA links: 0, TI-LFA nodes: 0
Link PSPF 0
Link PQ 0
Node PSPF 0
Node PQ 0
LFA 0 LFA SPF nodes: 0
Area 0 Area addresses: 0
PRC 0.005 Add: 1 modify: 0 delete: 0
Last 10 routes:
10::/64
Route summary 0 Summary route nodes: 0
Total 0.005
Log date : 2019-09-07 02:17:38
Log key : 7
Trigger count : 1
Trigger event : Logic interface changed
SPF details :
Phase Duration Description
TE tunnel ADJ 0 TE SPF nodes: 0
Topology 0 SPF nodes: 0
BSPF 0 Candidate NBRs: 0
TI-LFA prepare 0 TI-LFA links: 0, TI-LFA nodes: 0
Link PSPF 0
Link PQ 0
Node PSPF 0
Node PQ 0
LFA 0 LFA SPF nodes: 0
Area 0 Area addresses: 0
PRC 0 Add: 0 modify: 0 delete: 0
Route summary 0 Summary route nodes: 0
Total 0
Log date : 2019-09-07 02:17:33
Log key : 6
Trigger count : 5
Trigger event : NextHop changed
SPF details :
Phase Duration Description
TE tunnel ADJ 0 TE SPF nodes: 0
Topology 0 SPF links changed: 1
BSPF 0 Candidate NBRs: 0
TI-LFA prepare 0 TI-LFA links: 0, TI-LFA nodes: 0
Link PSPF 0
Link PQ 0
Node PSPF 0
Node PQ 0
LFA 0 LFA SPF nodes: 0
Area 0 Area addresses: 0
PRC 0.003 Add: 0 modify: 0 delete: 1
Last 10 routes:
3::/24
Route summary 0 Summary route nodes: 0
Total 0.003
Log date : 2019-09-07 02:17:21
Log key : 5
Trigger count : 1
Trigger event : Direct route changed
SPF details :
Phase Duration Description
TE tunnel ADJ 0 TE SPF nodes: 0
Topology 0 SPF nodes: 0
BSPF 0 Candidate NBRs: 0
TI-LFA prepare 0 TI-LFA links: 0, TI-LFA nodes: 0
Link PSPF 0
Link PQ 0
Node PSPF 0
Node PQ 0
LFA 0 LFA SPF nodes: 0
Area 0 Area addresses: 0
PRC 0.006 Add: 1 modify: 0 delete: 0
Last 10 routes:
3::/24
Route summary 0 Summary route nodes: 0
Total 0.006
Log date : 2019-09-07 02:17:11
Log key : 4
Trigger count : 1
Trigger event : IPv6 mode changed
SPF details :
Phase Duration Description
TE tunnel ADJ 0 TE SPF nodes: 0
Topology 0 SPF nodes: 3
BSPF 0 Candidate NBRs: 0
TI-LFA prepare 0 TI-LFA links: 0, TI-LFA nodes: 0
Link PSPF 0
Link PQ 0
Node PSPF 0
Node PQ 0
LFA 0 LFA SPF nodes: 0
Area 0 Area addresses: 1
PRC 0 Add: 0 modify: 0 delete: 0
Route summary 0 Summary route nodes: 0
Total 0
Log date : 2019-09-07 01:09:33
Log key : 3
Trigger count : 2
Trigger event : DIS changed
SPF details :
Phase Duration Description
TE tunnel ADJ 0 TE SPF nodes: 0
Topology 0.001 SPF nodes: 3
BSPF 0 Candidate NBRs: 0
TI-LFA prepare 0 TI-LFA links: 0, TI-LFA nodes: 0
Link PSPF 0
Link PQ 0
Node PSPF 0
Node PQ 0
LFA 0 LFA SPF nodes: 0
Area 0 Area addresses: 1
PRC 0 Add: 0 modify: 0 delete: 0
Route summary 0 Summary route nodes: 0
Total 0.001
Log date : 2019-09-07 01:09:25
Log key : 2
Trigger count : 2
Trigger event : LSP updated
SPF details :
Phase Duration Description
TE tunnel ADJ 0 TE SPF nodes: 0
Topology 0 SPF links changed: 1
BSPF 0 Candidate NBRs: 0
TI-LFA prepare 0 TI-LFA links: 0, TI-LFA nodes: 0
Link PSPF 0
Link PQ 0
Node PSPF 0
Node PQ 0
LFA 0 LFA SPF nodes: 0
Area 0 Area addresses: 1
PRC 0 Add: 0 modify: 0 delete: 0
Route summary 0 Summary route nodes: 0
Total 0
Log date : 2019-09-07 01:08:49
Log key : 1
Trigger count : 1
Trigger event : Area address changed
SPF details :
Phase Duration Description
TE tunnel ADJ 0 TE SPF nodes: 0
Topology 0 SPF nodes: 0
BSPF 0 Candidate NBRs: 0
TI-LFA prepare 0 TI-LFA links: 0, TI-LFA nodes: 0
Link PSPF 0
Link PQ 0
Node PSPF 0
Node PQ 0
LFA 0 LFA SPF nodes: 0
Area 0 Area addresses: 1
PRC 0 Add: 0 modify: 0 delete: 0
Route summary 0 Summary route nodes: 0
Total 0
Level-2 SPF Log
---------------
Log date : 2019-09-07 02:18:09
Log key : 10
Trigger count : 2
Trigger event : LSP updated
SPF details :
Phase Duration Description
TE tunnel ADJ 0 TE SPF nodes: 0
Topology 0 SPF nodes: 0
BSPF 0 Candidate NBRs: 0
TI-LFA prepare 0 TI-LFA links: 0, TI-LFA nodes: 0
Link PSPF 0
Link PQ 0
Node PSPF 0
Node PQ 0
LFA 0 LFA SPF nodes: 0
Area 0 Area addresses: 0
PRC 0 Add: 0 modify: 0 delete: 0
Route summary 0 Summary route nodes: 0
Total 0
Log date : 2019-09-07 02:18:09
Log key : 9
Trigger count : 2
Trigger event : NextHop changed
SPF details :
Phase Duration Description
TE tunnel ADJ 0 TE SPF nodes: 0
Topology 0.002 SPF nodes: 3
BSPF 0 Candidate NBRs: 0
TI-LFA prepare 0 TI-LFA links: 0, TI-LFA nodes: 0
Link PSPF 0
Link PQ 0
Node PSPF 0
Node PQ 0
LFA 0 LFA SPF nodes: 0
Area 0 Area addresses: 1
PRC 0 Add: 0 modify: 0 delete: 0
Route summary 0.001 Summary route nodes: 0
Total 0.003
Log date : 2019-09-07 02:17:40
Log key : 8
Trigger count : 2
Trigger event : Logic interface changed
SPF details :
Phase Duration Description
TE tunnel ADJ 0 TE SPF nodes: 0
Topology 0 SPF nodes: 0
BSPF 0 Candidate NBRs: 0
TI-LFA prepare 0 TI-LFA links: 0, TI-LFA nodes: 0
Link PSPF 0
Link PQ 0
Node PSPF 0
Node PQ 0
LFA 0 LFA SPF nodes: 0
Area 0 Area addresses: 0
PRC 0 Add: 0 modify: 0 delete: 0
Route summary 0 Summary route nodes: 0
Total 0
Log date : 2019-09-07 02:17:38
Log key : 7
Trigger count : 1
Trigger event : Logic interface changed
SPF details :
Phase Duration Description
TE tunnel ADJ 0 TE SPF nodes: 0
Topology 0 SPF nodes: 0
BSPF 0 Candidate NBRs: 0
TI-LFA prepare 0 TI-LFA links: 0, TI-LFA nodes: 0
Link PSPF 0
Link PQ 0
Node PSPF 0
Node PQ 0
LFA 0 LFA SPF nodes: 0
Area 0 Area addresses: 0
PRC 0 Add: 0 modify: 0 delete: 0
Route summary 0 Summary route nodes: 0
Total 0
Log date : 2019-09-07 02:17:33
Log key : 6
Trigger count : 5
Trigger event : NextHop changed
SPF details :
Phase Duration Description
TE tunnel ADJ 0 TE SPF nodes: 0
Topology 0 SPF links changed: 1
BSPF 0 Candidate NBRs: 0
TI-LFA prepare 0 TI-LFA links: 0, TI-LFA nodes: 0
Link PSPF 0
Link PQ 0
Node PSPF 0
Node PQ 0
LFA 0 LFA SPF nodes: 0
Area 0 Area addresses: 0
PRC 0.001 Add: 0 modify: 0 delete: 0
Route summary 0 Summary route nodes: 0
Total 0.001
Log date : 2019-09-07 02:17:21
Log key : 5
Trigger count : 1
Trigger event : Direct route changed
SPF details :
Phase Duration Description
TE tunnel ADJ 0 TE SPF nodes: 0
Topology 0 SPF nodes: 0
BSPF 0 Candidate NBRs: 0
TI-LFA prepare 0 TI-LFA links: 0, TI-LFA nodes: 0
Link PSPF 0
Link PQ 0
Node PSPF 0
Node PQ 0
LFA 0 LFA SPF nodes: 0
Area 0 Area addresses: 0
PRC 0 Add: 0 modify: 0 delete: 0
Route summary 0 Summary route nodes: 0
Total 0
Log date : 2019-09-07 02:17:11
Log key : 4
Trigger count : 1
Trigger event : IPv6 mode changed
SPF details :
Phase Duration Description
TE tunnel ADJ 0 TE SPF nodes: 0
Topology 0.001 SPF nodes: 3
BSPF 0 Candidate NBRs: 0
TI-LFA prepare 0 TI-LFA links: 0, TI-LFA nodes: 0
Link PSPF 0
Link PQ 0
Node PSPF 0
Node PQ 0
LFA 0 LFA SPF nodes: 0
Area 0 Area addresses: 1
PRC 0 Add: 0 modify: 0 delete: 0
Route summary 0 Summary route nodes: 0
Total 0.001
Log date : 2019-09-07 01:09:33
Log key : 3
Trigger count : 2
Trigger event : DIS changed
SPF details :
Phase Duration Description
TE tunnel ADJ 0 TE SPF nodes: 0
Topology 0 SPF nodes: 3
BSPF 0 Candidate NBRs: 0
TI-LFA prepare 0 TI-LFA links: 0, TI-LFA nodes: 0
Link PSPF 0
Link PQ 0
Node PSPF 0
Node PQ 0
LFA 0 LFA SPF nodes: 0
Area 0 Area addresses: 1
PRC 0 Add: 0 modify: 0 delete: 0
Route summary 0 Summary route nodes: 0
Total 0
Log date : 2019-09-07 01:09:25
Log key : 2
Trigger count : 2
Trigger event : LSP updated
SPF details :
Phase Duration Description
TE tunnel ADJ 0 TE SPF nodes: 0
Topology 0 SPF links changed: 1
BSPF 0 Candidate NBRs: 0
TI-LFA prepare 0 TI-LFA links: 0, TI-LFA nodes: 0
Link PSPF 0
Link PQ 0
Node PSPF 0
Node PQ 0
LFA 0 LFA SPF nodes: 0
Area 0 Area addresses: 1
PRC 0 Add: 0 modify: 0 delete: 0
Route summary 0 Summary route nodes: 0
Total 0
Log date : 2019-09-07 01:08:49
Log key : 1
Trigger count : 1
Trigger event : Area address changed
SPF details :
Phase Duration Description
TE tunnel ADJ 0 TE SPF nodes: 0
Topology 0 SPF nodes: 0
BSPF 0 Candidate NBRs: 0
TI-LFA prepare 0 TI-LFA links: 0, TI-LFA nodes: 0
Link PSPF 0
Link PQ 0
Node PSPF 0
Node PQ 0
LFA 0 LFA SPF nodes: 0
Area 0 Area addresses: 1
PRC 0 Add: 0 modify: 0 delete: 0
Route summary 0 Summary route nodes: 0
Total 0
Table 13 Command output
|
Field |
Description |
|
Date |
Start date of route calculation. |
|
Time |
Start time of route calculation. |
|
Duration |
Route calculation duration in seconds. The value is accurate to six decimal places. |
|
Count |
Number of events that trigger the current route calculation. |
|
Trigger event |
Type of the most recent event that triggers route calculation: · NextHop changed. · DIS changed. · Interface metric changed. · Interface MTR information changed. · SPF link changed. · Default route changed. · Summary route changed. · IPv6 mode changed. · FRR configuration changed. · Prefix priority configuration changed. · Route preference changed. · ISPF configuration changed. · Import filter policy changed. · ECMP configuration changed. · PIC configuration changed. · Interface LFA exclude changed. · ATT configuration changed. · GR/NSR first SPF. · GR over. · T3 timeout. · Direct route changed. · Logic interface changed. · Route leakage configuration changed. · NSR over. · Entered overload state. · Exited overload state. · Area address changed. · Route policy changed. · Redistributed route updated. · LSP updated. · MT disabled. · MT enabled. · RIB smooth. |
|
Log date |
Generation time of the route calculation logs. |
|
Log key |
Route calculation log key. |
|
Trigger count |
Number of events that trigger the current route calculation. |
|
SPF details |
Detailed information about the route calculation phases. |
|
Phase |
Route calculation phase: · TE tunnel ADJ—TE tunnel adjacency calculation. This value is not supported in the current software version. · Topology—Topology calculation. · BSPF—Backup SPF calculation. · TI-LFA prepare—TI-LFA calculation preparation. This value is not supported in the current software version. · Link PSPF—SPF calculation after PSPF convergence for link protection. This value is not supported in the current software version. · Link PQ—P space and Q space calculation for link protection. This value is not supported in the current software version. · Node PSPF—SPF calculation after PSPF convergence for node protection. This value is not supported in the current software version. · Node PQ—P space and Q space calculation for node protection. This value is not supported in the current software version. · LFA—LFA calculation. · Area—Area calculation. · PRC—Prefix calculation. · Route summary—Route summarization calculation. |
|
Description |
Route calculation phase description: · TE SPF nodes—Number of SPF nodes for TE tunnel adjacency calculation. This value is not supported in the current software version. · SPF nodes—Number of SPF nodes for topology calculation. · Candidate NBRs—Number of candidate neighbors. · TI-LFA links—Number of TI-LFA protected links. This value is not supported in the current software version. · TI-LFA nodes—Number of TI-LFA protected nodes. This value is not supported in the current software version. · LFA SPF nodes—Number of SPF nodes for LFA calculation. · Area addresses—Number of area addresses. · Add, modify, and delete—Prefix calculation summary. · Last 10 routes—10 routes that are most recently calculated. · Summary route nodes—Number of summarized routes. |
|
Total |
Total duration time of all route calculation phases. |
Related commands
reset isis event-log spf
display isis graceful-restart status
Use display isis graceful-restart status to display IS-IS GR state.
Syntax
display isis graceful-restart status [ level-1 | level-2 ] [ process-id ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
level-1: Displays the IS-IS Level-1 GR state.
level-2: Displays the IS-IS Level-2 GR state.
process-id: Specifies a process by its ID in the range of 1 to 65535. If you do not specify this argument, the command displays GR state of all IS-IS processes.
Examples
# Display IS-IS GR state.
<Sysname> display isis graceful-restart status
Restart information for IS-IS(1)
--------------------------------
Restart status: COMPLETE
Restart phase: Finish
Restart t1: 3, count 10; Restart t2: 60; Restart t3: 300
SA Bit: supported
Level-1 restart information
---------------------------
Total number of interfaces: 1
Number of waiting LSPs: 0
Level-2 restart information
---------------------------
Total number of interfaces: 1
Number of waiting LSPs: 0
Table 14 Command output
|
Field |
Description |
|
Restart status |
Current GR state: · RESTARTING—In this state, forwarding can be ensured. · STARTING—In this state, forwarding cannot be ensured. · COMPLETE—GR is completed. |
|
Restart phase |
Current Restart phase: · Initialization. · LSDB synchronization. · TE tunnel prepare. · First SPF computation. · Redistribution. · Second SPF computation. · LSP stability—Ready to generate LSPs. · LSP generation. · Finish. |
|
Restart t1 |
T1 timer, in seconds. |
|
count |
Number of T1 timer expirations. |
|
Restart t2 |
T2 timer, in seconds. |
|
Restart t3 |
T3 timer, in seconds. |
|
SA Bit |
Whether SA is supported. |
|
Total number of interfaces |
Total number of IS-IS interfaces. |
|
Number of waiting LSPs |
Number of LSPs not obtained by the GR restarter from GR helpers during LSDB synchronization. |
display isis interface
Use display isis interface to display IS-IS interface information.
Syntax
display isis interface [ [ interface-type interface-number ] [ verbose ] | statistics ] [ process-id ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
interface-type interface-number: Displays information for a specified IS-IS interface. If you do not specify this argument, the command displays information about all interfaces.
verbose: Displays detailed information about an interface. If you do not specify this keyword, the command displays brief information about an interface.
statistics: Displays IS-IS interface statistics.
process-id: Displays IS-IS interface information for an IS-IS process specified by its ID in the range of 1 to 65535. If you do not specify this argument, the command displays interface information for all IS-IS processes.
Examples
# Display brief IS-IS interface information.
<Sysname> display isis interface
Interface information for IS-IS(1)
----------------------------------
Interface: Vlan-interface100
Index IPv4 state IPv6 state Circuit ID MTU Type DIS
00001 Up Down 1 1497 L1/L2 No/No
# Display detailed IS-IS interface information.
<Sysname> display isis interface verbose
Interface information for IS-IS(1)
----------------------------------
Interface: Vlan-interface100
Index IPv4 state IPv6 state Circuit ID MTU Type DIS
00001 Up Down 1 1497 L1/L2 No/No
SNPA address : 000c-29e8-1bd5
IP address : 192.168.220.10
Secondary IP address(es) :
IPv6 link-local address :
Extended circuit ID : 1
CSNP timer value : L1 10 L2 10
Hello timer value : 10
Hello multiplier value : 3
LSP timer value : L12 33
LSP transmit-throttle count : L12 5
Cost : L1 100 L2 100
Cost source : L1 Default L2 Default
IPv6 cost : L1 10 L2 10
IPv6 cost source : L1 Default L2 Default
Priority : L1 64 L2 64
Retransmit timer value : L12 5
LDP state : L1 Init L2 No-LDP
LDP sync state : L1 Init L2 Achieved
MPLS TE status : L1 Disabled L2 Disabled
IPv4 BFD : Disabled
IPv6 BFD : Disabled
IPv4 FRR LFA backup : L1 Enabled L2 Enabled
IPv6 FRR LFA backup : L1 Enabled L2 Enabled
IPv4 FRR TI-LFA : L1 Enabled L2 Enabled
IPv4 FRR remote-LFA : L1 Disabled L2 Disabled
IPv4 prefix suppression : Disabled
IPv6 prefix suppression : Disabled
IPv4 tag : 1
IPv6 tag : 4294967295
IPv4 primary path detection mode: BFD ctrl
IPv6 primary path detection mode: BFD ctrl
Table 15 Command output
|
Field |
Description |
|
Interface |
Interface type and number. |
|
Index |
Interface index. |
|
IPv4 state |
IPv4 state: · Up—The interface is up at both the link layer and network layer. · Down—The interface is down at the link layer and network layer. · Lnk:Up/IP:Dn—The interface is up at the link layer but is down at the network layer. |
|
IPv6 state |
IPv6 state: · Up—The interface is up at both the link layer and network layer. · Down—The interface is down at the link layer and network layer. · Lnk:Up/IP:Dn—The interface is up at the link layer but is down at the network layer. |
|
Circuit ID |
Circuit ID. If IS-IS is not successfully enabled on the broadcast interface, this field displays 0(Invalid). |
|
MTU |
Interface MTU. |
|
Type |
Interface link adjacency type. |
|
DIS |
Indicates whether the interface is elected as the Level-1/Level-2 DIS. In a P2P network, this field displays a hyphen (-) because DIS election is not performed. |
|
SNPA address |
Subnet access point address. |
|
IP address |
Primary IP address. |
|
Secondary IP address(es) |
Secondary IP addresses. |
|
IPv6 link-local address |
IPv6 link local address. |
|
Extended circuit ID |
Extended circuit ID for a P2P link. |
|
CSNP timer value |
Interval for sending CSNP packets. |
|
Hello timer value |
Interval for sending Hello packets. |
|
Hello multiplier value |
Number of invalid Hello packets. |
|
LSP timer value |
Minimum interval for sending LSP packets. |
|
LSP transmit-throttle count |
Number of LSP packets sent each time. |
|
Cost |
Cost of the interface. |
|
Cost source |
Link cost source: · Default—Default link cost. · Global—Global link cost. · Auto—Automatically calculated link cost. · Manual—Manually configured link cost. · IGP_LDP—Link cost advertised by LDP IGP. · LinkUp—Maximum link cost advertised during the specified period. This field is available in Release 6522 and later. |
|
IPv6 cost |
IPv6 link cost of the interface. |
|
IPv6 cost source |
IPv6 link cost source: · Default—Default link cost. · Global—Global link cost. · Auto—Automatically calculated link cost. · Manual—Manually configured link cost. · IGP_LDP—Link cost advertised by LDP IGP. · LinkUp—Maximum link cost advertised during the specified period. This field is available in Release 6522 and later. |
|
Priority |
DIS priority. |
|
Retransmit timer value |
Retransmission interval for LSPs on a P2P link. |
|
MPLS TE status |
This field is not supported in the current software version. MPLS TE status: Enabled or Disabled. |
|
LDP state |
LDP state: · Init—LDP is not reported. · No-LDP—LDP is not configured. · Not ready—LDP session is not established. · Ready—LDP session is established. |
|
LDP sync state |
LDP synchronization state: · Init—Initialized. · Achieved—Synchronized. · Max cost—Maintain the maximum cost. |
|
IPv4 BFD |
Whether BFD for IS-IS is enabled: · Disabled. · Enabled. |
|
IPv6 BFD |
Whether BFD for IPv6 IS-IS is enabled: · Disabled. · Enabled. |
|
IPv4 FRR LFA backup |
Whether LFA calculation is enabled for IPv4 FRR: · Disabled. · Enabled. |
|
IPv6 FRR LFA backup |
Whether LFA calculation is enabled for IPv6 FRR: · Disabled. · Enabled. |
|
IPv4 FRR TI-LFA |
This field is not supported in the current software version. Whether LFA calculation is enabled for IPv6 FRR: · Disabled. · Enabled. |
|
IPv4 FRR remote-LFA |
IPv4 remote LFA calculation status: · Disabled. · Enabled. |
|
IPv4 prefix suppression |
Whether IPv4 IS-IS prefix suppression is enabled: · Disabled. · Enabled. |
|
IPv6 prefix suppression |
Whether IPv6 IS-IS prefix suppression is enabled: · Disabled. · Enabled. |
|
IPv4 tag |
IPv4 tag value of the interface. |
|
IPv6 tag |
IPv6 tag value of the interface. |
|
IPv4 primary path detection mode |
IPv4 primary path detection mode: · BFD ctrl—BFD control packet mode. · BFD echo—BFD echo packet mode. |
|
IPv6 primary path detection mode |
IPv6 primary path detection mode: · BFD ctrl—BFD control packet mode. · BFD echo—BFD echo packet mode. |
# Display IS-IS interface statistics.
<Sysname> display isis interface statistics
Interface statistics information for IS-IS(1)
--------------------------------------------
Type IPv4 up/down IPv6 up/down
LAN 1/0 0/0
P2P 0/0 0/0
Table 16 Command output
|
Field |
Description |
|
Type |
Network type of the interface: · LAN—Broadcast network. · P2P—Point-to-point network. |
|
IPv4 up |
Number of IS-IS interfaces in up state. |
|
IPv4 down |
Number of IS-IS interfaces in down state. |
|
IPv6 up |
Number of IS-ISv6 interfaces in up state. |
|
IPv6 down |
Number of IS-ISv6 interfaces in down state. |
display isis interface hello-sent
Use display isis interface hello-sent to display information about the first three and last three packets sent by an interface.
Syntax
display isis interface [ interface-type interface-number ] hello-sent [ process-id ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
interface-type interface-number: Specifies an interface by its type and number. If you do not specify an interface, this command displays information about the first three and last three packets sent by all interfaces.
process-id: Specifies a process by its ID in the range of 1 to 65535. If you do not specify this argument, the command displays information for all IS-IS processes.
Examples
# Display information about the first three and last three packets sent by all interfaces for all IS-IS processes.
<Sysname> display isis interface hello-sent
Interface information for IS-IS(1)
----------------------------------
Interface: Vlan-interface10
First 3 L1 hello packets sent:
2021-10-21 15:10:14:687, succeeded
2021-10-21 15:10:14:698, succeeded
2021-10-21 15:10:22:506, succeeded
Last 3 L1 hello packets sent:
2021-10-21 16:19:11:724, succeeded
2021-10-21 16:19:19:440, succeeded
2021-10-21 16:19:27:858, succeeded
First 3 L2 hello packets sent:
2021-10-21 15:10:14:688, succeeded
2021-10-21 15:10:14:699, succeeded
2021-10-21 15:10:24:404, succeeded
Last 3 L2 hello packets sent:
2021-10-21 16:19:11:176, succeeded
2021-10-21 16:19:19:453, succeeded
2021-10-21 16:19:28:544, succeeded
Table 17 Command output
|
Field |
Description |
|
Interface |
Interface name. |
|
First 3 L1 hello packets sent |
Time when the first three Level-1 hello packets were sent and the packet sending result. |
|
Last 3 L1 hello packets sent |
Time when the last three Level-1 hello packets were sent before this command was executed and the packet sending result. |
|
First 3 L2 hello packets sent |
Time when the first three Level-2 hello packets were sent and the packet sending result. |
|
Last 3 L2 hello packets sent |
Time when the last three Level-2 hello packets were sent before this command was executed and the packet sending result. |
|
First 3 P2P hello packets sent |
Time when the first three P2P hello packets were sent and the packet sending result. |
|
Last 3 P2P hello packets sent |
Time when the last three P2P hello packets were sent before this command was executed and the packet sending result. |
display isis lsdb
Use display isis lsdb to display IS-IS LSDB information.
Syntax
display isis lsdb [ [ level-1 | level-2 ] | local | [ lsp-id lspid | lsp-name lspname ] | verbose ] * [ process-id ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
level-1: Displays the level-1 LSDB.
level-2: Displays the level-2 LSDB.
local: Displays LSP information generated locally.
lsp-id lspid: Specifies an LSP ID, in the form of sysID. Pseudo ID-fragment num, where sysID represents the originating node or pseudo node. Pseudo ID is separated by a dot from sysID and by a hyphen from fragment num.
lsp-name lspname: Specifies the LSP name, in the form of Symbolic name.Pseudo ID-fragment num, where Pseudo ID is separated by a dot from Symbolic name and by a hyphen from fragment num. If the Pseudo ID is 0, specify the LSP name in the form Symbolic name-fragment num.
verbose: Displays LSDB detailed information. If you do not specify this keyword, the command displays brief information about LSDB.
process-id: Specifies an IS-IS process by its ID in the range of 1 to 65535. If you do not specify this argument, the command displays LSDBs for all IS-IS processes.
Usage guidelines
If no level is specified, the command displays both Level-1 and Level-2 LSDB information.
Examples
# Display brief Level-1 LSDB information.
<Sysname> display isis lsdb level-1
Database information for IS-IS(1)
--------------------------------
ATTENTION: System is overloaded.
Overload is set for isolation.
Level-1 Link State Database
---------------------------
LSPID Seq Num Checksum Holdtime Length ATT/P/OL
-------------------------------------------------------------------------------
0000.0000.0001.00-00* 0x00000087 0xf846 1152 183 0/0/0
0000.0000.0003.00-00 0x00000005 0x4bee 520 177 0/0/0
0000.0000.0003.00-01 0x00000004 0x7245 520 45 0/0/0
0000.0000.0011.00-00 0x0000000b 0xcdf6 815 183 0/0/0
*-Self LSP, +-Self LSP(Extended), ATT-Attached, P-Partition, OL-Overload
# Display detailed Level-1 LSDB information.
<Sysname> display isis lsdb level-1 verbose
Database information for IS-IS(1)
--------------------------------
ATTENTION: System is overloaded.
Overload is set for isolation.
Level-1 Link State Database
---------------------------
LSPID Seq Num Checksum Holdtime Length ATT/P/OL
-------------------------------------------------------------------------------
0000.0000.0001.00-00* 0x00000080 0x73f 1185 183 0/0/0
Source 0000.0000.0001.00
IID 10
ITID 0
NLPID IPv4
Area address 10
IPv4 address 192.168.220.10
MT ID 0000 (-/-)
MT ID 0002 (-/-)
MT ID 0006 (-/-)
+NBR ID
0000.0000.0011.00 Cost: 100
IPv6 unicast NBR ID
6464.6464.6464.01 Cost: 10 MT ID: 2
MT NBR ID
6464.6464.6464.01 Cost: 10 MT ID: 6
+IP-Extended
192.168.220.0 255.255.255.0 Cost: 100
IPv4 unicast
1.1.1.1 255.255.255.255 Cost: 0 MT ID: 6
IPv4 unicast
10.10.10.0 255.255.255.0 Cost: 10 MT ID: 6
IPv6 unicast
1:1:1::1/128 Cost: 0 MT ID: 2
IPv6 unicast
10:10:10::/64 Cost: 10 MT ID: 2
Router ID 1.1.1.1
0000.0000.0003.00-00 0x00000005 0x4bee 887 177 0/0/0
Source 0000.0000.0003.00
NLPID IPv4
Area address 10
IPv4 address 10.10.10.10
IPv4 address 192.168.220.20
+NBR ID
0000.0000.0001.00 Cost: 10
Router ID 3.3.3.3
0000.0000.0003.00-01 0x00000004 0x7245 887 45 0/0/0
Source 0000.0000.0003.00
+IP-Extended
10.10.10.0 255.255.255.0 Cost: 10
+IP-Extended
192.168.220.0 255.255.255.0 Cost: 10
*-Self LSP, +-Self LSP(Extended), ATT-Attached, P-Partition, OL-Overload
Table 18 Command output
|
Field |
Description |
|
ATTENTION: System is overloaded |
The overload bit is set. |
|
Overload is set manually |
The overload bit is manually set. |
|
Overload is set for isolation |
The overload bit is set by the isolation feature. This field is available in Release 6522 and later. |
|
LSPID |
LSP ID. |
|
Seq Num |
LSP sequence number. |
|
Checksum |
LSP checksum. |
|
Holdtime |
LSP lifetime, which decreases as time elapses. |
|
Length |
LSP length. |
|
ATT/P/OL |
· ATT—Attach bit. · P—Partition bit. · OL—Overload bit. 1 means the LSP bit is set and 0 means the LSP bit is not set. |
|
Source |
System ID of the originating router. |
|
HOST NAME |
Dynamic host name of the originating router. |
|
ORG ID |
Original system ID of the virtual system of the originating router. |
|
IID |
Multi-instance process ID. |
|
ITID |
Multi-instance topology ID. The value of this field is fixed at 0 in the current software version. |
|
NLPID |
Network layer protocol the originating router runs. |
|
Area address |
Area address of the originating router. |
|
IPv4 address |
IP address of the originating router's IS-IS interface. |
|
IPv6 address |
IPv6 address of the originating router's IS-ISv6 interface. |
|
MT ID 0000 (-/-) MT ID 0002 (-/-) MT ID 0006 (-/-) |
Topology supported by the originating router (0/0/0 indicates ATT/P/OL): · 0000—Base topology. · 0002—IPv6 unicast topology. · 0006—IPv4 unicast topology. · (-/-)—Attach bit/overload bit. |
|
NBR ID |
Neighbor ID of the originating router. |
|
MT NBR ID |
IPv4 unicast topology neighbor information about the originating router. |
|
IPv6 unicast NBR ID |
IPv6 unicast neighbor information about the originating router. |
|
Router ID |
Router ID. |
|
IP-Internal |
Internal IP address and mask of the originating router. |
|
IP-External |
External IP address and mask of the originating router. |
|
IP-Extended |
Extended information about the originating router, including the IP address, subnet mask, and prefix SID information. |
|
Cost |
Cost. |
|
Auth |
Authentication information of the originating router. |
|
IPV6 |
Internal IPv6 address and prefix of the originating router. |
|
IPV6-Ext |
External IPv6 address and prefix of the originating router. |
|
IPv4 unicast |
IPv4 unicast reachability information about the originating router. |
|
IPv6 unicast |
Internal IPv6 unicast reachability information about the originating router. |
|
IPv6 unicast-ext |
External IPv6 unicast reachability information about the originating router. |
display isis lsdb statistics
Use display isis lsdb statistics to display IS-IS LSDB statistics.
Syntax
display isis lsdb statistics [ level-1 | level-2 ] [ process-id ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
level-1: Displays Level-1 LSDB statistics.
level-2: Displays Level-2 LSDB statistics.
process-id: Specifies an IS-IS process by its ID in the range of 1 to 65535. If you do not specify this argument, the command displays LSDB statistics for all IS-IS processes.
Usage guidelines
If you do not specify a level, the command displays both Level-1 and Level-2 LSDB statistics.
Examples
# Display IS-IS LSDB statistics.
<Sysname> display isis lsdb statistics
Database Statistics information for IS-IS(1)
-----------------------------------------
Level-1 LSDB Statistics
-----------------------
LSP source ID LSP count
--------------------------------------------------------------------------------
Total 333
1111.1111.1111.00 1
2222.2222.2222.00 256
2222.2222.2222.01 1
bbbb.bbbb.0001.00 75
Level-2 LSDB Statistics
-----------------------
LSP source ID LSP count
--------------------------------------------------------------------------------
Total 663
1111.1111.1111.00 256
2222.2222.2222.00 256
2222.2222.2222.01 1
aaaa.aaaa.0001.00 75
bbbb.bbbb.0001.00 75
Table 19 Command output
|
Field |
Description |
|
LSP count |
Number of LSPs generated by a source. |
|
Total |
Number of LSPs generated by all sources. |
Related commands
display isis lsdb
display isis name-table
Use display isis name-table to display the host name-to-system ID mapping table.
Syntax
display isis name-table [ process-id ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
process-id: Displays the host name to system ID mapping table for an IS-IS process specified by its ID in the range of 1 to 65535. If you do not specify this argument, the command displays the host name to system ID mapping table for all IS-IS processes.
Examples
# Display the IS-IS host name to system ID mapping table.
<Sysname> display isis name-table
Name table information for IS-IS(1)
-----------------------------------
System ID Hostname Type Level
6789.0000.0001 RUTA DYNAMIC Level-1
6789.0000.0001 RUTA DYNAMIC Level-2
0000.0000.0041 RUTB STATIC Level-1
0000.0000.0041 RUTB STATIC Level-2
6789.0000.0001.01 DIS-A DYNAMIC Level-1
0000.0000.0041.01 DIS-B DYNAMIC Level-2
Table 20 Command output
|
Field |
Description |
|
System ID |
System ID. |
|
Hostname |
Host name. |
|
Type |
Mapping type: · STATIC. · DYNAMIC. |
|
Level |
Level on which the system ID-to-host name mapping takes effect: Level-1 or Level-2. |
display isis non-stop-routing status
Use display isis non-stop-routing status to display IS-IS NSR status.
Syntax
display isis non-stop-routing status
Views
Any view
Predefined user roles
network-admin
network-operator
Examples
# Display IS-IS NSR status.
<Sysname> display isis non-stop-routing status
Nonstop Routing information for IS-IS(1)
----------------------------------------
NSR phase: Finish
Table 21 Command output
|
Field |
Description |
|
NSR phase |
NSR phase: · Initialization. · Smooth. · TE tunnel prepare. · First SPF computation. · Redistribution. · Second SPF computation. · LSP stability—Ready to generate LSPs. · LSP generation. · Finish. |
display isis packet
Use display isis packet to display IS-IS packet statistics.
Syntax
display isis packet { csnp | hello | lsp | psnp } by-interface [ verbose ] [ interface-type interface-number ] [ process-id ]
display isis packet { csnp | hello | lsp | psnp } [ verbose ] [ process-id ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
csnp: Displays CSNP packet statistics.
hello: Displays hello packet statistics.
lsp: Displays LSP packet statistics.
psnp: Displays PSNP packet statistics.
by-interface: Displays packet statistics on a per-interface basis.
verbose: Displays detailed packet statistics.
interface-type interface-number: Specifies an interface by its type and number. If you do not specify this option, the command displays IS-IS packet statistics for all interfaces.
process-id: Specifies an IS-IS process by its ID in the range of 1 to 65535. If you do not specify this argument, the command displays packet statistics for all IS-IS processes.
Examples
# Display detailed hello packet statistics on a per-interface basis.
<Sysname> display isis packet hello by-interface verbose
Hello packet information for IS-IS(1)
-------------------------------------
Interface: Vlan-interface10
Total output packets : 0 Total output error packets : 0
Total input packets : 0 Total input error packets : 0
Total output packets with 1.5 hello intervals : 0
Total input packets with 1.5 hello intervals : 0
Input packets with errors
Bad packet length : 0 Bad header length : 0
Jumbo packet : 0 Bad protocol description : 0
Bad protocol ID : 0 Bad protocol version : 0
Unknown packet type : 0 Bad max area count : 0
Bad system ID length : 0 Bad circuit type : 0
Bad auth TLV : 0 Bad area address TLV : 0
Auth failure : 0 Excessive area addresses : 0
Bad NBR TLV : 0 Excessive auth TLVs : 0
Excessive IF Addr TLVs : 0 Excessive IF addresses : 0
Bad IF address TLV : 0 Duplicate system ID : 0
Bad TLV length : 0 Bad IP address : 0
Duplicate IP address : 0 Mismatched area address : 0
Mismatched protocol : 0 Mismatched network type : 0
Bad IPv6 address TLV : 0 Bad IPv6 address : 0
Duplicate IPv6 address : 0 Bad MT ID TLV : 0
SNPA conflict (LAN) : 0 Excessive NBR SNPAs (LAN) : 0
Mismatched level (LAN) : 0 Bad 3-Way option TLV (P2P) : 0
No common MT ID (P2P) : 0 Bad circuit ID (P2P) : 0
Bad IID TLV : 0
# Display detailed hello packet statistics.
<Sysname> display isis packet hello verbose
Hello packet information for IS-IS(1)
-------------------------------------
Total output packets : 0 Total output error packets : 0
Total input packets : 0 Total input error packets : 0
Total output packets with 1.5 hello intervals : 0
Total input packets with 1.5 hello intervals : 0
Input packets with errors
Bad packet length : 0 Bad header length : 0
Jumbo packet : 0 Bad protocol description : 0
Bad protocol ID : 0 Bad protocol version : 0
Unknown packet type : 0 Bad max area count : 0
Bad system ID length : 0 Bad circuit type : 0
Bad auth TLV : 0 Bad area address TLV : 0
Auth failure : 0 Excessive area addresses : 0
Bad NBR TLV : 0 Excessive auth TLVs : 0
Excessive IF Addr TLVs : 0 Excessive IF addresses : 0
Bad IF address TLV : 0 Duplicate system ID : 0
Bad TLV length : 0 Bad IP address : 0
Duplicate IP address : 0 Mismatched area address : 0
Mismatched protocol : 0 Mismatched network type : 0
Bad IPv6 address TLV : 0 Bad IPv6 address : 0
Duplicate IPv6 address : 0 Bad MT ID TLV : 0
SNPA conflict (LAN) : 0 Excessive NBR SNPAs (LAN) : 0
Mismatched level (LAN) : 0 Bad 3-Way option TLV (P2P) : 0
No common MT ID (P2P) : 0 Bad circuit ID (P2P) : 0
Bad IID TLV : 0
Table 22 Command output
|
Field |
Description |
|
Number of hello packets that were sent at intervals greater than 1.5 times the hello interval. |
|
|
Total input packets with 1.5 hello intervals |
Number of hello packets that were received at intervals greater than 1.5 times the hello interval. |
|
Input packets with errors |
Statistics for packets with the following errors: · Bad packet length—Invalid packet length. · Bad header length—Invalid header length. · Jumbo packet—The packet length exceeds the buffer size or the interface MTU. · Bad protocol description—Invalid protocol description. · Bad protocol ID—Invalid protocol identifier. · Bad protocol version—Invalid protocol version. · Unknown packet type—Unknown packet type. · Bad max area count—Invalid maximum number of area addresses. · Bad system ID length—Invalid system ID length. · Bad circuit type—Invalid interface type. · Bad auth TLV—Invalid authentication TLV. · Bad area address TLV—Invalid area address TLV. · Auth failure—Authentication failure. · Excessive area addresses—Excessive area addresses. · Bad NBR TLV—Invalid neighbor TLV. · Excessive auth TLVs—Excessive authentication TLVs. · Excessive IF Addr TLVs—Excessive interface address TLVs. · Excessive IF addresses—Excessive interface addresses. · Bad IF address TLV—Invalid interface address TLV. · Duplicate system ID—Duplicate system IDs. · Bad TLV length—Invalid TLV length. · Bad IP address—The IP address does not belong to the same network as the local interface address. · Duplicate IP address—Duplicate IP addresses. · Mismatched area address—Mismatched area addresses. · Mismatched protocol—Mismatched protocols. · Mismatched network type—Mismatched network types. · Bad IPv6 address TLV—Invalid IPv6 address TLV. · Bad IPv6 address—Invalid IPv6 address. · Duplicate IPv6 address—Duplicate IPv6 addresses. · Bad MT ID TLV—Invalid topology ID TLV. · SNPA conflict (LAN)—SNPA conflict. · Excessive NBR SNPAs (LAN)—Excessive neighbor SNPAs. · Mismatched level (LAN)—Mismatched levels. · Bad 3-Way option TLV (P2P)—Invalid three-way handshake information. · No common MT ID (P2P)—No common topology ID. · Bad circuit ID (P2P)—Invalid circuit ID. · Bad IID TLV—The multi-instance TLV length is smaller than the minimum length specified in the protocol. |
# Display detailed LSP packet statistics on a per-interface basis.
<Sysname> display isis packet lsp by-interface verbose
LSP packet information for IS-IS(1)
-----------------------------------
Interface: Vlan-interface10
Total output packets : 0 Total output error packets : 0
Total input packets : 0 Total input error packets : 0
Input packets with errors
Bad packet length : 0 Bad header length : 0
Jumbo packet : 0 SNPA conflict (LAN) : 0
Smaller than header : 0 Bad protocol description : 0
Bad protocol ID : 0 Bad protocol version : 0
Unknown packet type : 0 Bad max area count : 0
No active NBR : 0 Bad system ID length : 0
Mismatched level : 0 Illegal IS type : 0
Sequence number is 0 : 0 Checksum is 0 : 0
Incorrect checksum : 0 Bad TLV length : 0
Mismatched protocol : 0 Bad auth TLV : 0
Auth failure : 0 Excessive auth TLVs : 0
Bad NBR TLV : 0 Bad extended IS TLV : 0
Bad IF address TLV : 0 Bad IPv6 IF address TLV : 0
Bad alias TLV : 0 Bad IP reachability TLV : 0
Bad MT IS TLV : 0 Bad area address TLV : 0
Bad MT ID TLV : 0 Bad MT IP TLV : 0
Bad MT IPv6 TLV : 0 Bad IPv6 reachability TLV : 0
Bad router ID TLV : 0 Bad IID TLV : 0
# Display detailed LSP packet statistics.
<Sysname> display isis packet lsp verbose
LSP packet information for IS-IS(1)
-----------------------------------
Total output packets : 0 Total output error packets : 0
Total input packets : 0 Total input error packets : 0
Input packets with errors
Bad packet length : 0 Bad header length : 0
Jumbo packet : 0 SNPA conflict (LAN) : 0
Smaller than header : 0 Bad protocol description : 0
Bad protocol ID : 0 Bad protocol version : 0
Unknown packet type : 0 Bad max area count : 0
No active NBR : 0 Bad system ID length : 0
Mismatched level : 0 Illegal IS type : 0
Sequence number is 0 : 0 Checksum is 0 : 0
Incorrect checksum : 0 Bad TLV length : 0
Mismatched protocol : 0 Bad auth TLV : 0
Auth failure : 0 Excessive auth TLVs : 0
Bad NBR TLV : 0 Bad extended IS TLV : 0
Bad IF address TLV : 0 Bad IPv6 IF address TLV : 0
Bad alias TLV : 0 Bad IP reachability TLV : 0
Bad MT IS TLV : 0 Bad area address TLV : 0
Bad MT ID TLV : 0 Bad MT IP TLV : 0
Bad MT IPv6 TLV : 0 Bad IPv6 reachability TLV : 0
Bad router ID TLV : 0 Bad IID TLV : 0
Table 23 Command output
|
Field |
Description |
|
Input packets with errors |
Statistics for packets with the following errors: · Bad packet length—Invalid packet length. · Bad header length—Invalid header length. · Jumbo packet—The packet length exceeds the maximum length of packets that can be received. · SNPA conflict (LAN)—SNPA conflict. · Smaller than header—The packet length is smaller than the fixed header length. · Bad protocol description—Invalid protocol description. · Bad protocol ID—Invalid protocol identifier. · Bad protocol version—Invalid protocol version. · Unknown packet type—Unknown packet type. · Bad max area count—Invalid maximum number of area addresses. · No active NBR—The packet is from an unknown neighbor. · Bad system ID length—Invalid system ID length. · Mismatched level—Mismatched levels. · Illegal IS type—Invalid IS type. · Sequence number is 0—The sequence number is 0. · Checksum is 0—The checksum is 0. · Incorrect checksum—Incorrect checksum. · Bad TLV length—Invalid TLV length. · Mismatched protocol—Mismatched protocols. · Bad auth TLV—Invalid authentication TLV. · Auth failure—Authentication failure. · Excessive auth TLVs—Excessive authentication TLVs. · Bad NBR TLV—Invalid neighbor TLV. · Bad extended IS TLV—Invalid extended IS TLV. · Bad IF address TLV—Invalid interface address TLV. · Bad IPv6 IF address TLV—Invalid IPv6 interface address TLV. · Bad alias TLV—Invalid alias TLV. · Bad IP reachability TLV—Invalid IP reachability TLV. · Bad MT IS TLV—Invalid topology IS TLV. · Bad area address TLV—Invalid area address TLV. · Bad MT ID TLV—Invalid topology ID TLV. · Bad MT IP TLV—Invalid IPv4 topology TLV. · Bad MT IPv6 TLV—Invalid IPv6 topology TLV. · Bad IPv6 reachability TLV—Invalid IPv6 reachability TLV. · Bad router ID TLV—Invalid router ID TLV. · Bad IID TLV—The multi-instance TLV length is smaller than the minimum length specified in the protocol. |
# Display detailed CSNP packet statistics on a per-interface basis.
<Sysname> display isis packet csnp by-interface verbose
CSNP packet information for IS-IS(1)
------------------------------------
Interface: Vlan-interface10
Total output packets : 0 Total output error packets : 0
Total input packets : 0 Total input error packets : 0
Input packets with errors
Bad packet length : 0 Bad header length : 0
Jumbo packet : 0 SNPA conflict (LAN) : 0
Smaller than header : 0 Bad protocol description : 0
Bad protocol ID : 0 Bad protocol version : 0
Unknown packet type : 0 Bad max area count : 0
No active NBR : 0 Bad system ID length : 0
Mismatched level : 0 Bad TLV length : 0
Auth failure : 0 Bad auth TLV : 0
Bad LSP TLV length : 0 Excessive auth TLVs : 0
Excessive LSPs : 0 Bad LSP ID : 0
Bad IID TLV : 0
# Display detailed CSNP packet statistics.
<Sysname> display isis packet csnp verbose
CSNP packet information for IS-IS(1)
------------------------------------
Total output packets : 0 Total output error packets : 0
Total input packets : 0 Total input error packets : 0
Input packets with errors
Bad packet length : 0 Bad header length : 0
Jumbo packet : 0 SNPA conflict (LAN) : 0
Smaller than header : 0 Bad protocol description : 0
Bad protocol ID : 0 Bad protocol version : 0
Unknown packet type : 0 Bad max area count : 0
No active NBR : 0 Bad system ID length : 0
Mismatched level : 0 Bad TLV length : 0
Auth failure : 0 Bad auth TLV : 0
Bad LSP TLV length : 0 Excessive auth TLVs : 0
Excessive LSPs : 0 Bad LSP ID : 0
Bad IID TLV : 0
Table 24 Command output
|
Field |
Description |
|
Input packets with errors |
Statistics for packets with the following errors: · Bad packet length—Invalid packet length. · Bad header length—Invalid header length. · Jumbo packet—The packet length exceeds the maximum length of packets that can be received. · SNPA conflict (LAN)—SNPA conflict. · Smaller than header—The packet length is smaller than the fixed header length. · Bad protocol description—Invalid protocol description. · Bad protocol ID—Invalid protocol identifier. · Bad protocol version—Invalid protocol version. · Unknown packet type—Unknown packet type. · Bad max area count—Invalid maximum number of area addresses. · No active NBR—The packet is from an unknown neighbor. · Bad system ID length—Invalid system ID length. · Mismatched level—Mismatched levels. · Bad TLV length—Invalid TLV length. · Auth failure—Authentication failure. · Bad auth TLV—Invalid authentication TLV. · Bad LSP TLV length—Invalid LSP TLV length. · Excessive auth TLVs—Excessive authentication TLVs. · Excessive LSPs—Excessive LSPs. · Bad LSP ID—Invalid LSP ID. · Bad IID TLV—The multi-instance TLV length is smaller than the minimum length specified in the protocol. |
# Display detailed PSNP packet statistics on a per-interface basis.
<Sysname> display isis packet psnp by-interface verbose
PSNP packet information for IS-IS(1)
------------------------------------
Interface: Vlan-interface10
Total output packets : 0 Total output error packets : 0
Total input packets : 0 Total input error packets : 0
Input packets with errors
Bad packet length : 0 Bad header length : 0
Jumbo packet : 0 SNPA conflict (LAN) : 0
Smaller than header : 0 Bad protocol description : 0
Bad protocol ID : 0 Bad protocol version : 0
Unknown packet type : 0 Bad max area count : 0
No active NBR : 0 Bad system ID length : 0
Mismatched level : 0 Bad TLV length : 0
Auth failure : 0 Bad auth TLV : 0
Bad LSP TLV length : 0 Excessive auth TLVs : 0
Excessive LSPs : 0 Bad LSP ID : 0
Bad IID TLV : 0
# Display detailed PSNP packet statistics.
<Sysname> display isis packet psnp verbose
PSNP packet information for IS-IS(1)
------------------------------------
Total output packets : 0 Total output error packets : 0
Total input packets : 0 Total input error packets : 0
Input packets with errors
Bad packet length : 0 Bad header length : 0
Jumbo packet : 0 SNPA conflict (LAN) : 0
Smaller than header : 0 Bad protocol description : 0
Bad protocol ID : 0 Bad protocol version : 0
Unknown packet type : 0 Bad max area count : 0
No active NBR : 0 Bad system ID length : 0
Mismatched level : 0 Bad TLV length : 0
Auth failure : 0 Bad auth TLV : 0
Bad LSP TLV length : 0 Excessive auth TLVs : 0
Excessive LSPs : 0 Bad LSP ID : 0
Bad IID TLV : 0
Table 25 Command output
|
Field |
Description |
|
Input packets with errors |
Statistics for packets with the following errors: · Bad packet length—Invalid packet length. · Bad header length—Invalid header length. · Jumbo packet—The packet length exceeds the maximum length of packets that can be received. · SNPA conflict (LAN)—SNPA conflict. · Smaller than header—The packet length is smaller than the fixed header length. · Bad protocol description—Invalid protocol description. · Bad protocol ID—Invalid protocol identifier. · Bad protocol version—Invalid protocol version. · Unknown packet type—Unknown packet type. · Bad max area count—Invalid maximum number of area addresses. · No active NBR—The packet is from an unknown neighbor. · Bad system ID length—Invalid system ID length. · Mismatched level—Mismatched levels. · Bad TLV length—Invalid TLV length. · Auth failure—Authentication failure. · Bad auth TLV—Invalid authentication TLV. · Bad LSP TLV length—Invalid LSP TLV length. · Excessive auth TLVs—Excessive authentication TLVs. · Excessive LSPs—Excessive LSPs. · Bad LSP ID—Invalid LSP ID. · Bad IID TLV—The multi-instance TLV length is smaller than the minimum length specified in the protocol. |
Related commands
reset isis packet
display isis peer
Use display isis peer to display IS-IS neighbor information.
Syntax
display isis peer [ statistics | verbose ] [ process-id ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
statistics: Displays IS-IS neighbor statistics.
verbose: Displays detailed IS-IS neighbor information. If you do not specify this keyword, the command displays brief IS-IS neighbor information.
process-id: Displays IS-IS neighbor information for an IS-IS process specified by its ID in the range of 1 to 65535. If you do not specify this argument, the command displays neighbor information for all IS-IS processes.
Examples
# Display brief IS-IS neighbor information.
<Sysname> display isis peer
Peer information for IS-IS(1)
-----------------------------
System ID: 0000.0000.0001
Interface: Vlan100 Circuit Id: 0000.0000.0001.01
State: Up HoldTime: 27s Type: L1(L1L2) PRI: 64
System ID: 0000.0000.0001
Interface: Vlan100 Circuit Id: 0000.0000.0001.01
State: Up HoldTime: 27s Type: L2(L1L2) PRI: 64
# Display detailed IS-IS neighbor information.
<Sysname> display isis peer verbose
Peer information for IS-IS(1)
----------------------------
System ID: 0000.1111.2222
Interface: Vlan100 Circuit Id: 0000.1111.2222.01
State: Up Holdtime: 6s Type: L1(L1L2) PRI: 64
Area address(es): 49
Peer IP address(es): 12.0.0.2
Peer local circuit ID: 1
Peer circuit SNPA address: 000c-293b-c4be
Uptime: 00:05:07
Adj protocol: IPv4
Adj P2P three-way handshake: No
Graceful Restart capable
Restarting signal: No
Suppress adjacency advertisement: No
Local topology:
0
Remote topology:
0 2
System ID: 0000.0000.0002
Interface: Vlan101 Circuit Id: 001
State: Up HoldTime: 27s Type: L1L2 PRI: --
Area address(es): 49
Peer IP address(es): 192.168.220.30
Peer local circuit ID: 1
Peer circuit SNPA address: 000c-29fd-ed69
Uptime: 00:05:07
Adj protocol: IPv4
Adj P2P three-way handshake: Yes
Peer extended circuit ID: 2
Graceful Restart capable
Restarting signal: No
Suppress adjacency advertisement: No
Table 26 Command output
|
Field |
Description |
|
System ID |
System ID of the neighbor. |
|
Interface |
Interface connecting to the neighbor. |
|
Circuit Id |
Circuit ID. |
|
State |
Circuit state. |
|
HoldTime |
Within the holdtime, if no hellos are received from the neighbor, the neighbor is considered down. If a hello is received, the holdtime is reset to the initial value. |
|
Type |
Circuit type: · L1—Means the circuit type is Level-1 and the neighbor is a Level-1 router. · L2—Means the circuit type is Level-2 and the neighbor is a Level-2 router. · L1(L1L2)—Means the circuit type is Level-1 and the neighbor is a Level-1-2 router. · L2(L1L2)—Means the circuit type is Level-2 and the neighbor is a Level-1-2 router. |
|
PRI |
DIS priority of the neighbor. |
|
Area address(es) |
Area address of the neighbor. |
|
Peer IP address(es) |
IP address of the neighbor. |
|
Peer IPv6 address(es) |
IPv6 address of the neighbor. |
|
Uptime |
Time elapsed since the neighbor relationship was formed. |
|
Adj Protocol |
Adjacency protocol: IPv4 or IPv6. |
|
Peer local circuit ID |
Circuit ID of the neighbor. |
|
Peer circuit SNPA address |
SNPA address of the neighbor. |
|
Adj P2P three-way handshake |
Indicates whether the neighbor supports P2P three-way handshake. |
|
Peer extended circuit ID |
Extended circuit ID of the neighbor interface. This field is available when the neighbor supports three-way handshake. |
|
Graceful Restart capable |
The neighbor has the GR helper capability. |
|
Restarting signal |
RR flag. |
|
Suppress adjacency advertisement |
SA flag. |
|
Local topology |
List of topologies supported by the local interface. |
|
Remote topology |
List of topologies supported by the neighbor interface. |
# Display IS-IS neighbor statistics.
<Sysname> display isis peer statistics
Peer Statistics information for IS-IS(1)
---------------------------------------
Type IPv4 Up/Init IPv6 Up/Init
LAN Level-1 1/0 0/0
LAN Level-2 1/0 0/0
P2P 0/0 0/0
Table 27 Command output
|
Field |
Description |
|
Type |
Neighbor type: · LAN Level-1—Number of Level-1 neighbors whose network type is broadcast. · LAN Level-2—Number of Level-2 neighbors whose network type is broadcast. · P2P—Number of neighbors whose network type is P2P. |
|
IPv4 Up |
Number of IPv4 neighbors in up state. |
|
IPv4 Init |
Number of IPv4 neighbors in init state. |
|
IPv6 Up |
Number of IPv6 neighbors in up state. |
|
IPv6 Init |
Number of IPv6 neighbors in init state. |
display isis peer hello-received
Use display isis peer hello-received to display information about hello packets received from neighbors.
Syntax
display isis peer hello-received [ process-id ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
process-id: Specifies a process by its ID in the range of 1 to 65535. If you do not specify this argument, the command displays information about hello packets received from neighbors for all IS-IS processes.
Examples
# Display information about hello packets received from neighbors for IS-IS process 1.
<Sysname> display isis peer hello-received 1
Peer Hello information for IS-IS(1)
-----------------------------------
System ID: 0000.0000.0002
Interface: Vlan10 Circuit Id: 0000.0000.0002.01
First 3 L1 hello packets received:
2021-10-21 15:10:14:687
2021-10-21 15:10:14:732
2021-10-21 15:10:23:618
Last 3 L1 hello packets received:
2021-10-21 16:21:39:078
2021-10-21 16:21:42:383
2021-10-21 16:21:45:721
System ID: 0000.0000.0003
Interface: Vlan10 Circuit Id: 0000.0000.0002.01
First 3 L2 hello packets received:
2021-10-21 15:10:14:688
2021-10-21 15:10:14:734
2021-10-21 15:10:24:090
Last 3 L2 hello packets received:
2021-10-21 16:21:39:078
2021-10-21 16:21:42:383
2021-10-21 16:21:45:722
Table 28 Command output
|
Field |
Description |
|
System ID |
System ID of the neighbor. |
|
Interface |
Local interface connected to the neighbor. |
|
Circuit ID |
Circuit ID. |
|
First 3 xx hello packets received |
Time when the first three hello packets were received. The xx argument represents the hello packet type: · L1—Level-1 hello packets. · L2—Level-2 hello packets. · P2P—P2P hello packets. |
|
Last 3 xx hello packets received |
Time when the last three hello packets were received before this command was executed. The xx argument represents the hello packet type: · L1—Level-1 hello packets. · L2—Level-2 hello packets. · P2P—P2P hello packets. |
display isis redistribute
Use display isis redistribute to display the redistributed IS-IS routing information.
Syntax
display isis redistribute [ ipv4 [ ip-address mask-length ] | ipv6 [ ipv6-address prefix-length ] ] [ level-1 | level-2 ] [ process-id ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
ipv4: Displays the redistributed IPv4 routing information.
ipv6: Displays the redistributed IPv6 routing information.
ipv6-address prefix-length: Displays redistributed routes for the specified IPv6 address and mask length. The value range for the prefix-length argument is 1 to 128.
ip-address mask-length: Specifies the destination IP address and mask length.
process-id: Specifies the IS-IS process by its ID in the range of 1 to 65535.
level-1: Displays the IS-IS Level-1 routing information.
level-2: Displays the IS-IS Level-2 routing information.
Usage guidelines
If you do not specify the ipv4 or ipv6 keyword, the command displays redistributed IPv4 routing information.
If you do not specify an IS-IS level, this command displays both Level-1 and Level-2 routing information.
Examples
# Display redistributed IPv4 IS-IS routing information.
<Sysname> display isis redistribute 1
Route information for IS-IS(1)
------------------------------
Level-1 IPv4 Redistribute Table
--------------------------------
Type IPv4 Destination IntCost ExtCost Tag State
--------------------------------------------------------------------------------
D 192.168.30.0/24 0 0 Active
D 11.11.11.11/32 0 0
D 10.10.10.0/24 0 0
Table 29 Command output
|
Field |
Description |
|
Route information for IS-IS(1) |
IS-IS process of the redistributed routing information. |
|
Level-1 IPv4 Redistribute Table |
Redistributed IPv4 routing information of IS-IS Level-1. |
|
Level-2 IPv4 Redistribute Table |
Redistributed IPv4 routing information of IS-IS Level-2. |
|
Type |
Redistributed route type. |
|
IPV4 Destination |
IPv4 destination address. |
|
IntCost |
Internal cost of the route. |
|
ExtCost |
External cost of the route. |
|
Tag |
Tag value. |
|
State |
Indicates whether the route is valid. |
# Display redistributed IPv6 IS-IS routing information.
<Sysname> display isis redistribute ipv6 1
Route information for IS-IS(1)
------------------------------
Level-1 IPv6 Redistribute Table
--------------------------------
Type : direct Destination: 12:1::/64
IntCost : 0 Tag :
State : Active
Level-2 IPv6 Redistribute Table
--------------------------------
Type : direct Destination: 12:1::/64
IntCost : 0 Tag :
State : Active
Table 30 Command output
|
Field |
Description |
|
Route information for IS-IS(1) |
Redistributed routing information for IPv6 IS-IS process 1. |
|
Level-1 IPv6 Redistribute Table |
Redistributed IPv6 IS-IS Level-1 routing information. |
|
Level-2 IPv6 Redistribute Table |
Redistributed IPv6 IS-IS Level-2 routing information. |
|
Type |
Redistributed route types: · Direct. · IS-ISv6. · Static. · OSPFv3. · BGP4+. · RIPng. |
|
Destination |
IPv6 destination address. |
|
IntCost |
Internal route cost. |
|
Tag |
Tag value. |
|
State |
Indicates whether the redistributed route is valid. |
display isis route
Use display isis route to display IS-IS routing information.
Syntax
display isis route [ ipv4 [ ip-address mask-length ] | ipv6 [ ipv6-address prefix-length ] ] [ [ level-1 | level-2 ] | verbose ] * [ process-id ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
ipv4: Displays IPv4 IS-IS routing information.
ip-address mask-length: Displays IPv4 IS-IS routing information for the specified IP address. The mask-length argument is in the range of 0 to 32.
ipv6: Displays IPv6 IS-IS routing information.
ipv6-address prefix-length: Displays IPv6 IS-IS routing information for the specified IPv6 address. The prefix-length argument is in the range of 0 to 128.
verbose: Displays detailed IS-IS routing information. If you do not specify this keyword, the command displays brief IS-IS routing information
process-id: Displays IS-IS routing information for an IS-IS process specified by its ID in the range of 1 to 65535. If you do not specify an IS-IS process, this command displays routing information for all IS-IS processes.
level-1: Displays Level-1 IS-IS routes.
level-2: Displays Level-2 IS-IS routes.
Usage guidelines
If you do not specify the ipv4 or ipv6 keyword, the command displays IPv4 IS-IS routing information.
If you do not specify a level, this command displays both Level-1 and Level-2 routing information.
Examples
# Display brief IPv4 IS-IS routing information.
<Sysname> display isis route
Route information for IS-IS(1)
-----------------------------
Level-1 IPv4 Forwarding Table
-----------------------------
IPv4 Destination IntCost ExtCost ExitInterface NextHop Flags
-------------------------------------------------------------------------------
8.8.8.0/24 10 NULL Vlan100 Direct D/L/-
9.9.9.0/24 20 NULL Vlan100 8.8.8.5 R/L/-
Flags: D-Direct, R-Added to Rib, L-Advertised in LSPs, U-Up/Down Bit Set
Level-2 IPv4 Forwarding Table
-----------------------------
IPv4 Destination IntCost ExtCost ExitInterface NextHop Flags
-------------------------------------------------------------------------------
8.8.8.0/24 10 NULL D/L/-
Flags: D-Direct, R-Added to Rib, L-Advertised in LSPs, U-Up/Down Bit Set
Table 31 Command output
|
Field |
Description |
|
Route information for IS-IS(1) |
Route information for IS-IS process 1. |
|
Level-1 IPv4 Forwarding Table |
IPv4 IS-IS routing information for Level-1. |
|
Level-2 IPv4 Forwarding Table |
IPv4 IS-IS routing information for Level-2. |
|
IPv4 Destination |
IPv4 destination address. |
|
IntCost |
Internal cost. |
|
ExtCost |
External cost. |
|
ExitInterface |
Output interface. |
|
NextHop |
Next hop. |
|
Flags |
Routing state flag: · D—Direct route. · R—The route has been added into the routing table. · L—The route has been advertised in an LSP. · U—Penetration flag. Setting it to UP can prevent an LSP sent from L2 to L1 from being sent back to L2. |
# Display detailed IPv4 IS-IS routing information.
<Sysname> display isis route verbose
Route information for IS-IS(1)
-----------------------------
Level-1 IPv4 Forwarding Table
-----------------------------
IPV4 Dest : 8.8.8.0/24 Int. Cost : 10 Ext. Cost : NULL
Admin Tag : - Src Count : 2 Flag : D/L/-
InLabel : 4294967295 InLabel Flag: -/-/-/-/-/-
NextHop : Interface : ExitIndex :
Direct Vlan100 0x00000000
Nib ID : 0x0 OutLabel : 4294967295 OutLabelFlag: -
LabelSrc : N/A Delay Flag : N/A
IPV4 Dest : 9.9.9.0/24 Int. Cost : 20 Ext. Cost : NULL
Admin Tag : - Src Count : 1 Flag : R/L/-
InLabel : 4294967295 InLabel Flag: -/-/-/-/-/-
NextHop : Interface : ExitIndex :
8.8.8.5 Vlan100 0x00000003
Nib ID : 0x0 OutLabel : 4294967295 OutLabelFlag: -
LabelSrc : N/A Delay Flag : N/A
Flags: D-Direct, R-Added to Rib, L-Advertised in LSPs, U-Up/Down Bit Set
InLabel flags: R-Readvertisement, N-Node SID, P-no PHP
E-Explicit null, V-Value, L-Local
OutLabelFlags: E-Explicit null, I-Implicit null, N-Nomal, P-SR label prefer
Level-2 IPv4 Forwarding Table
-----------------------------
IPV4 Dest : 8.8.8.0/24 Int. Cost : 10 Ext. Cost : NULL
Admin Tag : - Src Count : 2 Flag : D/L/-
InLabel : 4294967295 InLabel Flag: -/-/-/-/-/-
NextHop : Interface : ExitIndex :
Direct Vlan100 0x00000001
Nib ID : 0x14000003 OutLabel : 4294967295 OutLabelFlag: -
LabelSrc : N/A Delay Flag : N/A
Flags: D-Direct, R-Added to Rib, L-Advertised in LSPs, U-Up/Down Bit Set
InLabel flags: R-Readvertisement, N-Node SID, P-no PHP
E-Explicit null, V-Value, L-Local
OutLabelFlags: E-Explicit null, I-Implicit null, N-Nomal, P-SR label prefer
Table 32 Command output
|
Field |
Description |
|
Route information for IS-IS(1) |
Route information for IS-IS process 1. |
|
Level-1 IPv4 Forwarding Table |
IPv4 IS-IS routing information for Level-1. |
|
Level-2 IPv4 Forwarding Table |
IPv4 IS-IS routing information for Level-2. |
|
IPv4 Dest |
IPv4 destination. |
|
Int. Cost |
Internal cost. |
|
Ext. Cost |
External cost. |
|
Admin Tag |
Tag. |
|
Src Count |
Count of advertising sources. |
|
Flag |
Route state flag: · R—The route has been installed into the routing table. · L—The route has been flooded in an LSP. · U—Route leaking flag. Setting it to UP can prevent an LSP sent from L2 to L1 from being sent back to L2. |
|
InLabel |
This field is not supported in the current software version. Incoming label. |
|
InLabel flag |
This field is not supported in the current software version. Incoming label flag: · R—Re-advertisement flag. If set, inter-level propagation or route redistribution exists. · N—Node-SID flag. If set, the prefix SID is the SID to an SR node. · P—No-PHP flag. If set, the penultimate node cannot pop the prefix SID. · E—Explicit null flag. If set, the upstream neighbor must replace the prefix SID with an explicit null flag before forwarding the packets. · V—Value/Index flag. If set, the prefix SID carries an absolute value. · L—Local flag. If set, the prefix SID has local significance. |
|
Next Hop |
Next hop. |
|
Interface |
Output interface. |
|
ExitIndex |
Index of the output interface. |
|
Nib ID |
ID assigned by the routing management module (next hop index). |
|
OutLabel |
This field is not supported in the current software version. Outgoing label. |
|
OutLabelFlag |
This field is not supported in the current software version. Outgoing label flag: · E—Explicit null flag. The upstream neighbor must replace the SID with an explicit null flag before forwarding the packets. · I—Implicit null flag. The upstream neighbor must replace the SID with an implicit null flag before forwarding the packets. This flag is not supported in the current software version. · N—Normal flag. · P—SR label preference flag. |
|
LabelSrc |
This field is not supported in the current software version. Label source: · SR—The label is allocated by the SR node. · SRMS—The label is allocated by the segment routing mapping server (SRMS). · N/A—No label exists. |
|
Delay Flag |
This field is not supported in the current software version. Microloop avoidance delay flag: · D—Microloop avoidance is configured. Route convergence is delayed. · N/A—Microloop avoidance is not configured or the microloop avoidance delay timer has expired. Route convergence is in progress. |
# Display IPv6 IS-IS routing information.
<Sysname> display isis route ipv6
Route information for IS-IS(1)
------------------------------
Level-1 IPv6 forwarding table
-----------------------------
Destination: 2001:1:: PrefixLen: 64
Flag : R/L/- Cost : 20
Next hop : FE80::200:5EFF:FE64:8905 Interface: Vlan100
Destination: 2001:2:: PrefixLen: 64
Flag : D/L/- Cost : 10
Next hop : Direct Interface: Vlan100
Flags: D-Direct, R-Added to Rib, L-Advertised in LSPs, U-Up/Down Bit Set
Level-2 IPv6 forwarding table
-----------------------------
Destination: 2001:1:: PrefixLen: 64
Flag : -/-/- Cost : 20
Destination: 2001:2:: PrefixLen: 64
Flag : D/L/- Cost : 10
Flags: D-Direct, R-Added to Rib, L-Advertised in LSPs, U-Up/Down Bit Set
Table 33 Command output
|
Field |
Description |
|
Destination |
IPv6 destination prefix. |
|
PrefixLen |
Length of the prefix. |
|
Flag/Flags |
Route flag: · D—This is a direct route. · R—The route has been added into the routing table. · L—The route has been advertised in an LSP. · U—Route leaking flag, indicating that the Level-1 route is from Level-2. U means the route will not be returned to Level-2. |
|
Cost |
Route cost. |
|
Next hop |
Next hop. |
|
Interface |
Output interface. |
# Display detailed IPv6 IS-IS routing information.
<Sysname> display isis route ipv6 verbose
Route information for IS-IS(1)
------------------------------
Level-1 IPv6 forwarding table
-----------------------------
IPv6 dest : 2001:1::/64
Flag : D/L/- Cost : 10
Admin tag : - Src count : 2
Nexthop : Direct
Interface : Vlan101
Nib ID : 0x0
IPv6 dest : 2001:2::/64
Flag : R/-/- Cost : 20
Admin tag : - Src count : 2
Nexthop : FE80::200:5EFF:FE64:8905
Interface : Vlan101
BkNexthop : FE80::200:5EFF:FE64:8905
BkInterface : Vlan101
Nib ID : 0x24000002
Flags: D-Direct, R-Added to Rib, L-Advertised in LSPs, U-Up/Down Bit Set
Level-2 IPv6 Forwarding Table
-----------------------------
IPv6 dest : 2001:1::/64
Flag : D/L/- Cost : 10
Admin tag : - Src count : 2
Nexthop : -
Interface : -
Nib ID : -
IPv6 dest : 2001:2::/64
Flag : D/L/- Cost : 10
Admin tag : - Src count : 2
Nexthop : -
Interface : -
Nib ID : -
Flags: D-Direct, R-Added to Rib, L-Advertised in LSPs, U-Up/Down Bit Set
Table 34 Command output
|
Field |
Description |
|
IPv6 dest |
IPv6 destination address and prefix. |
|
Flag/Flags |
Route flag: · D—This is a direct route. · R—The route has been added into the routing table. · L—The route has been advertised in an LSP. · U—Route leaking flag, indicating the Level-1 route is from Level-2. U means the route will not be returned to Level-2. |
|
Cost |
Route cost. |
|
Admin tag |
Administrative tag. |
|
Src count |
Number of advertisement sources. |
|
Nexthop |
Next hop. |
|
Interface |
Output interface. |
|
BkNexthop |
Backup next hop. |
|
BkInterface |
Backup output interface. |
|
Nib ID |
Next hop index assigned by the routing management module. |
display isis spf-tree
Use display isis spf-tree to display IS-IS SPF tree information.
Syntax
display isis spf-tree [ ipv4 | ipv6 ] [ [ level-1 | level-2 ] | [ source-id source-id | verbose ] ] * [ process-id ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
ipv4: Displays IPv4 IS-IS SPF tree information.
ipv6: Displays IPv6 IS-IS SPF tree information.
level-1: Displays Level-1 IS-IS SPF tree information. If you do not specify a level, the command displays both Level-1 and Level-2 SPF tree information.
level-2: Displays Level-2 SPF tree information. If you do not specify a level, the command displays both Level-1 and Level-2 SPF tree information.
verbose: Displays detailed IS-IS SPF tree information. If you do not specify this keyword, the command displays brief IS-IS SPF tree information.
source-id source-id: Displays detailed information about an SPF node. The source-id argument represents the system ID of the SPF node, in XXXX.XXXX.XXXX.XX format.
process-id: Specifies an IS-IS process by its ID in the range of 1 to 65535. If you do not specify this argument, the command displays SPF tree information for all IS-IS processes.
Usage guidelines
If you do not specify the ipv4 or ipv6 keyword, the command displays IPv4 IS-IS SPF tree information.
Examples
# Display brief IPv4 IS-IS SPF tree information.
<Sysname> display isis spf-tree
Shortest Path Tree for IS-IS(1)
-------------------------------
Flags: S-Node is on SPF tree T-Node is on tent list
O-Node is overload R-Node is directly reachable
I-Node or Link is isolated D-Node or Link is to be deleted
C-Neighbor is child P-Neighbor is parent
V-Link is involved N-Link is a new path
L-Link is on change list U-Protocol usage is changed
H-Nexthop is changed
Level-1 Shortest Path Tree
--------------------------
SpfNode NodeFlag SpfLink LinkCost LinkFlag
-------------------------------------------------------------------------------
0000.0000.0032.00 S/-/-/-/-/-
-->0000.0000.0032.01 10 -/-/C/-/-/-/-/-/-
-->0000.0000.0064.00 10 -/-/C/-/-/-/-/-/-
0000.0000.0032.01 S/-/-/R/-/-
-->0000.0000.0064.00 0 -/-/C/-/-/-/-/-/-
-->0000.0000.0032.00 0 -/-/-/P/-/-/-/-/-
0000.0000.0064.00 S/-/-/R/-/-
-->0000.0000.0032.00 10 -/-/-/P/-/-/-/-/-
-->0000.0000.0032.01 10 -/-/-/P/-/-/-/-/-
Level-2 Shortest Path Tree
--------------------------
SpfNode NodeFlag SpfLink LinkCost LinkFlag
-------------------------------------------------------------------------------
0000.0000.0032.00 S/-/-/-/-/-
-->0000.0000.0032.01 10 -/-/C/-/-/-/-/-/-
-->0000.0000.0064.00 10 -/-/C/-/-/-/-/-/-
0000.0000.0032.01 S/-/-/R/-/-
-->0000.0000.0064.00 0 -/-/C/-/-/-/-/-/-
-->0000.0000.0032.00 0 -/-/-/P/-/-/-/-/-
0000.0000.0064.00 S/-/-/R/-/-
-->0000.0000.0032.00 10 -/-/-/P/-/-/-/-/-
-->0000.0000.0032.01 10 -/-/-/P/-/-/-/-/-
# Display detailed IPv4 IS-IS SPF tree information.
<Sysname> display isis spf-tree verbose
Shortest Path Tree for IS-IS(1)
-------------------------------
Flags: S-Node is on SPF tree T-Node is on tent list
O-Node is overload R-Node is directly reachable
I-Node or Link is isolated D-Node or Link is to be deleted
C-Neighbor is child P-Neighbor is parent
V-Link is involved N-Link is a new path
L-Link is on change list U-Protocol usage is changed
H-Nexthop is changed
Level-1 Shortest Path Tree
--------------------------
SpfNode : 0000.0000.0001.00
Distance : 0
TE distance : 0
NodeFlag : S/-/-/-/-/-
RelayNibID : 0x0
TE tunnel count: 0
Nexthop count : 0
SpfLink count : 1
-->0000.0000.0004.04
LinkCost : 10
LinkNewCost : 10
LinkFlag : -/-/C/-/-/-/-/-/-
LinkSrcCnt : 1
Type : Adjacent Interface : N/A
Cost : 10 Nexthop : N/A
InterfaceIP: N/A NeighborIP: N/A
SpfNode : 0000.0000.0004.04
Distance : 10
TE distance : 10
NodeFlag : S/-/-/R/-/-
RelayNibID : 0x14000001
TE tunnel count: 0
Nexthop count : 0
SpfLink count : 2
-->0000.0000.0001.00
LinkCost : 0
LinkNewCost : 0
LinkFlag : -/-/-/P/-/-/-/-/-
LinkSrcCnt : 1
Type : Remote Interface : N/A
Cost : 0 Nexthop : N/A
InterfaceIP: N/A NeighborIP: N/A
-->0000.0000.0004.00
LinkCost : 0
LinkNewCost : 0
LinkFlag : -/-/C/-/-/-/-/-/-
LinkSrcCnt : 1
Type : Remote Interface : Vlan50
Cost : 0 Nexthop : 1.1.1.3
InterfaceIP: N/A NeighborIP: N/A
Level-2 Shortest Path Tree
--------------------------
SpfNode : 0000.0000.0001.00
Distance : 0
TE distance : 0
NodeFlag : S/-/-/-/-/-
RelayNibID : 0x0
TE tunnel count: 0
Nexthop count : 0
SpfLink count : 1
-->0000.0000.0004.04
LinkCost : 10
LinkNewCost : 10
LinkFlag : -/-/C/-/-/-/-/-/-
LinkSrcCnt : 1
Type : Adjacent Interface : N/A
Cost : 10 Nexthop : N/A
InterfaceIP: N/A NeighborIP: N/A
SpfNode : 0000.0000.0004.04
Distance : 10
TE distance : 10
NodeFlag : S/-/-/R/-/-
RelayNibID : 0x0
TE tunnel count: 0
Nexthop count : 0
SpfLink count : 2
-->0000.0000.0001.00
LinkCost : 0
LinkNewCost : 0
LinkFlag : -/-/-/P/-/-/-/-/-
LinkSrcCnt : 1
Type : Remote Interface : N/A
Cost : 0 Nexthop : N/A
InterfaceIP: N/A NeighborIP: N/A
-->0000.0000.0004.00
LinkCost : 0
LinkNewCost : 0
LinkFlag : -/-/C/-/-/-/-/-/-
LinkSrcCnt : 1
Type : Remote Interface : Vlan50
Cost : 0 Nexthop : 1.1.1.3
InterfaceIP: N/A NeighborIP: N/A
Table 35 Command output
|
Field |
Description |
|
SpfNode |
ID of the topology node. |
|
Distance |
Shortest distance from the root node to the local node. |
|
TE distance |
Shortest distance from the root node to the local node (including tunnel links). If tunnel is not configured, TE distance equals to Distance. |
|
NodeFlag |
Node flag: · S—The node is on the SPF tree. · T—The node is on the tent list. · O—The node is overloaded. · R—The node is directly connected. · I—The node is isolated. · D—The node is to be deleted. |
|
RelayNibID |
Next hop ID of the node after route recursion. |
|
Nexthop count |
Next hop count. |
|
Nexthop |
Primary next hop of the node or the link advertising source. |
|
AdvMtID |
Topology from which the routing information is learned: · 0—Base topology. · 6-4094—Other topologies. |
|
Interface |
Primary output interface of the node or the link advertising source. |
|
BkNexthop |
Backup next hop. |
|
BkInterface |
Backup output interface. |
|
Neighbor |
ID of the primary next hop neighbor. |
|
BkNeighbor |
ID of the backup next hop neighbor. |
|
SpfLink |
Topology link. |
|
SpfLink count |
Number of topology links. |
|
LinkCost |
Link cost. |
|
LinkNewCost |
New link cost. |
|
LinkFlag |
Link flag: · I—The link is isolated. · D—The link is to be deleted. · C—The neighbor is a child node. · P—The neighbor is the parent node. · V—The link is involved. · N—The link is a new path. · L—The link is on the change list. · U—The protocol usage of the link is changed. · H—The next hop of the link is changed. |
|
LinkSrcCnt |
Number of link advertising sources. |
|
Type |
Type of the link advertising source: · Adjacent—The link advertising source is a local neighbor. · Remote—The link advertising source is advertised by a remote node in an LSP. |
|
Cost |
Cost of the link advertising source. |
|
Remote-LFA |
Remote LFA backup information. |
|
RLfaNeighbor |
System ID of the remote LFA backup next hop. |
|
PQNode |
System ID of the PQ node. |
|
PQNodePrefix |
PQ node prefix. |
|
OutLabel |
Backup label to the PQ node. |
# Display brief IPv6 IS-IS SPF tree information.
<Sysname> display isis spf-tree ipv6
Shortest Path Tree for IS-IS(1)
-------------------------------
Flags: S-Node is on SPF tree T-Node is on tent list
O-Node is overload R-Node is directly reachable
I-Node or Link is isolated D-Node or Link is to be deleted
C-Neighbor is child P-Neighbor is parent
V-Link is involved N-Link is a new path
L-Link is on change list U-Protocol usage is changed
H-Nexthop is changed
Level-1 Shortest Path Tree
----------------------------------
SpfNode NodeFlag SpfLink LinkCost LinkFlag
-------------------------------------------------------------------------------
0000.0000.0032.00 S/-/-/-/-/-
-->0000.0000.0032.01 10 -/-/C/-/-/-/-/-/-
-->0000.0000.0064.00 10 -/-/C/-/-/-/-/-/-
0000.0000.0032.01 S/-/-/R/-/-
-->0000.0000.0064.00 0 -/-/C/-/-/-/-/-/-
-->0000.0000.0032.00 0 -/-/-/P/-/-/-/-/-
0000.0000.0064.00 S/-/-/R/-/-
-->0000.0000.0032.00 10 -/-/-/P/-/-/-/-/-
-->0000.0000.0032.01 10 -/-/-/P/-/-/-/-/-
Level-2 Shortest Path Tree
----------------------------------
SpfNode NodeFlag SpfLink LinkCost LinkFlag
-------------------------------------------------------------------------------
0000.0000.0032.00 S/-/-/-/-/-
-->0000.0000.0032.01 10 -/-/C/-/-/-/-/-/-
-->0000.0000.0064.00 10 -/-/C/-/-/-/-/-/-
0000.0000.0032.01 S/-/-/R/-/-
-->0000.0000.0064.00 0 -/-/C/-/-/-/-/-/-
-->0000.0000.0032.00 0 -/-/-/P/-/-/-/-/-
0000.0000.0064.00 S/-/-/R/-/-
-->0000.0000.0032.00 10 -/-/-/P/-/-/-/-/-
-->0000.0000.0032.01 10 -/-/-/P/-/-/-/-/-
# Display detailed Level-1 IPv6 IS-IS SPF tree information.
<Sysname> display isis spf-tree ipv6 level-1 verbose
Shortest Path Tree for IS-IS(1)
-------------------------------
Flags: S-Node is on SPF tree T-Node is on tent list
O-Node is overload R-Node is directly reachable
I-Node or Link is isolated D-Node or Link is to be deleted
C-Neighbor is child P-Neighbor is parent
V-Link is involved N-Link is a new path
L-Link is on change list U-Protocol usage is changed
H-Nexthop is changed
Level-1 Shortest Path Tree
--------------------------
SpfNode : 0000.0000.0032.00
Distance : 0
TE distance : 0
NodeFlag : S/-/-/-/-/-
RelayNibID : 0x0
TE tunnel count: 0
Nexthop count : 0
SpfLink count : 2
-->0000.0000.0032.01
LinkCost : 10
LinkNewCost : 10
LinkFlag : -/-/C/-/-/-/-/-/-
LinkSrcCnt : 1
Type : Adjacent Interface: N/A
Cost : 10 Nexthop : N/A
-->0000.0000.0064.00
LinkCost : 10
LinkNewCost : 10
LinkFlag : -/-/C/-/-/-/-/-/-
LinkSrcCnt : 1
Type : Adjacent Interface: Tun1
Cost : 10 Nexthop : FE80::A0A:A40
SpfNode : 0000.0000.0032.01
Distance : 10
TE distance : 10
NodeFlag : S/-/-/R/-/-
RelayNibID : 0x0
TE tunnel count: 0
Nexthop count : 0
SpfLink count : 2
-->0000.0000.0064.00
LinkCost : 0
LinkNewCost : 0
LinkFlag : -/-/C/-/-/-/-/-/-
LinkSrcCnt : 1
Type : Adjacent Interface: Vlan2
Cost : 10 Nexthop : FE80::200:12FF:FE34:1
-->0000.0000.0032.00
LinkCost : 0
LinkNewCost : 0
LinkFlag : -/-/-/P/-/-/-/-/-
LinkSrcCnt : 1
Type : Adjacent Interface: N/A
Cost : 0 Nexthop : N/A
SpfNode : 0000.0000.0064.00
Distance : 10
TE distance : 10
NodeFlag : S/-/-/R/-/-
RelayNibID : 0x0
TE tunnel count: 0
Nexthop count : 2
Neighbor : 0000.0000.0064.00 Interface : Vlan2
NextHop : FE80::200:12FF:FE34:1
BkNeighbor: N/A BkInterface: N/A
BkNextHop : N/A
Neighbor : 0000.0000.0064.00 Interface : Tun1
NextHop : FE80::A0A:A40
BkNeighbor: N/A BkInterface: N/A
BkNextHop : N/A
SpfLink count : 2
-->0000.0000.0032.00
LinkCost : 10
LinkNewCost : 10
LinkFlag : -/-/-/P/-/-/-/-/-
LinkSrcCnt : 1
Type : Remote Interface: N/A
Cost : 10 Nexthop : N/A
AdvMtID : 0
-->0000.0000.0064.00
LinkCost : 10
LinkNewCost : 10
LinkFlag : -/-/C/-/-/-/-/-/-
LinkSrcCnt : 1
Type : Remote Interface: Tun1
Cost : 10 Nexthop : FE80::A0A:A40
AdvMtID : 0
Table 36 Command output
|
Field |
Description |
|
SpfNode |
ID of the topology node. |
|
Distance |
Shortest distance from the root node to the current node. |
|
TE distance |
Shortest distance from the root node to the current node (including tunnel links). If no tunnels are configured, TE distance equals Distance. |
|
NodeFlag |
Node flag: · S—The node is on the SPF tree. · T—The node is on the tent list. · O—The node is overloaded. · R—The node is directly connected. · I—The node is isolated. · D—The node is to be deleted. |
|
TE tunnel count |
Number of tunnels destined for this node. |
|
Nexthop count |
Number of next hops. |
|
NextHop |
Primary next hop of the node or the link advertising source. |
|
AdvMtID |
Topology from which the routing information is learned: · 0—IPv4 unicast topology. · 2—IPv6 unicast topology. · 6-4094—Other topologies. |
|
Interface |
Primary output interface of the node or the link advertising source. |
|
BkNextHop |
Backup next hop. |
|
BkInterface |
Backup output interface. |
|
Neighbor |
ID of the primary next hop neighbor. |
|
BkNeighbor |
ID of the backup next hop neighbor. |
|
SpfLink |
Topology link. |
|
SpfLink count |
Number of topology links. |
|
LinkCost |
Link cost. |
|
LinkNewCost |
New link cost. |
|
LinkFlag |
Link flag: · I—The link is isolated. · D—The link is to be deleted. · C—The neighbor is a child node. · P—The neighbor is the parent node. · V—The link is involved. · N—The link is a new path. · L—The link is on the change list. · U—The protocol of the link is changed. · H—The next hop of the link is changed. |
|
LinkSrcCnt |
Number of link advertising sources. |
|
Type |
Type of the link advertising source: · Adjacent—The link advertising source is a local neighbor. · Remote—The link advertising source is advertised by a remote node in an LSP. |
|
Cost |
Cost of the link advertising source. |
display isis statistics
Use display isis statistics to display IS-IS statistics.
Syntax
display isis statistics [ ipv4 | ipv6 ] [ level-1 | level-1-2 | level-2 ] [ process-id ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
ipv4: Displays IPv4 IS-IS statistics. If you do not specify this option, the command displays both IPv4 and IPv6 statistics.
ipv6: Displays IPv6 IS-IS statistics.
level-1: Displays IS-IS Level-1 statistics.
level-1-2: Displays IS-IS Level-1-2 statistics.
level-2: Displays IS-IS Level-2 statistics.
process-id: Displays statistics for an IS-IS process specified by its ID in the range of 1 to 65535. If you do not specify an IS-IS process, this command displays the statistics for all IS-IS processes.
Usage guidelines
If you do not specify a level, this command displays both Level-1 and Level-2 routing information.
Examples
# Display IS-IS statistics.
<Sysname> display isis statistics
Statistics information for IS-IS(1)
----------------------------------
Level-1 Statistics
------------------
MTR(base)
Learnt routes information:
Total IPv4 Learnt Routes in IPv4 Routing Table: 1
Imported routes information:
IPv4 Imported Routes:
Static: 0 Direct: 0
ISIS: 0 BGP: 0
RIP: 0 OSPF: 0
Total Number: 0
MTR(base)
Learnt routes information:
Total IPv6 Learnt Routes in IPv6 Routing Table: 0
Imported routes information:
IPv6 Imported Routes:
Static: 0 Direct: 0
ISISv6: 0 BGP4+: 0
RIPng: 0 OSPFv3: 0
Total Number: 0
Lsp information:
LSP Source ID: No. of used LSPs
7777.8888.1111 001
Level-2 Statistics
------------------
MTR(base)
Learnt routes information:
Total IPv4 Learnt Routes in IPv4 Routing Table: 0
Imported routes information:
IPv4 Imported Routes:
Static: 0 Direct: 0
ISIS: 0 BGP: 0
RIP: 0 OSPF: 0
Total Number: 0
MTR(base)
Learnt routes information:
Total IPv6 Learnt Routes in IPv6 Routing Table: 0
Imported routes information:
IPv6 Imported Routes:
Static: 0 Direct: 0
ISISv6: 0 BGP4+: 0
RIPng: 0 OSPFv3: 0
Total Number: 0
Lsp information:
LSP Source ID: No. of used LSPs
7777.8888.1111 001
Table 37 Command output
|
Field |
Description |
|
Statistics information for IS-IS(processid) |
Statistics for the IS-IS process. |
|
Level-1 Statistics |
Level-1 statistics. |
|
Level-2 Statistics |
Level-2 statistics. |
|
MTR(topo-name) |
MTR topology. If this field displays base, the topology is the base topology. |
|
Learnt routes information |
· Total IPv4 Learnt Routes in IPv4 Routing Table—Number of learned IPv4 routes. · Total IPv6 Learnt Routes in IPv6 Routing Table—Number of learned IPv6 routes. |
|
IPv4 Imported Routes |
Numbers of different types of redistributed IPv4 routes, including static, direct, IS-IS, BGP, RIP, and OSPF routes. |
|
IPv6 Imported Routes |
Numbers of different types of redistributed IPv6 routes, including static, direct, IS-ISv6, BGP4+, RIPng, and OSPFv3 routes. |
|
Lsp information |
LSP information: · LSP Source ID—ID of the source system. · No. of used LSPs—Number of used LSPs. |
display isis troubleshooting
Use display isis troubleshooting to display IS-IS neighbor relationship troubleshooting information.
Syntax
display isis troubleshooting
Views
Any view
Predefined user roles
network-admin
network-operator
Examples
# Display IS-IS neighbor relationship troubleshooting information.
<Sysname> display isis troubleshooting
IS-IS troubleshooting information
---------------------------------
Total entries: 3
Time Sequence Description
2021-07-20 19:31:28 101 The state of IS-IS process 1 level-1 neighbor 0000.0000.0001 changed to DOWN because the interface went down. Please check the interface state. (Interface: VLAN10, neighbor IPv4 address: 10.1.1.1; neighbor IPv6 address: FE80::8ae3:1156:17)
2021-07-20 15:33:28 100 The state of IS-IS process 1 level-2 neighbor 0000.0000.0001 changed to DOWN because the IS-IS level was changed. Please check IS-IS configuration. (Interface: VLAN10, neighbor IPv4 address: 10.1.1.1; neighbor IPv6 address: FE80::8ae3:1156:17)
2021-07-20 15:28:00 99 The state of IS-IS process 1 level-2 neighbor 0000.0000.0001 changed to DOWN because the hold timer expired and a hello packet with bad protocol version was dropped at 15:27:59. Please execute the display isis packet hello command to check hello packet statistics. (Interface: VLAN10, neighbor IPv4 address: 10.1.1.1; neighbor IPv6 address: FE80::8ae3:1156:17, CPU usage: 5%, IPv4 ping result: 5 packets succeeded, 0 packets timed out, IPv6 ping result: 5 packets succeeded, 0 packets timed out)
Table 38 Command output
|
Field |
Description |
|
Total entries |
Total number of IS-IS neighbor relationship troubleshooting entries. |
|
Time |
Time when the IS-IS neighbor was disconnected. The most recent entry is displayed first. |
|
Sequence |
Sequence number of the IS-IS neighbor relationship troubleshooting entry. |
|
Description |
IS-IS neighbor relationship troubleshooting information, including the IS-IS process ID, IS-IS level, neighbor ID, reason, and recommended action. · The state of IS-IS process 1 level-1 neighbor 0000.0000.0001 changed to DOWN because the IS-IS process was reset (Interface: Vlan10, neighbor IPv4 address: 10.1.1.1; neighbor IPv6 address: FE80::8ae3:1156:17). · The state of IS-IS process 1 level-1 neighbor 0000.0000.0001 changed to DOWN because the IS-IS process was gracefully restarted (Interface: Vlan10, neighbor IPv4 address: 10.1.1.1; neighbor IPv6 address: FE80::8ae3:1156:17). · The state of IS-IS process 1 level-1 neighbor 0000.0000.0001 changed to DOWN because the IS-IS process was deleted (Interface: Vlan10, neighbor IPv4 address: 10.1.1.1; neighbor IPv6 address: FE80::8ae3:1156:17). · The state of IS-IS process 1 level-1 neighbor 0000.0000.0001 changed to DOWN because the reset isis peer command was executed (Interface: Vlan10, neighbor IPv4 address: 10.1.1.1; neighbor IPv6 address: FE80::8ae3:1156:17). · The state of IS-IS process 1 level-1 neighbor 0000.0000.0001 changed to DOWN because the IS-IS level was changed. Please check IS-IS configuration (Interface: Vlan10, neighbor IPv4 address: 10.1.1.1; neighbor IPv6 address: FE80::8ae3:1156:17). · The state of IS-IS process 1 level-1 neighbor 0000.0000.0001 changed to DOWN because the IS-IS area was deleted. Please check IS-IS configuration (Interface: Vlan10, neighbor IPv4 address: 10.1.1.1; neighbor IPv6 address: FE80::8ae3:1156:17). · The state of IS-IS process 1 level-1 neighbor 0000.0000.0001 changed to DOWN because the IS-IS process was stopped. Please check IS-IS process state (Interface: Vlan10, neighbor IPv4 address: 10.1.1.1; neighbor IPv6 address: FE80::8ae3:1156:17). · The state of IS-IS process 1 level-1 neighbor 0000.0000.0001 changed to DOWN because the LSP sequence number exceeds the maximum sequence number (Interface: Vlan10, neighbor IPv4 address: 10.1.1.1; neighbor IPv6 address: FE80::8ae3:1156:17). · The state of IS-IS process 1 level-1 neighbor 0000.0000.0001 changed to DOWN because the interface went down. Please check the interface state (Interface: Vlan10, neighbor IPv4 address: 10.1.1.1; neighbor IPv6 address: FE80::8ae3:1156:17). · The state of IS-IS process 1 level-1 neighbor 0000.0000.0001 changed to DOWN because the interface was deleted or the bound VPN instance was changed. Please check the interface state and settings (Interface: Vlan10, neighbor IPv4 address: 10.1.1.1; neighbor IPv6 address: FE80::8ae3:1156:17). · The state of IS-IS process 1 level-1 neighbor 0000.0000.0001 changed to DOWN because IS-IS interface parameters changed. Please check the interface parameters (Interface: Vlan10, neighbor IPv4 address: 10.1.1.1; neighbor IPv6 address: FE80::8ae3:1156:17). · The state of IS-IS process 1 level-1 neighbor 0000.0000.0001 changed to DOWN because IS-IS packet receiving and sending were disabled. Please check the interface settings (Interface: Vlan10, neighbor IPv4 address: 10.1.1.1; neighbor IPv6 address: FE80::8ae3:1156:17). · The state of IS-IS process 1 level-1 neighbor 0000.0000.0001 changed to DOWN because the circuit level changed on the interface. Please check the interface settings (Interface: Vlan10, neighbor IPv4 address: 10.1.1.1; neighbor IPv6 address: FE80::8ae3:1156:17). · The state of IS-IS process 1 level-1 neighbor 0000.0000.0001 changed to DOWN because the circuit type changed on the interface. Please check the interface settings (Interface: Vlan10, neighbor IPv4 address: 10.1.1.1; neighbor IPv6 address: FE80::8ae3:1156:17). · The state of IS-IS process 1 level-1 neighbor 0000.0000.0001 changed to DOWN because the interface address was deleted or IS-IS was disabled on interface. Please check the interface settings (Interface: Vlan10, neighbor IPv4 address: 10.1.1.1; neighbor IPv6 address: FE80::8ae3:1156:17). · The state of IS-IS process 1 level-1 neighbor 0000.0000.0001 changed to DOWN because the interface IPv6 address was deleted or IPv6 IS-IS was disabled on interface. Please check the interface settings (Interface: Vlan10, neighbor IPv4 address: 10.1.1.1; neighbor IPv6 address: FE80::8ae3:1156:17). · The state of IS-IS process 1 level-1 neighbor 0000.0000.0001 changed to DOWN because IPv4 IS-IS was disabled on interface. Please check the interface settings (Interface: Vlan10, neighbor IPv4 address: 10.1.1.1; neighbor IPv6 address: FE80::8ae3:1156:17). · The state of IS-IS process 1 level-1 neighbor 0000.0000.0001 changed to DOWN because IPv6 IS-IS was disabled on interface. Please check the interface settings (Interface: Vlan10, neighbor IPv4 address: 10.1.1.1; neighbor IPv6 address: FE80::8ae3:1156:17). · The state of IS-IS process 1 level-1 neighbor 0000.0000.0001 changed to DOWN because the BFD session went down. Please check the BFD session state (Interface: Vlan10, neighbor IPv4 address: 10.1.1.1; neighbor IPv6 address: FE80::8ae3:1156:17). · The state of IS-IS process 1 level-1 neighbor 0000.0000.0001 changed to DOWN because the BFD session was administratively down. Please check the BFD session state (Interface: Vlan10, neighbor IPv4 address: 10.1.1.1; neighbor IPv6 address: FE80::8ae3:1156:17). · The state of IS-IS process 1 level-1 neighbor 0000.0000.0001 changed to DOWN because the local BFD configuration changed. Please check the BFD session information (Interface: Vlan10, neighbor IPv4 address: 10.1.1.1; neighbor IPv6 address: FE80::8ae3:1156:17). · The state of IS-IS process 1 level-1 neighbor 0000.0000.0001 changed to DOWN because the remote BFD configuration changed. Please check the BFD session information on remote end (Interface: Vlan10, neighbor IPv4 address: 10.1.1.1; neighbor IPv6 address: FE80::8ae3:1156:17). · The state of IS-IS process 1 level-1 neighbor 0000.0000.0001 changed to DOWN because the IPv6 topology mode changed. Please check the IPv6 topology mode settings (Interface: Vlan10, neighbor IPv4 address: 10.1.1.1; neighbor IPv6 address: FE80::8ae3:1156:17). · The state of IS-IS process 1 level-1 neighbor 0000.0000.0001 changed to DOWN because the wait-to-delete BFD TLV timed out. Please check the BFD session information (Interface: Vlan10, neighbor IPv4 address: 10.1.1.1; neighbor IPv6 address: FE80::8ae3:1156:17). · The state of IS-IS process 1 level-1 neighbor 0000.0000.0001 changed to INIT because a hello packet with mismatched circuit type was received (Interface: Vlan10, neighbor IPv4 address: 10.1.1.1; neighbor IPv6 address: FE80::8ae3:1156:17). · The state of IS-IS process 1 level-1 neighbor 0000.0000.0001 changed to INIT because a hello packet with mismatched area was received (Interface: Vlan10, neighbor IPv4 address: 10.1.1.1; neighbor IPv6 address: FE80::8ae3:1156:17). · The state of IS-IS process 1 level-1 neighbor 0000.0000.0001 changed to DOWN because a P2P hello packet with mismatched area was received (Interface: Vlan10, neighbor IPv4 address: 10.1.1.1; neighbor IPv6 address: FE80::8ae3:1156:17). · The state of IS-IS process 1 level-1 neighbor 0000.0000.0001 changed to INIT because a hello packet with mismatched protocol was received (Interface: Vlan10, neighbor IPv4 address: 10.1.1.1; neighbor IPv6 address: FE80::8ae3:1156:17). · The state of IS-IS process 1 level-1 neighbor 0000.0000.0001 changed to INIT because a hello packet without SNPA address was received (Interface: Vlan10, neighbor IPv4 address: 10.1.1.1; neighbor IPv6 address: FE80::8ae3:1156:17). · The state of IS-IS process 1 level-1 neighbor 0000.0000.0001 changed to INIT because a hello packet without local SNPA address was received (Interface: Vlan10, neighbor IPv4 address: 10.1.1.1; neighbor IPv6 address: FE80::8ae3:1156:17). · The state of IS-IS process 1 level-1 neighbor 0000.0000.0001 changed to DOWN because the neighbor system ID corresponding to the SNPA address in the received hello packet is different from the neighbor system ID carried in the hello packet (Interface: Vlan10, neighbor IPv4 address: 10.1.1.1; neighbor IPv6 address: FE80::8ae3:1156:17). · The state of IS-IS process 1 level-1 neighbor 0000.0000.0001 changed to DOWN because the P2P neighbor was gracefully down. Please check the GR configuration of GR helper (Interface: Vlan10, neighbor IPv4 address: 10.1.1.1; neighbor IPv6 address: FE80::8ae3:1156:17). · The state of IS-IS process 1 level-1 neighbor 0000.0000.0001 changed to DOWN because a P2P hello packet with incorrect system ID was received (Interface: Vlan10, neighbor IPv4 address: 10.1.1.1; neighbor IPv6 address: FE80::8ae3:1156:17). · The state of IS-IS process 1 level-1 neighbor 0000.0000.0001 changed to DOWN because a P2P hello packet with incorrect circuit ID was received (Interface: Vlan10, neighbor IPv4 address: 10.1.1.1; neighbor IPv6 address: FE80::8ae3:1156:17). · The state of IS-IS process 1 level-1 neighbor 0000.0000.0001 changed to INIT because a P2P hello packet with incorrect extended circuit ID was received (Interface: Vlan10, neighbor IPv4 address: 10.1.1.1; neighbor IPv6 address: FE80::8ae3:1156:17). · The state of IS-IS process 1 level-1 neighbor 0000.0000.0001 changed to INIT because a P2P hello packet with adjacency three-way state down was received (Interface: Vlan10, neighbor IPv4 address: 10.1.1.1; neighbor IPv6 address: FE80::8ae3:1156:17). · The state of IS-IS process 1 level-1 neighbor 0000.0000.0001 changed to DOWN because a P2P hello packet with mismatched circuit type was received (Interface: Vlan10, neighbor IPv4 address: 10.1.1.1; neighbor IPv6 address: FE80::8ae3:1156:17). · The state of IS-IS process 1 level-1 neighbor 0000.0000.0001 changed to DOWN because no hello packets were received within the hold time. Please check the connection to the neighbor (Interface: Vlan10, neighbor IPv4 address: 10.1.1.1; neighbor IPv6 address: FE80::8ae3:1156:17; CPU usage: 25%; IPv4 ping result: 0 packets succeeded, 5 packets timed out; IPv6 ping result: 0 packets succeeded, 5 packets timed out). · The state of IS-IS process 1 level-1 neighbor 0000.0000.0001 changed to DOWN because the hold timer expired and a hello packet with bad protocol version was dropped at 15:27:59. Please execute the display isis packet hello command to check hello packet statistics (Interface: Vlan10, neighbor IPv4 address: 10.1.1.1; neighbor IPv6 address: FE80::8ae3:1156:17; CPU usage: 25%; IPv4 ping result: 5 packets succeeded, 0 packets timed out; IPv6 ping result: 5 packets succeeded, 0 packets timed out). For more information, see Table 7. |
Related commands
reset isis troubleshooting
display osi
Use display osi to display OSI connection information.
Syntax
display osi [ slot slot-number ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
slot slot-number: Specifies an IRF member device by its member ID. If you do not specify a member device, this command displays OSI connection information for all member devices.
Examples
# Display OSI connection information.
<Sysname> display osi
Total OSI socket number: 2
Location: slot 0
Creator: isisd[1539]
State: N/A
Options: SO_FILTER
Error: 0
Receiving buffer(cc/hiwat/lowat/drop/state): 0 / 1048576 / 1 / 0 / N/A
Sending buffer(cc/hiwat/lowat/state): 0 / 262144 / 512 / N/A
Type: 2
Enabled interfaces:
Vlan-interface100
MAC address: 0180-c200-0014
Location: slot 0
Creator: isisd[1539]
State: N/A
Options: SO_FILTER
Error: 0
Receiving buffer(cc/hiwat/lowat/drop/state): 0 / 1048576 / 1 / 0 / N/A
Sending buffer(cc/hiwat/lowat/state): 0 / 262144 / 512 / N/A
Type: 2
Enabled interfaces:
Vlan-interface100
MAC address: 0180-c200-0014
Table 39 Command output
|
Field |
Description |
|
Total OSI socket number |
Total number of OSI sockets. |
|
Creator |
Name of the socket creator. The process ID of the creator is displayed in the square brackets. |
|
State |
This field always displays N/A. |
|
Options |
Socket options: · SO_FILTER—Filter option is configured. · N/A—No option is configured. |
|
Error |
Number of errors that affect the socket session. |
|
Receiving buffer(cc/hiwat/lowat/drop/state) |
Receiving buffer information, including the current used space, maximum space, minimum space, number of dropped packets, and status. |
|
Sending buffer(cc/hiwat/lowat/state) |
Sending buffer information, including the current used space, maximum space, minimum space, and status. |
|
Type |
Type 2 socket, corresponding to unreliable connectionless-oriented transport layer protocols. |
|
Enabled interfaces |
Input interfaces and matched multicast MAC addresses. Only packets received from Ethernet link-layer interfaces need to match the multicast MAC addresses. |
display osi statistics
Use display osi statistics to display OSI packet statistics.
Syntax
display osi statistics [ slot slot-number ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
slot slot-number: Specifies an IRF member device by its member ID. If you do not specify a member device, this command displays OSI packet statistics for all member devices.
Examples
# Display OSI packet statistics.
<Sysname> display osi statistics
Received packets:
Total: 35
Relay received: 35
Relay forwarded: 35
Invalid service slot: 0
No matched socket: 0
Not delivered, input socket full: 0
Sent packets:
Total: 19
Relay forwarded: 19
Relay received: 19
Failed: 0
Table 40 Command output
|
Field |
Description |
|
Received packets |
Statistics of received packets: · Total—Total number of received link layer packets. · Relay received—Number of inbound packets on the cards that host the input interfaces. These packets are relayed from other cards. This count is not included in the total count of received packets. · Relay forwarded—Number of inbound packets relayed to the cards that host the input interfaces. · Invalid service slot—Number of packets discarded because of the unavailability of the cards that host the input interfaces. · No matched socket—Number of discarded packets due to mismatches in input interfaces, MAC addresses, or connection filter criteria. · Not delivered, input socket full—Number of undelivered packets due to a socket receiving buffer overflow. |
|
Sent packets |
Statistics of sent packets: · Total—Total number of packets that IS-IS sent over OSI connections. · Relay forwarded—Number of outbound packets relayed to the cards that host the output interfaces. This count is not included in the total count of sent packets. · Relay received—Number of outbound packets on the cards that host the output interfaces. These packets are relayed from other cards. · Failed—Number of packets that failed to be sent. |
Related commands
reset osi statistics
distribute bgp-ls
Use distribute bgp-ls to advertise IS-IS link state information to BGP.
Use undo distribute bgp-ls to restore the default.
Syntax
distribute bgp-ls [ instance-id id ] [ level-1 | level-2 ]
undo distribute bgp-ls [ level-1 | level-2 ]
Default
The device does not advertise IS-IS link state information to BGP.
Views
IS-IS view
Predefined user roles
network-admin
Parameters
instance-id id: Specifies an instance by its ID in the range of 0 to 65535. If you do not specify this option, the command advertises IS-IS link state information of instance 0 to BGP.
level-1: Advertises the Level-1 IS-IS link state information to BGP.
level-2: Advertises the Level-2 IS-IS link state information to BGP.
Usage guidelines
After the device advertises IS-IS link state information to BGP, BGP can advertise the information for intended applications.
If multiple IS-IS processes have the same instance ID and link state information, only the link state information of the IS-IS process with the smallest process ID is advertised.
To advertise the same link state information of different IS-IS processes to BGP, specify different instance IDs for the IS-IS processes.
If you do not specify a level for the distribute bgp-ls command, both Level-1 and Level-2 IS-IS link state information are advertised to BGP.
If you do not specify a level for the undo distribute bgp-ls command, neither Level-1 nor Level-2 IS-IS link state information can be advertised to BGP.
Examples
# Advertise link state information of IS-IS process 1 to BGP.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] distribute bgp-ls
domain-authentication send-only
Use domain-authentication send-only to configure IS-IS not to check the authentication information in the received Level-2 packets, including LSPs, CSNPs, and PSNPs.
Use undo domain-authentication send-only to restore the default.
Syntax
domain-authentication send-only
undo domain-authentication send-only
Default
When domain authentication mode and key are configured, a Level-2 or Level-1-2 router checks the authentication information in the received packets.
Views
IS-IS view
Predefined user roles
network-admin
Usage guidelines
When domain authentication mode and key are configured, a Level-2 or Level-1-2 router adds the key in the specified mode into transmitted Level-2 packets (including LSPs, CSNPs, and PSNPs). It also checks the key in the received Level-2 packets.
To prevent packet exchange failure in case of an authentication key change, configure IS-IS not to check the authentication information in the received packets.
Examples
# Configure IS-IS not to check the authentication information in the received packets.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] domain-authentication send-only
Related commands
area-authentication send-only
domain-authentication-mode
isis authentication send-only
domain-authentication-mode
Use domain-authentication-mode to specify the routing domain authentication mode and a key.
Use undo domain-authentication-mode to restore the default.
Syntax
domain-authentication-mode { { gca key-id { hmac-sha-1 | hmac-sha-224 | hmac-sha-256 | hmac-sha-384 | hmac-sha-512 } [ nonstandard ] | md5 | simple } { cipher | plain } string | keychain keychain-name } [ ip | osi ]
undo domain-authentication-mode
Default
No routing domain authentication mode or key is configured.
Views
IS-IS view
Predefined user roles
network-admin
Parameters
gca: Specifies the GCA mode.
key-id: Uniquely identifies an SA in the range of 1 to 65535. The sender inserts the Key ID into the authentication TLV, and the receiver authenticates the packet by using the SA that is selected based on the Key ID.
hmac-sha-1: Specifies the HMAC-SHA-1 algorithm.
hmac-sha-224: Specifies the HMAC-SHA-224 algorithm.
hmac-sha-256: Specifies the HMAC-SHA-256 algorithm.
hmac-sha-384: Specifies the HMAC-SHA-384 algorithm.
hmac-sha-512: Specifies the HMAC-SHA-512 algorithm.
nonstandard: Specifies the nonstandard GCA authentication mode.
md5: Specifies the MD5 authentication mode.
simple: Specifies the simple authentication mode.
cipher: Specifies a key in encrypted form.
plain: Specifies a key in plaintext form. For security purposes, the key specified in plaintext form will be stored in encrypted form.
string: Specifies the key. Its plaintext form is a case-sensitive string of 1 to 16 characters. Its encrypted form is a case-sensitive string of 33 to 53 characters.
keychain: Specifies the keychain authentication mode.
keychain-name: Specifies a keychain by its name, a case-sensitive string of 1 to 63 characters.
ip: Checks IP-related fields in LSPs.
osi: Checks OSI-related fields in LSPs.
Usage guidelines
The configured key in the specified mode is inserted into all outgoing Level-2 packets (LSP, CSNP, and PSNP) and is used for authenticating the incoming Level-2 packets.
The keychain authentication mode supports only the HMAC-MD5 algorithm.
· Before IS-IS sends a Level-2 packet, it uses the valid send key obtained from the keychain to authenticate the packet. If no valid send key exists or the valid send key does not use the HMAC-MD5 algorithm, the authentication fails and the packet does not contain the authentication information.
· After IS-IS receives a Level-2 packet, it uses a valid accept key obtained from the keychain to authenticate the packet. If no valid accept key exists or all valid accept keys fail to authenticate the packet, the authentication fails and the packet is discarded.
All the backbone routers must have the same authentication mode and key.
If neither ip nor osi is specified, the OSI-related fields in LSPs are checked.
When you specify the GCA mode, follow these guidelines:
· If you do not specify the nonstandard keyword, the device can communicate only with devices that use the GCA mode.
· If you specify the nonstandard keyword, the device can communicate only with devices that use the nonstandard GCA mode.
Examples
# Set the routing domain authentication mode to simple, and set the plaintext key to 123456.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] domain-authentication-mode plain 123456
Related commands
area-authentication-mode
domain-authentication send-only
isis authentication-mode
event-log size
Use event-log size to set the maximum number of log entries that IS-IS can record.
Use undo event-log size to remove the configuration.
Syntax
event-log { hello { peer-change | received-abnormal | received-dropped | sent-abnormal | sent-failed } | peer } size count
undo event-log peer size
Default
IS-IS can record 100 log entries for each log type.
Views
IS-IS view
Predefined user roles
network-admin
Parameters
hello: Specifies the maximum number of log entries for received and sent hello packets.
peer-change: Specifies the maximum number of log entries for hello packets received and sent during neighbor state change.
received-abnormal: Specifies the maximum number of log entries for abnormally received hello packets, which were received at intervals greater than or equal to 0.5 times the holdtime (number of missed hello packets multiplied by the hello interval).
received-dropped: Specifies the maximum number of log entries for received hello packets that were dropped.
sent-abnormal: Specifies the maximum number of log entries for abnormally sent hello packets, which were sent at intervals greater than or equal to 1.5 times the hello interval.
sent-failed: Specifies the maximum number of log entries for hello packets that failed to be sent.
peer: Specifies the maximum number of neighbor state change log entries.
count: Specifies the maximum number of log entries in the range of 0 to 65535. If you set the value of this argument to 0 for a log type, IS-IS does not record logs for the log type.
Examples
# Set the maximum number of neighbor state change log entries that IS-IS process 1 can record to 50.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] event-log peer size 50
fast-reroute
Use fast-reroute to configure IS-IS FRR.
Use undo fast-reroute to disable IS-IS FRR.
Syntax
In IS-IS IPv4 unicast address family view:
fast-reroute { lfa [ ecmp-shared | level-1 | level-2 ] | route-policy route-policy-name }
undo fast-reroute { lfa [ level-1 | level-2 ] | route-policy }
In IS-IS IPv6 unicast address family view:
fast-reroute { lfa [ level-1 | level-2 ] | route-policy route-policy-name }
undo fast-reroute { lfa [ level-1 | level-2 ] | route-policy }
Default
IS-IS FRR is disabled.
Views
IS-IS IPv4 unicast address family view
IS-IS IPv6 unicast address family view
Predefined user roles
network-admin
Parameters
lfa: Calculates a backup next hop through Loop Free Alternate (LFA) calculation for all Level-1 or Level-2 routes.
ecmp-shared: Calculates a backup next hop through LFA calculation for all routes, including ECMP routes. ECMP routes share one backup next hop. If you do not specify this keyword, IS-IS calculates a backup next hop through LFA calculation only for non-ECMP routes.
level-1: Specifies Level-1 routes.
level-2: Specifies Level-2 routes.
route-policy route-policy-name: Uses the specified routing policy to designate a backup next hop. The route-policy-name argument is a case-sensitive string of 1 to 63 characters.
Usage guidelines
To calculate a shared backup next hop through LFA calculation for ECMP routes, execute this command with the ecmp-shared keyword. If the next hops of all ECMP routes fail, IS-IS uses the shared backup next hop to forward packets. The shared backup next hop is installed into the RIB as an ECMP route. The state of the route is Backup in the output from the display ip routing-table command.
Example
# Enable FRR for IS-IS process 1 and configure IS-IS FRR to calculate a backup next hop through LFA calculation for all routes.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] address-family ipv4
[Sysname-isis-1-ipv4] fast-reroute lfa
fast-reroute remote-lfa maximum-cost
Use fast-reroute remote-lfa maximum-cost to set the maximum cost from the source node of a protected link to a PQ node.
Use undo fast-reroute remote-lfa maximum-cost to restore the default.
Syntax
fast-reroute remote-lfa maximum-cost cost [ level-1 | level-2 ]
undo fast-reroute remote-lfa maximum-cost [ level-1 | level-2 ]
Default
The maximum cost from the source node of a protected link to a PQ node is 16777215.
Views
IS-IS IPv4 unicast address family view
Predefined user roles
network-admin
Parameters
cost: Specifies a cost value in the range of 1 to 16777215.
level-1: Applies the configuration to Level-1 areas.
level-2: Applies the configuration to the Level-2 area.
Usage guidelines
The cost values from different PQ nodes to the source node of a specific protected link might be different. You can use this command to filter PQ nodes based on the cost value.
If you specify neither the level-1 nor the level-2 keyword, this command applies to all IS-IS areas.
Examples
# Set the maximum cost from the source node of a protected link to a PQ node to 200.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] address-family ipv4
[Sysname-isis-1-ipv4] fast-reroute remote-lfa maximum-cost 200
fast-reroute remote-lfa prefix-list
Use fast-reroute remote-lfa prefix-list to specify a prefix list to filter remote LFA PQ nodes.
Use undo fast-reroute remote-lfa prefix-list to restore the default.
Syntax
fast-reroute remote-lfa prefix-list prefix-list-name [ level-1 | level-2 ]
undo fast-reroute remote-lfa prefix-list [ level-1 | level-2 ]
Default
Any PQ node can be selected as the backup next hop by remote LFA FRR.
Views
IS-IS IPv4 unicast address family view
Predefined user roles
network-admin
Parameters
prefix-list-name: Specifies a prefix list by its name, a case-sensitive string of 1 to 63 characters.
level-1: Applies the configuration to Level-1 areas.
level-2: Applies the configuration to the Level-2 area.
Usage guidelines
If you specify neither the level-1 nor the level-2 keyword, this command applies to all IS-IS areas.
Examples
# Use prefix list test1 to filter remote LFA PQ nodes.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] address-family ipv4
[Sysname-isis-1-ipv4] fast-reroute remote-lfa prefix-list test1
Related commands
ip prefix-list
fast-reroute remote-lfa tunnel ldp
Use fast-reroute remote-lfa tunnel ldp to enable IS-IS remote LFA FRR.
Use undo fast-reroute remote-lfa tunnel ldp to disable IS-IS remote LFA FRR.
Syntax
fast-reroute remote-lfa tunnel ldp [ level-1 | level-2 ]
undo fast-reroute remote-lfa tunnel ldp [ level-1 | level-2 ]
Default
IS-IS remote LFA FRR is disabled.
Views
IS-IS IPv4 unicast address family view
Predefined user roles
network-admin
Parameters
level-1: Applies the configuration to Level-1 areas.
level-2: Applies the configuration to the Level-2 area.
Usage guidelines
Configure remote LFA FRR to prevent traffic loss caused by link or node failures.
Before configuring remote LFA FRR, you must perform the following tasks:
· Use the mpls ldp command to enable MPLS LDP globally.
· Use the mpls ldp enable command to enable MPLS LDP on all interfaces participating in MPLS forwarding.
· Use the fast-reroute lfa command to enable LFA FRR for the IS-IS level at which remote LFA FRR will be implemented.
If you specify neither the level-1 nor the level-2 keyword, this command applies to all IS-IS areas.
Examples
# Enable remote LFA FRR.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] address-family ipv4
[Sysname-isis-1-ipv4] fast-reroute remote-lfa tunnel ldp
Related commands
fast-reroute
mpls ldp (MPLS Command Reference)
mpls ldp enable (MPLS Command Reference)
fast-reroute tiebreaker
Use fast-reroute tiebreaker to set the priority for the node-protection or lowest-cost backup path selection policy.
Use undo fast-reroute tiebreaker to restore the default.
Syntax
fast-reroute tiebreaker { lowest-cost | node-protecting } preference preference [ level-1 | level-2 ]
undo fast-reroute tiebreaker { lowest-cost | node-protecting } [ level-1 | level-2 ]
Default
The priority values of the node-protection and lowest-cost backup path selection policies are 40 and 20, respectively.
Views
IS-IS IPv4 unicast address family view
IS-IS IPv6 unicast address family view
Predefined user roles
network-admin
Parameters
lowest-cost: Sets a priority value for the lowest-cost backup path selection policy.
node-protecting: Sets a priority value for the node-protection backup path selection policy.
preference preference: Specifies a priority value in the range of 1 to 255. A higher value indicates a higher priority.
level-1: Applies the configuration to Level-1 areas.
level-2: Applies the configuration to the Level-2 area.
Usage guidelines
If you execute this command multiple times for a backup path selection policy, the most recent configuration takes effect.
If the node-protection policy has a higher priority but the backup path calculation fails, IS-IS uses the lowest-cost policy for further calculation.
If the lowest-cost policy has a higher priority but the backup path calculation fails, IS-IS does not perform further backup path calculation.
If you do not specify a level, the command takes effect on both Level-1 and Level-2 areas.
Examples
# Set the priority value of the node-protection backup path selection policy to 100.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] address-family ipv4
[Sysname-isis-1-ipv4] fast-reroute tiebreaker node-protecting preference 100
Related commands
fast-reroute
filter-policy export
Use filter-policy export to configure IS-IS to filter redistributed routes.
Use undo filter-policy export to remove the configuration.
Syntax
filter-policy { acl-number | prefix-list prefix-list-name | route-policy route-policy-name } export [ protocol [ process-id ] ]
undo filter-policy export [ protocol [ process-id ] ]
Default
IS-IS does not filter redistributed routes.
Views
IS-IS IPv4 unicast address family view
IS-IS IPv6 unicast address family view
Predefined user roles
network-admin
Parameters
acl-number: Specifies an ACL by its number in the range of 2000 to 3999 to filter redistributed routes.
prefix-list prefix-list-name: Specifies a prefix list by its name, a case-sensitive string of 1 to 63 characters, to filter redistributed routes by destination address.
route-policy route-policy-name: Specifies a routing policy by its name, a case-sensitive string of 1 to 63 characters, to filter redistributed routes.
protocol: Filters routes redistributed from the specified routing protocol. If no protocol is specified, the command filters all redistributed routes.
process-id: Specifies a process by its ID in the range of 1 to 65535. This argument is available only when the protocol is isis, ospf, rip, isisv6, ospfv3, or ripng. The default process ID is 1.
Usage guidelines
This command filters routes redistributed by the import-route command. Only routes that have not been filtered can be advertised.
To use an advanced ACL (with a number from 3000 to 3999) in the command, configure the ACL using one of the following methods:
· To deny/permit a route with the specified destination, use the rule [ rule-id ] { deny | permit } ip source sour-addr sour-wildcard command.
· To deny/permit a route with the specified destination and mask, use the rule [ rule-id ] { deny | permit } ip source sour-addr sour-wildcard destination dest-addr dest-wildcard command.
The source keyword specifies the destination address of a route and the destination keyword specifies the subnet mask of the route. For the configuration to take effect, specify a contiguous subnet mask.
Examples
# Use basic ACL 2000 to filter redistributed routes.
<Sysname> system-view
[Sysname] acl basic 2000
[Sysname-acl-ipv4-basic-2000] rule deny source 192.168.10.0 0.0.0.255
[Sysname-acl-ipv4-basic-2000] quit
[Sysname] isis 1
[Sysname-isis-1] address-family ipv4
[Sysname-isis-1-ipv4] filter-policy 2000 export
# Configure advanced ACL 3000 to permit only route 113.0.0.0/16 to pass. Use advanced ACL 3000 to filter redistributed routes.
[Sysname] acl advanced 3000
[Sysname-acl-ipv4-adv-3000] rule 10 permit ip source 113.0.0.0 0 destination 255.255.0.0 0
[Sysname-acl-ipv4-adv-3000] rule 100 deny ip
[Sysname-acl-ipv4-adv-3000] quit
[Sysname] isis 1
[Sysname-isis 1] address-family ipv4
[Sysname-isis-1-ipv4] filter-policy 3000 export
Related commands
display isis route
filter-policy import
Use filter-policy import to configure IS-IS to filter routes calculated using received LSPs.
Use undo filter-policy import to restore the default.
Syntax
filter-policy { acl-number | prefix-list prefix-list-name | route-policy route-policy-name } import
undo filter-policy import
Default
IS-IS does not filter routes calculated using received LSPs.
Views
IS-IS IPv4 unicast address family view
IS-IS IPv6 unicast address family view
Predefined user roles
network-admin
Parameters
acl-number: Specifies an ACL by its number in the range of 2000 to 3999 to filter routes calculated using received LSPs.
prefix-list prefix-list-name: Specifies a prefix list by its name, a case-sensitive string of 1 to 63 characters, to filter routes calculated using received LSPs by destination address.
route-policy route-policy-name: Specifies a routing policy by its name, a case-sensitive string of 1 to 63 characters, to filter received routes.
Usage guidelines
This command filters received routes. Only routes that have not been filtered can be added into the routing table.
To use an advanced ACL (with a number from 3000 to 3999) in the command, configure the ACL using one of the following methods:
· To deny/permit a route with the specified destination, use the rule [ rule-id ] { deny | permit } ip source sour-addr sour-wildcard command.
· To deny/permit a route with the specified destination and mask, use the rule [ rule-id ] { deny | permit } ip source sour-addr sour-wildcard destination dest-addr dest-wildcard command.
The source keyword specifies the destination address of a route and the destination keyword specifies the subnet mask of the route. For the configuration to take effect, specify a contiguous subnet mask.
Examples
# Use basic ACL 2000 to filter routes calculated using received LSPs.
<Sysname> system-view
[Sysname] acl basic 2000
[Sysname-acl-ipv4-basic-2000] rule deny source 192.168.10.0 0.0.0.255
[Sysname-acl-ipv4-basic-2000] quit
[Sysname] isis 1
[Sysname-isis-1] address-family ipv4
[Sysname-isis-1-ipv4] filter-policy 2000 import
# Use advanced ACL 3000 to filter routes calculated using received LSPs and install only route 113.0.0.0/16 to the IP routing table.
<Sysname> system-view
[Sysname] acl advanced 3000
[Sysname-acl-ipv4-adv-3000] rule 10 permit ip source 113.0.0.0 0 destination 255.255.0.0 0
[Sysname-acl-ipv4-adv-3000] rule 100 deny ip
[Sysname-acl-ipv4-adv-3000] quit
[Sysname] isis 1
[Sysname-isis 1] address-family ipv4
[Sysname-isis-1-ipv4] filter-policy 3000 import
Related commands
display ip routing-table
flash-flood
Use flash-flood to enable IS-IS LSP flash flooding.
Use undo flash-flood to disable IS-IS LSP flash flooding.
Syntax
flash-flood [ flood-count flooding-count | max-timer-interval flooding-interval | [ level-1 | level-2 ] ] *
undo flash-flood [ level-1 | level-2 ]
Default
IS-IS LSP flash flooding is disabled.
Views
IS-IS view
Predefined user roles
network-admin
Parameters
flood-count flooding-count: Specifies the maximum number of LSPs to be flooded before the next SPF calculation, in the range of 1 to 15. The default is 5.
max-timer-interval flooding-interval: Specifies the delay of the flash flooding, in the range of 10 to 50000 milliseconds. The default is 10.
level-1: Enables flash flooding for Level-1.
level-2: Enables flash flooding for Level-2.
Usage guidelines
If no level is specified, the command enables IS-IS LSP flash flooding for both Level-1 and Level-2.
Examples
# Enable fast flooding, and set the maximum LSPs to be sent to 10 and the delay time to 100 milliseconds.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] flash-flood flood-count 10 max-timer-interval 100
graceful-restart
Use graceful-restart to enable IS-IS GR.
Use undo graceful-restart to disable IS-IS GR.
Syntax
graceful-restart
undo graceful-restart
Default
IS-IS GR is disabled.
Views
IS-IS view
Predefined user roles
network-admin
Usage guidelines
IS-IS GR and IS-IS NSR are mutually exclusive. Therefore, do not configure the graceful-restart command and the non-stop-routing command at the same time.
Examples
# Enable GR for IS-IS process 1.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] graceful-restart
Related commands
graceful-restart suppress-sa
graceful-restart suppress-sa
Use graceful-restart suppress-sa to suppress the Suppress-Advertisement (SA) bit during restart.
Use undo graceful-restart suppress-sa to restore the default.
Syntax
graceful-restart suppress-sa
undo graceful-restart suppress-sa
Default
The SA bit is set during restart.
Views
IS-IS view
Predefined user roles
network-admin
Usage guidelines
Suppressing the SA bit is mainly for avoiding black hole route. If a router starts or reboots without keeping the local forwarding table, sending packets to the router might result in severe packet loss. To avoid this, you can set the SA bit of the hello packet sent by the GR restarter to 1. Upon receiving such hello packets, the GR helpers will not advertise the GR restarter through LSP.
Examples
# Suppress the SA bit during graceful restart.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] graceful-restart suppress-sa
Related commands
graceful-restart
graceful-restart t1
Use graceful-restart t1 to set the T1 timer.
Use undo graceful-restart t1 to restore the default.
Syntax
graceful-restart t1 seconds count count
undo graceful-restart t1
Default
The T1 timer is 3 seconds and can expire 10 times.
Views
IS-IS view
Predefined user roles
network-admin
Parameters
seconds: Specifies the T1 timer in the range of 3 to 10 seconds.
count: Specifies the number of times that the T1 timer can expire, in the range of 1 to 20.
Usage guidelines
The T1 timer specifies the number of times that GR restarter can send a Restart TLV with the RR bit set. After restart, the GR restarter sends a Restart TLV with the RR bit set to its neighbor. If the restarting router receives a Restart TLV with the RA set from its neighbor before the T1 timer expires, the GR process starts. Otherwise, the GR process fails.
To avoid GR timer configuration failure, follow these guidelines when you set the GR timers:
· The product of the T1 timer and the number of times that the T1 timer can expire must be smaller than the T2 timer.
· The T2 timer must be smaller than the T3 timer.
Examples
# Set the T1 timer of IS-IS process 1 to 5 seconds, and the expiration times to 5.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] graceful-restart t1 5 count 5
Related commands
graceful-restart
graceful-restart t2
graceful-restart t3
graceful-restart t2
Use graceful-restart t2 to set the T2 timer.
Use undo graceful-restart t2 to restore the default.
Syntax
graceful-restart t2 seconds
undo graceful-restart t2
Default
The T2 timer is 60 seconds.
Views
IS-IS view
Predefined user roles
network-admin
Parameters
seconds: Specifies the T2 timer in the range of 30 to 65535 seconds.
Usage guidelines
The T2 timer specifies the LSDB synchronization interval. Each LSDB has a T2 timer. The Level-1-2 router has two T2 timers: a Level-1 timer and a Level-2 timer. If the LSDBs have not achieved synchronization before the two timers expire, the GR process fails.
To avoid GR timer configuration failure, follow these guidelines when you set the GR timers:
· The product of the T1 timer and the number of times that the T1 timer can expire must be smaller than the T2 timer.
· The T2 timer must be smaller than the T3 timer.
Examples
# Set the T2 timer of IS-IS process 1 to 50 seconds.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] graceful-restart t2 50
Related commands
graceful-restart
graceful-restart t1
graceful-restart t3
graceful-restart t3
Use graceful-restart t3 to set the T3 timer.
Use undo graceful-restart t3 to restore the default.
Syntax
graceful-restart t3 seconds
undo graceful-restart t3
Default
The T3 timer is 300 seconds.
Views
IS-IS view
Predefined user roles
network-admin
Parameters
seconds: Specifies the T3 timer in the range of 300 to 65535 seconds.
Usage guidelines
The T3 timer specifies the GR interval. The GR interval is set as the holdtime in hello PDUs. Within the interval, the neighbors maintain their adjacency with the GR restarter. If the GR process has not completed within the holdtime, the neighbors tear down the neighbor relationship and the GR process fails.
To avoid GR timer configuration failure, follow these guidelines when you set the GR timers:
· The product of the T1 timer and the number of times that the T1 timer can expire must be smaller than the T2 timer.
· The T2 timer must be smaller than the T3 timer.
Examples
# Set the T3 timer of IS-IS process 1 to 500 seconds.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] graceful-restart t3 500
Related commands
graceful-restart
graceful-restart t1
graceful-restart t2
ignore-att
Use ignore-att to configure IS-IS not to calculate the default route through the ATT bit.
Use undo ignore-att to restore the default.
Syntax
ignore-att
undo ignore-att
Default
IS-IS calculates the default route through the ATT bit.
Views
IS-IS view
Predefined user roles
network-admin
Examples
# Configure IS-IS not to calculate the default route through the ATT bit.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] ignore-att
import-route
Use import-route to redistribute routes from another routing protocol or another IS-IS process.
Use undo import-route to disable route redistribution.
Syntax
In IS-IS IPv4 unicast address family view:
import-route bgp [ as-number ] [ allow-ibgp ] [ cost cost-value | cost-type { external | internal } | [ level-1 | level-1-2 | level-2 ] | route-policy route-policy-name | tag tag ] *
import-route bgp [ as-number ] [ allow-ibgp ] inherit-cost [ [ level-1 | level-1-2 | level-2 ] | route-policy route-policy-name | tag tag ] *
import-route { direct | static } [ cost cost-value | cost-type { external | internal } | [ level-1 | level-1-2 | level-2 ] | route-policy route-policy-name | tag tag ] *
import-route { direct | static } inherit-cost [ [ level-1 | level-1-2 | level-2 ] | route-policy route-policy-name | tag tag ] *
import-route { isis | ospf | rip } [ process-id | all-processes ] [ allow-direct | cost cost-value | cost-type { external | internal } | [ level-1 | level-1-2 | level-2 ] | route-policy route-policy-name | tag tag ] *
import-route { isis | ospf | rip } [ process-id | all-processes ] inherit-cost [ allow-direct | [ level-1 | level-1-2 | level-2 ] | route-policy route-policy-name | tag tag ] *
undo import-route { bgp | direct | { isis | ospf | rip } [ process-id | all-processes ] | static }
In IS-IS IPv6 unicast address family view:
import-route bgp4+ [ as-number ] [ allow-ibgp ] [ [ cost cost-value | inherit-cost ] | cost-type { external | internal } | [ level-1 | level-1-2 | level-2 ] | route-policy route-policy-name | tag tag ] *
import-route { direct | static } [ [ cost cost-value | inherit-cost ] | cost-type { external | internal } | [ level-1 | level-1-2 | level-2 ] | route-policy route-policy-name | tag tag ] *
import-route { isisv6 | ospfv3 | ripng } [ process-id ] [ allow-direct | [ cost cost-value | inherit-cost ] | cost-type { external | internal } | [ level-1 | level-1-2 | level-2 ] | route-policy route-policy-name | tag tag ] *
undo import-route { bgp4+ | direct | { isisv6 | ospfv3 | ripng } [ process-id | all-processes ] | static }
Default
IS-IS does not redistribute routes from other routing protocols or processes.
Views
IS-IS IPv4 unicast address family view
IS-IS IPv6 unicast address family view
Predefined user roles
network-admin
Parameters
bgp: Redistributes BGP routes.
direct: Redistributes direct routes.
isis: Redistributes IS-IS routes.
ospf: Redistributes OSPF routes.
rip: Redistributes RIP routes.
static: Redistributes static routes.
bgp4+: Redistributes IPv6 BGP routes.
isisv6: Redistributes IPv6 IS-IS routes.
ospfv3: Redistributes OSPFv3 routes.
ripng: Redistributes RIPng routes.
as-number: Specifies an AS by its number in the range of 1 to 4294967295. If you do not specify this argument for the BGP or BGP4+ protocol, the command redistributes all IPv4 or IPv6 EBGP routes. As a best practice, specify an AS to prevent the system from redistributing excessive routes.
process-id: Specifies a process by its ID in the range of 1 to 65535.
all-processes: Redistributes routes from all the processes of the specified routing protocol.
allow-ibgp: Allows redistribution of IBGP routes.
allow-direct: Redistributes the networks of the local interfaces enabled with the specified routing protocol. By default, the networks of the local interfaces are not redistributed. If you specify both the allow-direct keyword and the route-policy route-policy-name option, make sure the if-match rule defined in the routing policy does not conflict with the allow-direct keyword. For example, if you specify the allow-direct keyword, do not configure the if-match route-type rule for the routing policy. Otherwise, the allow-direct keyword does not take effect.
cost cost-value: Specifies a cost for redistributed routes, which is in the range of 0 to 4261412864.
· For the styles of narrow, narrow-compatible, and compatible, the cost is in the range of 0 to 63.
· For the styles of wide and wide-compatible, the cost is in the range of 0 to 4261412864.
cost-type { external | internal }: Specifies the cost type. The internal type indicates internal routes, and the external type indicates external routes. If external is specified, the cost of a redistributed route is added by 64 to make internal routes take priority over external routes. The type is external by default. The keywords are available only when the cost type is narrow, narrow-compatible, or compatible.
inherit-cost: Specifies to use the original cost of redistributed routes.
level-1: Redistributes routes into the Level-1 routing table.
level-1-2: Redistributes routes into both Level-1 and Level-2 routing tables.
level-2: Redistributes routes into the Level-2 routing table. If no level is specified, the routes are redistributed into the Level-2 routing table by default.
route-policy route-policy-name: Redistributes only routes matching the specified routing policy. The route-policy-name argument is a case-sensitive string of 1 to 63 characters.
tag tag: Specifies a tag value for marking redistributed routes, in the range of 1 to 4294967295.
Usage guidelines
IS-IS takes all the redistributed routes as external routes to destinations outside the IS-IS routing domain.
If you specify the cost or inherit-cost keyword, the effective cost varies by cost style. For the styles of narrow, narrow-compatible, and compatible, the cost is in the range of 0 to 63. If the cost is more than 63, 63 is used. For the style of wide or wide-compatible, the configured value is the effective value.
This import-route command cannot redistribute default routes. The command redistributes only active routes. To display route state information, use the display ip routing-table protocol command.
The import-route bgp or import-route bgp4+ command redistributes only EBGP routes.
The import-route bgp allow-ibgp or import-route bgp4+ allow-ibgp command redistributes both EBGP and IBGP routes. Because this command might cause routing loops, use it with caution.
If you do not specify the cost or inherit-cost keyword, the cost of a redistributed route is 0.
The undo import-route { isis | ospf | rip } all-processes or undo import-route { isisv6 | ospfv3 | ripng } all-processes command removes only the configuration made by the import-route { isis | ospf | rip } all-processes or import-route { isisv6 | ospfv3 | ripng } all-processes command, instead of the configuration made by the import-route { isis | ospf | rip } process-id or import-route { isisv6 | ospfv3 | ripng } process-id command.
Examples
# Redistribute static routes into IS-IS, and set the cost for redistributed routes to 15.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] address-family ipv4
[Sysname-isis-1-ipv4] import-route static cost 15
Related commands
import-route limit
import-route isis level-1 into level-2
Use import-route isis level-1 into level-2 to enable route advertisement from Level-1 to Level-2.
Use undo import-route isis level-1 into level-2 to disable route advertisement from Level-1 to Level-2.
Syntax
import-route isis level-1 into level-2 [ filter-policy { ipv4-acl-number | prefix-list prefix-list-name | route-policy route-policy-name } | tag tag ] *
undo import-route isis level-1 into level-2
Default
Route advertisement from Level-1 to Level-2 is enabled.
Views
IS-IS IPv4 unicast address family view
Predefined user roles
network-admin
Parameters
filter-policy: Specifies a filtering policy.
ipv4-acl-number: Specifies an ACL by its number in the range of 2000 to 3999 to filter routes from Level-1 to Level-2.
prefix-list prefix-list-name: Specifies an IPv4 prefix list by its name, a case-sensitive string of 1 to 63 characters, to filter routes from Level-1 to Level-2 by destination address.
route-policy route-policy-name: Specifies a routing policy by its name, a case-sensitive string of 1 to 63 characters, to filter routes from Level-1 to Level-2.
tag tag: Specifies a tag for marking redistributed routes, in the range of 1 to 4294967295.
Usage guidelines
If a routing policy is used, the routing policy must be specified in the import-route isis level-1 into level-2 command to filter routes from Level-1 to Level-2. Other routing policies specified for route reception and redistribution do not affect the route leaking.
If a filtering policy is configured, only Level-1 routes not filtered out can be advertised into the Level-2 area.
Examples
# Enable route advertisement from Level-1 to Level-2.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] address-family ipv4
[Sysname-isis-1-ipv4] import-route isis level-1 into level-2
Related commands
import-route
import-route isis level-1 into level-2
import-route isis level-2 into level-1
Use import-route isis level-2 into level-1 to enable route advertisement from Level-2 to Level-1.
Use undo import-route isis level-2 into level-1 to restore the default.
Syntax
import-route isis level-2 into level-1 [ filter-policy { ipv4-acl-number | prefix-list prefix-list-name | route-policy route-policy-name } | tag tag ] *
undo import-route isis level-2 into level-1
Default
Route advertisement from Level-2 to Level-1 is disabled.
Views
IS-IS IPv4 unicast address family view
Predefined user roles
network-admin
Parameters
filter-policy: Specifies a filtering policy.
ipv4-acl-number: Specifies an ACL by its number in the range of 2000 to 3999 to filter routes from Level-2 to Level-1.
prefix-list prefix-list-name: Specifies an IPv4 prefix list by its name, a case-sensitive string of 1 to 63 characters, to filter routes from Level-2 to Level-1 by destination address.
route-policy route-policy-name: Uses the specified routing policy to filter routes from Level-2 to Level-1. The route-policy-name argument is a case-sensitive string of 1 to 63 characters.
tag tag: Specifies a tag for marking redistributed routes, in the range of 1 to 4294967295.
Usage guidelines
If a routing policy is used, the routing policy must be specified in the import-route isis level-2 into level-1 command to filter routes from Level-2 to Level-1. Other routing policies specified for route reception and redistribution does not affect the route leaking.
If a filtering policy is configured, only Level-2 routes not filtered out can be advertised into the Level-1 area.
Examples
# Enable route advertisement from Level-2 to Level-1.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] address-family ipv4
[Sysname-isis-1-ipv4] import-route isis level-2 into level-1
Related commands
import-route
import-route isis level-1 into level-2
import-route isisv6 level-1 into level-2
Use import-route isisv6 level-1 into level-2 to enable route advertisement from Level-1 to Level-2.
Use undo import-route isisv6 level-1 into level-2 to disable route advertisement from Level-1 to Level-2.
Syntax
import-route isisv6 level-1 into level-2 [ filter-policy { ipv6-acl-number | prefix-list prefix-list-name | route-policy route-policy-name } | tag tag ] *
undo import-route isisv6 level-1 into level-2
Default
Route advertisement from Level-1 to Level-2 is enabled.
Views
IS-IS IPv6 unicast address family view
Predefined user roles
network-admin
Parameters
filter-policy: Specifies a filtering policy.
ipv6-acl-number: Specifies an IPv6 ACL by its number in the range of 2000 to 3999.
prefix-list prefix-list-name: Specifies an IPv6 prefix list by its name, a case-sensitive string of 1 to 63 characters.
route-policy route-policy-name: Specifies a routing policy by its name, a case-sensitive string of 1 to 63 characters.
tag tag: Specifies an administrative tag for marking redistributed routes, in the range of 1 to 4294967295.
Usage guidelines
This command enables a Level-1-2 router to redistribute Level-1 routes to Level-2 routers and Level-1-2 routers in the local area.
Examples
# Enable route advertisement from Level-1 to Level-2.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] address-family ipv6
[Sysname-isis-1-ipv6] import-route isisv6 level-1 into level-2
import-route isisv6 level-2 into level-1
Use import-route isisv6 level-2 into level-1 to enable IPv6 IS-IS route advertisement from Level-2 to Level-1.
Use undo import-route isisv6 level-2 into level-1 to restore the default.
Syntax
import-route isisv6 level-2 into level-1 [ filter-policy { ipv6-acl-number | prefix-list prefix-list-name | route-policy route-policy-name } | tag tag ] *
undo import-route isisv6 level-2 into level-1
Default
Route advertisement from Level-2 to Level-1 is disabled.
Views
IS-IS IPv6 unicast address family view
Predefined user roles
network-admin
Parameters
filter-policy: Specifies a filtering policy.
ipv6-acl-number: Specifies an IPv6 ACL by its number in the range of 2000 to 3999.
prefix-list prefix-list-name: Specifies an IPv6 prefix list by its name, a case-sensitive string of 1 to 63 characters.
route-policy route-policy-name: Specifies a routing policy by its name, a case-sensitive string of 1 to 63 characters.
tag: Specifies an administrative tag for marking redistributed routes, in the range of 1 to 4294967295.
Usage guidelines
This command enables a Level-1-2 router to redistribute Level-2 routes to the Level-1 and Level-1-2 routers in the local area.
Examples
# Enable IPv6 IS-IS route advertisement from Level-2 to Level-1.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] address-family ipv6
[Sysname-isis-1-ipv6] import-route isisv6 level-2 into level-1
import-route limit
Use import-route limit to configure the maximum number of redistributed Level 1/Level 2 routes.
Use undo import-route limit to restore the default.
Syntax
import-route limit number
undo import-route limit
Default
For the S6520X-EI switch series, the maximum number of redistributed Level 1/Level 2 routes is 65536 for IPv4 IS-IS and 6144 for IPv6 IS-IS. For the S6520X-HI and S5560X-HI switch series, the maximum number of redistributed Level 1/Level 2 routes is 131072 for IPv4 IS-IS and 6144 for IPv6 IS-IS. For the S6520X-SI, S6520-SI, and MS4600 switch series, the maximum number of redistributed Level 1/Level 2 routes is 16384 for IPv4 IS-IS and 6144 for IPv6 IS-IS. For the S5000-EI switch series, the maximum number of redistributed Level 1/Level 2 routes is 8192 for IPv4 IS-IS and 3072 for IPv6 IS-IS.
Views
IS-IS IPv4 unicast address family view
IS-IS IPv6 unicast address family view
Predefined user roles
network-admin
Parameters
number: Specifies the maximum number of redistributed Level 1/Level 2 routes.For the S6520X-EI switch series, the value range for this argument is 1 to 65536 for IPv4 IS-IS and 1 to 32768 for IPv6 IS-IS. For the S6520X-HI and S5560X-HI switch series, the value range for this argument is 1 to 131072 for IPv4 IS-IS and 1 to 65536 for IPv6 IS-IS. For the S6520X-SI, S6520-SI, and MS4600 switch series, the value range for this argument is 1 to 16384 for IPv4 IS-IS and 1 to 8192 for IPv6 IS-IS. For the S5000-EI switch series, the value range for this argument is 1 to 8192 for IPv4 IS-IS and 1 to 4096 for IPv6 IS-IS.
Examples
# Configure IS-IS process 1 to redistribute up to 1000 Level 1/Level 2 routes.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] address-family ipv4
[Sysname-isis-1-ipv4] import-route limit 1000
Related commands
import-route
isis
Use isis to enable IS-IS and enter IS-IS view.
Use undo isis to disable IS-IS.
Syntax
isis [ process-id ] [ vpn-instance vpn-instance-name ]
undo isis [ process-id ]
Default
IS-IS is disabled.
Views
System view
Predefined user roles
network-admin
Parameters
process-id: Specifies an IS-IS process by its ID in the range of 1 to 65535. The default is 1.
vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters. If no VPN instance is specified, the IS-IS process runs on the public network.
Examples
# Enable IS-IS process 1 and set the system ID to 0000.0000.0002 and area ID to 01.0001.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] network-entity 01.0001.0000.0000.0002.00
Related commands
isis enable
isis authentication send-only
Use isis authentication send-only to configure an IS-IS interface not to check the authentication information in the received hello packets.
Use undo isis authentication send-only to remove the configuration.
Syntax
isis authentication send-only [ level-1 | level-2 ]
undo isis authentication send-only [ level-1 | level-2 ]
Default
When interface authentication mode and key are configured, an IS-IS interface checks the authentication information in the received packets.
Views
Interface view
Predefined user roles
network-admin
Parameters
level-1: Configures IS-IS not to check the authentication information in the received Level-1 hello packets.
level-2: Configures IS-IS not to check the authentication information in the received Level-2 hello packets.
Usage guidelines
When peer authentication mode and key are configured, an IS-IS interface adds the key in the specified mode into transmitted hello packets. It also checks the key in the received hello packets.
To prevent packet exchange failure in case of an authentication key change, configure the IS-IS interface not to check the authentication information in the received packets.
Examples
# Configure VLAN-interface 10 not to check the authentication information in the received Level-1 hello packets.
<Sysname> system-view
[Sysname] interface vlan-interface 10
[Sysname-Vlan-interface10] isis authentication send-only level-1
Related commands
area-authentication send-only
domain-authentication send-only
isis authentication-mode
isis authentication-mode
Use isis authentication-mode to specify the neighbor relationship authentication mode and a key.
Use undo isis authentication-mode to remove the configuration.
Syntax
isis [ process-id process-id ] authentication-mode { { gca key-id { hmac-sha-1 | hmac-sha-224 | hmac-sha-256 | hmac-sha-384 | hmac-sha-512 } [ nonstandard ] | md5 | simple } { cipher | plain } string | keychain keychain-name } [ level-1 | level-2 ] [ ip | osi ]
undo isis [ process-id process-id ] authentication-mode [ level-1 | level-2 ]
Default
No neighbor relationship authentication mode or key is configured.
Views
Interface view
Predefined user roles
network-admin
Parameters
process-id process-id: Specifies an IS-IS multi-instance process by its ID in the range of 1 to 65535. If you do not specify this option, the traditional IS-IS process is specified.
gca: Specifies the GCA mode.</