- Table of Contents
-
- 09-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-Basic BGP commands
- 07-Advanced BGP commands
- 08-Policy-based routing commands
- 09-IPv6 static routing commands
- 10-RIPng commands
- 11-OSPFv3 commands
- 12-IPv6 policy-based routing commands
- 13-Routing policy commands
- 14-RIR commands
- Related Documents
-
Title | Size | Download |
---|---|---|
05-IS-IS commands | 1.74 MB |
advertise application link-attributes
bfd all-interfaces adjust-cost
bfd all-interfaces session-restrict-adj
display isis event-log graceful-restart
display isis flex-algo spf-tree
display isis global-statistics
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 microloop-avoidance enable
fast-reroute microloop-avoidance rib-update-delay
fast-reroute primary-path-detect bfd
fast-reroute remote-lfa maximum-cost
fast-reroute remote-lfa prefix-list
fast-reroute remote-lfa tunnel ldp
fast-reroute tiebreaker (Flexible algorithm view)
flex-algo (segment routing view)
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 bfd session-restrict-adj exclude
isis fast-reroute lfa-backup exclude
isis fast-reroute remote-lfa disable
isis ipv6 bfd adjust-cost exclude
isis ipv6 bfd session-restrict-adj
isis ipv6 bfd session-restrict-adj exclude
isis ipv6 fast-reroute lfa-backup exclude
isis ipv6 primary-path-detect bfd
isis ipv6 primary-path-detect bfd exclude
isis peer hold-max-cost duration
isis primary-path-detect bfd exclude
isis troubleshooting max-number
metric-bandwidth advertisement enable
metric-delay advertisement enable
reset isis event-log graceful-restart
segment-routing microloop-avoidance enable
segment-routing microloop-avoidance rib-update-delay
segment-routing microloop-avoidance strict-sid-only
timer lsp-flood suppress-flapping
timer lsp-generation suppress-flapping
timer purge-zero-lsp route-calculate-delay
timer route-calculate suppress-flapping
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]
advertise application link-attributes
Use advertise application link-attributes to enable IS-IS to advertise application-specific link attributes (ASLA).
Use undo advertise application link-attributes to disable IS-IS from advertising application-specific link attributes.
Syntax
advertise application link-attributes { bandwidth | delay| srlg | te | unidirectional-bandwidth } [ asla-only ]
undo advertise application link-attributes { bandwidth | delay| srlg | te | unidirectional-bandwidth }
advertise application link-attributes { te [ suppression ] | srlg [ suppression ] } *
undo advertise application link-attributes { te [ suppression ] | srlg [ suppression ] } *
Default
IS-IS does not advertise any application-specific link attributes.
Views
IS-IS IPv4 address family view
IS-IS IPv6 address family view
Predefined user roles
network-admin
Parameters
bandwidth: Advertises link bandwidth information defined by RFC 5305. Bandwidth information defined by RFC 5305 is static, and bandwidth information defined by RFC 8570 is dynamic.
delay: Advertises link delay information.
srlg: Advertises link SRLG attribute information.
te: Advertises the TE attributes, link delay, and link bandwidth.
unidirectional-bandwidth: Advertises link bandwidth information defined by RFC 8570.
asla-only: Allows IS-IS to advertise link attribute information through only ASLA sub-TLVs, and prevents IS-IS from advertising link attribute information through Shared Risk Link Group TLVs and Extended IS Reachability TLVs. If you do not specify the asla-only keyword, IS-IS can advertise link attribute information through ASLA sub-TLVs, Shared Risk Link Group TLVs, or Extended IS Reachability TLVs.
te suppression: Suppresses IS-IS from advertising TE attributes, link delay information, and link bandwidth information. If you do not specify the suppression keyword, the command does not suppress IS-IS from advertising TE attributes, link delay, and bandwidth information.
srlg suppression: Suppresses IS-IS from advertising SRLG attribute information. If you do not specify the suppression keyword, the command does not suppress IS-IS from advertising SRLG attribute information.
Usage guidelines
IS-IS advertises application-specific link attributes in ASLA sub-TLVs for use by specific applications. In the current software version, IS-IS only advertises link attributes for use by flexible algorithms. This feature is required when the flexible algorithm uses link delay metric or TE metric for path calculation. After you enable this feature, each ASLA sub-TLV will carry a link attribute sub-sub-TLV that can contain the TE attributes, delay, bandwidth, and SRLG attribute of a link.
If the flexible algorithm uses link delay metric, link attribute sub-sub-TLVs can carry link attribute information only after you enable IS-IS link delay advertisement.
If the flexible algorithm uses TE metric, link attribute sub-sub-TLVs can carry link attribute information only after the following requirements are met:
· MPLS TE is enabled for each node that participates in path calculation for that flexible algorithm.
· MPLS and MPLS TE are enabled on each interface that participates in path calculation for that flexible algorithm.
· TE is enabled for IS-IS. To enable TE, perform one of the following tasks:
¡ Use the te attribute enable command to enable TE for IS-IS.
¡ Use the router-id command to enable IPv6 TE.
· Use advertise application link-attributes to enable ASLA advertisement for IS-IS.
When the flexible algorithm uses the TE metric reported by interfaces, configure only the isis te-metric flex-algo command.
IS-IS also advertises TE attribute and SRLG attribute information through Extended IS Reachability TLVs and Shared Risk Link Group TLVs, respectively. To reduce the LSDB size, specify the asla-only keyword when executing this command, so that IS-IS advertises link attribute information only through ASLA sub-TLVs. Table 1 shows the impact of the asla-only keyword.
Figure 1 Impact of the asla-only keyword on link attribute information advertisement
Advertised link attribute information |
Without the asla-only keyword |
With the asla-only keyword |
bandwidth |
Both ASLA sub-TLVs and Extended IS Reachability TLVs advertise the following bandwidth information defined by RFC 5305: · Type 9—Maximum Link Bandwidth. · Type 10—Maximum Reservable Link Bandwidth. · Type 11—Unreserved Bandwidth. |
Only ASLA sub-TLVs advertise the following bandwidth information defined by RFC 5305: · Type 9—Maximum Link Bandwidth. · Type 10—Maximum Reservable Link Bandwidth. · Type 11—Unreserved Bandwidth. |
delay |
Both ASLA sub-TLVs and Extended IS Reachability TLVs advertise the following link delay information defined by RFC 8570: · Type 33—Unidirectional Link Delay. · Type 34—Min/Max Unidirectional Link Delay. · Type 35—Unidirectional Delay Variation. |
Only ASLA sub-TLVs advertise the following link delay information defined by RFC 8570: · Type 33—Unidirectional Link Delay. · Type 34—Min/Max Unidirectional Link Delay. · Type 35—Unidirectional Delay Variation. |
srlg |
ASLA sub-TLVs advertise the SRLG attribute information defined by RFC 8919. Shared Risk Link Group TLVs advertise the SRLG attribute information defined by RFC 5307 and RFC 6119. |
Only ASLA sub-TLVs advertise the SRLG attribute information defined by RFC 8919. |
te |
ASLA sub-TLVs advertise the TE attribute information, link delay information, and bandwidth information defined by RFC 8919. Extended IS Reachability TLVs advertise the following information: · TE attribute information defined by RFC 5305. · Link delay information and bandwidth information defined by RFC 8570. |
Only ASLA sub-TLVs advertise the TE attribute information, link delay information, and bandwidth information defined by RFC 8919. |
unidirectional-bandwidth |
Both ASLA sub-TLVs and Extended IS Reachability TLVs advertise the following bandwidth information defined by RFC 8570: · Type 37—Unidirectional Residual Bandwidth. · Type 38—Unidirectional Available Bandwidth. · Type 39—Unidirectional Utilized Bandwidth. |
Only ASLA sub-TLVs advertise the following bandwidth information defined by RFC 8570: · Type 37—Unidirectional Residual Bandwidth. · Type 38—Unidirectional Available Bandwidth. · Type 39—Unidirectional Utilized Bandwidth. |
To suppress IS-IS from advertising TE attribute information, link delay information, and bandwidth information in Extended IS Reachability TLVs, use one of the following commands:
· advertise application link-attributes te asla-only
· advertise application link-attributes te suppression
To suppress IS-IS from advertising SRLG attribute information in Shared Risk Link Group TLVs, use one of the following commands:
· advertise application link-attributes srlg asla-only
· advertise application link-attributes srlg suppression
This feature is available when the link cost style is wide, compatible, or wide-compatible.
Examples
# Enable IS-IS to advertise application-specific link attributes, including TE attributes, link delay, link bandwidth, and SRLG attribute.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] cost-style wide
[Sysname-isis-1] address-family ipv6
[Sysname-isis-1-ipv6] advertise application link-attributes te srlg
Related commands
advertise link-attributes
cost-style
metric-bandwidth advertisement enable
metric-delay advertisement enable
router-id (Segment Routing Command Reference)
te attribute enable
advertise link-attributes
Use advertise link-attributes to enable IS-IS to advertise link attributes in LSPs.
Use undo advertise link-attributes to restore the default.
Syntax
advertise link-attributes
undo advertise link-attributes
Default
IS-IS does not advertise link attributes in LSPs.
Views
IS-IS IPv4 address family view
IS-IS IPv6 address family view
Predefined user roles
network-admin
Usage guidelines
Link attributes advertised in LSPs include the following:
· IP address.
· Link delay information. (The attribute is included after you enable link delay advertisement by using the metric-delay advertisement enable command.)
· Link bandwidth information. (The attribute is included after you enable link bandwidth advertisement by using the metric-bandwidth advertisement enable command.)
Multiple P2P neighbors might exist between two devices. To ensure correct route calculation, configure each device to advertise IP address of the local interface to its neighbors by using the advertise link-attributes or router-id command.
You can execute this command only after the link cost style is wide, compatible or wide-compatible.
Examples
# Enable IS-IS process 1 to advertise link attributes in LSPs.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] address-family ipv4
[Sysname-isis-1-ipv4] advertise link-attributes
Related commands
cost-style
metric-bandwidth advertisement enable
metric-delay advertisement enable
router-id (Segment Routing Command Reference)
advertise-definition enable
Use advertise-definition enable to enable FAD advertisement on a node.
Use undo advertise-definition enable to disable FAD advertisement on a node.
Syntax
advertise-definition enable
undo advertise-definition enable
Default
FAD advertisement is disabled on a node.
Views
Flexible algorithm view
Predefined user roles
network-admin
Usage guidelines
This feature enables a node to advertise its FAD. To calculate optimal paths for a flexible algorithm, you must enable this feature on a minimum of one node in the topology.
If a node does not advertise its FAD (for example, flexible algorithm 128), it can participate in flexible algorithm 128 only when it meets the following requirements:
1. The node receives the definitions of flexible algorithm 128 advertised by neighbors, and selects an FAD with the highest priority.
2. The metric type in the selected FAD is supported by the node.
This feature is available when the link cost style is wide, compatible, or wide-compatible.
Examples
# Enable FAD advertisement for flexible algorithm 128.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] flex-algo 128
[Sysname-isis-1-flex-algo-128] advertise-definition enable
Related commands
cost-style
display isis flex-algo route
affinity exclude-any
Use affinity exclude-any to specify the exclude-any constraint for a flexible algorithm.
Use undo affinity exclude-any to restore the default.
Syntax
affinity exclude-any affinity-name&<1-32>
undo affinity exclude-any
Default
The flexible algorithm topology excludes no links.
Views
Flexible algorithm view
Predefined user roles
network-admin
Parameters
affinity-name&<1-32>: Specifies affinity attributes by their names. The affinity attribute name must be a case-sensitive string of 1 to 32 characters. &<1-32> indicates that you can specify a maximum of 32 affinity attribute names. The specified affinity attribute names must already exist.
Usage guidelines
A link will be excluded from the flexible algorithm topology if it has an affinity attribute that is included in the exclude-any constraint.
This feature is available when the link cost style is wide, compatible, or wide-compatible.
Examples
# Exclude links with affinity attribute red from the topology of flexible algorithm 128.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] flex-algo 128
[Sysname-isis-1-flex-algo-128] affinity exclude-any red
Related commands
cost-style
affinity include-all
Use affinity include-all to specify the include-all constraint for a flexible algorithm.
Use undo affinity include-all to restore the default.
Syntax
affinity include-all affinity-name&<1-32>
undo affinity include-all
Default
The flexible algorithm topology excludes no links.
Views
Flexible algorithm view
Predefined user roles
network-admin
Parameters
affinity-name&<1-32>: Specifies affinity attributes by their names. The affinity attribute name must be a case-sensitive string of 1 to 32 characters. &<1-32> indicates that you can specify a maximum of 32 affinity attribute names. The specified affinity attribute names must already exist.
Usage guidelines
A link will be excluded from the flexible algorithm topology if it does not have all the affinity attributes that are included in the include-all constraint.
This feature is available when the link cost style is wide, compatible, or wide-compatible.
Examples
# Exclude links that do not have affinity attributes red and blue from the topology of flexible algorithm 128.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] flex-algo 128
[Sysname-isis-1-flex-algo-128] affinity include-all red blue
Related commands
affinity-map
cost-style
affinity include-any
Use affinity include-any to specify the include-any constraint for a flexible algorithm.
Use undo affinity include-any to restore the default.
Syntax
affinity include-any affinity-name&<1-32>
undo affinity include-any
Default
The flexible algorithm topology excludes no links.
Views
Flexible algorithm view
Predefined user roles
network-admin
Parameters
affinity-name&<1-32>: Specifies affinity attributes by their names. The affinity attribute name must be a case-sensitive string of 1 to 32 characters. &<1-32> indicates that you can specify a maximum of 32 affinity attribute names. The specified affinity attribute names must already exist.
Usage guidelines
A link will be excluded from the flexible algorithm topology if it does not have any affinity attribute that is included in the include-any constraint.
This feature is available when the link cost style is wide, compatible, or wide-compatible.
Examples
# Include links with affinity attribute red in the topology of flexible algorithm 128.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] flex-algo 128
[Sysname-isis-1-flex-algo-128] affinity include-any red
Related commands
affinity-map
cost-style
affinity-map
Use affinity-map to map an affinity attribute name to an affinity bit.
Use affinity-map to remove the configuration.
Syntax
affinity-map affinity-name bit-position bit
undo affinity-map affinity-name
Default
No affinity attribute name is mapped to an affinity bit.
Views
IS-IS view
Predefined user roles
network-admin
Parameters
affinity-name: Specifies an affinity attribute name, a case-sensitive string of 1 to 32 characters.
bit: Specifies an affinity bit by its number. The value range for this argument is 0 to 255.
Usage guidelines
IS-IS supports a maximum of 256 affinity bits. They are numbered from 0 to 255. You can use this feature to map different affinity attribute names to these bits. For example, after you use the affinity-map blue bit-position 3 command, affinity attribute name blue is mapped to affinity bit 3.
After you map a name to each affinity bit, you can specify the affinity attributes of a link or defines flexible algorithm topologies by using affinity attribute names.
To avoid configuration failure, follow these guidelines:
· You cannot map different affinity attribute names to the same affinity bit.
· Perform this task only when the link cost style is wide, compatible, or wide-compatible.
Examples
# Map affinity attribute name red to affinity bit 1.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] affinity-map red bit-position 1
Related commands
cost-style
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. In simple authentication mode and GCA authentication mode, the plaintext form of the key is a case-sensitive string of 1 to 16 characters, and the encrypted form is a case-sensitive string of 33 to 53 characters. In MD5 authentication mode, the plaintext form of the key is a case-sensitive string of 1 to 255 characters, and the encrypted form is a case-sensitive string of 33 to 373 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.
IS-IS keychain authentication supports the HMAC-MD5 and HMAC-SM3 authentication algorithms. If the HMAC-MD5 algorithm is used, the key ID can be any value in the range supported by the key-id argument. If the HMAC-SM3 algorithm is used, the key ID must be in the range of 0 to 65535.
When keychain authentication is used, IS-IS receives and sends packets as follows:
· 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 or HMAC-SM3 algorithm, the authentication fails and the packet does not contain authentication information.
· After IS-IS receives a Level-1 packet, it processes the packet as follows:
¡ If the authentication algorithm of the packet is HMAC-MD5, IS-IS 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.
¡ If the authentication algorithm of the packet is HMAC-SM3, IS-IS uses the key ID of the received packet to obtain the corresponding valid accept key from the keychain. Then, IS-IS uses the accept key to authenticate the packet. If IS-IS cannot find a valid accept key based on the key ID of the received packet or the packet fails the authentication, 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 (including non-H3C 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.
In MD5 authentication mode, execute the undo area-authentication-mode command before version switch if the key lengths supported by the two versions are different.
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
bfd all-interfaces adjust-cost
Use bfd all-interfaces adjust-cost to enable BFD session state-based interface cost adjustment for an IS-IS process.
Use undo bfd all-interfaces adjust-cost to disable BFD session state-based interface cost adjustment for an IS-IS process.
Syntax
bfd all-interfaces adjust-cost { cost-offset | max }
undo bfd all-interfaces adjust-cost
Default
BFD session state-based interface cost adjustment is disabled.
Views
IS-IS IPv4 address family view
IS-IS IPv6 address family view
Predefined user roles
network-admin
Parameters
cost-offset: Specifies the interface cost adjustment value. The value range for this argument is 1 to 16777213. When the BFD session goes down, the interface cost is cost-offset plus the original interface cost, and cannot exceed 16777214.
max: Sets the interface cost to the maximum value (16777214) when the BFD session goes down.
Usage guidelines
IMPORTANT: For the bfd all-interfaces adjust-cost command to take effect on an IS-IS process, enable BFD for that IS-IS process first. |
After you enable BFD for IS-IS link failure detection, the IS-IS neighbor relationship goes down when the BFD session is down and comes up when the BFD session is up. When the BFD session state changes frequently, IS-IS neighbor relationship flapping will occur. The running of services (such as BGP) that rely on IS-IS might be interrupted. To resolve this issue, use one of the following commands to enable BFD session state-based interface cost adjustment for IS-IS:
· bfd all-interfaces adjust-cost
· isis bfd adjust-cost
· isis ipv6 bfd adjust-cost
These commands are different as follows:
· The bfd all-interfaces adjust-cost command takes effect on all interfaces in an IPv4 or IPv6 IS-IS process. After you execute this command, IS-IS adjusts the interface cost value as follows:
¡ When the BFD session on an interface in the IS-IS process goes down, IS-IS increases the cost value for the interface.
¡ When the BFD session on an interface in the IS-IS process comes up again, IS-IS restores the cost value for the interface to the original value.
· The isis bfd adjust-cost and isis ipv6 bfd adjust-cost commands take effect only on one IS-IS interface. To enable BFD session state-based interface cost adjustment on a single interface, perform the following tasks:
a. Make sure the IS-IS process to which the interface belongs is not enabled with BFD session state-based interface cost adjustment.
You can use the undo bfd all-interfaces adjust-cost command to disable this feature for an IS-IS process.
b. Use the isis bfd adjust-cost or isis ipv6 bfd adjust-cost command to enable this feature on the interface.
· For an IS-IS interface, the configuration of the isis bfd adjust-cost or isis ipv6 bfd adjust-cost command takes precedence over that of the bfd all-interfaces adjust-cost command.
Examples
# Enable BFD session state-based interface cost adjustment for IS-IS process 1, and set the interface cost adjustment value to 100.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] address-family ipv4
[Sysname-isis-1-ipv4] bfd all-interfaces adjust-cost 100
Related commands
isis bfd adjust-cost
isis ipv6 bfd adjust-cost
bfd all-interfaces enable
Use bfd all-interfaces enable to enable BFD for an IS-IS process.
Use undo bfd all-interfaces enable to disable BFD for an IS-IS process.
Syntax
bfd all-interfaces enable
undo bfd all-interfaces enable
Default
BFD is disabled for an IS-IS process.
Views
IS-IS IPv4 address family view
IS-IS IPv6 address family view
Predefined user roles
network-admin
Usage guidelines
IS-IS exchanges hello packets at specific intervals with its neighbors to detect neighbor state changes. If IS-IS does not receive any hello packets from a neighbor within the advertised neighbor relationship hold time, it considers the neighbor down and recalculates the routes. The hold time is the hello multiplier multiplied by the hello interval and the default hold time is 30 seconds. This mechanism is not efficient at neighbor state change detection. Serious packet loss might occur when a neighbor goes down.
To resolve this issue, use this command to enable BFD for the IS-IS process. BFD provides a single mechanism to quickly detect and monitor the connectivity of links between IS-IS neighbors, reducing route convergence time.
You can use the bfd all-interfaces enable, isis bfd enable, or isis ipv6 bfd enable command to enable IS-IS BFD. These commands are different as follows:
· The bfd all-interfaces enable command enables BFD on all interfaces in an IPv4 or IPv6 IS-IS process.
· The isis bfd enable and isis ipv6 bfd enable commands take effect only on one IS-IS interface. To enable BFD on a single IS-IS interface, perform the following tasks:
a. Make sure the IS-IS process to which the interface belongs is not enabled with BFD.
You can use the undo bfd all-interfaces enable command to disable BFD for an IS-IS process.
b. Use the isis bfd enable or isis ipv6 bfd enable command to enable BFD on the IS-IS interface.
Examples
# Enable BFD for IS-IS process 1.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] address-family ipv4
[Sysname-isis-1-ipv4] bfd all-interfaces enable
Related commands
isis bfd enable
isis ipv6 bfd enable
bfd all-interfaces session-restrict-adj
Use bfd all-interfaces session-restrict-adj to enable BFD session state-based control of adjacency establishment and maintenance for an IS-IS process.
Use undo bfd all-interfaces session-restrict-adj to disable BFD session state-based control of adjacency establishment and maintenance for an IS-IS process.
Syntax
bfd all-interfaces session-restrict-adj
undo bfd all-interfaces session-restrict-adj
Default
BFD session state-based control of adjacency establishment and maintenance is disabled for an IS-IS process.
Views
IS-IS IPv4 address family view
IS-IS IPv6 address family view
Predefined user roles
network-admin
Usage guidelines
IMPORTANT: For the bfd all-interfaces session-restrict-adj command to take effect on an IS-IS process, enable BFD for that IS-IS process first. |
When BFD detects a Layer 3 forwarding failure between two devices, the BFD session goes down, causing the IPv4 IS-IS adjacency to go down. If Layer 2 forwarding is still available, the devices still can exchange IS-IS packets and re-establish the adjacency. This might cause traffic loss.
To avoid the issue, execute this command on both the local and remote devices. This command enables the interfaces in these IS-IS processes to carry BFD-enabled TLVs in hello packets. After the BFD session between the two devices goes down, the devices do not establish an adjacency if the exchanged BFD-enabled TLVs are identical.
If you configure this command for an existing adjacency, the BFD session state does not affect the adjacency relationship within the hold time. This mechanism avoids adjacency flappings during BFD session establishment.
You can use one of the following commands to enable BFD session state-based control of IS-IS adjacency establishment and maintenance:
· bfd all-interfaces session-restrict-adj
· isis bfd session-restrict-adj
· isis ipv6 bfd session-restrict-adj
These commands are different as follows:
· The bfd all-interfaces session-restrict-adj command takes effect on all interfaces in an IPv4 or IPv6 IS-IS process.
· The isis bfd session-restrict-adj and isis ipv6 bfd session-restrict-adj commands take effect only on one IS-IS interface. To enable BFD session state-based control of adjacency establishment and maintenance on a single IS-IS interface, perform the following tasks:
a. Make sure the IS-IS process to which the IS-IS interface belongs is not enabled with BFD session state-based control of adjacency establishment and maintenance.
You can use the undo bfd all-interfaces session-restrict-adj command to disable this feature for an IS-IS process.
b. Use the isis bfd session-restrict-adj or isis ipv6 bfd session-restrict-adj command to enable this feature on the IS-IS interface.
Examples
# Enable BFD session state-based control of adjacency establishment and maintenance for IS-IS process 1.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] address-family ipv4
[Sysname-isis-1-ipv4] bfd all-interfaces session-restrict-adj
Related commands
bfd all-interfaces enable
isis bfd session-restrict-adj
isis ipv6 bfd session-restrict-adj
bfd all-interfaces template
Use bfd all-interfaces template to apply a BFD template to an IS-IS process.
Use undo bfd all-interfaces template to restore the default.
Syntax
bfd all-interfaces template template-name
undo bfd all-interfaces template
Default
No BFD template is applied to an IS-IS process. The system uses the default BFD detection parameters to establish BFD sessions with neighbors.
Views
IS-IS IPv4 address family view
IS-IS IPv6 address family view
Predefined user roles
network-admin
Parameters
template-name: Specifies the name of a BFD template, a case-sensitive string of 1 to 63 characters.
Usage guidelines
After you enable BFD for IS-IS and apply a BFD template, IS-IS notifies BFD of the following information when using BFD to detect the link to a neighbor:
· Destination address.
· Source address.
· Detection parameters defined in the BFD template.
BFD establishes a BFD session based on the information received. By editing detection parameters for the template, you can adjust the speed at which IS-IS detects link failures. For more information about BFD templates, see configuring BFD in High Availability Configuration Guide.
This command takes effect only when BFD is enabled for IS-IS and the specified BFD template exists.
You can use the bfd all-interfaces template, isis bfd template, or isis ipv6 bfd template command to apply a BFD template. These commands are different as follows:
· The bfd all-interfaces template command takes effect on all interfaces in an IPv4 or IPv6 IS-IS process.
· The isis bfd template and isis ipv6 bfd template commands take effect on a specific IS-IS interface.
· The interface-specific template configuration takes precedence over the process-specific template configuration.
Examples
# Apply BFD template TEMP1 to IS-IS process 1.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] address-family ipv4
[Sysname-isis-1-ipv4] bfd all-interfaces template TEMP1
Related commands
bfd all-interfaces enable
bfd template (High Availability Command Reference)
isis bfd enable
isis bfd template
isis ipv6 bfd enable
isis ipv6 bfd template
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 1 to 63.
· For styles wide and wide-compatible, the cost value is in the range of 1 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
color-mapping
Use color-mapping to map a color attribute to a flexible algorithm.
Use undo color-mapping to remove the mapping between a color attribute and a flexible algorithm.
Syntax
color-mapping color-value flex-algo flex-algo-id
undo color-mapping color-value flex-algo flex-algo-id
Default
A color attribute is not mapped to any flexible algorithm.
Views
SR flexible algorithm view
Predefined user roles
network-admin
Parameters
color-value: Specifies a color attribute value in the range of 0 to 4294967295.
flex-algo-id: Specifies a flexible algorithm ID in the range of 128 to 255.
Usage guidelines
Execute this command to forward packets through the path calculated by the specified flexible algorithm in an SR MPLS network where multiple paths exist between the source and destination nodes.
After you execute this command, an SR node processes a received BGP route that carries the color attribute as follows:
1. Finds the flexible algorithm mapped to the color attribute.
2. Finds the path calculated by the flexible algorithm based on the destination address of the BGP route.
3. Iterates the BGP route to the path.
Then, the SR node will forward packets that match the BGP route through the path.
If a BGP route received by the SR node does not carry the extended community attribute, you can perform either of the following tasks to specify a color attribute for the route:
· Add a color value to the route by using a routing policy.
· Execute the default-color command to specify a default color value for the route.
A color attribute can be mapped to only one flexible algorithm, but a flexible algorithm can be mapped to multiple color attributes.
Examples
# Map color attribute 11 to flexible algorithm 128.
<Sysname> system-view
[Sysname] segment-routing
[Sysname-segment-routing] flex-algo
[Sysname-sr-flex-algo] color-mapping 11 flex-algo 128
Related commands
flex-algo
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 1 to 63.
wide: Receives and sends only wide cost style packets. The wide cost is in the range of 1 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 the compatible or narrow-compatible keyword is specified.
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 [ route-policy route-policy-name ]
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
IPv6 router ID : 1000::1
Fast reroute : Disabled
Microloop-avoidance
level-1 : Disabled
level-2 : Disabled
IPv6 microloop-avoidance
level-1 : Disabled
level-2 : Disabled
Microloop-avoidance RIB-update-delay
level-1 : 5000
level-2 : 5000
IPv6 microloop-avoidance RIB-update-delay
level-1 : 5000
level-2 : 5000
Fast-reroute remote-LFA
level-1 : Disabled
level-2 : Disabled
Node-protecting preference
level-1 : 40
level-2 : 40
Lowest-cost preference
level-1 : 20
level-2 : 20
SRLG preference
level-1 : 10
level-2 : 10
Link-state : Link-state
Instance ID : 10
Level-1 : Enabled
Level-2 : Enabled
Link attribute advertisement : Disabled
Metric-delay advertisement
level-1 : Disabled
level-2 : Disabled
Metric-delay advertisement suppression
Timer : 120
Percent Threshold : 10
Absolute Threshold : 1000
Metric-bandwidth advertisement
level-1 : Disabled
level-2 : Disabled
Metric-bandwidth advertisement suppression
Timer : 120
Preference : 15
LSP length receive : 1497
LSP length originate
level-1 : 1497
level-2 : 1497
Maximum imported routes : 1000
BFD : Enabled
BFD session-restrict-adj : Enabled
BFD adjust cost : Maximum
BFD template : TEMP1
Primary path detection mode : Ctrl
Timers
LSP-max-age : 1200
LSP-refresh : 900
SPF mode : Normal
SPF intervals : 5 50 200
Advertise application specific link attributes
TE : Disabled
SRLG : Disabled
Bandwidth : Disabled
Delay : Disabled
Link-Loss : Disabled
Unidirectional-Bandwidth : Disabled
IPv6 enabled
Multi-topology : Standard
Fast reroute : Disabled
SRv6-policy autoroute : Disabled
Preference : 15
Maximum imported routes : 1000
SPF mode : Normal
SPF intervals : 5 50 200
Link attribute advertisement: Disabled
BFD : Enabled
BFD session-restrict-adj : Enabled
BFD adjust cost : Maximum
BFD template : TEMP2
Primary path detection mode : Ctrl
Link attribute advertisement: Disabled
Metric-delay advertisement
level-1 : Disabled
level-2 : Disabled
Metric-delay advertisement suppression
Timer : 120
Percent Threshold : 10
Absolute Threshold : 1000
Metric-bandwidth advertisement
level-1 : Disabled
level-2 : Disabled
Metric-bandwidth advertisement suppression
Timer : 120
Advertise application specific link attributes
TE : Disabled
SRLG : Disabled
Bandwidth : Disabled
Delay : Disabled
Link-Loss : Disabled
Unidirectional-Bandwidth: Disabled
Segment routing IPv4
MPLS : Disabled
Adjacency : Disabled
Member-port adjacency : Disabled
Auto-adjacency : Disabled
Delete-delay : 1500
Configured SRGB : 25000 27000
Effective SRGB : 25000 27000
Level-1 tunnel count : 0
Level-2 tunnel count : 0
Local block : 210000 220000
Fast-reroute TI-LFA
level-1 : Disabled
level-2 : Disabled
Node-protecting preference
level-1 : 40
level-2 : 40
Lowest-cost preference
level-1 : 20
level-2 : 20
SRLG preference
level-1 : 10
level-2 : 10
SR microloop avoidance
level-1 : Disabled
level-2 : Disabled
SR microloop avoidance RIB-update-delay
level-1 : 5000
level-2 : 5000
Segment routing IPv6
SRv6 : Disabled
Segment routing IPv6 advertisement
L3 service SID : Enabled
SRv6 SRH compression
level-1 : Disable
level-2 : Disable
Fast-reroute TI-LFA
level-1 : Disabled
level-2 : Disabled
Node-protecting preference
level-1 : 40
level-2 : 40
Lowest-cost preference
level-1 : 20
level-2 : 20
SRLG preference
level-1 : 10
level-2 : 10
SR microloop avoidance
level-1 : Disabled
level-2 : Disabled
SR microloop avoidance RIB-update-delay
level-1 : 5000
level-2 : 5000
End.X SID deletion delay
State : Enabled
Delay time : 1800 sec
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. |
IPv6 router ID |
IPv6 router ID. |
Whether IS-IS isolation is enabled. |
|
Process state |
IS-IS process state. If you shut down the process by using the shutdown process command, this field displays Admin-down. If the process is not shut down, this field is not displayed. |
Fast reroute |
IS-IS FRR status: · Disabled—IS-IS FRR is disabled. · LFA—IS-IS FRR automatically calculates a backup next hop. · 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. |
Microloop-avoidance |
Microloop avoidance status for IPv4 IS-IS: Disabled or Enabled. |
IPv6 microloop-avoidance |
Microloop avoidance status for IPv6 IS-IS: Disabled or Enabled. |
Microloop-avoidance RIB-update-delay |
|
IPv6 microloop-avoidance RIB-update-delay |
Microloop avoidance RIB-update-delay timer for IPv6 IS-IS. |
Fast-reroute TI-LFA |
TI-LFA FRR status: Disabled or Enabled. |
Node-protecting preference |
Priority of the node-protection backup path selection policy. |
Lowest-cost preference |
Priority of the lowest-cost backup path selection policy. |
SRLG preference |
Priority of the shared risk link group (SRLG)-disjoint backup path selection policy. |
Link-state |
IS-IS link state information advertisement. · Link-state—The device advertises IS-IS link state information to all protocols, such as BGP. · BGP-LS—The device advertises IS-IS link state information to only BGP. |
Instance ID |
IS-IS instance ID. |
Link attribute advertisement |
Link attribute advertisement status: Disabled or Enabled. |
Metric-delay advertisement |
Link delay advertisement status: Disabled or Enabled. |
Metric-delay advertisement suppression |
Information about link delay advertisement suppression: · Timer—Link delay advertisement suppression timer in seconds. · Percent threshold—Suppression threshold for the delay variation ratio in percentage. · Absolute threshold—Suppression threshold for the absolute value of the delay variation in microseconds. This field is not displayed if IS-IS link delay advertisement is disabled. |
Metric-bandwidth advertisement |
Link bandwidth advertisement status: Disabled or Enabled. |
Metric-bandwidth advertisement suppression |
Link bandwidth advertisement suppression timer in seconds. This field is not displayed if link bandwidth advertisement is disabled. |
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. |
BFD |
BFD is enabled for the IS-IS process. This field is available only when BFD is enabled for the IS-IS process. |
BFD session state-based control of adjacency establishment and maintenance is enabled for the IS-IS process. This field is available only when this feature is enabled for the IS-IS process. |
|
BFD adjust cost |
Interface cost adjustment parameters: · cost-offset—Interface cost adjustment value. The value range for cost-offset is 1 to 16777213. When the BFD session goes down, the interface cost is cost-offset plus the original interface cost. · Maximum—Maximum interface cost value (16777214). When the BFD session goes down, IS-IS will adjust the interface cost to the maximum. This field is available only when BFD session state-based interface cost adjustment is enabled for the IS-IS process. |
BFD template |
BFD template applied to the IS-IS process. If no template is applied, this field is not displayed. |
BFD is used for primary link failure detection in the IS-IS process. Primary link failure detection modes include: · Ctrl—BFD control packet mode. · Echo—BFD echo packet mode. This field is available only when BFD is used for primary link failure detection in the IS-IS process. |
|
Timers |
Timers: · LSP-max-age—Maximum life period of LSPs. · LSP-refresh—Refresh interval of LSPs. · SPF mode—SPF interval calculation mode. · SPF intervals—Interval between SPF calculations. |
IS-IS ASLA advertisement settings. |
|
TE |
Whether IS-IS advertises the TE attribute, link delay, and link bandwidth. The Asla-only attribute indicates that IS-IS is suppressed from advertising TE attribute information, link delay information, and bandwidth information in Extended IS Reachability TLVs. |
SRLG |
Whether IS-IS advertises the SRLG attribute. The Asla-only attribute indicates that IS-IS is suppressed from advertising SRLG attribute information in Shared Risk Link Group TLVs. |
Bandwidth |
Whether IS-IS advertises the link bandwidth information defined by RFC 5305. The Asla-only attribute indicates that IS-IS is suppressed from advertising the link bandwidth information defined by RFC 5305 in Extended IS Reachability TLVs. |
Delay |
Whether IS-IS advertises link delay information. The Asla-only attribute indicates that IS-IS is suppressed from advertising link delay information in Extended IS Reachability TLVs. |
Unidirectional-Bandwidth |
Whether IS-IS advertises the link bandwidth information defined by RFC 8570. The Asla-only attribute indicates that IS-IS is suppressed from advertising the link bandwidth information defined by RFC 8570 in Extended IS Reachability TLVs. |
IPv6 enabled |
IPv6 is enabled. |
Multi-topology |
IPv6 unicast topology mode: · Standard—IPv6 unicast topology standard mode. · Compatible—IPv6 unicast topology compatible mode. |
SRv6-policy AutoRoute |
Whether automatic route advertisement is enabled for the SRv6 TE policy or SRv6 TE policy group. · Disabled—Not enabled. · level-1—Enabled at Level 1. · level-2—Enabled at Level 2. · level-1-2—Enabled at Level 1-2. |
Segment routing is supported: · MPLS—SR-MPLS status: Disabled or Enabled. · Adjacency—Adjacency label allocation status: Disabled or Enabled. · Member-port adjacency—Whether adjacency label allocation is enabled on member interfaces. · Auto-adjacency—Whether SR-MPLS adjacency label allocation is enabled. If this feature is not configured, this field is not displayed. ¡ Protected—SR-MPLS dynamically allocates protected adjacency labels. ¡ Disabled—SR-MPLS adjacency label allocation is disabled. · Delete-delay—Delay timer for deletion of protected adjacency labels. · Effective SRGB—SRGB range that takes effect. · Configured SRGB—Configured SRGB range. This field is displayed when SRGB is configured. · Level-1 tunnel count—Number of Level-1 SR tunnels. · Level-2 tunnel count—Number of Level-2 SR tunnels. · Local block—Minimum and maximum label values of the SRLB. |
|
Segment routing IPv6 |
Segment routing is supported: SRv6—SRV6 status: Disabled or Enabled. |
SRv6 advertisement information. |
|
L3 service SID |
Whether L3 service SID advertisement is enabled. |
SRv6 SRH compression |
Whether SRv6 SRH compression is enabled. |
Fast-reroute TI-LFA |
Topology independent LFA (TI-LFA) FRR status: Disabled or Enabled. |
Node-protecting preference |
Priority of the node-protection backup path selection policy. |
Lowest-cost preference |
Priority of the lowest-cost backup path selection policy. |
SRLG preference |
Priority of the shared risk link group (SRLG)-disjoint backup path selection policy. |
SR microloop avoidance |
SR microloop avoidance status: Disabled or Enabled. |
SR microloop avoidance RIB-update-delay |
SR microloop avoidance RIB-update-delay timer. |
End.X SID deletion delay |
Information about dynamic End.X SID deletion delay: · State—Status of dynamic End.X SID deletion delay: Disabled or Enabled. · Delay time—End.X SID deletion delay timer in seconds. |
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
slot slot-number: Specifies a card by its slot number.
Examples
# Display IS-IS GR log information for the specified slot.
<Sysname> display isis event-log graceful-restart slot 0
IS-IS loginfo :
Sep 18 08:48:24 2015 slot 0 Process 1 enter GR restarting phase(Initialization).
Sep 18 08:48:24 2015 slot 0 Process 1 enter GR phase (LSDB synchronization).
Sep 18 08:48:24 2015 slot 0 Process 1 enter GR phase (TE tunnel prepare).
Sep 18 08:48:24 2015 slot 0 Process 1 enter GR phase (First SPF computation).
Sep 18 08:48:25 2015 slot 0 Process 1 enter GR phase (Redistribution).
Sep 18 08:48:25 2015 slot 0 Process 1 enter GR phase (Second SPF computation).
Sep 18 08:48:25 2015 slot 0 Process 1 enter GR phase (LSP stability).
Sep 18 08:48:25 2015 slot 0 Process 1 enter GR phase (LSP generation).
Sep 18 08:48:25 2015 slot 0 Process 1 enter GR phase (Finish).
Sep 18 08:48:25 2015 slot 0 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. · 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 (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 change.
<Sysname> display isis event-log hello peer-change
Hello logs for IS-IS(1)
-----------------------
Interface: XGE0/0/6; NbrSystemID: 0000.0000.0002
Level-2 peer Up->Down at 2019-11-21 15:10:10:207
First 3 hello packets sent:
2019-11-21 11:34:33:311, succeeded
2019-11-21 11:34:33:323, succeeded
2019-11-21 11:34:41:057, succeeded
Last 3 hello packets sent:
2019-11-21 15:09:44:106, succeeded
2019-11-21 15:09:54:075, succeeded
2019-11-21 15:10:03:203, succeeded
First 3 hello packets received:
2019-11-21 11:34:33:321
2019-11-21 11:34:33:978
2019-11-21 11:34:43:524
Last 3 hello packets received:
2019-11-21 15:10:01:063
2019-11-21 15:10:04:370
2019-11-21 15:10:07:851
Interface: XGE0/0/6; NbrSystemID: 0000.0000.0002
Level-1 peer Up->Down at 2019-11-21 15:10:10:206
First 3 hello packets sent:
2019-11-21 11:34:33:310, succeeded
2019-11-21 11:34:33:320, succeeded
2019-11-21 11:34:42:845, succeeded
Last 3 hello packets sent:
2019-11-21 15:09:50:074, succeeded
2019-11-21 15:09:57:643, succeeded
2019-11-21 15:10:05:665, succeeded
First 3 hello packets received:
2019-11-21 11:34:33:313
2019-11-21 11:34:35:738
2019-11-21 11:34:44:346
Last 3 hello packets received:
2019-11-21 15:10:01:062
2019-11-21 15:10:04:370
2019-11-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: 2019-06-06 Time: 14:51:20:121 Interface: XGE0/0/6
PDU type: L1 hello; errno: 132
Date: 2019-06-06 Time: 14:51:20:121 Interface: XGE0/0/6
PDU type: L2 hello; errno: 132
Date: 2019-06-06 Time: 11:20:20:116 Interface: XGE0/0/7
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)
---------------------------
Hello logs for IS-IS(1)
---------------------------
Date: 2019-06-06 Time: 11:21:12:121 Interface: XGE0/0/6
PDU type: L1 hello, last one sent: 2019-06-06 11:20:51:916
Date: 2019-06-06 Time: 11:56:21:312 Interface: XGE0/0/7
PDU type: P2P hello, last one sent: 2019-06-06 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: 2019-06-06 Time: 14:51:22:791 Interface: XGE0/0/6
PDU type: L1 hello, NbrSystemID: 0000.0000.0001
Drop reason: Excessive area addresses
Date: 2019-06-06 Time: 14:51:20:121 Interface: XGE0/0/7
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(vpna-1)
---------------------------
Date: 2019-06-06 Time: 10:12:22:121 Interface: XGE0/0/6
PDU type: L1 hello, NbrSystemID: 0000.0000.0001
Last one received: 2019-06-06 10:12:01:212
Date: 2019-06-06 Time: 14:51:20:121 Interface: XGE0/0/6
PDU type: L1 hello, NbrSystemID: 0000.0000.0001
Last one received: 2019-06-06 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-09-25 10:19:48 1111.1111.1111.01-00 0x00000001 Generated LSP purge packet
2019-09-25 10:19:48 1111.1111.1111.01-00 0x00000001 Received LSP purge packet
2019-09-25 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-09-25 10:19:48 1111.1111.1111.01-00 0x00000001 Generated LSP purge packet
2019-09-25 10:19:48 1111.1111.1111.01-00 0x00000001 Received LSP purge packet
2019-09-25 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-09-25 17:18:48 0000.0000.0012.00-00 0x00000038 Received LSP
2019-09-25 17:18:48 0000.0000.0011.00-00 0x00000042 Received LSP
2019-09-25 17:18:48 0000.0000.0012.00-00 0x00000039 Generated LSP
2019-09-25 17:18:48 0000.0000.0012.00-00 0x00000038 Received LSP
2019-09-25 17:18:48 0000.0000.0011.00-00 0x00000042 Received LSP
2019-09-25 17:18:48 0000.0000.0012.00-00 0x00000002 Generated LSP
2019-09-25 17:18:48 0000.0000.0011.01-00 0x00000032 Received LSP
2019-09-25 17:18:48 0000.0000.0011.02-00 0x00000035 Received LSP
2019-09-25 17:18:48 0000.0000.0011.01-00 0x00000032 Received LSP
2019-09-25 17:18:48 0000.0000.0011.02-00 0x00000035 Received LSP
2019-09-25 17:18:47 0000.0000.0012.00-00 0x00000001 Generated LSP
Level-2 LSP log
---------------
Date Time LSPID Seq Num Event
--------------------------------------------------------------------------------
2019-09-25 17:18:48 0000.0000.0012.00-00 0x00000002 Generated LSP
2019-09-25 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 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
--------------------------------------------------------------------------------
2019-11-21 15:10:10 0000.0000.0002 L2 CircuitDown XGE0/0/6
2019-11-21 15:10:10 0000.0000.0002 L1 CircuitDown XGE0/0/6
Table 10 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 IS-IS IPv4 route calculation log information.
ipv6: Displays IS-IS IPv6 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 IS-IS IPv4 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
-------------------------------------------------------------------------------
2015-09-07 11:10:45 0 4 Interface metric changed
2015-09-07 09:26:40 0 4 LSP updated
2015-09-07 09:26:28 0 2 DIS changed
2015-09-07 09:26:21 0.001 2 LSP updated
2015-09-07 09:26:07 0.001 3 Direct route changed
Level-2 SPF Log
---------------
Date Time Duration Count Trigger event
-------------------------------------------------------------------------------
2015-09-07 11:10:45 0 4 Interface metric changed
2015-09-07 09:26:40 0 4 LSP updated
2015-09-07 09:26:28 0 2 DIS changed
2015-09-07 09:26:21 0 2 LSP updated
2015-09-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 : 2015-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 : 2015-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 : 2015-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 : 2015-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 : 2015-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 : 2015-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 : 2015-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 : 2015-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 : 2015-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 : 2015-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 11 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. · TE tunnel updated. · TE tunnel metric 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. · TE tunnel configuration changed. · TE tunnel destination changed. · 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. · Topology—Topology calculation. · BSPF—Backup SPF calculation. · TI/R-LFA prepare—TI-LFA/Remote LFA calculation preparation. · 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. · SPF nodes—Number of SPF nodes for topology calculation. · Candidate NBRs—Number of candidate neighbors. · 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
-------------------------------------------------------------------------------
2015-09-07 11:10:45 0 4 Interface metric changed
2015-09-07 09:26:40 0 4 LSP updated
2015-09-07 09:26:28 0 2 DIS changed
2015-09-07 09:26:21 0.001 2 LSP updated
2015-09-07 09:26:07 0.001 3 Direct route changed
Level-2 SPF Log
---------------
Date Time Duration Count Trigger event
-------------------------------------------------------------------------------
2015-09-07 11:10:45 0 4 Interface metric changed
2015-09-07 09:26:40 0 4 LSP updated
2015-09-07 09:26:28 0 2 DIS changed
2015-09-07 09:26:21 0 2 LSP updated
2015-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 : 2015-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 : 2015-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 : 2011-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 : 2015-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 : 2015-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 : 2015-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 : 2015-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 : 2015-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 : 2015-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 : 2015-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 : 2015-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 : 2015-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 : 2015-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 : 2015-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 : 2015-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 : 2015-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 : 2015-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 : 2015-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 : 2015-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 : 2015-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 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. · Interface MTR information changed. · SPF link changed. · Default route changed. · Summary route changed. · TE tunnel updated. · TE tunnel metric 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. · TE tunnel configuration changed. · TE tunnel destination changed. · 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. · Topology—Topology calculation. · BSPF—Backup SPF calculation. · TI-LFA prepare—TI-LFA calculation preparation. · 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. · SPF nodes—Number of SPF nodes for topology calculation. · Candidate NBRs—Number of candidate neighbors. · 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 flex-algo route
Use display isis flex-algo route to display information about routes calculated by a flexible algorithm.
Syntax
display isis flex-algo flex-algo-id route [ level-1 | level-2 ] [ process-id ] [ verbose ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
flex-algo-id: Specifies a flexible algorithm by its ID. The value range for this argument is 128 to 255.
level-1: Specifies Level-1 routes.
level-2: Specifies Level-2 routes.
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 routes calculated by the specified flexible algorithm for all IS-IS processes that use that flexible algorithm.
verbose: Displays detailed information about routes calculated by the specified flexible algorithm. If you do not specify this keyword, the command displays brief information about these routes.
Usage guidelines
If you do not specify the level-1 or level-2 keyword, the command displays information about Level-1 and Level-2 routes.
Examples
# Display brief information about routes calculated by flexible algorithm 255.
<Sysname> display isis flex-algo 255 route
Flex Algo Route Information for IS-IS(2)
----------------------------------------
Level-1 Flex Algo Route
-----------------------
Destination : 1:: PrefixLen: 64
Flag : D/-/- Cost : 0
Next hop : Direct Interface: NULL0
Destination : 2000:2:2:1:: PrefixLen: 64
Flag : R/-/- Cost : 10
Next hop : FE80::2AFC:CEFF:FE65:206 Interface: XGE0/0/6
Flags: D-Direct, R-Added to Rib, L-Advertised in LSPs, U-Up/Down Bit Set
Table 13 Command output
Field |
Description |
Flex Algo Route Information for IS-IS(2) |
Flexible algorithm route information for IS-IS process 2. |
Level-1 Flex Algo Route |
IS-IS Level-1 routing information. |
Level-2 Flex Algo Route |
IS-IS Level-2 routing information. |
Destination |
IPv6 destination prefix. |
PrefixLen |
Prefix length. |
Flag |
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. |
NextHop |
Next hop. Direct means the route is directly connected. |
Interface |
Output interface. |
# Display detailed information about routes calculated by flexible algorithm 255.
<Sysname> display isis flex-algo 255 route verbose
Flex Algo Route Information for IS-IS(10)
-----------------------------------------
Level-1 Flex Algo Route
-----------------------
IPv6 dest : 1000:3:3:1::/64
Flag : D/-/- Cost : 0
Admin tag : - Src count : 1
Algorithm : 255
Priority : Low
Nexthop : Direct
Interface : NULL0 Delay Flag : N/A
Nib ID : 0x0
IPv6 dest : 2000:2:2:1::/64
Flag : R/-/- Cost : 10
Admin tag : - Src count : 1
Algorithm : 255
Priority : Low
Nexthop : FE80::2AFC:CEFF:FE65:206
Interface : XGE0/0/6 Delay Flag : N/A
TI-LFA:
Interface : XGE0/0/7
BkNextHop : FE80::2ADF:D9FF:FEE3:707
LsIndex : 0x80000001
Backup label stack(top->bottom): {4001::1:0:0}
Nib ID : 0x24000005
Flags: D-Direct, R-Added to Rib, L-Advertised in LSPs, U-Up/Down Bit Set
Table 14 Command output
Field |
Description |
Flex Algo Route Information for IS-IS(10) |
Flexible algorithm route information for IS-IS process 10. |
Level-1 Flex Algo Route |
IS-IS Level-1 routing information. |
Level-2 Flex Algo Route |
IS-IS Level-2 routing information. |
IPv6 dest |
IPv6 destination address and prefix. |
Flag |
Route flag: · D—The route 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. |
Algorithm |
Flexible algorithm ID. |
Nexthop |
Next hop. Direct means the route is directly connected. |
Interface |
Output interface. |
TI-LFA |
TI-LFA backup information. |
BKNextHop |
TI-LFA/Remote LFA backup next hop. |
LsIndex |
Label stack index. |
Backup label stack(top->bottom) |
Backup path label stack. N/A indicates that no label stack exists. |
Nib ID |
Next hop index assigned by the routing management module. |
display isis flex-algo spf-tree
Use display isis flex-algo spf-tree to display information about the SPF tree calculated by a flexible algorithm.
Syntax
display isis flex-algo flex-algo-id spf-tree { ipv4 | ipv6 } [ level-1 | level-2 ] [ process-id ] [ source-id source-id | verbose ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
flex-algo-id: Specifies a flexible algorithm by its ID. The value range for this argument is 128 to 255.
ipv4: Specifies the IPv4 SPF tree.
ipv6: Specifies the IPv6 SPF tree.
level-1: Specifies the IS-IS Level-1 SPF tree.
level-2: Specifies the IS-IS Level-2 SPF tree.
source-id source-id: Specifies an advertisement source by its system ID in the format of XXXX.XXXX.XXXX.XX. If you do not specify this option, the command displays information about the SPF trees calculated on all advertisement sources.
process-id: Specifies a process by its ID in the range of 1 to 65535. If you do not specify this argument, the command applies to all processes that use the specified flexible algorithm.
verbose: Displays detailed information about the SPF tree calculated by the specified flexible algorithm.
Usage guidelines
If you do not specify the level-1 keyword or the level-2 keyword, the command displays information about the Level-1 and Level-2 SPF trees.
Examples
# Display information about the IPv4 SPF tree calculated by flexible algorithm 255.
<Sysname> display isis flex-algo 255 spf-tree ipv4
Flex Algo SPF Information for IS-IS(2)
--------------------------------------
Level-2 Flex Algo SPF
---------------------
PostNode Cost NextHopCnt ChildLink
--------------------------------------------------------------
0000.0000.0001.00 20 1
-->0000.0000.0008.01
0000.0000.0003.00 10 1
-->0000.0000.0001.00
0000.0000.0008.00 0 0
-->0000.0000.0008.02
0000.0000.0008.01 30 1
0000.0000.0008.02 10 0
-->0000.0000.0003.00
Field |
Description |
Flex Algo SPF Information for IS-IS(xx) |
Information about the SPF tree calculated by a flexible algorithm in an IS-IS process. The xx argument represents the process ID. |
Level-1 Flex Algo SPF |
Level-1 SPF tree information. |
Level-2 Flex Algo SPF |
Level-2 SPF tree information. |
PostNode |
Node ID. |
Cost |
Routing cost. |
NextHopCnt |
Number of next hops. |
# Display detailed information about the IPv6 SPF tree calculated by flexible algorithm 130.
<Sysname> display isis flex-algo 130 spf-tree ipv6 verbose
Flex Algo SPF Information for IS-IS(10)
---------------------------------------
Level-2 Flex Algo SPF
---------------------
SpfNode : 0000.0000.0004.01
Distance : 20
TEDistance : 0
DelayDistance : 0
Metric Type : IGP
Nexthop count : 1
Neighbor : 0000.0000.0004.00 Interface : XGE0/0/9
Nexthop : FE80::2ADF:E0FF:FEA1:809
BkNeighbor : N/A BkInterface: N/A
BkNexthop : N/A
SpfNode : 0000.0000.0003.02
Distance : 20
TEDistance : 0
DelayDistance : 0
Metric Type : IGP
Nexthop count : 1
Neighbor : 0000.0000.0002.00 Interface : XGE0/0/6
Nexthop : FE80::2ADF:D3FF:FE2D:606
BkNeighbor : N/A BkInterface: N/A
BkNexthop : N/A
SpfNode : 0000.0000.0001.00
Distance : 0
TEDistance : 0
DelayDistance : 0
Metric Type : IGP
Nexthop count : 0
SpfNode : 0000.0000.0002.00
Distance : 10
TEDistance : 0
DelayDistance : 0
Metric Type : IGP
Nexthop count : 1
Neighbor : 0000.0000.0002.00 Interface : XGE0/0/6
Nexthop : FE80::2ADF:D3FF:FE2D:606
BkNeighbor : N/A BkInterface: N/A
BkNexthop : N/A
TI-LFA :
TiLfaNeighbor : 0000.0000.0004.00 TiLfaInterface: GE1/0/4
TiLfaNexthop : FE80::2ADF:E0FF:FEA1:809
PNode SrcID : 0000.0000.0003.00 QNode SrcID : 0000.0000.0003.00
PNode prefix : N/A PNode SidIndex: 3001::1:0:0
Protect : Link
Label stack : {3001::1:0:0}
SpfNode : 0000.0000.0004.00
Distance : 10
TEDistance : 0
DelayDistance : 0
Metric Type : IGP
Nexthop count : 1
Neighbor : 0000.0000.0004.00 Interface : XGE0/0/9
Nexthop : FE80::2ADF:E0FF:FEA1:809
BkNeighbor : N/A BkInterface: N/A
BkNexthop : N/A
TI-LFA :
TiLfaNeighbor : 0000.0000.0002.00 TiLfaInterface: GE1/0/1
TiLfaNexthop : FE80::2ADF:D3FF:FE2D:606
PNode SrcID : 0000.0000.0003.00 QNode SrcID : 0000.0000.0003.00
PNode prefix : N/A PNode SidIndex: 3001::1:0:0
Protect : Link
Label stack : {3001::1:0:0}
SpfNode : 0000.0000.0003.00
Distance : 20
TEDistance : 0
DelayDistance : 0
Metric Type : IGP
Nexthop count : 2
Neighbor : 0000.0000.0002.00 Interface : XGE0/0/6
Nexthop : FE80::2ADF:D3FF:FE2D:606
BkNeighbor : N/A BkInterface: N/A
BkNexthop : N/A
Neighbor : 0000.0000.0004.00 Interface : XGE0/0/9
Nexthop : FE80::2ADF:E0FF:FEA1:809
BkNeighbor : N/A BkInterface: N/A
BkNexthop : N/A
SpfNode : 0000.0000.0004.02
Distance : 10
TEDistance : 0
DelayDistance : 0
Metric Type : IGP
Nexthop count : 0
Table 16 Command output
Field |
Description |
SpfNode |
ID of the topology node. |
Distance |
· If the flexible algorithm uses IGP metric, this field displays the shortest distance from the root node to the local node. · If the flexible algorithm does not use IGP metric, this field displays 0. |
TEDistance |
· If the flexible algorithm uses TE metric, this field displays the shortest distance from the root node to the local node. · If the flexible algorithm does not use TE metric, this field displays 0. |
DelayDistance |
· If the flexible algorithm uses delay metric, this field displays the shortest distance from the root node to the local node. · If the flexible algorithm does not use delay metric, this field displays 0. |
Metric type of the flexible algorithm. Options include IGP, link delay and TE cost. |
|
Nexthop count |
Number of next hops. |
Neighbor |
System ID of the neighbor node that is the primary next hop of the node. |
Interface |
Output interface of the primary next hop. |
Nexthop |
Primary next hop of the node. |
MADuration |
Flex-Algo SR microloop avoidance duration, in milliseconds. |
MALStack |
Flex-Algo SR microloop avoidance label stack. |
BkNeighbor |
System ID of the neighbor node that is the backup next hop of the node. |
BkInterface |
Output interface of the backup next hop. |
BkNexthop |
Backup next hop of the node. |
TI-LFA information: · TiLfaNeighbor—ID of the TI-LFA backup next hop neighbor. · TiLfaInterface—Output interface of the TI-LFA backup next hop. · TiLfaNexthop—TI-LFA backup next hop. · PNode SrcID—Source ID of the P node. · QNode SrcID—Source ID of the Q node. · PNode prefix—Prefix of the P node. N/A indicates that the destination node is in the P space. · PNode SidIndex—End SID of the P node. N/A indicates that the destination node is in the P space. · Protect—TI-LFA traffic protection type: ¡ Link—Link protection. ¡ Node—Node protection. · Label stack—Label stack. N/A indicates that no label stack exists. |
display isis global-flex-algo
Use display isis global-flex-algo to display information about the FADs received and advertised by a node.
Syntax
display isis global-flex-algo [ algorithm-id flex-algo-id ] [ level-1 | level-2 ] [ process-id ] [ system-id system-id ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
algorithm-id flex-algo-id: Specifies a flexible algorithm by its ID. The value range for this argument is 128 to 255. If you do not specify this option, this command displays information about the FADs received and advertised by the node for all flexible algorithms.
level-1: Specifies Level-1 areas.
level-2: Specifies the Level-2 area.
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 the FADs received and advertised by the node for all IS-IS processes.
system-id system-id: Specifies an FAD advertisement source by its system ID. If you do not specify this option, the command displays information about the FADs advertised by all sources.
Usage guidelines
If you do not specify the level-1 keyword or the level-2 keyword, the command displays the Level-1 and Level-2 FADs received and advertised by the node.
If you do not specify any keywords, the command displays the FADs received and advertised by the node.
Examples
# Display the Level-2 FADs received and advertised by the node.
<Sysname> display isis global-flex-algo level-2
Flex-Algo Information for IS-IS(1)
-------------------------------------------------------
Level-2 Flex-Algo Information
-----------------------------
Algorithm 128
MetricType : IGP
Flex-Algo Exclude Any Ext Admin Group:
N/A
Flex-Algo Include Any Ext Admin Group:
N/A
Flex-Algo Include All Ext Admin Group:
N/A
Flex-Algo Exclude SRLG:
N/A
SrcCount 1
SrcInfo:
SourceID : 0000.0000.2001.00
Priority : 128
MetricType : IGP
LSPInfo
LSPID 0000.0000.2001.00-00
Priority 128
MetricType IGP
Table 17 Command output
Field |
Description |
Flex-Algo Information for IS-IS(xx) |
Flexible algorithm information for an IS-IS process. The xx argument represents the process ID. |
Level-1 Flex-Algo Information |
IS-IS Level-1 flexible algorithm information. |
Level-2 Flex-Algo Information |
IS-IS Level-2 flexible algorithm information. |
Algorithm xx |
Information about flexible algorithm xx. |
MetricType |
Metric type of the flexible algorithm advertised by the source of the highest priority. · IGP—Link cost. · Delay—Link delay. · Te-cost—TE metric. |
Flex-Algo Exclude Any Ext Admin Group |
The exclude-any constraint in the FAD. N/A indicates that no exclude-any constraint is set. |
Flex-Algo Include Any Ext Admin Group |
The include-any constraint in the FAD. N/A indicates that no include-any constraint is set. |
Flex-Algo Include All Ext Admin Group |
The include-all constraint in the FAD. N/A indicates that no include-all constraint is set. |
Flex-Algo Exclude SRLG |
SRLG links excluded by the flexible algorithm. If no exclude SRLG constraints are configured, this field displays N/A. |
SrcCount |
Number of advertisement sources. |
SrcInfo |
Advertisement source information: · SourceID—System ID. · Priority—Flexible algorithm priority. · MetricType—Metric type of the flexible algorithm. ¡ IGP—Link cost. ¡ Delay—Link delay. ¡ Te-cost—TE metric. |
LSPInfo |
LSP advertised by the source: · LSPID—LSP ID. · Priority—Priority of the flexible algorithm in the LSP. · MetricType—Metric type of the flexible algorithm in the LSP. ¡ IGP—Link cost. ¡ Delay—Link delay. ¡ Te-cost—TE metric. |
display isis global-statistics
Use display isis global-statistics to display global IS-IS statistics.
Syntax
display isis global-statistics [ public | vpn-instance vpn-instance-name ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
public: Specifies the public network.
vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters.
Usage guidelines
If you do not specify any keywords, the command displays global IS-IS statistics for the public network and all VPN instances.
Examples
# Display global IS-IS statistics.
<Sysname> display isis global-statistics
IS-IS global statistics
Instance count: 2 Process count: 2
Interface information:
Type IPv4 up/down IPv6 up/down
LAN 0/0 0/0
P2P 1/0 0/0
Peer information:
Type IPv4 Up/Init IPv6 Up/Init
LAN Level-1 0/0 0/0
LAN Level-2 0/0 0/0
P2P 1/0 0/0
Packet information:
Total output packets: 1022
Total input packets: 1023
LSP information:
Total level-1 LSPs: 2
Total level-2 LSPs: 2
Route information:
Type IPv4 IPv6
Level-1 1 0
Level-2 2 0
Table 18 Command output
Field |
Description |
Interface information |
Interface status statistics. |
Type |
Interface link adjacency type. |
IPv4 up/down |
Number of IPv4 interfaces in up or down state. |
IPv6 up/down |
Number of IPv6 interfaces in up or down state. |
Type |
Neighbor type: · LAN Level-1—Number of Level-1 neighbors with the broadcast network type. · LAN Level-2—Number of Level-2 neighbors with the broadcast network type. · P2P—Number of neighbors with the point-to-point (P2P) network type. |
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. |
Packet information |
Statistics of received and sent protocol packets. |
Total output packets |
Number of sent protocol packets. |
Total input packets |
Number of received protocol packets. |
LSP information |
Number of LSPs in the LSDB. |
Total level-1 LSPs |
Number of Level-1 LSPs. |
Total level-2 LSPs |
Number of Level-2 LSPs. |
Route Information |
Route statistics: · Level-1—Level-1 IS-IS route statistics. · Level-2—Level-2 IS-IS route statistics. · IPv4—IPv4 IS-IS route statistics. · IPv6—IPv6 IS-IS route statistics. |
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 19 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: Ten-GigabitEthernet0/0/7
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: Ten-GigabitEthernet0/0/7
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
IPv6 cost : L1 10 L2 10
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
Link quality : GOOD
Cost adjusted at low quality : 50
IPv4 BFD : Disabled
IPv6 BFD : Disabled
IPv4 BFD session-restrict-adj : Enabled
IPv6 BFD session-restrict-adj : Disabled
IPv4 BFD template : TEMP1
IPv6 BFD template : TEMP2
IPv4 FRR LFA backup : Enabled
IPv6 FRR LFA backup : Enabled
IPv4 FRR TI-LFA : L1 Enabled L2 Enabled
IPv6 FRR TI-LFA : L1 Enabled L2 Enabled
IPv4 FRR remote-LFA : L1 Enabled L2 Enabled
IPv4 prefix suppression : Disabled
IPv6 prefix suppression : Disabled
IPv4 tag : 1
IPv6 tag : 0
IPv4 BFD adjust cost : Maximum
IPv6 BFD adjust cost : Maximum
IPv4 primary path detection mode : BFD ctrl
IPv6 primary path detection mode : BFD ctrl
Te-Metric FlexAlgo : 100
Average delay : 1000
Min delay : 10
Max delay : 500
Delay variation : 200
Static adjacency SID
Nexthop Adjacency-SID Type Protected Result
12.0.0.2 100 Index N Succeeded
Table 20 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. |
CircuitID |
Circuit ID. · 0(Invalid)—IS-IS is not successfully enabled on the broadcast interface. · 1—IS-IS is successfully enabled on the broadcast interface. |
MTU |
Interface MTU. |
Type |
Interface link adjacency type. |
DIS |
Indicates whether the interface is elected as the Level-1/Level-2 DIS. On 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. |
IPv6 cost |
IPv6 link cost of the interface. |
Priority |
DIS priority. |
Retransmit timer value |
Retransmission interval for LSPs on a P2P link. |
MPLS TE status |
MPLS TE status: Enabled or Disabled. |
Link quality |
Link quality: · GOOD—The bit error ratio is below the upper threshold or drops below the lower threshold. · LOW—The bit error ratio exceeds the upper threshold. This field is displayed only when the interface is configured with the isis link-quality adjust-cost command. |
Cost adjusted at low quality |
Interface cost adjustment parameters: · xx—Value added to the interface cost. When the link quality is LOW, the interface cost is xx plus the original interface cost. · Maximum—Sets the interface cost to the maximum when the link quality is LOW. This field is displayed only when the interface is configured with the isis link-quality adjust-cost command. |
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. |
Whether BFD is enabled on the IPv4 IS-IS interface: · Disabled. · Enabled. · Enabled, inherited—BFD is enabled on the IS-IS interface. The inherited attribute indicates that the interface inherits the global configuration of this feature from the IPv4 IS-IS process to which the interface belongs. · Excluded—The BFD capacity of the IS-IS interface is suppressed by the isis bfd exclude command. |
|
IPv6 BFD |
Whether BFD is enabled on the IPv6 IS-IS interface: · Disabled. · Enabled. · Enabled, inherited—BFD is enabled on the IS-IS interface. The inherited attribute indicates that the interface inherits the global configuration of this feature from the IPv6 IS-IS process to which the interface belongs. · Excluded—The BFD capacity of the IS-IS interface is suppressed by the isis ipv6 bfd exclude command. |
IPv4 BFD session-restrict-adj |
Whether BFD session state-based control of adjacency establishment and maintenance is enabled on the IPv4 IS-IS interface: · Disabled. · Enabled. · Enabled, inherited—BFD session state-based control of adjacency establishment and maintenance is enabled on the interface. The inherited attribute indicates that the interface inherits the global configuration of this feature from the IPv4 IS-IS process to which the interface belongs. · Excluded—BFD session state-based control of adjacency establishment and maintenance is suppressed on the interface by the isis bfd session-restrict-adj exclude command. |
IPv6 BFD session-restrict-adj |
Whether BFD session state-based control of adjacency establishment and maintenance is enabled on the IPv6 IS-IS interface: · Disabled. · Enabled. · Enabled, inherited—BFD session state-based control of adjacency establishment and maintenance is enabled on the interface. The inherited attribute indicates that the interface inherits the global configuration of this feature from the IPv6 IS-IS process to which the interface belongs. · Excluded—BFD session state-based control of adjacency establishment and maintenance is suppressed on the interface by the isis ipv6 bfd session-restrict-adj exclude command. |
IPv4 BFD template |
BFD template applied to the IPv4 IS-IS interface. If no BFD template is applied to the interface, this field displays the BFD template applied to the IS-IS process in IPv4 address family view. If no BFD template is applied either to the interface or to the process, this field is not displayed. |
IPv6 BFD template |
BFD template applied to the IPv6 IS-IS interface. If no BFD template is applied to the interface, this field displays the BFD template applied to the IS-IS process in IPv6 address family view. If no BFD template is applied either to the interface or to the process, this field is not displayed. |
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 |
IPv4 TI-LFA calculation status: · Disabled. · Enabled. |
IPv6 FRR TI-LFA |
IPv6 TI-LFA calculation status: · 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 BFD adjust cost |
Whether BFD session state-based interface cost adjustment is enabled on the IPv4 IS-IS interface: · Disabled. · cost-offset—Interface cost adjustment value. The value range for cost-offset is 1 to 16777213. When the BFD session goes down, the interface cost is cost-offset plus the original interface cost. · cost-offset, inherited—Interface cost adjustment value. The value range for cost-offset is 1 to 16777213. The inherited attribute indicates that the interface inherits the global configuration of cost-offset from the IPv4 IS-IS process to which the interface belongs. · Maximum—Maximum interface cost value (16777214). When the BFD session goes down, IS-IS will adjust the interface cost to the maximum. · Maximum, inherited—Maximum interface cost value (16777214). When the BFD session goes down, IS-IS will adjust the interface cost to the maximum. The inherited attribute indicates that the interface inherits this configuration from the IPv4 IS-IS process to which the interface belongs. · Excluded—BFD session state-based interface cost adjustment is suppressed on the interface by the isis bfd adjust-cost exclude command. |
IPv6 BFD adjust cost |
Whether BFD session state-based interface cost adjustment is enabled on the IPv6 IS-IS interface: · Disabled. · cost-offset—Interface cost adjustment value. The value range for cost-offset is 1 to 16777213. When the BFD session goes down, the interface cost is cost-offset plus the original interface cost. · cost-offset, inherited—Interface cost adjustment value. The value range for cost-offset is 1 to 16777213. The inherited attribute indicates that the interface inherits the global configuration of cost-offset from the IPv6 IS-IS process to which the interface belongs. · Maximum—Maximum interface cost value (16777214). When the BFD session goes down, IS-IS will adjust the interface cost to the maximum. · Maximum, inherited—Maximum interface cost value (16777214). When the BFD session goes down, IS-IS will adjust the interface cost to the maximum. The inherited attribute indicates that the interface inherits this configuration from the IPv6 IS-IS process to which the interface belongs. · Excluded—BFD session state-based interface cost adjustment is suppressed on the interface by the isis ipv6 bfd adjust-cost exclude command. |
IPv4 primary path detection mode |
IPv4 primary path detection mode: · BFD ctrl—BFD control packet mode. · BFD ctrl, inherited—BFD control packet mode. The inherited attribute indicates that the interface inherits this configuration from the IPv4 IS-IS process to which the interface belongs. · BFD echo—BFD echo packet mode. · BFD echo, inherited—BFD echo packet mode. The inherited attribute indicates that the interface inherits this configuration from the IPv4 IS-IS process to which the interface belongs. · Disabled—The IS-IS interface does not use BFD for primary link failure detection. · Excluded—The IS-IS interface is disabled from using BFD for primary link failure detection by the isis primary-path-detect bfd exclude command. |
IPv6 primary path detection mode |
IPv6 primary path detection mode: · BFD ctrl—BFD control packet mode. · BFD ctrl, inherited—BFD control packet mode. The inherited attribute indicates that the interface inherits this configuration from the IPv6 IS-IS process to which the interface belongs. · BFD echo—BFD echo packet mode. · BFD echo, inherited—BFD echo packet mode. The inherited attribute indicates that the interface inherits this configuration from the IPv6 IS-IS process to which the interface belongs. · Disabled—The IS-IS interface does not use BFD for primary link failure detection. · Excluded—The IS-IS interface is disabled from using BFD for primary link failure detection by the isis ipv6 primary-path-detect bfd exclude command. |
Te-Metric FlexAlgo |
IS-IS TE cost specified for flexible algorithm. |
Average delay |
Average link delay in microseconds. |
Max delay |
Maximum link delay in microseconds. |
Min delay |
Minimum link delay in microseconds. |
Delay variation |
Acceptable link delay variation in microseconds. |
Static adjacency SID configured on the interface. |
|
Nexthop |
Next hop IP address. This field displays 0.0.0.0 for a P2P network. |
Type |
Adjacency SID type: · Absolute—Absolute value of the adjacency SID. · Index—Index value of the adjacency SID. |
Protected |
Whether the adjacency SID is protected: · N—Not protected. · Y—Protected. |
Result |
Adjacency SID application result: · Succeeded—Applied for adjacency SID successfully. · Conflicting—Adjacency SID conflict occurred. · Init—Adjacency SID application is in progress or adjacency SID assignment is not enabled. |
# 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 21 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: Ten-GigabitEthernet0/0/6
First 3 L1 hello packets sent:
2019-11-21 15:10:14:687, succeeded
2019-11-21 15:10:14:698, succeeded
2019-11-21 15:10:22:506, succeeded
Last 3 L1 hello packets sent:
2019-11-21 16:19:11:724, succeeded
2019-11-21 16:19:19:440, succeeded
2019-11-21 16:19:27:858, succeeded
First 3 L2 hello packets sent:
2019-11-21 15:10:14:688, succeeded
2019-11-21 15:10:14:699, succeeded
2019-11-21 15:10:24:404, succeeded
Last 3 L2 hello packets sent:
2019-11-21 16:19:11:176, succeeded
2019-11-21 16:19:19:453, succeeded
2019-11-21 16:19:28:544, succeeded
Table 22 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 local-flex-algo
Use display isis local-flex-algo to display the configuration for a flexible algorithm on a node.
Syntax
display isis local-flex-algo [ algorithm-id flex-algo-id ] [ process-id ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
algorithm-id flex-algo-id: Specifies a flexible algorithm by its ID. The value range for this argument is 128 to 255. If you do not specify this option, the command displays the configuration for all flexible algorithms.
process-id: Specifies a process by its ID in the range of 1 to 65535. If you do not specify this argument, the command applies to all processes.
Examples
# Display the configuration for flexible algorithm 128 in all processes.
<Sysname> display isis local-flex-algo algorithm-id 128
IS-IS(2) Protocol Information
Flex-Algo(128)
Definition advertisement : Enabled
Priority : 128
MetricType : IGP
Fast-reroute : Enabled
Fast-reroute TI-LFA : Enabled
Microloop-avoidance : Enabled
microloop avoidance RIB-update-delay
level-1 : 5000
level-2 : 5000
SR microloop avoidance : Enabled
SR microloop avoidance RIB-update-delay
level-1 : 5000
level-2 : 5000
SR microloop avoidance strict-sid-only: Disabled
Node-protecting preference
level-1 : 40
level-2 : 40
Lowest-cost preference
level-1 : 20
level-2 : 20
Table 23 Command output
Field |
Description |
IS-IS(xx) Protocol Information |
Flexible algorithm configuration in an IS-IS process. The xx argument represents the process ID. |
Flex-Algo(xx) |
Configuration for a flexible algorithm. The xx argument represents the flexible algorithm ID. |
Definition advertisement |
Whether FAD advertisement is enabled. |
Priority |
Priority of the flexible algorithm. |
MetricType |
Metric type of the flexible algorithm. |
Fast-reroute |
Whether FRR is enabled. IGP indicates that the metric type is IGP. |
Fast-reroute TI-LFA |
Whether TI-LFA FRR is enabled. |
Microloop-avoidance |
Whether FRR microloop avoidance is enabled for the flexible algorithm. |
microloop avoidance RIB-update-delay |
Microloop avoidance RIB-update-delay timer specified for the flexible algorithm. |
SR microloop avoidance |
Whether SR microloop avoidance is enabled for the flexible algorithm. |
SR microloop avoidance RIB-update-delay |
SR microloop avoidance RIB-update-delay timer specified for the flexible algorithm. |
SR microloop avoidance strict-sid-only |
Whether strict SID encapsulation is enabled for flexible algorithm SR microloop avoidance. |
Node-protecting preference |
Priority of the node-protection backup path selection policy: · level-1—Priority value for the backup path selection policy in Level-1 areas. · level-2—Priority value for the backup path selection policy in the Level-2 area. |
Lowest-cost preference |
Priority of the lowest-cost backup path selection policy: · level-1—Priority value for the backup path selection policy in Level-1 areas. · level-2—Priority value for the backup path selection policy in the Level-2 area. |
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 manually.
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 manually.
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 IPv6
Area address 10
IPv4 address 192.168.220.10
IPv6 address 10::1
MT ID 0002 (-/-)
MT ID 0006 (-/-)
+NBR ID
0000.0000.0011.00 Cost: 100
LAN-ADJ-SID:
Flags (F/B/V/L/S/P): 0/1/1/1/0/0 Weight: 0
System ID Adjacency SID
0000.0000.0002 10101
IPv6 unicast NBR ID
6464.6464.6464.01 Cost: 10 MT ID: 2
Interface IPv6 address: 100::1
NBR Interface IPv6 address: 100::2
+IP-Extended
192.168.220.0 255.255.255.0 Cost: 100
IPv6
10::/64 Cost: 10
IPv6 unicast
10::/64 Cost: 10 MT ID: 2
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
Flag: 0, Average delay: 1000 us
Remaining bandwidth: 15624999796736 bytes/sec
Available bandwidth: 15624999796736 bytes/sec
Utilized bandwidth: 0 bytes/sec
SR/SRv6 Link Maximum SID Depths
MPLS MSD : 13
P2P-ADJ-SID
Flags (F/B/V/L/S/P): 0/0/0/1/1/0 Weight: 0
Adjacency SID: 24182
SRv6 End.X SID
SID : 1000:0:0:18::
Function type: End.X with PSP
+IP-Extended
1.1.1.1 255.255.255.255 Cost: 0
Prefix-SID: 10 Algorithm: 128
Prefix-SID flags (R/N/P/E/V/L): 0/1/0/0/0/0
+IP-Extended
192.168.100.0 255.255.255.0 Cost: 10
Router ID 1.1.1.1
Router capability
Router ID: 1.1.1.1 Flags (D/S): 0/0
Segment routing (I/V/H): 1/0/0
SRGB base: 16000 SRGB range : 8001
Segment routing local block (-): 0x00
SRLB base: 16000 SRLB range : 8000
SR/SRv6 Node Maximum SID Depths
MPLS MSD : 13
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
Level-2 Link State Database
---------------------------
LSPID Seq Num Checksum Holdtime Length ATT/P/OL
-------------------------------------------------------------------------------
0000.0000.2001.00-00 0x00000007 0x3e3c 1191 187 0/0/0
Source 0000.0000.2001.00
NLPID IPv4
Area address 10.0001
IPv4 address 192.168.24.2
+NBR ID
0000.0000.4001.02 Cost: 10
Admin group: 0x00000000
Physical bandwidth: 0 bytes/sec
Reservable bandwidth: 0 bytes/sec
Unreserved bandwidth for each TE class:
TE class 0: 0 bytes/sec TE class 1: 0 bytes/sec
TE class 2: 0 bytes/sec TE class 3: 0 bytes/sec
TE class 4: 0 bytes/sec TE class 5: 0 bytes/sec
TE class 6: 0 bytes/sec TE class 7: 0 bytes/sec
TE class 8: 0 bytes/sec TE class 9: 0 bytes/sec
TE class 10: 0 bytes/sec TE class 11: 0 bytes/sec
TE class 12: 0 bytes/sec TE class 13: 0 bytes/sec
TE class 14: 0 bytes/sec TE class 15: 0 bytes/sec
TE cost: 10
Bandwidth constraint model: Prestandard DS-TE RDM
Bandwidth constraints:
BC[0]: 0 bytes/sec BC[1]: 0 bytes/sec
Interface IP address: 192.168.24.2
+IP-Extended
192.168.24.0 255.255.255.0 Cost: 10
+IP-Extended
192.168.51.0 255.255.255.0 Cost: 0
Router ID 2.2.2.2
+SRLG NBR ID
0000.0000.4001.02
Interface IP address: 192.168.24.2
Shared risk link group: 10
0000.0000.4001.00-00* 0x00000006 0x26e4 1197 179 0/0/0
Source 0000.0000.4001.00
NLPID IPv4
Area address 10.0002
IPv4 address 192.168.24.4
+NBR ID
0000.0000.4001.02 Cost: 10
Admin group: 0x00000000
Physical bandwidth: 0 bytes/sec
Reservable bandwidth: 0 bytes/sec
Unreserved bandwidth for each TE class:
TE class 0: 0 bytes/sec TE class 1: 0 bytes/sec
TE class 2: 0 bytes/sec TE class 3: 0 bytes/sec
TE class 4: 0 bytes/sec TE class 5: 0 bytes/sec
TE class 6: 0 bytes/sec TE class 7: 0 bytes/sec
TE class 8: 0 bytes/sec TE class 9: 0 bytes/sec
TE class 10: 0 bytes/sec TE class 11: 0 bytes/sec
TE class 12: 0 bytes/sec TE class 13: 0 bytes/sec
TE class 14: 0 bytes/sec TE class 15: 0 bytes/sec
TE cost: 10
Bandwidth constraint model: Prestandard DS-TE RDM
Bandwidth constraints:
BC[0]: 0 bytes/sec BC[1]: 0 bytes/sec
Interface IP address: 192.168.24.4
+IP-Extended
192.168.24.0 255.255.255.0 Cost: 10
Router ID 4.4.4.4
IPv6 router ID 1::1
Router capability
Router ID: 192.168.24.4 Flags (D/S): 0/0
Segment routing (I/V/H): 1/0/0
SRGB base: 16000 SRGB range : 8001
Segment routing local block (-): 0x00
SRLB base: 16000 SRLB range : 8000
SRv6 capability flags (O): 0
SR/SRv6 Node Maximum SID Depths
SRv6 Segment Left: 5
SRv6 End Pop MSD : 5
SRv6 T.Insert MSD: 5
SRv6 T.Encaps MSD: 5
SRv6 End D MSD : 5
SR Algorithm
Algorithm: 0
Algorithm: 255
Flex-Algo Definition
Algorithm: 255 Metric-Type: IGP Alg-type: SPF Priority: 128
Flex-Algo Exclude Any Ext Admin Group:
0x00000002
Flex-Algo Definition Flags:
M-flag: 1
+SRv6 locator
MT ID : 0
Locator: 1000::/32
Cost : 0 Flag (D): 0 Algorithm : 0
Flag(A): 0
End SID: 1000:0:0:1::
Function type: End with PSP
+SRLG NBR ID
0000.0000.0002.01
Interface IP address: 192.168.1.101
Shared risk link group: 12
+Application Specific SRLG NBR ID
0000.0000.0002.01
L flag: 0, SA-Length: 1, UDA-Length: 1
Standard Applications: 0x10
User Defined Applications: 0x10
Link local IP address: 192.168.1.101
Interface IP address: 192.168.1.101
Shared risk link group: 12
0000.0000.4001.02-00* 0x00000001 0xdefb 950 54 0/0/0
Source 0000.0000.4001.02
NLPID IPv4
+NBR ID
0000.0000.2001.00 Cost: 0
+NBR ID
0000.0000.4001.00 Cost: 0
*-Self LSP, +-Self LSP(Extended), ATT-Attached, P-Partition, OL-Overload
# Display detailed Level-2 LSDB information.
<Sysname> display isis lsdb level-2 verbose
Database information for IS-IS(1)
---------------------------------
Level-2 Link State Database
---------------------------
LSPID Seq Num Checksum Holdtime Length ATT/P/OL
-------------------------------------------------------------------------------
0000.0000.2001.00-00* 0x0000005b 0x7304 806 216 0/0/0
Source 0000.0000.2001.00
NLPID IPv4 IPv6
Area address 10.0001
IPv4 address 192.168.24.2
+NBR ID
0000.0000.4001.02 Cost: 10
Application Specific Link Attributes
L flag: 0, SA-Length: 1, UDA-Length: 1
Standard Applications: 0x10 Flex-Algo
User Defined Applications: 0x10 Flex-Algo
Ext Admin Group:
0x00000400
+IP-Extended
192.168.24.0 255.255.255.0 Cost: 10
IPv6-ext
1::/64 Cost: 0
IPv6-ext
1::9/128 Cost: 0
Router capability
Router ID: 192.168.24.2 Flags (D/S): 0/0
SRv6 capability flags (O/C): 0/0
SR/SRv6 Node Maximum SID Depths
SRv6 Segment Left: 5
SRv6 End Pop MSD : 5
SRv6 T.Insert MSD: 5
SRv6 T.Encaps MSD: 5
SRv6 End D MSD : 5
SR Algorithm
Algorithm: 0
Algorithm: 128
Algorithm: 129
Flex-Algo Definition
Algorithm: 128 Metric-Type:IGP Alg-type: SPF Priority: 255
Flex-Algo Definition
Algorithm: 129 Metric-Type:IGP Alg-type: SPF Priority: 128
Flex-Algo Definition Flags:
M-flag: 1
Flex-Algo Exclude SRLG:
10
+SRv6 locator
MT ID : 0
Flag(A): 0
Locator: 10:1::/120
Cost : 0 Flag (D): 0 Algorithm: 128
End SID: 10:1::1
Flag (C) : 0
Function type: End with PSP
+SRLG NBR ID
0000.0000.0002.01
Interface IP address: 192.168.1.101
Shared risk link group: 12
+Application Specific SRLG NBR ID
0000.0000.0002.01
L flag: 0, SA-Length: 1, UDA-Length: 1
Standard Applications: 0x10
User Defined Applications: 0x10
Link local IP address: 192.168.1.101
Interface IP address: 192.168.1.101
Shared risk link group: 12
0000.0000.4001.00-00 0x00000057 0xcaec 1098 167 0/0/0
Source 0000.0000.4001.00
NLPID IPv4 IPv6
Area address 10.0002
IPv4 address 192.168.24.4
IPv4 address 192.168.46.4
IPv6 address 1::2
IPv6 address 2::9
+NBR ID
0000.0000.4001.02 Cost: 10
+IP-Extended
6.6.6.6 255.255.255.255 Cost: 10
+IP-Extended
192.168.24.0 255.255.255.0 Cost: 10
+IP-Extended
192.168.46.0 255.255.255.0 Cost: 10
IPv6
1::/64 Cost: 10
IPv6
2::9/128 Cost: 0
0000.0000.4001.02-00 0x00000032 0xd643 1191 55 0/0/0
Source 0000.0000.4001.02
NLPID IPv4 IPv6
+NBR ID
0000.0000.2001.00 Cost: 0
+NBR ID
0000.0000.4001.00 Cost: 0
*-Self LSP, +-Self LSP(Extended), ATT-Attached, P-Partition, OL-Overload
Table 24 Command output
Field |
Description |
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. |
Application Specific Link Attributes |
Application specific link attributes, which indicate that the link attribute is associated with a flexible algorithm. |
L flag |
Legacy flag, which is fixed at 0. |
SA-Length |
Standard application identifier bit mask length in bytes. |
UDA-Length |
User defined application identifier bit mask length in bytes. |
Standard Applications |
Standard application. |
User Defined Applications |
User defined application. |
Ext Admin Group |
Extended admin groups. |
IPv6 unicast NBR ID |
IPv6 unicast neighbor information about the originating router. |
Admin group |
Link management group attribute. |
Physical bandwidth |
Physical bandwidth. |
Reservable bandwidth |
Reserved bandwidth. |
Unreserved bandwidth for each TE class |
Available bandwidth reserved for each TE class. |
TE class |
Available bandwidth for each of the 8 or 16 TE classes. |
Bandwidth constraint model |
Bandwidth constraint model: · Prestandard DS-TE RDM. · IETF DS-TE RDM. · IETF DS-TE MAM. |
BC |
Bandwidth constraint value. The Prestandard model supports 2 BCs, and the IETF modes support a maximum of 8 BCs. |
Interface IP address |
IP address of the local interface. |
Neighbor IP address |
IP address of the remote interface. |
Interface IPv6 address |
IPv6 address of the local interface. |
NBR Interface IPv6 address |
IPv6 address of the remote interface. |
Router ID |
IPv4 router ID. |
IPv6 router ID |
IPv6 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. |
Flag |
Average link delay flag indicating whether the average link delay exceeds 16777215 microseconds: · 0—Stable link state whose average delay is shorter than or equivalent to 16777215 microseconds. · 1—Unstable link state whose average delay is longer than 16777215 microseconds. |
Average delay |
Average delay in microseconds. |
Flag |
Min/Max link delay flag indicating whether the Min/Max link delay exceeds 16777215 microseconds. · 0—Stable link state whose Min/Max delay is shorter than or equivalent to 16777215 microseconds. · 1—Unstable link state whose Min/Max delay is longer than 16777215 microseconds. |
Min delay |
Minimum link delay in microseconds. |
Max delay |
Maximum link delay in microseconds. |
Delay variation |
Acceptable link delay variation in microseconds. |
Remaining bandwidth |
Remaining bandwidth in byte/s. |
Available bandwidth |
Available bandwidth in byte/s. |
Utilized bandwidth |
Used bandwidth in byte/s. |
SR/SRv6 Link Maximum SID Depths |
SR-MPLS/SRv6 Link Maximum SID Depths (MSD) sub-TLV information. |
MPLS MSD |
Maximum number of SIDs that SR-MPLS can encapsulate in a packet. |
LAN-ADJ-SID |
SID advertisement information from the LAN adjacency path. |
P2P-ADJ-SID |
SID advertisement information from the P2P adjacency path. |
Flags (F/B/V/L/S/P) |
Adjacency SID flag: · F—Address family flag. If set, the adjacency SID refers to an IPv6 adjacency. If not set, the adjacency SID refers to an IPv4 adjacency. · B—Backup flag. If set, the adjacency SID is eligible for link protection. · V—Value/Index flag. If set, the adjacency SID carries an absolute value. If not set, the adjacency SID carries an index value. · L—Local flag. If set, the adjacency SID has local significance. If not set, the adjacency SID has global significance. · S—Set flag. If set, the adjacency SID refers to a set of adjacencies. · P—Permanence flag. If set, the SID is allocated to a neighbor permanently, regardless of whether the device restarts or interface flapping occurs. |
Weight |
Path weight. |
Adjacency SID |
SID advertised by the adjacency path. |
SRv6 Lan End.X SID |
|
SRv6 End.X SID |
P2P adjacency SRv6 End.X SID sub-TLV information. |
SID |
SRv6 SID. |
Function type |
SID function type: · End (NO-FLAVOR)—End SID without any flavors. · End with PSP—End SID with Penultimate Segment Pop (PSP). · End with USP—End SID with Ultimate Segment Pop (USP). · End with PSP&USP—End SID with PSP and USP. · End with PSP, USP & USD—End SID with PSP and USP, and Ultimate Segment Decapsulation (USD). · End.X (NO-FLAVOR)—End.X SID without any flavors. · End.X with PSP—End.X SID with PSP. · End.X with USP—End.X SID with USP. · End.X with PSP&USP—End.X SID with PSP and USP. · End.X with PSP, USP & USD—End.X SID with PSP and USP, and USD. · End.T (no PSP, no USP)—End.T SID without PSP and USP. · End.T with PSP—End.T SID with PSP. · End.T with USP—End.T SID with USP. · End.T with PSP&USP—End.T SID with PSP and USP. · End.DT4—End.DT4 SID. · End.DT6—End.DT6 SID. · End.DT46—End.DT46 SID. · End.DX6—End.DX6 SID. · End with COC (NO-FLAVOR)—Compressed End SID without any flavors. · End.X with COC (NO-FLAVOR)—Compressed End.X SID without any flavors. · End.X with PSP&COC—Compressed End.X SID with PSP. · End.X with PSP&USP&COC—Compressed End.X SID with PSP and USP. |
Flags (B/S/P) |
SRv6 flag: · B—Backup flag. If set, the SID can be used for link protection. · S—Set flag. If set, the SID can be allocated to multiple neighbors. · P—Permanence flag. If set, the SID is allocated to a neighbor permanently even if the neighbor relationship is re-established. |
Prefix-SID flags (R/N/P/E/V/L) |
· 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. |
Prefix-SID |
Prefix SID. |
FAPM |
Flexible algorithm prefix metric. |
Algorithm |
Type of the algorithm associated to the prefix. · 0 represents the SPF algorithm. · A value of 128 to 255 represents the flexible algorithm. |
Router capability |
Route capability sub-TLV information. |
Flags (D/S) |
Inter-level leaking flag: · D—D flag. If set, the route capability TLV cannot be leaked from Level-1 to Level-2. · S—S flag. If set, the route capability TLV must be flooded across the entire routing domain. If not set, the route capability TLV cannot be leaked between levels. |
Segment routing (I/V/H) |
SR capability sub-TLV flag: · I—MPLS IPv4 flag. If set, the router is capable of processing SR-MPLS encapsulated IPv4 packets on all interfaces. · V—MPLS IPv6 flag. If set, the router is capable of processing SR-MPLS encapsulated IPv6 packets on all interfaces. This flag is not supported in the current software version. · H—SRv6 flag. If set, the router is capable of processing SRv6 encapsulated packets with Segment Routing Headers (SRHs) on all interfaces. This flag is not supported in the current software version. |
SRGB base |
Minimum label value of the SRGB range. |
SRGB range |
Number of labels of the SRGB. |
Segment routing local block (-) |
Local block sub-TLV information for segment routing. (-) indicates that no flags are defined. The field value is fixed at 0x00. |
SRLB base |
Minimum label value of the SRLB range. |
SRLB range |
Number of labels in the SRLB. |
SRv6 capability flags (O) |
SRv6 capability sub-TLV information. If the O flag is set, the router supports the OAM flag. |
SR/SRv6 Node Maximum SID Depths |
SR-MPLS or SRv6 Maximum SID Depths (MSD) sub-TLV information. |
SRv6 Segments Left |
The maximum value of the Segment Left field in the Segment Routing Header (SRH). |
SRv6 End Pop MSD |
The maximum number of SIDs that can be popped out by edge nodes supporting PSP or USP. If the destination address of a packet is the local SID of a device, the device is the edge node of the packet. |
SRv6 T.Insert MSD |
The maximum number of SIDs that a transit node can insert into a packet through an SR policy. If the destination address of a packet is neither a local address nor SID of a device, the device is the transit node of the packet. |
SRv6 T.Encaps MSD |
The maximum number of SIDs that a transit node can encapsulate into a packet through an SR policy. |
SRv6 End D MSD |
The maximum number of SIDs that an edge node can decapsulate. |
SR Algorithm |
SR algorithm information. |
Algorithm |
Advertised SR algorithm ID. |
Flex-Algo Definition |
FAD advertised by an SR node: · Algorithm—Flexible algorithm ID. 0 represents the SPF algorithm, and a value of 128 to 255 represents the flexible algorithm. · Metric-Type—Metric type of the flexible algorithm. · Alg-type—Flexible algorithm calculation type. · Priority—Priority of the flexible algorithm. · Flexible algorithm extended administrative group. ¡ Flex-Algo Exclude Any Ext Admin Group—A link will be excluded from the flexible algorithm topology if it has an affinity that is included in the group. ¡ Flex-Algo Include All Ext Admin Group—A link will be excluded from the flexible algorithm topology if it does not have all the affinities that are included in the group. ¡ Flex-Algo Include Any Ext Admin Group—A link will be excluded from the flexible algorithm topology if it does not have an affinity that is included in the group. · Flex-Algo Definition Flags—FAD flag information. The M-Flag indicates whether the flexible algorithm uses FAPM to calculate inter-area route prefixes and external route prefixes. If this flag is set, the flexible algorithm uses FAPM to calculate inter-area route prefixes and external route prefixes. |
SRv6 Locator |
SRv6 Locator TLV. |
SID locator. |
|
Flag (D) |
Leaking flag. If set, locator TLVs cannot be leaked from Level-1 to Level-2. |
Algorithm |
Algorithm ID. 0 represents the SPF algorithm, and a value of 128 to 255 represents the flexible algorithm. |
Flag (A) |
Anycast locator flag. If set, the locator is an anycast locator. |
End SID |
SRv6 End SID. |
Flag (C) |
SRv6 compression flag. If set, the SID is compressed. |
L2 bundle member attributes |
L2 Bundle Member Attributes TLV. |
Flags (P/-/-/-/-/-/-/-) |
Flag information. When the P flag is set, the TLV carries sub-TLVs used to distinguish parallel links. |
L2 bundle attribute descriptors |
L2 bundle attribute descriptors. |
Link local identifiers count: n |
Link ID information about member interfaces. n represents the number of link IDs. |
L2-Bundle-Member-LAN-ADJ-SID |
Adjacency SID information about member interfaces on LAN adjacency links. |
L2-Bundle-Member-ADJ-SID |
Adjacency SID information about member interfaces on P2P adjacency links. |
Flags (F/*/V/L/S/P/-/-) |
Prefix SID flag information: · F—Address family flag. If set, the adjacency SID refers to an IPv6 adjacency. If not set, the adjacency SID refers to an IPv4 adjacency. · V—Value/Index flag. If set, the adjacency SID carries an absolute value. If not set, the adjacency SID carries an index value. · L—Local flag. If set, the adjacency SID has local significance. If not set, the adjacency SID has global significance. · S—Set flag. If set, the adjacency SID refers to a set of adjacencies. · P—Persistence flag. If set, the adjacency SID remains unchanged. |
SRLG NBR ID |
SRLG information advertised to the IPv4 IS-IS neighbor. |
Interface IP address |
IPv4 address of the local interface. |
Neighbor IP address |
IPv4 address of the remote interface. |
IPV6 SRLG NBR ID |
SRLG information advertised to the IPv6 IS-IS neighbor. |
Interface IPv6 address |
IPv6 address of the local interface. |
Neighbor IPv6 address |
IPv6 address of the remote interface. |
Shared risk link group |
Group number of the SRLG to which the local interface belongs. |
Application Specific SRLG NBR ID |
Application-specific SRLG information advertised to the IPv6 IS-IS neighbor. Only flexible algorithm is supported. |
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 IS-IS Level-1 LSDB statistics.
level-2: Displays IS-IS 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 no level is specified, 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 25 Command output
Field |
Description |
LSP source ID |
ID of the source system. |
LSP count |
Number of LSPs with the same source ID. |
Total |
Total number of LSPs. |
Related commands
display isis lsdb
display isis mesh-group
Use display isis mesh-group to display IS-IS mesh group configuration information.
Syntax
display isis mesh-group [ process-id ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
process-id: Displays IS-IS mesh-group configuration 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 IS-IS mesh group configuration information for all IS-IS processes.
Examples
# Add Ten-GigabitEthernet 0/0/6 and Ten-GigabitEthernet 0/0/7 to mesh group 100.
<Sysname> system-view
[Sysname] interface ten-gigabitethernet 0/0/6
[Sysname-Ten-GigabitEthernet0/0/6] isis mesh-group 100
[Sysname-Ten-GigabitEthernet0/0/6] quit
[Sysname] interface ten-gigabitethernet 0/0/7
[Sysname-Ten-GigabitEthernet0/0/7] isis mesh-group 100
# Display IS-IS mesh-group configuration information.
[Sysname-Ten-GigabitEthernet0/0/7] display isis mesh-group
Mesh Group information for IS-IS(1)
----------------------------------------------------------------------
Interface Status
XGE1/0/6 Blocked
XGE1/0/7 100
Table 26 Command output
Field |
Description |
Interface |
Interface name. |
Status |
Mesh group the interface belongs to/whether a blocked interface is configured. |
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 27 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 [ process-id ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
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 NSR status information for all IS-IS processes.
Examples
# Display IS-IS NSR status.
<Sysname> display isis non-stop-routing status
Nonstop Routing information for IS-IS(1)
----------------------------------------
NSR phase: Finish
Table 28 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: Ten-GigabitEthernet0/0/6
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 0.5 holdtime : 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 BFD TLV : 0 Bad global IPv6 address TLV: 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 0.5 holdtime : 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 BFD TLV : 0 Bad global IPv6 address TLV: 0
Bad IID TLV : 0
Table 29 Command output
Field |
Description |
Total output packets with 1.5 hello intervals |
Total number of hello packets sent at intervals greater than 1.5 times the hello interval. |
Total input packets with 0.5 holdtime |
Total number of hello packets received at intervals greater than 0.5 times the holdtime. |
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 BFD TLV—Invalid BFD TLV. · Bad global IPv6 address TLV—Invalid global IPv6 address TLV. · 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: Ten-GigabitEthernet0/0/6
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 SRLG 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 SRLG TLV : 0
Bad IID TLV : 0
Table 30 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 SRLG TLV—Invalid SRLG 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: Ten-GigabitEthernet0/0/6
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 31 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: Ten-GigabitEthernet0/0/6
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 32 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: XGE0/0/7 Circuit Id: 0000.0000.0001.01
State: Up HoldTime: 27s Type: L1(L1L2) PRI: 64
System ID: 0000.0000.0001
Interface: XGE0/0/7 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: XGE0/0/7 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 IPv6 address(es): FE80::541F:98FF:FE5E:205
Peer IPv6 global address(es): 100::2
Peer local circuit ID: 1
Peer circuit SNPA address: 000c-293b-c4be
Uptime: 00:05:07
Adj protocol: IPv4
IPv4 adjacency state: Up
Adj P2P three-way handshake: No
Graceful Restart capable
Restarting signal: No
Suppress adjacency advertisement: No
Local topology:
0 2
Remote topology:
0 2
Local BFD support:
(MTID:0, IPv4)
Remote BFD support:
(MTID:0, IPv4)
System ID: 0000.0000.0002
Interface: XGE0/0/8 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
Local topology:
0
Remote topology:
0
Local BFD support:
(MTID:0, IPv4)
Remote BFD support:
(MTID:0, IPv4)
Table 33 Command output
Field |
Description |
System ID |
System ID of the neighbor. |
Interface |
Interface connecting to the neighbor. |
Circuit Id |
Circuit ID. · For broadcast links, if no DIS is elected, this field displays ---. If a DIS is elected, this field displays the ID of the DIS. · For P2P links, this field always displays 001. |
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. · L1L2—Means the circuit type is Level-1-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. |
Peer IPv6 global address(es) |
Global unicast IPv6 address of the remote interface. |
Uptime |
Time elapsed since the neighbor relationship was formed. |
Adj Protocol |
Adjacency protocol: IPv4 or IPv6. |
IPv4 adjacency state |
IPv4 adjacency state: Up or Down. This field is not displayed if IPv4 is not supported. |
IPv6 adjacency state |
IPv6 adjacency state: Up or Down. This field is not displayed if IPv6 is not supported. |
Adjacency not up |
Reason why the adjacency relationship is down: Waiting for BFD session to come up. This field is no longer displayed after the adjacency relationship comes up. |
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 |
Whether or not to suppress the SA bit upon restart. |
Local topology |
List of topologies supported by the local interface. |
Remote topology |
List of topologies supported by the neighbor interface. |
Local BFD support |
Support of the local end for adjacency establishment and maintenance control based on BFD session state: · (MTID:0, IPv4)—Adjacency establishment and maintenance control based on BFD session state is supported in IPv4 unicast topology 0. · (MTID:0, IPv6)—Adjacency establishment and maintenance control based on BFD session state is supported in IPv6 unicast topology 0. · (MTID:2, IPv6)—Adjacency establishment and maintenance control based on BFD session state is supported in IPv6 unicast topology 2. This field is not displayed if the local end does not support adjacency establishment and maintenance control based on BFD session state. |
Remote BFD support |
Support of the remote end for adjacency establishment and maintenance control based on BFD session state: · (MTID:0, IPv4)—Adjacency establishment and maintenance control based on BFD session state is supported in IPv4 unicast topology 0. · (MTID:0, IPv6)—Adjacency establishment and maintenance control based on BFD session state is supported in IPv6 unicast topology 0. · (MTID:2, IPv6)—Adjacency establishment and maintenance control based on BFD session state is supported in IPv6 unicast topology 2. This field is not displayed if the remote end does not support adjacency establishment and maintenance control based on BFD session state. |
# 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 34 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 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: XGE0/0/6 Circuit Id: 0000.0000.0002.01
First 3 L1 hello packets received:
2019-11-21 15:10:14:687
2019-11-21 15:10:14:732
2019-11-21 15:10:23:618
Last 3 L1 hello packets received:
2019-11-21 16:21:39:078
2019-11-21 16:21:42:383
2019-11-21 16:21:45:721
System ID: 0000.0000.0003
Interface: XGE0/0/6 Circuit Id: 0000.0000.0002.01
First 3 L2 hello packets received:
2019-11-21 15:10:14:688
2019-11-21 15:10:14:734
2019-11-21 15:10:24:090
Last 3 L2 hello packets received:
2019-11-21 16:21:39:078
2019-11-21 16:21:42:383
2019-11-21 16:21:45:722
Table 35 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, where xx 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, where xx 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.
ip-address mask-length: Specifies the destination IP address and mask length.
ipv6: Displays the redistributed IPv6 routing information.
ipv6-address prefix-length: Specifies the destination IPv6 address and prefix length. The value range for the prefix-length argument is 1 to 128.
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 the 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 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
Type: D -Direct, I -ISIS, S -Static, O -OSPF, B -BGP, R -RIP
Table 36 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 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 37 Command output
Field |
Description |
Route information for IS-IS(1) |
Redistributed route information for IS-IS process 1. |
Level-1 IPv6 Redistribute Table |
Redistributed route information of IS-IS Level-1. |
Level-2 IPv6 Redistribute Table |
Redistributed route information of IS-IS Level-2. |
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 IS-IS IPv4 routing information.
ip-address mask-length: Displays IS-IS IPv4 routing information for the specified IP address. The mask-length argument is in the range of 0 to 32.
ipv6: Displays IS-IS IPv6 routing information.
ipv6-address prefix-length: Displays IS-IS IPv6 routing information for the specified IPv6 address. The prefix-length argument is in the range of 0 to 128.
level-1: Displays Level-1 IS-IS routing information.
level-2: Displays Level-2 IS-IS routing information.
verbose: Displays detailed IS-IS IPv4 routing information. If you do not specify this keyword, the command displays brief IS-IS routing information
process-id: Displays IS-IS IPv4 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.
Usage guidelines
If you do not specify the ipv4 or ipv6 keyword, the command displays IS-IS IPv4 routing information.
If you do not specify a level, this command displays both Level-1 and Level-2 routing information.
Examples
# Display brief IS-IS IPv4 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 XGE0/0/7 Direct D/L/-
9.9.9.0/24 20 NULL XGE0/0/7 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 38 Command output
Field |
Description |
Route information for IS-IS(1) |
Route information for IS-IS process 1. |
Level-1 IPv4 Forwarding Table |
IS-IS IPv4 routing information for Level-1. |
Level-2 IPv4 Forwarding Table |
IS-IS IPv4 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 IS-IS IPv4 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 XGE0/0/7 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 XGE0/0/7 0x00000003
Nib ID : 0x0 OutLabel : 4294967295 OutLabelFlag: -
LabelSrc : N/A Delay Flag : N/A
Remote-LFA:
Interface : XGE0/0/8
BkNextHop : 31.1.1.3 LsIndex : 0x01000002
Tunnel destination address: 4.4.4.9
Backup label: {2174}
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 XGE0/0/7 0x00000000
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 39 Command output
Field |
Description |
Route information for IS-IS(1) |
Route information for IS-IS process 1. |
Level-1 IPv4 Forwarding Table |
IS-IS IPv4 routing information for Level-1. |
Level-2 IPv4 Forwarding Table |
IS-IS IPv4 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 |
Incoming label. |
InLabel flag |
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. |
NextHop |
Next hop. |
Interface |
Output interface. |
ExitIndex |
Index of the output interface. |
Nib ID |
ID assigned by the routing management module (next hop index). |
OutLabel |
Outgoing label. |
OutLabelFlag |
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 preferred flag. |
LabelSrc |
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 |
Microloop avoidance delay flag: · D—Microloop avoidance is configured. Route convergence is delayed. · N/A—Microloop avoidance is not configured or the microloop avoidance RIB-update-delay timer has expired. Route convergence is in progress. |
SR microloop label stack (top->bottom) |
SR microloop label stack arranged from top to bottom. |
TI-LFA |
TI-LFA backup information. |
BKNextHop |
TI-LFA/Remote LFA backup next hop. |
LsIndex |
Label stack index. |
Backup label stack(top->bottom) |
Backup path label stack. N/A indicates that no label stack exists. |
Route label |
Route label. |
Remote-LFA |
Remote LFA backup information. |
Tunnel destination address |
LDP tunnel destination address. |
Backup label |
Backup label to the PQ node. N/A indicates that no label exists. |
# 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: XGE0/0/6
Destination: 2001:2:: PrefixLen: 64
Flag : D/L/- Cost : 10
Next hop : Direct Interface: XGE0/0/6
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 40 Command output
Field |
Description |
Destination |
IPv6 destination prefix. |
PrefixLen |
Prefix length. |
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 type and number, or SRv6 TE policy name. |
# 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 : 2::2/128
Flag : R/L/- Cost : 10
Admin tag : - Src count : 1
Algorithm : 0
Priority : Medium
Nexthop : FE80::86FB:DDFF:FE3F:1007
Interface : XGE0/0/7 Delay Flag : N/A
BkNexthop : FE80::86FB:D4FF:FE1B:E05
BkInterface : XGE0/0/6
Nib ID : 0x24000008
IPv6 dest : 2012::/64
Flag : D/L/- Cost : 10
Admin tag : - Src count : 2
Algorithm : 0
Priority : Low
Nexthop : Direct
Interface : XGE0/0/7 Delay Flag : N/A
Nib ID : 0x0
IPv6 dest : 2023::/64
Flag : R/L/- Cost : 20
Admin tag : - Src count : 2
Algorithm : 0
Priority : Low
Nexthop : FE80::86FB:D4FF:FE1B:E05
Interface : XGE0/0/6 Delay Flag : N/A
Nib ID : 0x24000007
Priority : Low
Nexthop : FE80::86FB:DDFF:FE3F:1007
Interface : XGE0/0/7 Delay Flag : N/A
Nib ID : 0x24000004
IPv6 dest : 2013::/64
Flag : D/L/- Cost : 10
Admin tag : - Src count : 2
Algorithm : 0
Priority : Low
Nexthop : Direct
Interface : XGE0/0/6 Delay Flag : N/A
Nib ID : 0x0
Flags: D-Direct, R-Added to Rib, L-Advertised in LSPs, U-Up/Down Bit Set
Level-2 IPv6 forwarding table
-----------------------------
IPv6 dest : 2::2/128
Flag : -/-/- Cost : 10
Admin tag : - Src count : 2
Nexthop : -
Interface : -
Nib ID : -
IPv6 dest : 2012::/64
Flag : D/L/- Cost : 10
Admin tag : - Src count : 3
Algorithm : 0
Priority : Low
Nexthop : Direct
Interface : XGE0/0/7 Delay Flag : N/A
Nib ID : 0x0
IPv6 dest : 2023::/64
Flag : -/-/- Cost : 20
Admin tag : - Src count : 2
Nexthop : -
Interface : -
Nib ID : -
IPv6 dest : 2013::/64
Flag : D/L/- Cost : 10
Admin tag : - Src count : 3
Algorithm : 0
Priority : Low
Nexthop : Direct
Interface : XGE0/0/6 Delay Flag : N/A
Nib ID : 0x0
Flags: D-Direct, R-Added to Rib, L-Advertised in LSPs, U-Up/Down Bit Set
Table 41 Command output
Field |
Description |
IPv6 dest |
IPv6 destination address and prefix. |
Flag/Flags |
Route flag: · D—The route 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. |
Algorithm |
Algorithm ID. 0 represents the SPF algorithm, and a value of 128 to 255 represents the flexible algorithm. |
Priority |
Route convergence priority. Options include critical, high, medium, and low. |
Nexthop |
Next hop. |
Interface |
Output interface type and number, or SRv6 TE policy name. |
BkNexthop |
Backup next hop. |
BkInterface |
Backup output interface. |
SR microloop label stack (top->bottom) |
SR microloop label stack arranged from top to bottom. |
TI-LFA |
TI-LFA backup information. |
BKNextHop |
TI-LFA backup next hop. |
LsIndex |
Label stack index. |
Backup label stack (top->bottom) |
Backup path label stack arranged from top to bottom. N/A indicates that no label stack exists. |
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 IS-IS IPv4 SPF tree information.
ipv6: Displays IS-IS IPv6 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.
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.
verbose: Displays detailed IS-IS SPF tree information. If you do not specify this keyword, the command displays brief IS-IS SPF tree information.
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 IS-IS IPv4 SPF tree information.
Examples
# Display brief IS-IS IPv4 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 IS-IS IPv4 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
SRP distance : 0
NodeFlag : S/-/-/-/-/-
RelayNibID : 0x0
TE tunnel count: 0
SRP count : 0
Nexthop count : 0
SpfLink count : 1
-->0000.0000.0004.04
LinkCost : 10
LinkNewCost : 10
MplsTeCost : 16777215
DelayCost : 16777215
LinkFlag : -/-/C/-/-/-/-/-/-
LinkSrcCnt : 1
Type : Adjacent Interface : N/A
Cost : 10 Nexthop : N/A
InterfaceIP: 192.168.1.101 NeighborIP: N/A
MplsTeCost : 16777215 DelayCost : 16777215
SpfNode : 0000.0000.0004.00
Distance : 10
TE Distance : 10
SRP distance : 0
NodeFlag : S/-/-/-/-/-
RelayNibID : 0x14000000
TE tunnel count: 1
Destination: 4.4.4.4 Interface : Tun0
TE cost : 10 Final cost : 10
SRP count : 0
Nexthop count : 2
Neighbor : 0000.0000.0004.00 Interface : Tun0
Nexthop : 4.4.4.4
BkNeighbor : N/A BkInterface: N/A
BkNexthop : N/A
Neighbor : 0000.0000.0004.00 Interface : XGE0/0/6
Nexthop : 1.1.1.3
BkNeighbor : N/A BkInterface: N/A
BkNexthop : N/A
Remote-LFA :
Protect : Link
RLfaNeighbor: 0000.0000.0003.00
PQNode : 0000.0000.0004.00
PQNodePrefix: 4.4.4.9/32
OutLabel : 2174
SpfLink count : 1
-->0000.0000.0004.04
LinkCost : 10
LinkNewCost : 10
MplsTeCost : 16777215
DelayCost : 16777215
LinkFlag : -/-/-/P/-/-/-/-/-
LinkSrcCnt : 1
Type : Remote Interface : N/A
Cost : 10 Nexthop : N/A
InterfaceIP: N/A NeighborIP: N/A
AdvMtID : 0
MplsTeCost : 16777215 DelayCost : 16777215
SpfNode : 0000.0000.0004.04
Distance : 10
TE distance : 10
SRP distance : 0
NodeFlag : S/-/-/R/-/-
RelayNibID : 0x14000001
TE tunnel count: 0
SRP count : 0
Nexthop count : 0
SpfLink count : 2
-->0000.0000.0001.00
LinkCost : 0
LinkNewCost : 0
MplsTeCost : 0
DelayCost : 0
LinkFlag : -/-/-/P/-/-/-/-/-
LinkSrcCnt : 1
Type : Remote Interface : N/A
Cost : 0 Nexthop : N/A
InterfaceIP: N/A NeighborIP: N/A
MplsTeCost : 0 DelayCost : 0
-->0000.0000.0004.00
LinkCost : 0
LinkNewCost : 0
MplsTeCost : 0
DelayCost : 0
LinkFlag : -/-/C/-/-/-/-/-/-
LinkSrcCnt : 1
Type : Remote Interface: XGE0/0/6
Cost : 0 Nexthop : 1.1.1.3
InterfaceIP: N/A NeighborIP: N/A
MplsTeCost : 0 DelayCost : 0
Level-2 Shortest Path Tree
--------------------------
SpfNode : 0000.0000.0001.00
Distance : 0
TE distance : 0
SRP distance : 0
NodeFlag : S/-/-/-/-/-
RelayNibID : 0x0
TE tunnel count: 0
SRP count : 0
Nexthop count : 0
SpfLink count : 1
-->0000.0000.0004.04
LinkCost : 10
LinkNewCost : 10
MplsTeCost : 16777215
DelayCost : 16777215
LinkFlag : -/-/C/-/-/-/-/-/-
LinkSrcCnt : 1
Type : Adjacent Interface : N/A
Cost : 10 Nexthop : N/A
InterfaceIP: N/A NeighborIP: N/A
MplsTeCost : 16777215 DelayCost : 16777215
SpfNode : 0000.0000.0004.00
Distance : 10
TE distance : 10
SRP distance : 0
NodeFlag : S/-/-/-/-/-
RelayNibID : 0x0
TE tunnel count: 1
Destination: 4.4.4.4 Interface : Tun0
TE cost : 10 Final cost : 10
SRP count : 0
Nexthop count : 2
Neighbor : 0000.0000.0004.00 Interface : Tun0
Nexthop : 4.4.4.4
BkNeighbor : N/A BkInterface: N/A
BkNexthop : N/A
Neighbor : 0000.0000.0004.00 Interface : XGE0/0/6
Nexthop : 1.1.1.3
BkNeighbor : N/A BkInterface: N/A
BkNexthop : N/A
SpfLink count : 1
-->0000.0000.0004.04
LinkCost : 10
LinkNewCost : 10
MplsTeCost : 16777215
DelayCost : 16777215
LinkFlag : -/-/-/P/-/-/-/-/-
LinkSrcCnt : 1
Type : Remote Interface : N/A
Cost : 10 Nexthop : N/A
InterfaceIP: N/A NeighborIP: N/A
AdvMtID : 0
MplsTeCost : 16777215 DelayCost : 16777215
SpfNode : 0000.0000.0004.04
Distance : 10
TE distance : 10
SRP distance : 0
NodeFlag : S/-/-/R/-/-
RelayNibID : 0x0
TE tunnel count: 0
SRP count : 0
Nexthop count : 0
SpfLink count : 2
-->0000.0000.0001.00
LinkCost : 0
LinkNewCost : 0
MplsTeCost : 0
DelayCost : 0
LinkFlag : -/-/-/P/-/-/-/-/-
LinkSrcCnt : 1
Type : Remote Interface : N/A
Cost : 0 Nexthop : N/A
InterfaceIP: N/A NeighborIP: N/A
MplsTeCost : 0 DelayCost : 0
-->0000.0000.0004.00
LinkCost : 0
LinkNewCost : 0
MplsTeCost : 0
DelayCost : 0
LinkFlag : -/-/C/-/-/-/-/-/-
LinkSrcCnt : 1
Type : Remote Interface: XGE0/0/6
Cost : 0 Nexthop : 1.1.1.3
InterfaceIP: N/A NeighborIP: N/A
MplsTeCost : 0 DelayCost : 0
# Display detailed information about the SPF node with system ID 0000.0000.0002.00.
<Sysname> display isis spf-tree source-id 0000.0000.0002.00
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.0002.00
Distance : 10
TE distance : 10
SRP distance : 0
NodeFlag : S/-/-/-/-/-
RelayNibID : 0x0
TE tunnel count: 0
SRP count : 0
Nexthop count : 1
Neighbor : 0000.0000.0002.00 Interface : XGE0/0/6
Nexthop : 101.1.1.2
BkNeighbor : N/A BkInterface: N/A
BkNexthop : N/A
SpfLink count : 2
-->0000.0000.0002.01
LinkCost : 60
LinkNewCost : 60
MplsTeCost : 16777215
DelayCost : 16777215
LinkFlag : -/-/-/P/-/-/-/-/-
LinkSrcCnt : 1
Type : Remote Interface : N/A
Cost : 60 Nexthop : N/A
InterfaceIP: 101.1.1.101 NeighborIP: N/A
AdvMtID : 0
MplsTeCost : 16777215 DelayCost : 16777215
-->0000.0000.0003.01
LinkCost : 10
LinkNewCost : 10
MplsTeCost : 16777215
DelayCost : 16777215
LinkFlag : -/-/C/-/-/-/-/-/-
LinkSrcCnt : 1
Type : Remote Interface : N/A
Cost : 10 Nexthop : N/A
InterfaceIP: N/A NeighborIP: N/A
AdvMtID : 0
MplsTeCost : 16777215 DelayCost : 16777215
Level-2 Shortest Path Tree
--------------------------
SpfNode : 0000.0000.0002.00
Distance : 10
TE distance : 10
SRP distance : 0
NodeFlag : S/-/-/-/-/-
RelayNibID : 0x0
TE tunnel count: 0
SRP count : 0
Nexthop count : 1
Neighbor : 0000.0000.0002.00 Interface : XGE0/0/6
Nexthop : 101.1.1.2
BkNeighbor : N/A BkInterface: N/A
BkNexthop : N/A
SpfLink count : 2
-->0000.0000.0002.01
LinkCost : 60
LinkNewCost : 60
MplsTeCost : 16777215
DelayCost : 16777215
LinkFlag : -/-/-/P/-/-/-/-/-
LinkSrcCnt : 1
Type : Remote Interface : N/A
Cost : 60 Nexthop : N/A
InterfaceIP: 101.1.1.101 NeighborIP: N/A
AdvMtID : 0
MplsTeCost : 16777215 DelayCost : 16777215
-->0000.0000.0003.01
LinkCost : 10
LinkNewCost : 10
MplsTeCost : 16777215
DelayCost : 16777215
LinkFlag : -/-/C/-/-/-/-/-/-
LinkSrcCnt : 1
Type : Remote Interface : N/A
Cost : 10 Nexthop : N/A
InterfaceIP: N/A NeighborIP: N/A
AdvMtID : 0
MplsTeCost : 16777215 DelayCost : 16777215
Table 42 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. |
SRP distance |
Shortest distance from the root node to the local node (including SRv6 TE policy links). If no SRv6 TE policy is configured, SRP 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. |
TE tunnel count |
Number of tunnels destined to this node. |
SRP count |
Number of SRv6 TE policies destined to this node. |
Destination |
Destination router. |
TE cost |
IGP cost of the TE tunnel. |
Final cost |
Final cost of the TE tunnel. |
Nexthop count |
Next hop count. |
Nexthop |
Primary next hop of the node or the link advertising source. |
MADuration |
Microloop avoidance RIB-update-delay timer in milliseconds. |
MALStack |
Microloop avoidance label stack. |
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. |
TiLfaNeighbor |
ID of the TI-LFA backup next hop neighbor. |
TiLfaInterface |
Output interface of the TI-LFA backup next hop. |
TiLfaNexthop |
TI-LFA backup next hop. |
PNode SrcID |
Source ID of the P node. |
QNode SrcID |
Source ID of the Q node. |
PNode prefix |
Prefix of the P node. N/A indicates that the prefix of the destination node is not displayed in the P space. |
PNode SidIndex |
Index value of the prefix SID for the P node. N/A indicates that the prefix SID of the destination node is not displayed in the P space. |
Protect |
TI-LFA/Remote LFA traffic protection type: · Link—Link protection. The direct primary link is excluded from backup path calculation. · Node—Node protection. The primary next hop node is excluded from backup path calculation. · SrlgLink—SRLG-disjoint link protection. The following links are excluded from backup path calculation: ¡ Direct primary link. ¡ Local links in the same SRLG as the direct primary link. · SrlgNode—SRLG-disjoint node protection. The following items are excluded from backup path calculation: ¡ Primary next hop node. ¡ Local links in the same SRLG as the direct primary link. |
Label stack |
Label stack. N/A indicates that no label stack exists. |
SpfLink |
Topology link. |
SpfLink count |
Number of topology links. |
LinkCost |
Link cost. |
LinkNewCost |
New link cost. |
MplsTeCost |
TE metric value for the IS-IS interface link. The maximum value is 16777215. |
DelayCost |
Latency for the IS-IS interface link. The maximum value is 16777215. |
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. |
InterfaceIP |
Interface IP address. |
NeighborIP |
Neighbor IP address. |
PolicyName |
Name of the SRv6 TE policy destined to this node. |
EndPoint |
Destination node of the SRv6 TE policy. |
Color |
Color value of the SRv6 TE policy. |
Auto cost |
IGP metric of the SRv6 TE policy. |
Final cost |
Effective IGP metric of the SRv6 TE policy. |
Auto route |
Automatic route type. Only Shortcut is supported in the current software version. |
State |
Whether the SRv6 TE policy is active. |
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
MplsTeCost : 16777215
DelayCost : 16777215
LinkFlag : -/-/C/-/-/-/-/-/-
LinkSrcCnt : 1
Type : Adjacent Interface : N/A
Cost : 10 Nexthop : N/A
InterfaceIP: N/A NeighborIP: N/A
MplsTeCost : 16777215 DelayCost : 16777215
-->0000.0000.0064.00
LinkCost : 10
LinkNewCost : 10
MplsTeCost : 16777215
DelayCost : 16777215
LinkFlag : -/-/C/-/-/-/-/-/-
LinkSrcCnt : 1
Type : Adjacent Interface : Tun1
Cost : 10 Nexthop : FE80::A0A:A40
InterfaceIP: N/A NeighborIP: N/A
MplsTeCost : 16777215 DelayCost : 16777215
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
MplsTeCost : 0
DelayCost : 0
LinkFlag : -/-/C/-/-/-/-/-/-
LinkSrcCnt : 1
Type : Adjacent Interface: XGE0/0/7
Cost : 10 Nexthop : FE80::200:12FF:FE34:1
InterfaceIP: N/A NeighborIP: N/A
MplsTeCost : 0 DelayCost : 0
-->0000.0000.0032.00
LinkCost : 0
LinkNewCost : 0
MplsTeCost : 0
DelayCost : 0
LinkFlag : -/-/-/P/-/-/-/-/-
LinkSrcCnt : 1
Type : Adjacent Interface : N/A
Cost : 0 Nexthop : N/A
InterfaceIP: N/A NeighborIP: N/A
MplsTeCost : 0 DelayCost : 0
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 : XGE0/0/7
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
MplsTeCost : 16777215
DelayCost : 16777215
LinkFlag : -/-/-/P/-/-/-/-/-
LinkSrcCnt : 1
Type : Remote Interface : N/A
Cost : 10 Nexthop : N/A
InterfaceIP: N/A NeighborIP: N/A
AdvMtID : 0
MplsTeCost : 16777215 DelayCost : 16777215
-->0000.0000.0064.00
LinkCost : 10
LinkNewCost : 10
MplsTeCost : 16777215
DelayCost : 16777215
LinkFlag : -/-/C/-/-/-/-/-/-
LinkSrcCnt : 1
Type : Remote Interface : Tun1
Cost : 10 Nexthop : FE80::A0A:A40
InterfaceIP: N/A NeighborIP: N/A
AdvMtID : 0
MplsTeCost : 16777215 DelayCost : 16777215
Table 43 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—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. |
MADuration |
SR microloop avoidance duration in milliseconds. |
MALStack |
SR microloop avoidance label stack. |
TiLfaNeighbor |
ID of the TI-LFA backup next hop neighbor. |
TiLfaInterface |
Output interface of the TI-LFA backup next hop. |
TiLfaNexthop |
TI-LFA backup next hop. |
PNode SrcID |
Source ID of the P node. |
QNode SrcID |
Source ID of the Q node. |
PNode prefix |
Prefix of the P node. N/A indicates that the prefix of the destination node is not displayed in the P space. |
PNode SidIndex |
Index value of the prefix SID for the P node. N/A indicates that the prefix SID of the destination node is not displayed in the P space. |
Protect |
TI-LFA/Remote LFA traffic protection type: · Link—Link protection. · Node—Node protection. |
Label stack |
Label stack. N/A indicates that no label stack exists. |
SpfLink |
Topology link. |
SpfLink count |
Number of topology links. |
LinkCost |
Link cost. |
LinkNewCost |
New link cost. |
MplsTeCost |
TE metric value for the IS-IS interface link. The maximum value is 16777215. |
DelayCost |
Latency for the IS-IS interface link. The maximum value is 16777215. |
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. |
InterfaceIP |
IP address of the interface, |
NeighborIP |
IP address of the neighbor. |
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 IS-IS IPv4 statistics. If you do not specify this option, the command displays IS-IS IPv4 and IPv6 statistics.
ipv6: Displays IS-IS IPv6 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 44 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. base represents the base topology. |
Learnt routes information |
Total IPv4 Learnt Routes in IPv4 Routing Table means number of learned IPv4 routes. Total IPv6 Learnt Routes in IPv6 Routing Table means 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.
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
2020-01-08 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: XGE0/0/6, neighbor IPv4 address: 10.1.1.1; neighbor IPv6 address: FE80::8ae3:1156:17)
2020-01-08 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: XGE0/0/6, neighbor IPv4 address: 10.1.1.1; neighbor IPv6 address: FE80::8ae3:1156:17)
2020-01-08 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: XGE0/0/6, 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 45 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: XGE0/0/6, 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: XGE0/0/6, 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: XGE0/0/6, 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: XGE0/0/6, 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: XGE0/0/6, 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: XGE0/0/6, 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: XGE0/0/6, 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: XGE0/0/6, 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: XGE0/0/6, 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: XGE0/0/6, 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: XGE0/0/6, 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: XGE0/0/6, 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: XGE0/0/6, 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: XGE0/0/6, 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: XGE0/0/6, 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: XGE0/0/6, 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: XGE0/0/6, 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: XGE0/0/6, 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: XGE0/0/6, 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: XGE0/0/6, 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: XGE0/0/6, 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: XGE0/0/6, 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: XGE0/0/6, 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: XGE0/0/6, 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: XGE0/0/6, 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: XGE0/0/6, 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: XGE0/0/6, 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: XGE0/0/6, 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: XGE0/0/6, 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: XGE0/0/6, 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: XGE0/0/6, 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: XGE0/0/6, 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: XGE0/0/6, 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: XGE0/0/6, 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 extended circuit ID was received (Interface: XGE0/0/6, 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: XGE0/0/6, 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: XGE0/0/6, 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: XGE0/0/6, 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: XGE0/0/6, 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
slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command displays OSI connection information for all cards.
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:
Ten-GigabitEthernet0/0/6
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:
Ten-GigabitEthernet0/0/6
MAC address: 0180-c200-0014
Table 46 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
slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command displays OSI packet statistics for all cards.
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 47 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 LPUs relayed from other cards. This count is not included in the total count of received packets. · Relay forwarded—Number of inbound packets relayed to LPUs. · Invalid service slot—Number of discarded packets due to unavailable LPUs. · 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 hosts 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 hosts the output interfaces. These packets are relayed from other cards. · Failed—Number of packets failed to be sent. |
Related commands
reset osi statistics
distribute
Use distribute to advertise IS-IS link state information to other protocols.
Use undo distribute to restore the default.
Syntax
distribute { bgp-ls | link-state } [ instance-id id ] [ level-1 | level-2 ]
undo distribute { bgp-ls | link-state } [ level-1 | level-2 ]
Default
The device does not advertise IS-IS link state information any other protocol.
Views
IS-IS view
Predefined user roles
network-admin
Parameters
bgp-ls: Advertises IS-IS link state information only to BGP.
link-state: Advertises IS-IS link state information to all protocols, such as BGP.
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 other protocols, these protocols can then 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 other protocols, specify a different instance ID for each IS-IS process.
If you do not specify a level for this command, both Level-1 and Level-2 IS-IS link state information will be advertised to other protocols.
When multiple IS-IS P2P neighbors exist between two devices, add IP addresses of the local interfaces into link state information, which enables other protocols to distinguish PPP links. To achieve this goal, use the advertise link-attributes or router-id command in IS-IS IPv6 address family view.
If you do not specify a keyword for the undo distribute command, IS-IS does not advertise link state information.
If you execute this command multiple times, the most recent configuration takes effect.
Examples
# Advertise link state information of IS-IS process 1 to BGP.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] distribute bgp-ls
Related commands
advertise link-attributes
router-id (Segment Routing Command Reference)
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. In simple authentication mode and GCA authentication mode, the plaintext form of the key is a case-sensitive string of 1 to 16 characters, and the encrypted form is a case-sensitive string of 33 to 53 characters. In MD5 authentication mode, the plaintext form of the key is a case-sensitive string of 1 to 255 characters, and the encrypted form is a case-sensitive string of 33 to 373 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.
IS-IS keychain authentication supports the HMAC-MD5 and HMAC-SM3 authentication algorithms. If the HMAC-MD5 algorithm is used, the key ID can be any value in the range supported by the key-id argument. If the HMAC-SM3 algorithm is used, the key ID must be in the range of 0 to 65535.
When keychain authentication is used, IS-IS receives and sends packets as follows:
· 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 or HMAC-SM3 algorithm, the authentication fails and the packet does not contain the authentication information.
· After IS-IS receives a Level-2 packet, it processes the packet as follows:
¡ If the authentication algorithm of the packet is HMAC-MD5, IS-IS 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.
¡ If the authentication algorithm of the packet is HMAC-SM3, IS-IS uses the key ID of the received packet to obtain the corresponding valid accept key from the keychain. Then, IS-IS uses the accept key to authenticate the packet. If IS-IS cannot find a valid accept key based on the key ID of the received packet or the packet fails the authentication, 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 (including non-H3C 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.
In MD5 authentication mode, execute the undo domain-authentication-mode command before version switch if the key lengths supported by the two versions are different.
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
exclude-srlg
Use exclude-srlg to configure the SRLG links to be excluded.
Use undo exclude-srlg to remove the configuration.
Syntax
exclude-srlg srlg-value&<1-32>
undo exclude-srlg
Default
All links on nodes that participate in flexible algorithm calculation join the flexible algorithm topology.
Views
Flexible algorithm view
Predefined user roles
network-admin
Parameters
srlg-value&<1-32>: Specifies a Shared Risk Link Group (SRLG) by its ID in the range of 0 to 4294967295. &<1-32> indicates that you can specify a maximum of 32 SRLGs.
Usage guidelines
This command enhances the reliability of route calculation results in scenarios where SR-MPLS uses a flexible algorithm for SRLSP calculation or where SRv6 uses a flexible algorithm for SRv6 tunnel calculation. After you execute this command, the specified SRLGs will be excluded from the flexible algorithm calculation.
This command is supported only when the link cost type is wide, compatible, or wide-compatible.
Examples
# Configure flexible algorithm calculation to exclude links in SRLGs 11 and 22.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] flex-algo 128
[Sysname-isis-1-flex-algo-128] exclude-srlg 11 22
Related commands
cost-style
fast-reroute
Use fast-reroute to configure IS-IS FRR.
Use undo fast-reroute to disable IS-IS FRR.
Syntax
fast-reroute { lfa [ ecmp-shared | level-1 | level-2 ] | route-policy route-policy-name }
undo fast-reroute { lfa [ ecmp-shared | 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.
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 or display ipv6 routing-table command.
After you specify the ecmp-shared keyword in this command, the following rules apply:
· If you also enable remote LFA FRR, the ecmp-shared keyword does not take effect. IS-IS calculates backup next hops only for non-ECMP routes.
· If you also enable TI-LFA FRR, TI-LFA can calculate a backup next hop for ECMP routes only when one of the following conditions exists:
¡ The primary next hops of those ECMP routes have the same IS-IS neighbors.
¡ The primary next hops of those ECMP routes are in the same SRLG group.
· If you also enable primary link failure detection through BFD and microloop avoidance, these features do not take effect.
The LFA calculation of FRR and IS-IS TE are mutually exclusive.
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
Related commands
fast-reroute microloop-avoidance enable (Segment Routing Command Reference)
isis primary-path-detect bfd
segment-routing microloop-avoidance enable (Segment Routing Command Reference)
fast-reroute enable
Use fast-reroute enable to enable FRR for a flexible algorithm.
Use undo fast-reroute enable to disable FRR for a flexible algorithm.
Syntax
fast-reroute enable
undo fast-reroute enable
Default
Flexible algorithm FRR is enabled.
Views
Flexible algorithm view
Predefined user roles
network-admin
Usage guidelines
The flexible algorithm FRR is similar to IS-IS LFA FRR, because it uses LFA to calculate a loop-free backup path with the lowest cost based on the topology.
If no backup paths exist in the topology, execute the undo fast-reroute enable command to disable flexible algorithm FRR to save device resources.
This feature is available only when the link cost style is wide, compatible, or wide-compatible.
Examples
# Disable FRR for flexible algorithm 128.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] flex-algo 128
[Sysname-isis-1-flex-algo-128] undo fast-reroute enable
Related commands
cost-style
fast-reroute microloop-avoidance enable
Use fast-reroute microloop-avoidance enable to enable FRR microloop avoidance for a flexible algorithm.
Use undo fast-reroute microloop-avoidance enable to disable FRR microloop avoidance for a flexible algorithm.
Syntax
fast-reroute microloop-avoidance enable
undo fast-reroute microloop-avoidance enable
Default
FRR microloop avoidance is enabled for flexible algorithms.
Views
Flexible algorithm view
Predefined user roles
network-admin
Usage guidelines
After a network failure occurs, some devices along the traffic forwarding path will perform route convergence. During the route convergence process, microloops might occur and cause packet loss and disorder if the route convergence on each device is not simultaneous.
To resolve this issue, enable this feature on the nodes next to the node that failed and set the microloop avoidance RIB-update-delay timer. Traffic will be forwarded through the backup path calculated by TI-LFA before the microloop avoidance RIB-update-delay timer expires.
Examples
# Disable FRR microloop avoidance for flexible algorithm 128.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] flex-algo 128
[Sysname-isis-1-flex-algo-128] undo fast-reroute microloop-avoidance enable
Related commands
fast-reroute microloop-avoidance rib-update-delay
fast-reroute microloop-avoidance rib-update-delay
Use fast-reroute microloop-avoidance rib-update-delay to set the FRR microloop avoidance RIB-update-delay timer for a flexible algorithm.
Use undo fast-reroute microloop-avoidance rib-update-delay to restore the default.
Syntax
fast-reroute microloop-avoidance rib-update-delay delay-time [ level-1 | level-2 ]
undo fast-reroute microloop-avoidance rib-update-delay [ level-1 | level-2 ]
Default
The FRR microloop avoidance RIB-update-delay timer is 5000 milliseconds.
Views
Flexible algorithm view
Predefined user roles
network-admin
Parameters
delay-time: Sets the FRR microloop avoidance RIB-update-delay timer in milliseconds. The value range for this argument is 1 to 60000.
level-1: Applies the FRR microloop avoidance RIB-update-delay timer to Level-1 areas.
level-2: Applies the FRR microloop avoidance RIB-update-delay timer for the Level-2 area.
Usage guidelines
For the FRR microloop avoidance RIB-update-delay timer to take effect, enable FRR microloop avoidance for the flexible algorithm first.
If you do not specify the level-1 or level-2 keyword, this command sets the FRR microloop avoidance RIB-update-delay timer for all IS-IS levels.
Examples
# Set the FRR microloop avoidance RIB-update-delay timer to 6000 milliseconds for flexible algorithm 128 in IS-IS process 1.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] flex-algo 128
[Sysname-isis-1-flex-algo-128] fast-reroute microloop-avoidance rib-update-delay 6000
Related commands
fast-reroute microloop-avoidance enable
fast-reroute primary-path-detect bfd
Use fast-reroute primary-path-detect bfd to enable BFD-powered primary link failure detection for an IS-IS process.
Use undo fast-reroute primary-path-detect bfd to disable BFD-powered primary link failure detection in an IS-IS process.
Syntax
fast-reroute primary-path-detect bfd { ctrl | echo }
undo fast-reroute primary-path-detect bfd
Default
An IS-IS process does not use BFD to detect primary link failures for IS-IS FRR and PIC.
Views
IS-IS IPv4 address family view
IS-IS IPv6 address family view
Predefined user roles
network-admin
Parameters
ctrl: Enables BFD control packet mode.
echo: Enables BFD echo packet mode.
Usage guidelines
This command enables IS-IS FRR and IS-IS PIC to use BFD to detect primary link failures. BFD can detect and report a primary link failure to IS-IS for a primary-backup path switchover. This can shorten the duration of service interruption.
To enable BFD-powered primary link failure detection, you can use the fast-reroute primary-path-detect bfd, isis primary-path-detect bfd, or isis ipv6 primary-path-detect bfd command.
These commands are different as follows:
· The fast-reroute primary-path-detect bfd command enables BFD-powered primary link failure detection on all interfaces in an IPv4 or IPv6 IS-IS process.
· The isis primary-path-detect bfd and isis ipv6 primary-path-detect bfd commands take effect only on one IS-IS interface. To enable BFD-powered primary link failure detection on a single IS-IS interface, perform the following tasks:
a. Make sure the IS-IS process to which the IS-IS interface belongs is not enabled with BFD-powered primary link failure detection.
You can use the undo fast-reroute primary-path-detect bfd command to disable this feature for an IS-IS process.
b. Use the isis primary-path-detect bfd or isis ipv6 primary-path-detect bfd command to enable this feature on the IS-IS interface.
Examples
# Enable BFD control packet mode for IS-IS FRR and PIC in IS-IS process 1.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] address-family ipv4
[Sysname-isis-1-ipv4] fast-reroute primary-path-detect bfd ctrl
Related commands
fast-reroute primary-path-detect bfd
isis ipv6 primary-path-detect bfd
isis primary-path-detect bfd
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
Multiple PQ nodes might reach the source node of a specific protected link. You can use this command to specify a prefix list to filter PQ nodes.
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 (Flexible algorithm view)
Use fast-reroute tiebreaker to set the priority of an FRR backup path selection policy for a flexible algorithm.
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
Flexible algorithm 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.
You can configure both backup path selection policies in an address family view. IS-IS will calculate a backup path by using the policies in descending order of their priorities until a backup path is calculated. If IS-IS fails to calculate a backup path, it does not perform further backup path calculation.
If IS-IS fails to calculate a backup path by using the lowest-cost policy, it 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 for flexible algorithm 255 in IS-IS process 1.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] flex-algo 255
[Sysname-isis-1-flex-algo-255] fast-reroute tiebreaker node-protecting preference 100
fast-reroute tiebreaker (IS-IS IPv4 unicast address family view/IS-IS IPv6 unicast address family view)
Use fast-reroute tiebreaker to set the priority for an FRR backup path selection policy.
Use undo fast-reroute tiebreaker to restore the default.
Syntax
fast-reroute tiebreaker { lowest-cost | node-protecting | srlg-disjoint } preference preference [ level-1 | level-2 ]
undo fast-reroute tiebreaker { lowest-cost | node-protecting | srlg-disjoint } [ level-1 | level-2 ]
Default
The priority values of the node-protection, lowest-cost, and SRLG-disjoint backup path selection policies are 40, 20, and 10, 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.
srlg-disjoint: Sets a priority value for the SRLG-disjoint 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
IS-IS FRR uses specific policies for backup path calculation. This command defines the priority for the backup path selection policy. The higher the value, the higher the priority of the associated backup path selection policy. Changing the backup path selection policy priority can affect the backup path calculation result for IS-IS FRR. The backup paths can provide node protection or link protection for traffic, or provide both node protection and link protection.
IS-IS FRR supports the following backup path selection policies that are used to generate different topologies for backup path calculation:
· Node protection—IS-IS FRR performs backup path calculation after excluding the primary next hop node.
· Lowest cost—IS-IS FRR performs backup path calculation after excluding the direct primary link.
· SRLG disjoint—When one link in the SRLG fails, the other links in the SRLG might also fail. If you use a link in this SRLG as the backup link for the failed link, protection does not take effect. To avoid this issue, IS-IS FRR excludes the local links in the same SRLG as the direct primary link and then performs backup path calculation.
For IS-IS FRR, the SRLG disjoint policy depends on the node protection and lowest cost policies.
If multiple backup path selection policies exist in an IS-IS process, the policy with the highest priority is used to calculate the backup path. If the policy fails to calculate the backup path, another policy with higher priority is used. IS-IS performs backup path calculation by using the node protection and lowest cost policies as follows:
· If the node protection policy has higher priority and fails to calculate the backup path, IS-IS uses the lowest cost policy to calculate the backup path. If the lowest cost policy still fails to calculate the backup path, reliability cannot be ensured upon primary link failure.
· If the lowest cost policy has higher priority and fails to calculate the backup path, IS-IS does not perform further backup path calculation with the node protection policy. Reliability cannot be ensured upon primary link failure.
You can repeat this command to specify the priorities for the lowest cost, node protection, and SRLG disjoint policies, respectively.
If you execute this command multiple times for a backup path selection policy, the most recent configuration takes effect.
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
fast-reroute ti-lfa enable
Use fast-reroute ti-lfa enable to enable TI-LFA (Topology-Independent Loop-free Alternate) FRR for a flexible algorithm.
Use undo fast-refroute ti-lfa enable to disable TI-LFA FRR for a flexible algorithm.
Syntax
fast-reroute ti-lfa enable
undo fast-reroute ti-lfa enable
Default
TI-LFA FRR is enabled for the flexible algorithm.
Views
network-admin
Usage guidelines
TI-LFA FRR calculates backup paths based on the flexible algorithm topology and the FAD. This feature can reduce data loss caused by link or node failures. When a link or node fails, the traffic can be forwarded along the backup path.
This feature is available when the link cost style is wide, compatible, or wide-compatible.
Examples
# Enable TI-LFA FRR for flexible algorithm 255.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] flex-algo 255
[Sysname-isis-1-flex-algo-255] fast-reroute ti-lfa enable
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
In IS-IS IPv4 unicast address family view:
filter-policy { ipv4-acl-number | prefix-list prefix-list-name | route-policy route-policy-name } export [ bgp | direct | { isis | ospf | rip } process-id | static ]
undo filter-policy export [ bgp | direct | { isis | ospf | rip } process-id | static ]
In IS-IS IPv6 unicast address family view:
filter-policy { ipv6-acl-number | prefix-list prefix-list-name | route-policy route-policy-name } export [ bgp4+ | direct | { isisv6 | ospfv3 | ripng } process-id | static ]
undo filter-policy export [ bgp4+ | direct | { isisv6 | ospfv3 | ripng } process-id | static ]
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.
bgp: Filters redistributed BGP routes.
bgp4+: Filters redistributed IPv6 BGP routes.
direct: Filters redistributed direct routes.
isis: Filters redistributed IS-IS routes.
isisv6: Filters redistributed IPv6 IS-IS routes.
ospf: Filters redistributed OSPF routes.
ospfv3: Filters redistributed OSPFv3 routes.
rip: Filters redistributed RIP routes.
ripng: Filters redistributed RIPng routes.
process-id: Specifies a process by its ID in the range of 1 to 65535.
static: Filters redistributed static routes.
Usage guidelines
If you do not specify any parameters, this command filters all redistributed routes.
This command filters routes redistributed by the import-route command. Only routes that have not been filtered can be advertised.
When you specify an ACL, follow these guidelines:
· If the ACL does not exist or does not have any rules, IS-IS does not filter any redistributed routes.
· If a rule in the ACL is applied to a VPN instance, the rule will deny all redistributed routes.
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 or permit a route with the specified destination, use the rule [ rule-id ] { deny | permit } ip source sour-addr sour-wildcard command.
· To deny or 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 pass the filter can be added into the routing table.
When you specify an ACL, follow these guidelines:
· If the ACL does not exist or does not have any rules, IS-IS does not filter any received routes.
· If a rule in the ACL is applied to a VPN instance, the rule will deny all received routes.
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 or permit a route with the specified destination, use the rule [ rule-id ] { deny | permit } ip source sour-addr sour-wildcard command.
· To deny or 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
flex-algo (IS-IS view)
Use flex-algo to create a flexible algorithm and enter its view, or enter the view of an existing flexible algorithm.
Use undo flex-algo to delete a flexible algorithm.
Syntax
flex-algo flex-algo-id
undo flex-algo flex-algo-id
Default
No flexible algorithms exist.
Views
IS-IS view
Predefined user roles
network-admin
Parameters
flex-algo-id: Specifies a flexible algorithm ID. The value range for this argument is 128 to 255. You can create multiple flexible algorithms in an IS-IS process.
Usage guidelines
You can identify a path calculation algorithm by checking the algorithm field in an IS-IS SID. The value range for this field is 0 to 255.
· A value of 0 represents the SPF algorithm based on IGP metric.
· A value of 128 to 255 represents the flexible algorithm based on specific metric type and constraints.
A flexible algorithm consists of the following parts:
· Calculation type—Algorithm used for path calculation. In the current software version, only SPF algorithm is supported.
· Metric type—Type of metric used for the shortest path calculation. In the current software version, only IS-IS link cost is supported.
· Constraint—Link filter criteria for topology generation. You can use a set of constraints to exclude links with specific affinity attributes from or include them in the flexible algorithm topology.
A flexible algorithm generates its topology as follows:
· Excludes the nodes that does not participate the path calculation for that flexible algorithm.
· Excludes links according to the constraints.
· Excludes the links that do not meet the flexible algorithm requirement on metric type.
· In a flexible algorithm topology, all nodes calculate optimal paths based on the calculation type and metric type in the FAD.
This feature is available when the link cost style is wide, compatible, or wide-compatible.
Examples
# Create flexible algorithm 128 and enter its view.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] flex-algo 128
[Sysname-isis-1-flex-algo-128]
Related commands
cost-style
flex-algo (segment routing view)
Use flex-algo to create and enter SR flexible algorithm view. If the SR flexible algorithm view already exists, the command directly enters SR flexible algorithm view.
Use undo flex-algo to delete the SR flexible algorithm view and all configuration in the view.
Syntax
flex-algo
undo flex-algo
Default
The SR flexible algorithm view does not exist.
Views
Segment routing view
Predefined user roles
network-admin
Examples
# Create and enter SR flexible algorithm view.
<Sysname> system-view
[Sysname] segment-routing
[Sysname-segment-routing] flex-algo
[Sysname-sr-flex-algo]
Related commands
segment-routing (Segment Routing Command Reference)
flex-algo algorithm
Use flex-algo algorithm to associate an SRv6 locator to a flexible algorithm.
Use undo flex-algo algorithm to restore the default.
Syntax
flex-algo algorithm algo-id
undo flex-algo algorithm
Default
An SRv6 locator is associated to flexible algorithm 0. IS-IS uses the SPF algorithm to calculate optimal paths to the locator.
Views
SRv6 locator view
Predefined user roles
network-admin
Parameters
algo-id: Specifies a flexible algorithm by its ID. The value range for this argument is 128 to 255.
Usage guidelines
With SRv6 enabled, IS-IS advertises SRv6 locator TLVs in LSPs. You can identify the algorithm associated to the locator by checking the algorithm field in an SRv6 locator TLV. By default, IS-IS uses the SPF algorithm to calculate the shortest path to an SRv6 locator, and the value for the algorithm field is 0.
If you associate an SRv6 locator to a flexible algorithm, IS-IS uses the flexible algorithm to calculate the shortest path to the locator.
You must associate an SRv6 locator to a flexible algorithm that already exists, or IS-IS will not advertise the locator.
If you execute this command multiple times on an interface, the most recent configuration takes effect.
Examples
# Associate SRv6 locator abc to flexible algorithm 128.
<Sysname> system-view
[Sysname] segment-routing ipv6
[Sysname-segment-routing-ipv6] locator abc ipv6-prefix 500::1 40 static 4
[Sysname-segment-routing-ipv6-locator-abc] flex-algo algorithm 128
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 ensure successful GR timer configuration, follow these restrictions and guidelines when you configure 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 ensure successful GR timer configuration, follow these restrictions and guidelines when you configure 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 ensure successful GR timer configuration, follow these restrictions and guidelines when you configure 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 enable route redistribution.
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 ] | no-sid | 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 ] | no-sid | 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 ] | [ level-1 | level-1-2 | level-2 ] | route-policy route-policy-name | tag tag ] *
import-route { direct | static } [ [ cost cost-value | inherit-cost ] | [ 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 ] | [ level-1 | level-1-2 | level-2 ] | route-policy route-policy-name | tag tag ] *
undo import-route { bgp4+ | direct | { isisv6 | ospfv3 | ripng } [ process-id ] | 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.
bgp4+: Redistributes IPv6 BGP routes.
as-number: Specifies an AS by its number in the range of 1 to 4294967295. If you do not specify this argument, the command redistributes all IPv4 or IPv6 EBGP routes. As a best practice, specify an AS to prevent the system from redistributing excessive routes.
direct: Redistributes direct routes.
isis: Redistributes IS-IS routes.
isisv6: Redistributes IPv6 IS-IS routes.
ospf: Redistributes OSPF routes.
ospfv3: Redistributes OSPFv3 routes.
rip: Redistributes RIP routes.
ripng: Redistributes RIPng routes.
process-id: Specifies a process by its ID in the range of 1 to 65535. The default value is 1.
static: Redistributes static routes.
all-processes: Redistributes routes from all the processes of the IS-IS, OSPF, or RIP routing protocol.
allow-ibgp: Allows redistribution of IBGP routes. The import-route bgp or import-route bgp4+ command redistributes only EBGP routes if you do not specify the allow-ibgp keyword. To redistribute IBGP routes in addition to EBGP routes, specify the allow-ibgp keyword. Improper redistribution of IBGP routes might cause routing loops. When you use the allow-ibgp keyword, make sure you understand its impact on the network.
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: Uses 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.
no-sid: Redistributes routes without keeping their SR labels. If you do not specify this keyword, IS-IS redistributes routes keeping their SR labels.
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.
After you specify the cost keyword or the 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.
If you do not specify the cost keyword or the inherit-cost keyword, the cost of a redistributed route is 0.
When you execute the undo form of the command, per-process setting has higher priority than the all-processes setting. The undo import-route { isis | ospf | rip } all-processes command cannot remove the setting configured for a process by using the import-route { isis | ospf | rip } process-id command. To remove the setting for that process, you must specify the process ID in the undo form of the command.
Examples
# Redistribute static routes into IS-IS, and set the cost of 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
display ip routing-table protocol
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 } | no-sid | 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.
no-sid: Redistributes routes from Level-1 to Level-2 without keeping their SR labels. If you do not specify this keyword, this command redistributes routes from Level-1 to Level-2 keeping their SR labels.
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.
When you specify an IPv4 ACL, follow these guidelines:
· If the ACL does not exist or does not have any rules, IS-IS does not filter any routes advertised from Level-1 to Level-2.
· If a rule in the ACL is applied to a VPN instance, the rule will deny all routes advertised from Level-1 to Level-2.
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 } | no-sid | 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.
no-sid: Redistributes routes from Level-2 to Level-1 without keeping their SR labels. If you do not specify this keyword, this command redistributes routes from Level-2 to Level-1 keeping their SR labels.
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.
When you specify an IPv4 ACL, follow these guidelines:
· If the ACL does not exist or does not have any rules, IS-IS does not filter any routes advertised from Level-2 to Level-1.
· If a rule in the ACL is applied to a VPN instance, the rule will deny all routes advertised from Level-2 to Level-1.
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.
When you specify an IPv6 ACL, follow these guidelines:
· If the ACL does not exist or does not have any rules, IS-IS does not filter any routes advertised from Level-1 to Level-2.
· If a rule in the ACL is applied to a VPN instance, the rule will deny all routes advertised from Level-1 to Level-2.
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
IPv6 IS-IS 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 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.
When you specify an IPv6 ACL, follow these guidelines:
· If the ACL does not exist or does not have any rules, IS-IS does not filter any routes advertised from Level-2 to Level-1.
· If a rule in the ACL is applied to a VPN instance, the rule will deny all routes advertised from Level-2 to Level-1.
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
The maximum number of redistributed Level 1/Level 2 routes equals the maximum value supported by the device.
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. The value range for this argument is 1 to 20000000.
Examples
# Configure IS-IS process 1 to redistribute up to 1000 Level 1/Level 2 IPv4 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 affinity flex-algo
Use isis affinity flex-algo to assign affinity attributes to IS-IS links.
Use undo isis affinity flex-algo to restore the default.
Syntax
isis process-id affinity flex-algo { affinity-name }&<1-32>
undo isis process-id affinity flex-algo
Default
An IS-IS link has no affinity attributes.
Views
Interface view
Predefined user roles
network-admin
Parameters
process-id: Specifies a process by its ID in the range of 1 to 65535.
affinity-name&<1-32>: Specifies affinity attributes by their names. The affinity attribute name must be a case-sensitive string of 1 to 32 characters. &<1-32> indicates that you can specify a maximum of 32 affinity attribute names. The specified affinity attributes must already exist.
Usage guidelines
If you perform this task on an IS-IS interface, the links between the interface and its neighbors will carry the affinity attributes that you have specified.
In a flexible algorithm scenario, these links will be filtered for path calculation based on the link constraints in the FAD.
Examples
# Assign affinity attribute red to interface Ten-GigabitEthernet 0/0/6.
<Sysname> system-view
[Sysname] interface ten-gigabitethernet 0/0/6
[Sysname-Ten-GigabitEthernet 0/0/6] isis 1 affinity flex-algo red
Related commands
affinity-map
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 Ten-GigabitEthernet 0/0/6 not to check the authentication information in the received Level-1 hello packets.
<Sysname> system-view
[Sysname] interface ten-gigabitethernet 0/0/6
[Sysname-Ten-GigabitEthernet0/0/6] 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.
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. In simple authentication mode and GCA authentication mode, the plaintext form of the key is a case-sensitive string of 1 to 16 characters, and the encrypted form is a case-sensitive string of 33 to 53 characters. In MD5 authentication mode, the plaintext form of the key is a case-sensitive string of 1 to 255 characters, and the encrypted form is a case-sensitive string of 33 to 373 characters.
keychain: Specifies the keychain authentication mode.
keychain-name: Specifies a keychain by its name, a case-sensitive string of 1 to 63 characters.
level-1: Configures the key for Level-1.
level-2: Configures the key for Level-2.
ip: Checks IP-related fields in LSPs and SNPs.
osi: Checks OSI-related fields in LSPs and SNPs.
Usage guidelines
The key in the specified mode is inserted into all outbound hello packets and is used for authenticating inbound hello packets. Only if the authentication succeeds can the neighbor relationship be formed.
IS-IS keychain authentication supports the HMAC-MD5 and HMAC-SM3 authentication algorithms. If the HMAC-MD5 algorithm is used, the key ID can be any value in the range supported by the key-id argument. If the HMAC-SM3 algorithm is used, the key ID must be in the range of 0 to 65535.
When keychain authentication is used, IS-IS receives and sends packets as follows:
· Before IS-IS sends a hello 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 or HMAC-SM3 algorithm, the authentication fails and the packet does not contain the authentication information.
· After IS-IS receives a hello packet, it processes the packet as follows:
¡ If the authentication algorithm of the packet is HMAC-MD5, IS-IS 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.
¡ If the authentication algorithm of the packet is HMAC-SM3, IS-IS uses the key ID of the received packet to obtain the corresponding valid accept key from the keychain. Then, IS-IS uses the accept key to authenticate the packet. If IS-IS cannot find a valid accept key based on the key ID of the received packet or the packet fails the authentication, the packet is discarded.
The level-1 and level-2 keywords are configurable on an interface that has had IS-IS enabled with the isis enable command.
If you configure a key without specifying a level, the key applies to both Level-1 and Level-2.
For two routers to become neighbors, the authentication mode and key at both ends must be identical.
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 (including non-H3C 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.
In MD5 authentication mode, execute the undo isis authentication-mode command before version switch if the key lengths supported by the two versions are different.
Examples
# On Ten-GigabitEthernet 0/0/6, set the authentication mode to simple, and set the plaintext key to 123456.
<Sysname> system-view
[Sysname] interface ten-gigabitethernet 0/0/6
[Sysname-Ten-GigabitEthernet0/0/6] isis authentication-mode simple plain 123456
Related commands
area-authentication-mode
domain authentication-mode
isis authentication send-only
isis bfd adjust-cost
Use isis bfd adjust-cost to enable BFD session state-based interface cost adjustment on an IPv4 IS-IS interface.
Use undo isis bfd adjust-cost to restore the default.
Syntax
isis bfd adjust-cost { cost-offset | max }
undo isis bfd adjust-cost
Default
An IPv4 IS-IS interface inherits the configuration of the bfd all-interfaces adjust-cost command in IS-IS IPv4 unicast address family view.
Views
Interface view
Predefined user roles
network-admin
cost-offset: Specifies the interface cost adjustment value. The value range for this argument is 1 to 16777213. When the BFD session goes down, the interface cost is cost-offset plus the original interface cost, and cannot exceed 16777214.
max: Sets the interface cost to the maximum value (16777214) when the BFD session goes down.
IMPORTANT: For the isis bfd adjust-cost command to take effect on an IPv4 IS-IS interface, enable BFD on that interface first. |
After you enable BFD for IPv4 IS-IS link failure detection, IPv4 IS-IS neighbor relationship flapping will occur upon frequent BFD session state changes. The running of services (such as BGP) that rely on IPv4 IS-IS might be interrupted. To resolve this issue, enable IPv4 IS-IS to adjust the interface cost according to the BFD session state. IPv4 IS-IS will adjust the cost value for an interface as follows to ensure fast route convergence against link state changes:
· When the BFD session on the interface goes down, IPv4 IS-IS increases the cost value for the interface.
· When the BFD session on the interface comes up again, IPv4 IS-IS restores the cost value for the interface to the original value.
You can perform one of the following tasks to enable BFD session state-based interface cost adjustment for IPv4 IS-IS:
· Use the bfd all-interfaces adjust-cost command in IPv4 IS-IS unicast address family view. This task takes effect on all interfaces in the current IPv4 IS-IS process.
· Use the isis bfd adjust-cost command in interface view. This task takes effect only on the current IPv4 IS-IS interface.
For an IPv4 IS-IS interface, the isis bfd adjust-cost command takes precedence over the bfd all-interfaces adjust-cost command. The interface uses the configuration of the bfd all-interfaces adjust-cost command only when you do not execute the isis bfd adjust-cost command on that interface.
Examples
# Enable BFD session state-based interface cost adjustment on IPv4 IS-IS interface Ten-GigabitEthernet 0/0/6, and set the interface cost adjustment value to 100.
<Sysname> system-view
[Sysname] interface ten-gigabitethernet 0/0/6
[Sysname-Ten-GigabitEthernet0/0/6] isis enable 1
[Sysname-Ten-GigabitEthernet0/0/6] isis bfd enable
[Sysname-Ten-GigabitEthernet0/0/6] isis bfd adjust-cost 100
Related commands
bfd all-interfaces adjust-cost
display isis interface
isis bfd enable
isis bfd adjust-cost exclude
Use isis bfd adjust-cost exclude to suppress BFD session state-based interface cost adjustment on an IPv4 IS-IS interface.
Use undo isis bfd adjust-cost exclude to restore the default.
Syntax
isis bfd adjust-cost exclude
undo isis bfd adjust-cost exclude
Default
IPv4 IS-IS can adjust the cost value for an interface according to the BFD session state.
Views
Interface view
Predefined user roles
network-admin
Usage guidelines
The bfd all-interfaces adjust-cost command enables BFD session state-based interface cost adjustment on all interfaces in an IS-IS process. To disable this feature on an interface in that IS-IS process, use the isis bfd adjust-cost exclude command on the interface.
When you use the following commands together on the same IPv4 IS-IS interface, the command that is used at last takes effect:
· isis bfd adjust-cost exclude
· isis bfd adjust-cost
Examples
# Suppress BFD session state-based interface cost adjustment on IPv4 IS-IS interface Ten-GigabitEthernet 0/0/6.
<Sysname> system-view
[Sysname] interface ten-gigabitethernet 0/0/6
[Sysname-Ten-GigabitEthernet0/0/6] isis enable 1
[Sysname-Ten-GigabitEthernet0/0/6] isis bfd adjust-cost exclude
Related commands
bfd all-interfaces adjust-cost
isis bfd adjust-cost
isis bfd enable
Use isis bfd enable to enable BFD on an IPv4 IS-IS interface.
Use undo isis bfd enable to restore the default.
Syntax
isis bfd enable
undo isis bfd enable
Default
An IPv4 IS-IS interface inherits the configuration of the bfd all-interfaces enable command in IS-IS IPv4 unicast address family view.
Views
Interface view
Predefined user roles
network-admin
Usage guidelines
IPv4 IS-IS exchanges hello packets at specific intervals with its neighbors to detect neighbor state changes. If IPv4 IS-IS does not receive any hello packets from a neighbor within the advertised neighbor relationship hold time, it considers the neighbor down and recalculates the routes. The hold time is the hello multiplier multiplied by the hello interval and the default hold time is 30 seconds. This mechanism is not efficient at neighbor state change detection. Serious packet loss might occur when a neighbor goes down.
To resolve this issue, use this command to enable BFD. BFD provides a single mechanism to quickly detect and monitor the connectivity of links between IPv4 IS-IS neighbors, reducing route convergence time.
You can perform one of the following tasks to enable BFD for IPv4 IS-IS:
· Use the bfd all-interfaces enable command in IPv4 IS-IS unicast address family view. This task takes effect on all interfaces in the current IPv4 IS-IS process.
· Use the isis bfd enable command in interface view. This task takes effect only on the current IPv4 IS-IS interface.
For an IPv4 IS-IS interface, the isis bfd enable command takes precedence over the bfd all-interfaces enable command. The interface uses the configuration of the bfd all-interfaces enable command only when you do not execute the isis bfd enable command on that interface.
Examples
# Enable BFD on IPv4 IS-IS interface Ten-GigabitEthernet 0/0/6.
<Sysname> system-view
[Sysname] interface ten-gigabitethernet 0/0/6
[Sysname-Ten-GigabitEthernet0/0/6] isis enable
[Sysname-Ten-GigabitEthernet0/0/6] isis bfd enable
Related commands
bfd all-interfaces enable
isis bfd exclude
Use isis bfd exclude to suppress the BFD capacity of an IPv4 IS-IS interface.
Use undo isis bfd exclude to restore the default.
Syntax
undo isis bfd exclude
Default
The BFD capacity of an IPv4 IS-IS interface is not suppressed.
Views
Interface view
Predefined user roles
network-admin
Usage guidelines
The bfd all-interfaces enable command enables BFD on all interfaces in an IPv4 IS-IS process. To disable BFD on an interface in that IS-IS process, use the isis bfd exclude command on the interface.
When you use the following commands together on the same IPv4 IS-IS interface, the command that is used at last takes effect:
· isis bfd exclude
· isis bfd enable
Examples
# Suppress the BFD capacity of IPv4 IS-IS interface Ten-GigabitEthernet 0/0/6.
<Sysname> system-view
[Sysname] interface ten-gigabitethernet 0/0/6
[Sysname-Ten-GigabitEthernet0/0/6] isis enable
[Sysname-Ten-GigabitEthernet0/0/6] isis bfd exclude
Related commands
bfd all-interfaces enable
isis bfd enable
isis bfd session-restrict-adj
Use isis bfd session-restrict-adj to enable BFD session state-based control of adjacency establishment and maintenance on an IPv4 IS-IS interface.
Use undo isis bfd session-restrict-adj to restore the default.
Syntax
isis bfd session-restrict-adj
undo isis bfd session-restrict-adj
Default
An IPv4 IS-IS interface inherits the configuration of the bfd all-interfaces session-restrict-adj command in IS-IS IPv4 unicast address family view.
Views
Interface view
Predefined user roles
network-admin
Usage guidelines
IMPORTANT: For the isis bfd session-restrict-adj command to take effect on an IPv4 IS-IS interface, enable BFD on that interface first. |
When BFD detects a Layer 3 forwarding failure between two devices, the BFD session goes down, which causes the IPv4 IS-IS adjacency to go down. If Layer 2 forwarding is still available, the devices can exchange IS-IS packets and re-establish the adjacency, which might cause traffic loss.
To avoid the issue, execute this command on the BFD-enabled interfaces of the local and remote devices, enabling the interfaces to carry BFD-enabled TLVs in hello packets. After the BFD session goes down, the routers do not establish an adjacency if the exchanged BFD-enabled TLVs are identical.
If you configure this command for an existing adjacency, the BFD session state does not affect the adjacency relationship within the hold time. This mechanism avoids adjacency flappings during the BFD session establishment.
You can perform one of the following tasks to enable BFD session state-based control of IPv4 IS-IS adjacency establishment and maintenance:
· Use the bfd all-interfaces session-restrict-adj command in IPv4 IS-IS unicast address family view. This task takes effect on all interfaces in the current IPv4 IS-IS process.
· Use the isis bfd session-restrict-adj command in interface view. This task takes effect only on the current IPv4 IS-IS interface.
For an IPv4 IS-IS interface, the isis bfd session-restrict-adj command takes precedence over the bfd all-interfaces session-restrict-adj command. The interface uses the configuration of the bfd all-interfaces session-restrict-adj command only when you do not execute the isis bfd session-restrict-adj command on that interface.
Examples
# Enable BFD session state-based control of adjacency establishment and maintenance on IPv4 IS-IS interface Ten-GigabitEthernet 0/0/6.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] isis enable
[Sysname-GigabitEthernet1/0/1] isis bfd enable
[Sysname-GigabitEthernet1/0/1] isis bfd session-restrict-adj
Related commands
bfd all-interfaces session-restrict-adj
isis bfd enable
isis bfd session-restrict-adj exclude
Use isis bfd session-restrict-adj exclude to suppress BFD session state-based control of adjacency establishment and maintenance on an IPv4 IS-IS interface.
Use undo isis bfd session-restrict-adj exclude to restore the default.
Syntax
isis bfd session-restrict-adj exclude
undo isis bfd session-restrict-adj exclude
Default
BFD session state-based control of adjacency establishment and maintenance is not suppressed on an IPv4 IS-IS interface.
Views
Interface view
Predefined user roles
network-admin
Usage guidelines
The bfd all-interfaces session-restrict-adj command enables BFD session state-based control of adjacency establishment and maintenance on all interfaces in an IPv4 IS-IS process. To disable this feature on an interface in that IS-IS process, use the isis bfd session-restrict-adj exclude command on the interface.
The command that is used at last takes effect when you use the following commands together on the same IPv4 IS-IS interface:
· isis bfd session-restrict-adj exclude
· isis bfd session-restrict-adj
Examples
# Suppress BFD session state-based control of adjacency establishment and maintenance on IPv4 IS-IS interface Ten-GigabitEthernet 0/0/6.
<Sysname> system-view
[Sysname] interface ten-gigabitethernet 0/0/6
[Sysname-Ten-GigabitEthernet0/0/6] isis enable 1
[Sysname-Ten-GigabitEthernet0/0/6] isis bfd session-restrict-adj exclude
Related commands
bfd all-interfaces session-restrict-adj
isis bfd session-restrict-adj
isis bfd template
Use isis bfd template to apply a BFD template to an IPv4 IS-IS interface.
Use undo isis bfd template to restore the default.
Syntax
isis bfd template template-name
undo isis bfd template
Default
No BFD template is applied to an IPv4 IS-IS interface. The system uses the template specified by the bfd all-interfaces template command in IPv4 address family view.
Views
Interface view
Predefined user roles
network-admin
Parameters
template-name: Specifies the name of a BFD template, a case-sensitive string of 1 to 63 characters.
Usage guidelines
After you enable BFD for IS-IS and apply a BFD template, IS-IS notifies BFD of the following information when using BFD to detect the link to a neighbor:
· Destination address.
· Source address.
· Detection parameters defined in the BFD template.
BFD establishes a BFD session based on the information received. By editing detection parameters for the template, you can adjust the speed at which IS-IS detects link failures. For more information about BFD templates, see configuring BFD in High Availability Configuration Guide.
This command takes effect only when BFD is enabled for IS-IS and the specified BFD template exists.
You can use the bfd all-interfaces template or isis bfd template command to apply a BFD template. These commands are different as follows:
· The bfd all-interfaces template command takes effect on all interfaces in an IPv4 IS-IS process.
· The isis bfd template commands take effect on a specific IS-IS interface.
· The interface-specific template configuration takes precedence over the process-specific template configuration.
Examples
# Apply BFD template TEMP1 to IPv4 IS-IS interface Ten-GigabitEthernet 0/0/6.
<Sysname> system-view
[Sysname] interface ten-gigabitethernet 0/0/6
[Sysname-Ten-GigabitEthernet0/0/6] isis enable
[Sysname-Ten-GigabitEthernet0/0/6] isis bfd template TEMP1
Related commands
bfd all-interfaces enable
bfd all-interfaces template
bfd template
isis bfd enable
isis circuit-level
Use isis circuit-level to set the circuit level for the interface.
Use undo isis circuit-level to restore the default.
Syntax
isis circuit-level [ level-1 | level-1-2 | level-2 ]
undo isis circuit-level
Default
An interface can establish either the Level-1 or Level-2 adjacency.
Views
Interface view
Predefined user roles
network-admin
Parameters
level-1: Sets the circuit level to Level-1.
level-1-2: Sets the circuit level to Level-1-2.
level-2: Sets the circuit level to Level-2.
Usage guidelines
For a Level-1 (Level-2) router, the circuit level can only be Level-1 (Level-2). For a Level-1-2 router, you must specify a circuit level for a specific interface to form only the specified level neighbor relationship.
Examples
# Ten-GigabitEthernet 0/0/6 is connected to a non-backbone router in the same area. Set the circuit level of Ethernet 1/1 to Level-1 to prevent sending and receiving Level-2 Hello packets.
<Sysname> system-view
[Sysname] interface ten-gigabitethernet 0/0/6
[Sysname-Ten-GigabitEthernet0/0/6] isis enable
[Sysname-Ten-GigabitEthernet0/0/6] isis circuit-level level-1
Related commands
is-level
isis circuit-type p2p
Use isis circuit-type p2p to set the network type of an interface to P2P.
Use undo isis circuit-type to restore the default.
Syntax
isis [ process-id process-id ] circuit-type p2p
undo isis [ process-id process-id ] circuit-type
Default
The network type of an interface varies by physical media. (The network type of a VLAN interface is broadcast.)
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.
Usage guidelines
Use this command only on a broadcast network with two attached routers.
Interfaces with different network types operate differently. For example, broadcast interfaces must elect a DIS and flood CSNP packets to synchronize the LSDBs. P2P interfaces do not need to elect a DIS, and use a different LSDB synchronization mechanism.
If only two routers exist on a broadcast network, set the network type of attached interfaces to P2P to avoid DIS election and CSNP flooding. This saves network bandwidth and speeds up network convergence.
Examples
# Set the network type of Ten-GigabitEthernet 0/0/6 to P2P.
<Sysname> system-view
[Sysname] interface ten-gigabitethernet 0/0/6
[Sysname-Ten-GigabitEthernet0/0/6] isis enable
[Sysname-Ten-GigabitEthernet0/0/6] isis circuit-type p2p
isis cost
Use isis cost to set the IS-IS cost for an interface.
Use undo isis cost to remove the configuration.
Syntax
isis [ process-id process-id ] cost cost-value [ level-1 | level-2 ]
undo isis [ process-id process-id ] cost [ level-1 | level-2 ]
Default
No IS-IS cost is configured for an interface.
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.
cost-value: Specifies an IS-IS cost in the range of 1 to 16777215.
level-1: Applies the cost to Level-1.
level-2: Applies the cost to Level-2.
Usage guidelines
If neither level-1 nor level-2 is included, the cost applies to both level-1 and level-2.
Examples
# Set the Level-2 IS-IS cost to 5 for Ten-GigabitEthernet 0/0/6.
<Sysname> system-view
[Sysname] interface ten-gigabitethernet 0/0/6
[Sysname-Ten-GigabitEthernet0/0/6] isis cost 5 level-2
Related commands
auto-cost enable
bandwidth-reference
isis dis-name
Use isis dis-name to configure a name for a DIS to represent the pseudo node on a broadcast network.
Use undo isis dis-name to restore the default.
Syntax
isis dis-name symbolic-name
undo isis dis-name
Default
No name is configured for the DIS.
Views
Interface view
Predefined user roles
network-admin
Parameters
symbolic-name: Specifies a DIS name, a case-sensitive string of 1 to 64 characters.
Usage guidelines
This command takes effect only on routers that have dynamic system ID to host name mapping enabled. This command does not take effect on Point-to-Point interfaces.
Examples
# Set the DIS name to LOCALAREA.
<Sysname> system-view
[Sysname] interface ten-gigabitethernet 0/0/6
[Sysname-Ten-GigabitEthernet0/0/6] isis dis-name LOCALAREA
Related commands
display isis name-table
is-name
isis dis-priority
Use isis dis-priority to specify a DIS priority at a specified level for an interface.
Use undo isis dis-priority to remove the configuration.
Syntax
isis dis-priority priority [ level-1 | level-2 ]
undo isis dis-priority [ level-1 | level-2 ]
Default
The priority of Level-1 and Level-2 is 64.
Views
Interface view
Predefined user roles
network-admin
Parameters
priority: Specifies a DIS priority in the range of 0 to 127.
level-1: Applies the DIS priority to Level-1.
level-2: Applies the DIS priority to Level-2.
On an IS-IS broadcast network, a router must be elected as the DIS at each routing level. Specify a DIS priority at a level for an interface. The greater the interface's priority is, the more likelihood it becomes the DIS. If multiple routers in the broadcast network have the same highest DIS priority, the router with the highest Subnetwork Point of Attachment (SNPA) address becomes the DIS. SNPA addresses are MAC addresses on a broadcast network.
IS-IS has no backup DIS. The router with a priority of 0 can also participate in DIS election.
If neither level-1 nor level-2 is specified, the DIS priority applies to both Level-1 and Level-2.
Examples
# Set the Level-2 DIS priority to 127 for Ten-GigabitEthernet 0/0/6.
<Sysname> system-view
[Sysname] interface ten-gigabitethernet 0/0/6
[Sysname-Ten-GigabitEthernet0/0/6] isis dis-priority 127 level-2
isis enable
Use isis enable to enable an IS-IS process on an interface.
Use undo isis enable to disable IS-IS.
Syntax
isis enable [ process-id ]
undo isis enable
Default
No IS-IS process is enabled on an interface.
Views
Interface 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.
Examples
# Enable IS-IS process 1 globally and enable it on the Ten-GigabitEthernet 0/0/6.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] network-entity 10.0001.1010.1020.1030.00
[Sysname-isis-1] quit
[Sysname] interface ten-gigabitethernet 0/0/6
[Sysname-Ten-GigabitEthernet0/0/6] isis enable 1
Related commands
isis
isis fast-reroute lfa-backup exclude
Use isis fast-reroute lfa-backup exclude to disable LFA calculation on an interface.
Use undo isis fast-reroute lfa-backup exclude to restore the default.
Syntax
isis fast-reroute lfa-backup exclude [ level-1 | level-2 ]
undo isis fast-reroute lfa-backup exclude [ level-1 | level-2 ]
Default
LFA calculation is enabled on an interface, and the interface can be elected as a backup interface.
Views
Interface view
Predefined user roles
network-admin
Parameters
level-1: Disables LFA calculation on the interface whose circuit level is Level-1.
level-2: Disables LFA calculation on the interface whose circuit level is Level-2.
Usage guidelines
When this command is configured, the interface does not participate in the LFA calculation, and cannot be elected as a backup interface.
If you do not specify the level-1 or level-2 keyword, LFA calculation is disabled on the interface regardless of its circuit level.
Examples
# Disable LFA calculation on Ten-GigabitEthernet 0/0/6.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] network-entity 10.0001.1010.1020.1030.00
[Sysname-isis-1] quit
[Sysname] interface ten-gigabitethernet 0/0/6
[Sysname-Ten-GigabitEthernet0/0/6] isis enable 1
[Sysname-Ten-GigabitEthernet0/0/6] isis fast-reroute lfa-backup exclude
Related commands
fast-reroute
isis fast-reroute remote-lfa disable
Use isis fast-reroute remote-lfa disable to disable remote LFA calculation on an interface.
Use undo isis fast-reroute remote-lfa disable to enable remote LFA calculation on an interface.
Syntax
isis fast-reroute remote-lfa disable [ level-1 | level-2 ]
undo isis fast-reroute remote-lfa disable [ level-1 | level-2 ]
Default
Remote LFA calculation is enabled on an interface.
Views
Interface 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
Use this command to disable remote LFA calculation on the interface to prevent it from participating in the calculation.
If you specify neither the level-1 nor the level-2 keyword, this command applies to all IS-IS areas.
Examples
# Disable remote LFA calculation on interface Ten-GigabitEthernet 0/0/6.
<Sysname> system-view
[Sysname] interface ten-gigabitethernet 0/0/6
[Sysname-Ten-GigabitEthernet0/0/6] isis enable 1
[Sysname-Ten-GigabitEthernet0/0/6] isis fast-reroute remote-lfa disable
# Disable remote LFA calculation on interface VLAN-interface 10.
<Sysname> system-view
[Sysname] interface vlan-interface 10
[Sysname-Vlan-interface10] isis enable 1
[Sysname-Vlan-interface10] isis fast-reroute remote-lfa disable
isis ipv6 bfd adjust-cost
Use isis ipv6 bfd adjust-cost to enable BFD session state-based interface cost adjustment on an IPv6 IS-IS interface.
Use undo isis ipv6 bfd adjust-cost to restore the default.
Syntax
isis ipv6 bfd adjust-cost { cost-offset | max }
undo isis ipv6 bfd adjust-cost
Default
An IPv6 IS-IS interface inherits the configuration of the bfd all-interfaces adjust-cost command in IS-IS IPv6 unicast address family view.
Views
Interface view
Predefined user roles
network-admin
Parameters
cost-offset: Specifies the interface cost adjustment value. The value range for this argument is 1 to 16777213. When the BFD session goes down, the interface cost is cost-offset plus the original interface cost, and cannot exceed 16777214.
max: Sets the interface cost to the maximum value (16777214) when the BFD session goes down.
Usage guidelines
IMPORTANT: For the isis ipv6 bfd adjust-cost command to take effect on an IPv6 IS-IS interface, enable BFD on that interface first. |
After you enable BFD for IPv6 IS-IS link failure detection, IPv6 IS-IS neighbor relationship flapping will occur upon frequent BFD session state changes. The running of services (such as BGP) that rely on IPv6 IS-IS might be interrupted. To resolve this issue, enable IPv6 IS-IS to adjust the interface cost according to the BFD session state. IPv6 IS-IS will adjust the cost value for an interface as follows to ensure fast route convergence against link state changes:
· When the BFD session on the interface goes down, IPv6 IS-IS increases the cost value for the interface.
· When the BFD session on the interface comes up again, IPv6 IS-IS restores the cost value for the interface to the original value.
You can perform one of the following tasks to enable IPv6 IS-IS to adjust the interface cost according to the BFD session state:
· Use the bfd all-interfaces adjust-cost command in IPv6 IS-IS unicast address family view. This task takes effect on all interfaces in the current IPv6 IS-IS process.
· Use the isis ipv6 bfd adjust-cost command in interface view. This task takes effect only on the current IPv6 IS-IS interface.
For an IPv6 IS-IS interface, the isis ipv6 bfd adjust-cost command takes precedence over the bfd all-interfaces adjust-cost command. The interface uses the configuration of the bfd all-interfaces adjust-cost command only when you do not execute the isis ipv6 bfd adjust-cost command on that interface.
Examples
# Enable BFD session state-based interface cost adjustment on IPv6 IS-IS interface Ten-GigabitEthernet 0/0/6, and set the interface cost adjustment value to 200.
<Sysname> system-view
[Sysname] interface ten-gigabitethernet 0/0/6
[Sysname-Ten-GigabitEthernet0/0/6] isis ipv6 enable 1
[Sysname-Ten-GigabitEthernet0/0/6] isis ipv6 bfd enable
[Sysname-Ten-GigabitEthernet0/0/6] isis ipv6 bfd adjust-cost 200
Related commands
bfd all-interfaces adjust-cost
display isis interface
isis ipv6 bfd enable
isis ipv6 bfd adjust-cost exclude
Use isis ipv6 bfd adjust-cost exclude to suppress BFD session state-based interface cost adjustment on an IPv6 IS-IS interface.
Use undo isis ipv6 bfd adjust-cost exclude to restore the default.
Syntax
isis ipv6 bfd adjust-cost exclude
undo isis ipv6 bfd adjust-cost exclude
Default
IPv6 IS-IS can adjust the cost value for an interface according to the BFD session state.
Views
Interface view
Predefined user roles
network-admin
Usage guidelines
The bfd all-interfaces adjust-cost command enables BFD session state-based interface cost adjustment on all interfaces in an IPv6 IS-IS process. To disable this feature on an interface in that IS-IS process, use the isis ipv6 bfd adjust-cost exclude command on the interface.
When you use the following commands together on the same IPv6 IS-IS interface, the command that is used at last takes effect:
· isis ipv6 bfd adjust-cost exclude
· isis ipv6 bfd adjust-cost
Examples
# Suppress BFD session state-based interface cost adjustment on IPv6 IS-IS interface Ten-GigabitEthernet 0/0/6.
<Sysname> system-view
[Sysname] interface ten-gigabitethernet 0/0/6
[Sysname-Ten-GigabitEthernet0/0/6] isis ipv6 enable 1
[Sysname-Ten-GigabitEthernet0/0/6] isis ipv6 bfd adjust-cost exclude
Related commands
bfd all-interfaces adjust-cost
isis ipv6 bfd adjust-cost
isis ipv6 bfd enable
Use isis ipv6 bfd enable to enable BFD on IPv6 IS-IS interface.
Use undo isis ipv6 bfd enable to restore the default.
Syntax
isis ipv6 bfd enable
undo isis ipv6 bfd enable
Default
An IPv4 IS-IS interface inherits the configuration of the bfd all-interfaces enable command in IS-IS IPv6 unicast address family view.
Views
Interface view
Predefined user roles
network-admin
Usage guidelines
IPv6 IS-IS exchanges hello packets at specific intervals with its neighbors to detect neighbor state changes. If IPv6 IS-IS does not receive any hello packets from a neighbor within the advertised neighbor relationship hold time, it considers the neighbor down and recalculates the routes. The hold time is the hello multiplier multiplied by the hello interval and the default hold time is 30 seconds. This mechanism is not efficient at neighbor state change detection. Serious packet loss might occur when a neighbor goes down.
To resolve this issue, use this command to enable BFD on the IPv6 IS-IS interface. BFD provides a single mechanism to quickly detect and monitor the connectivity of links between IPv6 IS-IS neighbors, reducing route convergence time.
You can perform one of the following tasks to enable BFD for IPv6 IS-IS:
· Use the bfd all-interfaces enable command in IPv6 IS-IS unicast address family view. This task takes effect on all interfaces in the current IPv6 IS-IS process.
· Use the isis ipv6 bfd enable command in interface view. This task takes effect only on the current IPv6 IS-IS interface.
For an IPv6 IS-IS interface, the isis ipv6 bfd enable command takes precedence over the bfd all-interfaces enable command. The interface uses the configuration of the bfd all-interfaces enable command only when you do not execute the isis ipv6 bfd enable command on that interface.
Examples
# Enable BFD on IPv6 IS-IS interface Ten-GigabitEthernet0/0/6.
<Sysname> system-view
[Sysname] interface ten-gigabitethernet 0/0/6
[Sysname-Ten-GigabitEthernet0/0/6] isis ipv6 bfd enable
Related commands
bfd all-interfaces enable
isis ipv6 bfd exclude
Use isis ipv6 bfd exclude to suppress the BFD capacity of an IPv6 IS-IS interface.
Use undo isis ipv6 bfd exclude to restore the default.
Syntax
isis ipv6 bfd exclude
undo isis ipv6 bfd exclude
Default
The BFD capacity of an IPv6 IS-IS interface is not suppressed.
Views
Interface view
Predefined user roles
network-admin
Usage guidelines
The bfd all-interfaces enable command enables BFD on all interfaces in an IPv6 IS-IS process. To disable BFD on an interface in that IS-IS process, use the isis ipv6 bfd exclude command on the interface.
When you use the following commands together on the same IPv6 IS-IS interface, the command that is used at last takes effect:
· isis ipv6 bfd exclude
· isis ipv6 bfd enable
Examples
# Suppress the BFD capacity of IPv6 IS-IS interface Ten-GigabitEthernet 0/0/6.
<Sysname> system-view
[Sysname] interface ten-gigabitethernet 0/0/6
[Sysname-Ten-GigabitEthernet0/0/6] isis ipv6 enable
[Sysname-Ten-GigabitEthernet0/0/6] isis ipv6 bfd exclude
Related commands
bfd all-interfaces enable
isis ipv6 bfd enable
isis ipv6 bfd session-restrict-adj
Use isis ipv6 bfd session-restrict-adj to enable BFD session state-based control of adjacency establishment and maintenance on an IPv6 IS-IS interface.
Use undo isis ipv6 bfd session-restrict-adj to restore the default.
Syntax
isis ipv6 bfd session-restrict-adj
undo isis ipv6 bfd session-restrict-adj
Default
An IPv6 IS-IS interface inherits the configuration of the bfd all-interfaces session-restrict-adj command in IS-IS IPv6 unicast address family view.
Views
Interface view
Predefined user roles
network-admin
Usage guidelines
IMPORTANT: For the isis ipv6 bfd session-restrict-adj command to take effect on an IPv6 IS-IS interface, enable BFD on that interface first. |
When BFD detects a Layer 3 forwarding failure between two devices, the BFD session goes down, which causes the IPv6 IS-IS adjacency to go down. If Layer 2 forwarding is still available, the devices can exchange IS-IS packets and re-establish the adjacency, which might cause traffic loss.
To avoid the issue, execute this command on the BFD-enabled interfaces of the local and remote devices, enabling the interfaces to carry BFD-enabled TLVs in hello packets. After the BFD session goes down, the routers do not establish an adjacency if the exchanged BFD-enabled TLVs are identical.
If you configure this command for an existing adjacency, the BFD session state does not affect the adjacency relationship within the hold time. This mechanism avoids adjacency flappings during the BFD session establishment.
You can perform one of the following tasks to enable BFD session state-based control of IPv6 IS-IS adjacency establishment and maintenance:
· Use the bfd all-interfaces session-restrict-adj command in IPv6 IS-IS unicast address family view. This task takes effect on all interfaces in the current IPv6 IS-IS process.
· Use the isis ipv6 bfd session-restrict-adj command in interface view. This task takes effect only on the current IPv6 IS-IS interface.
For an IPv6 IS-IS interface, the isis ipv6 bfd session-restrict-adj command takes precedence over the bfd all-interfaces session-restrict-adj command. The interface uses the configuration of the bfd all-interfaces session-restrict-adj command only when you do not execute the isis ipv6 bfd session-restrict-adj command on that interface.
Examples
# Enable BFD session state-based control of adjacency establishment and maintenance on IPv6 IS-IS interface Ten-GigabitEthernet 0/0/6.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] isis ipv6 enable
[Sysname-GigabitEthernet1/0/1] isis ipv6 bfd enable
[Sysname-GigabitEthernet1/0/1] isis ipv6 bfd session-restrict-adj
Related commands
bfd all-interfaces session-restrict-adj
isis ipv6 bfd enable
isis ipv6 bfd session-restrict-adj exclude
Use isis ipv6 bfd session-restrict-adj exclude to suppress BFD session state-based control of adjacency establishment and maintenance on an IPv6 IS-IS interface.
Use undo isis ipv6 bfd session-restrict-adj exclude to restore the default.
Syntax
isis ipv6 bfd session-restrict-adj exclude
undo isis ipv6 bfd session-restrict-adj exclude
Default
BFD session state-based control of adjacency establishment and maintenance is not suppressed on an IPv6 IS-IS interface.
Views
Interface view
Predefined user roles
network-admin
Usage guidelines
The bfd all-interfaces session-restrict-adj command enables BFD session state-based control of adjacency establishment and maintenance on all interfaces in an IPv6 IS-IS process. To disable this feature on an interface in that IS-IS process, use the isis ipv6 bfd session-restrict-adj exclude command on the interface.
When you use the following commands together on the same IPv6 IS-IS interface, the command that is used at last takes effect:
· isis ipv6 bfd session-restrict-adj exclude
· isis ipv6 bfd session-restrict-adj
Examples
# Suppress BFD session state-based control of adjacency establishment and maintenance on IPv6 IS-IS interface Ten-GigabitEthernet 0/0/6.
<Sysname> system-view
[Sysname] interface ten-gigabitethernet 0/0/6
[Sysname-Ten-GigabitEthernet0/0/6] isis ipv6 enable 1
[Sysname-Ten-GigabitEthernet0/0/6] isis ipv6 bfd session-restrict-adj exclude
Related commands
bfd all-interfaces session-restrict-adj
isis ipv6 bfd session-restrict-adj
isis ipv6 bfd template
Use isis ipv6 bfd template to apply a BFD template to an IPv6 IS-IS interface.
Use undo isis ipv6 bfd template to restore the default.
Syntax
isis ipv6 bfd template template-name
undo isis ipv6 bfd template
Default
No BFD template is applied to an IPv6 IS-IS interface. The system uses the template specified by the bfd all-interfaces template command in IPv6 address family view.
Views
Interface view
Predefined user roles
network-admin
Parameters
template-name: Specifies the name of a BFD template, a case-sensitive string of 1 to 63 characters.
Usage guidelines
After you enable BFD for IS-IS and apply a BFD template, IS-IS notifies BFD of the following information when using BFD to detect the link to a neighbor:
· Destination address.
· Source address.
· Detection parameters defined in the BFD template.
BFD establishes a BFD session based on the information received. By editing detection parameters for the template, you can adjust the speed at which IS-IS detects link failures. For more information about BFD templates, see configuring BFD in High Availability Configuration Guide.
This command takes effect only when BFD is enabled for IS-IS and the specified BFD template exists.
You can use the bfd all-interfaces template or isis ipv6 bfd template command to apply a BFD template. These commands are different as follows:
· The bfd all-interfaces template command takes effect on all interfaces in an IPv6 IS-IS process.
· The isis ipv6 bfd template commands take effect on a specific IS-IS interface.
· The interface-specific template configuration takes precedence over the process-specific template configuration.
Examples
# Apply BFD template TEMP1 to IPv6 IS-IS interface Ten-GigabitEthernet 0/0/6.
<Sysname> system-view
[Sysname] interface ten-gigabitethernet 0/0/6
[Sysname-Ten-GigabitEthernet0/0/6] isis ipv6 enable
[Sysname-Ten-GigabitEthernet0/0/6] isis ipv6 bfd template TEMP1
Related commands
bfd all-interfaces enable
bfd all-interfaces template
bfd template
isis bfd enable
isis ipv6 cost
Use isis ipv6 cost to set the IPv6 IS-IS cost for an interface.
Use undo isis ipv6 cost to remove the configuration.
Syntax
isis [ process-id process-id ] ipv6 cost cost-value [ level-1 | level-2 ]
undo isis [ process-id process-id ] ipv6 cost [ level-1 | level-2 ]
Default
No IPv6 IS-IS cost is configured for an interface.
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.
cost-value: Specifies an IPv6 IS-IS cost in the range of 1 to 16777215.
level-1: Applies the cost to Level-1 routes.
level-2: Applies the cost to Level-2 routes.
Usage guidelines
This command applies to interfaces that are enabled with IPv6 IS-IS.
This command takes effect only when the standard MTR mode is enabled.
Examples
# Set the IPv6 IS-IS cost to 10 for Ten-GigabitEthernet0/0/6.
<Sysname> system-view
[Sysname] isis 100
[Sysname-isis-100] address-family ipv6 unicast
[Sysname-isis-100-ipv6] quit
[Sysname-isis-100] quit
[Sysname] interface ten-gigabitethernet 0/0/6
[Sysname-Ten-GigabitEthernet0/0/6] isis ipv6 enable 100
[Sysname-Ten-GigabitEthernet0/0/6] isis ipv6 cost 10
isis ipv6 enable
Use isis ipv6 enable to enable IPv6 for IS-IS on an interface.
Use undo isis ipv6 enable to disable IPv6 for IS-IS on an interface.
Syntax
isis ipv6 enable [ process-id ]
undo isis ipv6 enable
Default
IPv6 is disabled for IS-IS on an interface.
Views
Interface 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.
Examples
# Enable IPv6 for IS-IS on Ten-GigabitEthernet0/0/6.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] network-entity 10.0001.1010.1020.1030.00
[Sysname-isis-1] address-family ipv6 unicast
[Sysname-isis-1-ipv6] quit
[Sysname-isis-1] quit
[Sysname] interface ten-gigabitethernet 0/0/6
[Sysname-Ten-GigabitEthernet0/0/6] ipv6 address 2002::1/64
[Sysname-Ten-GigabitEthernet0/0/6] isis ipv6 enable 1
isis ipv6 fast-reroute lfa-backup exclude
Use isis ipv6 fast-reroute lfa-backup exclude to disable LFA calculation on an interface.
Use undo isis ipv6 fast-reroute lfa-backup exclude to restore the default.
Syntax
isis ipv6 fast-reroute lfa-backup exclude [ level-1 | level-2 ]
undo isis ipv6 fast-reroute lfa-backup exclude [ level-1 | level-2 ]
Default
LFA calculation is enabled on an interface.
Views
Interface view
Predefined user roles
network-admin
Parameters
level-1: Disables LFA calculation on the interface whose circuit level is Level-1.
level-2: Disables LFA calculation on the interface whose circuit level is Level-2.
Usage guidelines
If you do not specify the level-1 or level-2 keyword, LFA calculation is disabled on the interface regardless of its circuit level.
Examples
# Disable LFA calculation on Ten-GigabitEthernet0/0/6.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] network-entity 10.0001.1010.1020.1030.00
[Sysname-isis-1] quit
[Sysname] interface ten-gigabitethernet 0/0/6
[Sysname-Ten-GigabitEthernet0/0/6] isis ipv6 enable 1
[Sysname-Ten-GigabitEthernet0/0/6] isis ipv6 fast-reroute lfa-backup exclude
Related commands
fast-reroute
isis ipv6 prefix-suppression
Use isis ipv6 prefix-suppression to enable prefix suppression on an interface.
Use undo isis ipv6 prefix-suppression to disable prefix suppression on an interface.
Syntax
isis ipv6 prefix-suppression
undo isis ipv6 prefix-suppression
Default
Prefix suppression is disabled on an interface.
Views
Interface view
Predefined user roles
network-admin
Usage guidelines
By default, IS-IS interfaces advertise their IPv6 prefixes in LSPs. Use this command to disable an interface from advertising its IPv6 prefix in LSPs. This enhances network security by preventing IP routing to the internal nodes and speeds up network convergence.
Examples
# Enable prefix suppression on Ten-GigabitEthernet0/0/6.
<Sysname> system-view
[Sysname] interface ten-gigabitethernet 0/0/6
[Sysname-Ten-GigabitEthernet0/0/6] isis ipv6 prefix-suppression
isis ipv6 primary-path-detect bfd
Use isis ipv6 primary-path-detect bfd to enable BFD-powered primary link failure detection on an IPv6 IS-IS interface.
Use undo isis ipv6 primary-path-detect bfd to restore the default.
Syntax
isis ipv6 primary-path-detect bfd { ctrl | echo }
undo isis ipv6 primary-path-detect bfd
Default
An IPv6 IS-IS interface inherits the configuration of the fast-reroute primary-path-detect bfd command in IS-IS IPv6 unicast address family view.
Views
Interface view
Predefined user roles
network-admin
Parameters
ctrl: Enables BFD control packet mode.
echo: Enables BFD echo packet mode.
Usage guidelines
This command enables IPv6 IS-IS FRR and PIC to use BFD to detect primary link failures. BFD can detect and report a primary link failure to IPv6 IS-IS for a primary-backup path switchover. This can shorten the duration of service interruption.
For an interface to run the BFD session in echo packet mode correctly, make sure the interface has an IPv6 global unicast address. For more information about IPv6 global unicast addresses, see IPv6 basics configuration in Layer 3—IP Services Configuration Guide.
You can perform one of the following tasks to enable BFD-powered primary link failure detection for IPv6 IS-IS FRR and PIC:
· Use the fast-reroute primary-path-detect bfd command in IPv6 IS-IS unicast address family view. This task takes effect on all interfaces in the current IPv6 IS-IS process.
· Use the isis ipv6 primary-path-detect bfd command in interface view. This task takes effect only on the current IPv6 IS-IS interface.
For an IPv6 IS-IS interface, the isis ipv6 primary-path-detect bfd command takes precedence over the fast-reroute primary-path-detect bfd command. The interface uses the configuration of the fast-reroute primary-path-detect bfd command only when you do not execute the isis ipv6 primary-path-detect bfd command on that interface.
Examples
# Enable BFD control packet mode for IPv6 IS-IS FRR on Ten-GigabitEthernet0/0/6.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] address-family ipv6
[Sysname-isis-1-ipv6] fast-reroute lfa
[Sysname-isis-1-ipv6] quit
[Sysname-isis-1] quit
[Sysname] interface ten-gigabitethernet 0/0/6
[Sysname-Ten-GigabitEthernet0/0/6] isis ipv6 primary-path-detect bfd ctrl
# Enable BFD echo packet mode for IPv6 IS-IS PIC on Ten-GigabitEthernet0/0/7.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] pic additional-path-always
[Sysname-isis-1] quit
[Sysname] bfd echo-source-ipv6 1::1
[Sysname] interface ten-gigabitethernet 0/0/7
[Sysname-Ten-GigabitEthernet0/0/7] isis ipv6 primary-path-detect bfd echo
Related commands
fast-reroute primary-path-detect bfd
isis ipv6 primary-path-detect bfd exclude
Use isis ipv6 primary-path-detect bfd exclude to suppress BFD-powered primary link failure detection on an IPv6 IS-IS interface.
Use undo isis ipv6 primary-path-detect bfd exclude to restore the default.
Syntax
isis ipv6 primary-path-detect bfd exclude
undo isis ipv6 primary-path-detect bfd exclude
Default
BFD-powered primary link failure detection is not suppressed on an IPv6 IS-IS interface.
Views
Interface view
Predefined user roles
network-admin
Usage guidelines
The fast-reroute primary-path-detect bfd command enables BFD-powered primary link failure detection on all interfaces in an IPv6 IS-IS process. To disable this feature on an interface in that IS-IS process, use the isis ipv6 primary-path-detect bfd exclude command on the interface.
When you use the following commands together on the same IPv6 IS-IS interface, the command that is used at last takes effect:
· isis ipv6 primary-path-detect bfd exclude
· isis ipv6 primary-path-detect bfd
Examples
# Suppress BFD-powered primary link failure detection on IPv6 IS-IS interface Ten-GigabitEthernet 0/0/6.
<Sysname> system-view
[Sysname] interface ten-gigabitethernet 0/0/6
[Sysname-Ten-GigabitEthernet0/0/6] isis ipv6 enable 1
[Sysname-Ten-GigabitEthernet0/0/6] isis ipv6 primary-path-detect bfd exclude
Related commands
fast-reroute primary-path-detect bfd
isis ipv6 primary-path-detect bfd
isis ipv6 tag
Use isis ipv6 tag to configure the administrative tag value on an interface.
Use undo isis ipv6 tag to restore the default.
Syntax
isis ipv6 tag tag
undo isis ipv6 tag
Default
No administrative tag value is configured on an interface.
Views
Interface view
Predefined user roles
network-admin
Parameters
tag: Specifies a tag value in the range of 1 to 4294967295.
Usage guidelines
To facilitate route filtering and management, use this command to configure the administrative tag value on an IS-IS interface. For example, after setting different administrative tag values for direct routes and non-direct routes in Level-2 area, you can then configure IS-IS to import only non-direct routes from Level-2 area to Level-1 area.
After you specify an administrative tag value, IS-IS always adds the specified tag value to the IPv6 prefix information in LSPs, regardless of the link cost style.
Examples
# Set the administrative tag value on Ten-GigabitEthernet0/0/6.
<Sysname> system-view
[Sysname] interface ten-gigabitethernet 0/0/6
[Sysname-Ten-GigabitEthernet0/0/6] isis ipv6 tag 4294967295
isis link-delay
Use isis link-delay to configure link delay settings on an IS-IS interface.
Use undo isis link-delay to remove link delay settings on an IS-IS interface.
Syntax
isis link-delay { average average-delay-value | min min-delay-value max max-delay-value | variation variation-value } *
undo isis link-delay { average | min | variation } *
Default
No link delay settings are configured on an IS-IS interface.
Views
Interface view
Predefined user roles
network-admin
Parameters
average average-delay-value: Specifies the average link delay on an interface in the range of 1 to 16777215 microseconds. The average-delay-value parameter represents the average link delay for the interface to send a packet to its directly-connected peer. If you do not specify this option, the delay value is the average link delay reported by the interface.
min min-delay-value: Specifies the minimum link delay on an interface in the range of 1 to 16777215 microseconds. The min-delay-value parameter represents the minimum link delay for the interface to send a packet to its directly-connected peer. If you do not specify this option, the delay value is the minimum link delay reported by the interface.
max max-delay-value: Specifies the maximum link delay on an interface in the range of 1 to 16777215 microseconds. The max-delay-value parameter represents the maximum link delay for the interface to send a packet to its directly-connected peer. If you do not specify this option, the delay value is the maximum link delay reported by the interface.
variation variation-value: Sets the acceptable delay variation on an interface in the range of 1 to 16777215 microseconds. The variation-value parameter represents the difference between two consecutive average link delays. If you do not specify this option, the delay variation value is the variation reported by the interface.
Usage guidelines
Perform either of the following tasks to obtain link delay information of an interface:
· Static configuration—Execute the isis link-delay command to manually configure link delay parameters on the interface.
· Dynamic acquisition—Execute the test-session bind interface command to bind the interface as the out interface of a TWAMP Light test session. Then, TWAMP Light will send the detected link delay information to the interface, and the interface will report the link delay information to IS-IS at periodic intervals. For more information about TWAMP, see NQA TWAMP-light configuration in Network Management and Monitoring Configuration Guide.
For the same interface, the isis link-delay command takes precedence over the test-session bind interface command.
The specified minimum link delay must be lower than or equal to the maximum one.
Examples
# Set the average link delay, minimum link delay, maximum link delay and acceptable link delay variation to 100, 10, 1000, 20 microseconds respectively for interface Ten-GigabitEthernet0/0/6.
<Sysname> system-view
[Sysname] interface ten-gigabitethernet 0/0/6
[Sysname-Ten-GigabitEthernet0/0/6] isis link-delay average 100 min 10 max 1000 variation 20
# Set the average link delay, minimum link delay, maximum link delay and acceptable link delay variation to 100, 10, 1000, 20 microseconds respectively for interface VLAN-interface10.
<Sysname> system-view
[Sysname] interface vlan-interface 10
[Sysname-Vlan-interface10] isis link-delay average 100 min 10 max 1000 variation 20
Related commands
test-session bind interface (Network Management and Monitoring Command Reference)
isis link-quality adjust-cost
Use isis link-quality adjust-cost to enable IS-IS to adjust the interface cost according to the link quality.
Use undo isis link-quality adjust-cost to disable IS-IS from adjusting the interface cost according to the link quality.
Syntax
isis link-quality adjust-cost { cost | max }
undo isis link-quality adjust-cost
Default
IS-IS does not adjust the interface cost according to the link quality.
Views
Interface view
Predefined user roles
network-admin
Parameters
cost: Specifies the value to be added to the interface cost when the link quality changes to LOW. The value range for this argument is 1 to 16777213. When the link quality changes to LOW, the interface cost is cost plus the original interface cost. The interface cost cannot exceed the maximum interface cost.
max: Sets the interface cost to the maximum when the link quality changes to LOW. The maximum interface cost varies by cost type:
· When the cost type is narrow, narrow-compatible, or compatible, the maximum interface cost is 63.
· When the cost type is wide or wide-compatible, the maximum interface cost is 16777215.
Usage guidelines
Error codes, which refer to bit differences between the received and source signals, cannot be avoided because of inevitable link aging and optical path jitter problems. A high error code ratio might cause service degradation or interruption.
To reduce the impact of error codes on an IS-IS network, you can enable IS-IS to adjust the interface cost according to the link quality.
After you configure this command on an interface, IS-IS adjusts the interface cost as follows:
· When the link quality of the interface becomes LOW, IS-IS increases the cost value for the interface.
· When the link quality of the interface restores to GOOD, IS-IS restores the cost value for the interface.
Examples
# Enable IS-IS to adjust the cost of interface Ten-GigabitEthernet0/0/6 according to the link quality, and set the value to be added to the interface cost to 200.
<Sysname> system-view
[Sysname] interface ten-gigabitethernet 0/0/6
[Sysname-Ten-GigabitEthernet0/0/6] isis link-quality adjust-cost 200
Related commands
cost-style
isis mesh-group
Use isis mesh-group to add an interface into a mesh group or block the interface.
Use undo isis mesh-group to restore the default.
Syntax
isis mesh-group { mesh-group-number | mesh-blocked }
undo isis mesh-group
Default
An interface does not belong to any mesh group and is not blocked.
Views
Interface view
Predefined user roles
network-admin
Parameters
mesh-group-number: Specifies a mesh group by its number in the range of 1 to 4294967295.
mesh-blocked: Configures the interface to send LSPs only after receiving LSP requests.
Usage guidelines
An interface not in a mesh group floods received LSPs to other interfaces. For an NBMA network with multiple point-to-point links, this mechanism causes repeated LSP flooding and bandwidth waste.
To solve this problem, use this command to add relevant interfaces to a mesh group. An interface in a mesh group only floods a received LSP to interfaces not in the same mesh group.
You can also use this command to block an interface. A blocked interface sends LSPs only after receiving LSP requests.
The mesh-group feature takes effect only on point-to-point links.
Examples
# Add interface Pos 2/2/1 to mesh group 3.
<Sysname> system-view
[Sysname] interface pos 2/2/1
[Sysname-Pos2/2/1] link-protocol ppp
[Sysname-Pos2/2/1] isis mesh-group 3
isis mib-binding
Use isis mib-binding to bind an IS-IS process to MIB.
Use undo isis mib-binding to restore the default.
Syntax
isis mib-binding process-id
undo isis mib-binding
Default
MIB operation is bound to the IS-IS process with the smallest process ID.
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.
Usage guidelines
If the specified the process ID does not exist, the MIB binding configuration fails.
Deleting an IS-IS process bound to MIB operation deletes the MIB binding configuration. MIB operation is bound to the IS-IS process with the smallest process ID.
Examples
# Bind IS-IS process 100 to MIB.
<Sysname> system-view
[Sysname] isis mib-binding 100
isis peer hold-max-cost duration
Use isis peer hold-max-cost duration to enable IS-IS to advertise the maximum link cost to neighbors within the specified period of time.
Use undo isis peer hold-max-cost duration to restore the default.
Syntax
isis peer hold-max-cost duration time
undo isis peer hold-max-cost duration
Default
IS-IS advertises the original link cost to neighbors during a route convergence.
Views
Interface view
Predefined user roles
network-admin
Parameters
time: Specifies the time period during which IS-IS advertises the maximum link cost to neighbors, in the range of 100 to 1000000 milliseconds.
Usage guidelines
On an IS-IS network, when a link recovers from failures or the state of an interface changes, IS-IS will re-establish neighbor relationships and perform route convergence. During the route convergence process, routing loops and traffic loss might occur because the convergence speeds of the nodes are different. To address this issue, enable IS-IS to advertise the maximum link cost to neighbors within the specified period of time, so the traffic forwarding path remains unchanged. After the specified period of time, IS-IS advertises the original link cost to neighbors and performs optimal route selection again.
For a P2P neighbor, the timer specified by the time argument starts after the neighbor becomes up. For a broadcast neighbor, the timer specified by the time argument starts after the neighbor becomes up and the DIS is elected.
When the cost type is wide, the maximum link cost is 16777214. When the cost type is Narrow, the maximum link cost is 63.
This command applies to both IPv4 IS-IS and IPv6 IS-IS.
Examples
# On interface Ten-GigabitEthernet0/0/6, enable IS-IS to advertise the maximum link cost to neighbors within 1000 milliseconds.
<Sysname> system-view
[Sysname] interface ten-gigabitethernet 0/0/6
[Sysname-Ten-GigabitEthernet0/0/6] isis peer hold-max-cost duration 1000
isis peer-ip-check
Use isis peer-ip-check to enable source address check for hello packets on an IS-IS P2P interface. An IS-IS P2P interface can establish a neighbor relationship only with a peer on the same network.
Use undo isis peer-ip-check to restore the default.
Syntax
isis peer-ip-check
undo isis peer-ip-check
Default
An IS-IS P2P interface can have a peer on a different network.
Interface view
Predefined user roles
network-admin
Examples
# Enable source address check for hello packets on Interface Ten-GigabitEthernet 0/0/6.
<Sysname> system-view
[Sysname] interface ten-gigabitethernet 0/0/6
[Sysname-Ten-GigabitEthernet0/0/6] isis peer-ip-check
Related commands
isis prefix-suppression
Use isis prefix-suppression to enable prefix suppression on an interface.
Use undo isis prefix-suppression to disable prefix suppression on an interface.
Syntax
isis prefix-suppression
undo isis prefix-suppression
Default
Prefix suppression is disabled on an interface.
Views
Interface view
Predefined user roles
network-admin
Usage guidelines
Use this command to disable an interface from advertising its prefix in LSPs. This enhances network security by preventing IP routing to the interval nodes and speeds up network convergence.
This command is also applicable to the secondary IP address of the interface.
Examples
# Enable prefix suppression on Ten-GigabitEthernet 0/0/6.
<Sysname> system-view
[Sysname] interface ten-gigabitethernet 0/0/6
[Sysname-Ten-GigabitEthernet0/0/6] isis prefix-suppression
isis primary-path-detect bfd
Use isis primary-path-detect bfd to enable BFD-powered primary link failure detection on an IPv4 IS-IS interface.
Use undo isis primary-path-detect bfd to restore the default.
Syntax
isis primary-path-detect bfd { ctrl | echo }
undo isis primary-path-detect bfd
Default
An IPv4 IS-IS interface inherits the configuration of the fast-reroute primary-path-detect bfd command in IS-IS IPv4 unicast address family view.
Views
Interface view
Predefined user roles
network-admin
Parameters
ctrl: Specifies the BFD control packet mode.
echo: Specifies the BFD echo packet mode.
Usage guidelines
This command enables IPv4 IS-IS FRR and PIC to use BFD to detect primary link failures. BFD can detect and report a primary link failure to IPv4 IS-IS for a primary-backup path switchover. This can shorten the duration of service interruption.
You can perform one of the following tasks to enable BFD-powered primary link failure detection for IPv4 IS-IS FRR and PIC:
· Use the fast-reroute primary-path-detect bfd command in IPv4 IS-IS unicast address family view. This task takes effect on all interfaces in the current IPv4 IS-IS process.
· Use the isis primary-path-detect bfd command in interface view. This task takes effect only on the current IPv4 IS-IS interface.
For an IPv4 IS-IS interface, the isis primary-path-detect bfd command takes precedence over the fast-reroute primary-path-detect bfd command. The interface uses the configuration of the fast-reroute primary-path-detect bfd command only when you do not execute the isis primary-path-detect bfd command on that interface.
Examples
# Enable BFD control packet mode for IPv4 IS-IS FRR on Ten-GigabitEthernet 0/0/6.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] address-family ipv4
[Sysname-isis-1-ipv4] fast-reroute lfa
[Sysname-isis-1-ipv4] quit
[Sysname-isis-1] quit
[Sysname] interface ten-gigabitethernet 0/0/6
[Sysname-Ten-GigabitEthernet0/0/6] isis primary-path-detect bfd ctrl
# Enable BFD echo packet mode for IPv4 IS-IS PIC on Ten-GigabitEthernet 0/0/7.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] pic additional-path-always
[Sysname-isis-1] quit
[Sysname] bfd echo-source-ip 1.1.1.1
[Sysname] interface ten-gigabitethernet 0/0/7
[Sysname-Ten-GigabitEthernet0/0/7] isis primary-path-detect bfd echo
Related commands
fast-reroute primary-path-detect bfd
isis primary-path-detect bfd exclude
Use isis primary-path-detect bfd exclude to suppress BFD-powered primary link failure detection on an IPv4 IS-IS interface.
Use undo isis primary-path-detect bfd exclude to restore the default.
Syntax
isis primary-path-detect bfd exclude
undo isis primary-path-detect bfd exclude
Default
BFD-powered primary link failure detection is not suppressed on an IPv4 IS-IS interface.
Views
Interface view
Predefined user roles
network-admin
Usage guidelines
The fast-reroute primary-path-detect bfd command enables BFD-powered primary link failure detection on all interfaces in an IPv4 IS-IS process. To disable this feature on an interface in that IS-IS process, use the isis primary-path-detect bfd exclude command on the interface.
When you use the following commands together on the same IPv4 IS-IS interface, the command that is used at last takes effect:
· isis primary-path-detect bfd exclude
· isis primary-path-detect bfd
Examples
# Suppress BFD-powered primary link failure detection on IPv4 IS-IS interface Ten-GigabitEthernet 0/0/6.
<Sysname> system-view
[Sysname] interface ten-gigabitethernet 0/0/6
[Sysname-Ten-GigabitEthernet0/0/6] isis enable 1
[Sysname-Ten-GigabitEthernet0/0/6] isis primary-path-detect bfd exclude
Related commands
fast-reroute primary-path-detect bfd
isis primary-path-detect bfd
isis silent
Use isis silent to disable the interface from sending and receiving IS-IS packets.
Use undo isis silent to restore the default.
Syntax
isis silent
undo isis silent
Default
An interface can send and receive IS-IS packets.
Views
Interface view
Predefined user roles
network-admin
Usage guidelines
This command is not available in loopback interface view.
Examples
# Disable Ten-GigabitEthernet 0/0/6 from sending and receiving IS-IS packets.
<<Sysname> system-view
[Sysname] interface ten-gigabitethernet 0/0/6
[Sysname-Ten-GigabitEthernet0/0/6] isis silent
isis small-hello
Use isis small-hello to configure the interface to send small hello packets without CLVs.
Use undo isis small-hello to restore the default.
Syntax
isis small-hello
undo isis small-hello
Default
An interface sends standard hello packets.
Views
Interface view
Predefined user roles
network-admin
Usage guidelines
This command is not available in loopback interface view.
Examples
# Configure Ten-GigabitEthernet 0/0/6 to send small Hello packets.
<Sysname> system-view
[Sysname] interface ten-gigabitethernet 0/0/6
[Sysname-Ten-GigabitEthernet0/0/6] isis small-hello
isis tag
Use isis tag to configure the administrative tag value for an interface.
Use undo isis tag to restore the default.
Syntax
isis tag tag
undo isis tag
Default
An interface is not configured with any administrative tag value.
Views
Interface view
Predefined user roles
network-admin
Parameters
tag: Specifies the tag value in the range of 1 to 4294967295.
Usage guidelines
To facilitate route filtering and management, use this command to configure the administrative tag value on an IS-IS interface. For example, after setting different administrative tag values for direct routes and non-direct routes in Level-2 area, you can then configure IS-IS to import only non-direct routes from Level-2 area to Level-1 area.
IS-IS adds the administrative tag to the network address information in LSPs only if the following conditions exist:
· An administrative tag value is specified.
· The link cost style is wide, wide-compatible, or compatible.
Examples
# Configure the administrative tag value for Ten-GigabitEthernet 0/0/6.
<Sysname> system-view
[Sysname] interface ten-gigabitethernet 0/0/6
[Sysname-Ten-GigabitEthernet0/0/6] isis tag 4294967295
isis te-metric flex-algo
Use isis te-metric flex-algo to specify the TE cost for flexible algorithm.
Use undo isis te-metric flex-algo to restore the default.
Syntax
isis te-metric flex-algo metric-value
undo isis te-metric flex-algo
Default
The TE cost for flexible algorithm is not specified on an interface.
Views
Interface view
Predefined user roles
network-admin
Parameters
metric-value: Specifies a TE cost in the range of 1 to 16777215.
Usage guidelines
IS-IS advertises application-specific link attributes in ASLA sub-TLVs for use by specific applications. After you use this command, IS-IS advertises TE metric information in ASLA sub-TLVs.
In the current software version, IS-IS only advertises link TE cost information for use by flexible algorithms. The source of the TE metric information advertised in ASLA sub-TLVs can be MPLS TE or configuration of the isis te-metric flex-algo command.
To enable ASLA sub-TLVs to advertise the TE cost reported by MPLS TE, make sure the following requirements are met:
· MPLS TE is enabled for each node that participates in path calculation for that flexible algorithm.
· MPLS and MPLS TE are enabled on each interface that participates in path calculation for that flexible algorithm.
· TE attribute advertisement has been enabled or IPv6 TE has been enabled for the IS-IS process. To enable TE attribute advertisement, execute the te attribute enable command. To enable IPv6 TE, execute the router-id command.
· Application-specific link attribute advertisement has been enabled for IS-IS. To enable application-specific link attribute advertisement, execute the advertise application link-attributes command.
To enable ASLA sub-TLVs to advertise the TE cost specified on the interface, execute the isis te-metric flex-algo command.
For ASLA sub-TLVs, the TE cost specified in the isis te-metric flex-algo command takes precedence over that reported by MPLS TE.
Examples
# Set the TE cost to 100 for flexible algorithm on Ten-GigabitEthernet 0/0/6.
<Sysname> system-view
[Sysname] interface ten-gigabitethernet 0/0/6
[Sysname-Ten-GigabitEthernet0/0/6] isis te-metric flex-algo 100
Related commands
advertise application link-attributes
metric-type te-cost
te attribute enable
isis timer csnp
Use isis timer csnp to set on the DIS of a broadcast network the interval for sending CSNP packets.
Use undo isis timer csnp to remove the configuration.
Syntax
isis timer csnp seconds [ level-1 | level-2 ]
undo isis timer csnp [ level-1 | level-2 ]
Default
The default CSNP interval is 10 seconds.
Views
Interface view
Predefined user roles
network-admin
Parameters
seconds: Specifies on the DIS of a broadcast network the interval for sending CSNP packets. The value range is 1 to 600 seconds.
level-1: Applies the interval to Level-1.
level-2: Applies the interval to Level-2.
Usage guidelines
On a broadcast network, this command only applies to the DIS, because the DIS sends CSNP packets periodically for LSDB synchronization.
If no level is specified, the CSNP interval applies to both Level-1 and Level-2.
Examples
# Configure Level-2 CSNP packets to be sent every 15 seconds over Ten-GigabitEthernet 0/0/6.
<Sysname> system-view
[Sysname] interface ten-gigabitethernet 0/0/6
[Sysname-Ten-GigabitEthernet0/0/6] isis timer csnp 15 level-2
isis timer hello
Use isis timer hello to set the interval for sending hello packets.
Use undo isis timer hello to remove the configuration.
Syntax
isis timer hello seconds [ level-1 | level-2 ]
undo isis timer hello [ level-1 | level-2 ]
Default
The hello interval is 10 seconds.
Views
Interface view
Predefined user roles
network-admin
Parameters
seconds: Specifies the interval for sending hello packets, in the range of 1 to 255 seconds.
level-1: Specifies the interval for sending Level-1 hello packets.
level-2: Specifies the interval for sending Level-2 hello packets.
Usage guidelines
If a neighbor does not receive any hello packets from the router within the advertised hold time, it considers the router down and recalculates the routes. The hold time is the hello multiplier multiplied by the hello interval.
Level-1 and Level-2 hello packets are sent independently on a broadcast network, so you need to specify an interval for each level. On a P2P link, Level-1 and Level-2 packets are both sent in P2P hello packets, and you need not specify an interval for each level.
You can configure the level-1 and level-2 keywords only on broadcast interfaces. Before you configure the level-1 or level-2 keyword, enable IS-IS on the interface.
The shorter the interval, the more system resources will be occupied.
If no level is specified, the hello interval applies to both Level-1 and Level-2.
Examples
# Configure Level-2 hello packets to be sent every 20 seconds over Ten-GigabitEthernet 0/0/6.
<Sysname> system-view
[Sysname] interface ten-gigabitethernet 0/0/6
[Sysname-Ten-GigabitEthernet0/0/6] isis timer hello 20 level-2
Related commands
isis timer holding-multiplier
isis timer holding-multiplier
Use isis timer holding-multiplier to set the IS-IS hello multiplier.
Use undo isis timer holding-multiplier to remove the configuration.
Syntax
isis timer holding-multiplier value [ level-1 | level-2 ]
undo isis timer holding-multiplier [ level-1 | level-2 ]
Default
The default IS-IS hello multiplier is 3.
Views
Interface view
Predefined user roles
network-admin
Parameters
value: Specifies the number of hello intervals, in the range of 3 to 1000.
level-1: Applies the number to the Level-1 IS-IS neighbor.
level-2: Applies the number to the Level-2 IS-IS neighbor.
Usage guidelines
The hello multiplier is the number of hello packets a neighbor must miss before declaring the router is down.
If a neighbor does not receive any hello packets from the router within the advertised hold time, it considers the router down and recalculates the routes. The hold time is the hello multiplier multiplied by the hello interval.
Level-1 and Level-2 hello packets are sent independently on a broadcast network, so you need to specify a hello multiplier for each level. On a P2P link, Level-1 and Level-2 packets are both sent in P2P hello packets, and you need not specify Level-1 or Level-2.
You can configure the level-1 and level-2 keywords only on broadcast interfaces. Before you configure the level-1 or level-2 keyword, enable IS-IS on the interface.
If no level is specified, the hello multiplier applies to both Level-1 and Level-2.
The value of hello multiplier multiplied by hello interval cannot be more than 65535.
Examples
# Set the hello multiplier to 6 for Ten-GigabitEthernet 0/0/6.
<Sysname> system-view
[Sysname] interface ten-gigabitethernet 0/0/6
[Sysname-Ten-GigabitEthernet0/0/6] isis timer holding-multiplier 6 level-2
Related commands
isis timer hello
isis timer lsp
Use isis timer lsp to set the minimum interval for sending LSPs on the interface and specify the maximum number of LSPs that can be sent per time.
Use undo isis timer lsp to restore the default.
Syntax
isis timer lsp time [ count count ]
undo isis timer lsp
Default
The minimum interval for sending LSPs on the interface is 33 milliseconds, and the maximum number of LSPs that can be sent at a time is 5.
Views
Interface view
Predefined user roles
network-admin
Parameters
time: Specifies the minimum interval for sending link-state packets, in the range of 1 to 1000 milliseconds.
count: Specifies the maximum number of link-state packets to be sent at one time, in the range of 1 to 1000.
Usage guidelines
If a change occurs in the LSDB, IS-IS advertises the changed LSP to neighbors. You can specify the minimum interval for sending these LSPs to control the amount of LSPs on the network.
Examples
# Set the interval to 500 milliseconds for sending LSPs on Ten-GigabitEthernet 0/0/6.
<Sysname> system-view
[Sysname] interface ten-gigabitethernet 0/0/6
[Sysname-Ten-GigabitEthernet0/0/6] isis timer lsp 500
Related commands
isis timer retransmit
isis timer retransmit
Use isis timer retransmit to configure the interval for retransmitting LSP packets over a point-to-point link.
Use undo isis timer retransmit to restore the default.
Syntax
isis timer retransmit seconds
undo isis timer retransmit
Default
The retransmission interval on a P2P link is 5 seconds.
Views
Interface view
Predefined user roles
network-admin
Parameters
seconds: Specifies the interval for retransmitting LSP packets, in the range of 1 to 300 seconds.
Usage guidelines
On a P2P link, IS-IS requires an advertised LSP be acknowledged. If no acknowledgment is received within a configurable interval, IS-IS will retransmit the LSP.
You do not need to use this command over a broadcast link where CSNPs are periodically broadcast to implement LSDB synchronization.
Examples
# Set the LSP retransmission interval on a P2P link to 50 seconds for Ten-GigabitEthernet 0/0/6.
<Sysname> system-view
[Sysname] interface ten-gigabitethernet 0/0/6
[Sysname-Ten-GigabitEthernet0/0/6]isis circuit-type p2p
[Sysname-Ten-GigabitEthernet0/0/6] isis timer retransmit 50
Related commands
isis circuit-type p2p
isis timer lsp
isis troubleshooting max-number
Use isis troubleshooting max-number to set the maximum number of IS-IS neighbor relationship troubleshooting entries.
Use undo isis troubleshooting max-number to restore the default.
Syntax
isis troubleshooting max-number number
undo isis troubleshooting max-number
Default
The maximum number of IS-IS neighbor relationship troubleshooting entries is 100.
Views
System view
Predefined user roles
network-admin
Parameters
number: Specifies the maximum number of IS-IS neighbor relationship troubleshooting entries, in the range of 0 to 65535. The value 0 means IS-IS does not record neighbor relationship troubleshooting entries.
Examples
# Set the maximum number of IS-IS neighbor relationship troubleshooting entries to 50.
<Sysname> system-view
[Sysname] isis troubleshooting max-number 50
is-level
Use is-level to specify the IS level.
Use undo is-level to restore the default.
Syntax
is-level { level-1 | level-1-2 | level-2 }
undo is-level
Default
The IS level is level-1-2.
Views
IS-IS view
Predefined user roles
network-admin
Parameters
level-1: Specifies Level-1, which means IS-IS only calculates intra-area routes and maintains the Level-1 LSDB.
level-1-2: Specifies Level-1-2, which means IS-IS calculates routes and maintains the LSDBs for both Level-1 and Level-2.
level-2: Specifies Level-2, which means IS-IS calculates routes and maintains the LSDB for Level-2 only.
Usage guidelines
If the only area is an IP network, configure all the routers as Level-2 for scalability.
Examples
# Set the IS level to Level-1 for IS-IS process 1.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] is-level level-1
is-name
Use is-name to specify a host name for the IS and enable dynamic system ID to hostname mapping.
Use undo is-name to disable dynamic system ID to hostname mapping.
Syntax
is-name sys-name
undo is-name
Default
Dynamic system ID to hostname mapping is disabled, and no host name is configured for the IS.
Views
IS-IS view
Predefined user roles
network-admin
Parameters
sys-name: Specifies a host name for the local IS, a case-sensitive string of 1 to 64 characters.
Usage guidelines
To display the host name rather than the system ID of an IS by using the display isis lsdb command, first enable dynamic system ID to hostname mapping.
Examples
# Configure a host name for the local IS.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] is-name RUTA
Related commands
display isis name-table
is-name map
Use is-name map to configure a system ID to host name mapping for a remote IS.
Use undo is-name map to remove the mapping.
Syntax
is-name map sys-id map-sys-name
undo is-name map sys-id
Default
No system ID to host name mapping is configured for a remote IS.
Views
IS-IS view
Predefined user roles
network-admin
Parameters
sys-id: Specifies the system ID or pseudonode ID of a remote IS.
map-sys-name: Specifies a host name for the remote IS, a case-sensitive string of 1 to 64 characters.
Usage guidelines
Each remote IS system ID corresponds to only one name.
Examples
# Map the host name RUTB to the system ID 0000.0000.0041 of the remote IS.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] is-name map 0000.0000.0041 RUTB
Related commands
display isis name-table
isolate enable
Use isolate enable to enable IS-IS isolation.
Use undo isolate enable to disable IS-IS isolation.
Syntax
isolate enable
undo isolate enable
Default
IS-IS isolation is disabled.
Views
IS-IS view
Predefined user roles
network-admin
Usage guidelines
To reduce impact on traffic forwarding, you can isolate a device before upgrading it. IS-IS isolation works as follows:
1. After IS-IS isolation is enabled for a device, IS-IS sets the overload bit in the LSPs advertised by the device and sets the link cost to the maximum value.
2. Each neighbor of the device reselects an optimal route based on the LSPs and stops forwarding traffic to the device. The device is fully isolated from the network and you can upgrade the device.
3. After the maintenance, disable IS-IS isolation on the device to gracefully add it back to the network by clearing its overload bit and restoring its link cost.
The isolated device does not advertise redistributed routes and routes received from other levels. To enable advertising these routes, execute the set-overload command.
Examples
# Isolate the device from the network in IS-IS process 1.
[Sysname] isis 1
[Sysname-isis-1] isolate enable
Related commands
set-overload
ispf enable
Use ispf enable to enable incremental SPF (ISPF).
Use undo ispf enable to disable ISPF.
Syntax
ispf enable
undo ispf enable
Default
ISPF is enabled.
Views
IS-IS view
IS-IS IPv6 unicast address family view
Predefined user roles
network-admin
Usage guidelines
When a network topology is changed, ISPF recomputes only the affected part of the SPT, instead of the entire SPT.
Examples
# Enable IS-IS ISPF.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] ispf enable
log-peer-change
Use log-peer-change to enable the logging of IS-IS neighbor state changes.
Use undo log-peer-change to disable the logging.
Syntax
log-peer-change
undo log-peer-change
Default
The logging of IS-IS neighbor state changes is enabled.
Views
IS-IS view
Predefined user roles
network-admin
Usage guidelines
This command enables sending logs about IS-IS neighbor state changes to the information center. For IS-IS neighbor state change logs to be sent correctly, you must also configure the information center parameters on the device. For more information about information center, see information center configuration in System Management Configuration Guide.
Examples
# Disable the logging of IS-IS neighbor state changes.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] undo log-peer-change
lsp-fragments-extend
Use lsp-fragments–extend to enable LSP fragment extension for a level.
Use undo lsp-fragments–extend to restore the default.
Syntax
lsp-fragments-extend [ level-1 | level-1-2 | level-2 ]
undo lsp-fragments-extend
Default
LSP fragment extension is disabled.
Views
IS-IS view
Predefined user roles
network-admin
Parameters
level-1: Applies the fragment extension to Level-1 LSPs.
level-1-2: Applies the fragment extension to both Level-1 and Level-2 LSPs.
level-2: Applies the fragment extension to Level-2 LSPs.
Usage guidelines
If no level is specified, the command enables LSP fragment extension for both Level-1 and Level-2.
Examples
# Enable LSP fragment extension for Level-2.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] lsp-fragments-extend level-2
lsp-length originate
Use lsp-length originate to configure the maximum size of generated Level-1 or Level-2 LSPs.
Use undo lsp-length originate to remove the configuration.
Syntax
lsp-length originate size [ level-1 | level-2 ]
undo lsp-length originate [ level-1 | level-2 ]
Default
The maximum size of generated Level-1 and Level-2 LSPs is 1497 bytes.
Views
IS-IS view
Predefined user roles
network-admin
Parameters
size: Specifies the maximum size of LSP packets, in the range of 512 to 16384 bytes.
level-1: Applies the size to Level-1 LSP packets.
level-2: Applies the size to Level-2 LSP packets.
Usage guidelines
If neither Level-1 nor Level-2 is specified in the command, the configured maximum size applies to the current IS-IS level.
Examples
# Set the maximum size of the generated Level-2 LSPs to 1024 bytes.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] lsp-length originate 1024 level-2
lsp-length receive
Use lsp-length receive to configure the maximum size of received LSPs.
Use undo lsp-length receive to restore the default.
Syntax
lsp-length receive size
undo lsp-length receive
Default
The maximum size of received LSPs is 1497 bytes.
Views
IS-IS view
Predefined user roles
network-admin
Parameters
size: Specifies the maximum size of received LSPs, in the range of 512 to 16384 bytes.
Examples
# Configure the maximum size of received LSPs to 1024 bytes.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] lsp-length receive 1024
maximum load-balancing
Use maximum load-balancing to configure the maximum number of ECMP routes for load balancing.
Use undo maximum load-balancing to restore the default.
Syntax
maximum load-balancing number
undo maximum load-balancing
Default
The maximum number of IS-IS ECMP routes equals the maximum number of ECMP routes, which is configurable by using the max-ecmp-num command.
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 ECMP routes. The value of 1 indicates that IS-IS does not perform load balancing. The value range for this argument is 1 to 64.
Usage guidelines
You can use the max-ecmp-num command to configure the maximum number of ECMP routes supported by the system as m. After a reboot, the value range for the number argument of the maximum load-balancing command is 1 to m.
Examples
# Set the maximum number of ECMP routes to 2.
<Sysname> system-view
[Sysname] isis 100
[Sysname-isis-100] address-family ipv4
[Sysname-isis-100-ipv4] maximum load-balancing 2
metric-bandwidth advertisement enable
Use metric-bandwidth advertisement enable to enable IS-IS to advertise link bandwidth information.
Use undo metric-bandwidth advertisement enable to disable IS-IS from advertising link bandwidth information.
Syntax
metric-bandwidth advertisement enable [ level-1 | level-2 ]
undo metric-bandwidth advertisement enable [ level-1 | level-2 ]
Default
IS-IS does not advertise link bandwidth information.
Views
IS-IS IPv4 address family view
IS-IS IPv6 address family view
Predefined user roles
network-admin
Parameters
level-1: Enables link bandwidth information advertisement for Level-1 routers.
level-2: Enables link bandwidth information advertisement for Level-2 routers.
Usage guidelines
Use this command to enable IS-IS to advertise link bandwidth information and report the information to the controller through BGP-LS. Then, the controller performs optimal route calculation based on the link bandwidth information.
This command takes effect only when one of the following conditions exists:
· You have enabled link attribute advertisement by executing the advertise link-attributes command.
· You have enabled MPLS TE for the IS-IS process by executing the mpls te enable command.
Examples
# Enable IS-IS process 1 to advertise link bandwidth information.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] address-family ipv4
[Sysname-isis-1-ipv4] metric-bandwidth advertisement enable
Related commands
advertise link-attributes
distribute bgp-ls
mpls te enable (MPLS Command Reference)
metric-bandwidth suppression
Use metric-bandwidth suppression to enable IS-IS to suppress link bandwidth information advertisement and configure the suppression timer.
Use undo metric-bandwidth suppression to disable IS-IS from suppressing link bandwidth information advertisement.
Syntax
metric-bandwidth suppression timer time-value
undo metric-bandwidth suppression
Default
Link bandwidth information advertisement is suppressed.
Views
IS-IS view
Predefined user roles
network-admin
Parameters
timer time-value: Specifies the suppression timer in the range of 0 to 600 seconds. The default timer is 120 seconds. To disable IS-IS from suppressing link bandwidth information advertisement, set the timer to 0.
Usage guidelines
By suppressing link bandwidth information advertisement, you can prevent device resources from being over consumed upon frequent bandwidth changes.
Link bandwidth advertisement suppression works as follows:
· The interface reports link bandwidth information to IS-IS at negotiated intervals.
· IS-IS advertises link bandwidth information through BGP-LS at intervals specified by the time-value argument. IS-IS does not advertise link bandwidth information until the suppression timer expires.
This command takes effect only after you enable link bandwidth information advertisement by executing the metric-bandwidth advertisement enable command.
As a best practice, the suppression timer you specified should not be less than the Ethernet interface measurement interval. For more information about Ethernet interfaces, see Ethernet interface configuration in Interface Management and Configuration Guide.
Examples
# Enable IS-IS process 1 to suppress link bandwidth information advertisement and set the suppression timer to 100 seconds.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] metric-bandwidth suppression timer 100
Related commands
metric-bandwidth advertisement enable
metric-delay advertisement enable
Use metric-delay advertisement enable to enable IS-IS to advertise link delay information.
Use undo metric-delay advertisement enable to disable IS-IS from advertising link delay information.
Syntax
metric-delay advertisement enable [ level-1 | level-2 ]
undo metric-delay advertisement enable [ level-1 | level-2 ]
Default
IS-IS does not advertise link delay information.
Views
IS-IS IPv4 address family view
IS-IS IPv6 address family view
Predefined user roles
network-admin
Parameters
level-1: Enables link delay information advertisement for Level-1 routers.
level-2: Enables link delay information advertisement for Level-2 routers.
Usage guidelines
Use this command to enable IS-IS to advertise link delay information and report the information to the controller through BGP-LS. Then, the controller performs optimal route calculation based on the link delay information.
This command takes effect only when one of the following conditions exists:
· You have enabled link attribute advertisement by executing the advertise link-attributes command.
· You have enabled MPLS TE for the IS-IS process by executing the mpls te enable command.
Examples
# Enable IS-IS process 1 to advertise link delay information.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] address-family ipv4
[Sysname-isis-1-ipv4] metric-delay advertisement enable
Related commands
advertise link-attributes
distribute bgp-ls
mpls te enable (MPLS Command Reference)
metric-delay suppression
Use metric-delay suppression to enable IS-IS to suppress link delay information advertisement and configure the suppression settings.
Use undo metric-delay suppression to disable IS-IS from suppressing link delay information advertisement.
Syntax
metric-delay suppression timer time-value percent-threshold percent-value absolute-threshold absolute-value
undo metric-delay suppression
Default
Link delay information advertisement is suppressed.
Views
IS-IS view
Predefined user roles
network-admin
Parameters
timer time-value: Specifies the suppression timer in the range of 0 to 600 seconds. The default timer is 120 seconds. To disable IS-IS from suppressing link delay information advertisement, set the timer to 0.
percent-value: Specifies the suppression threshold for link delay variation ratio in the range of 0 to 100%. The default threshold is 10%. If this argument is unnecessary, you can set it to 0.
absolute-value: Specifies the suppression threshold for the absolute value of link delay variation in the range of 0 to 10000 microseconds. The default threshold is 1000 microseconds. If this argument is unnecessary, you can set it to 0.
Usage guidelines
By suppressing link delay information advertisement, you can prevent device resources from being over consumed upon frequent link delay changes.
Link delay advertisement suppression works as follows:
· The interface reports link delay information to IS-IS at negotiated intervals.
· IS-IS advertises link delay information through BGP-LS at intervals specified by the time-value argument. IS-IS does not advertise link delay information within the suppression timer except for the following conditions:
¡ The variation ratio between two consecutive minimum delays is larger than or equivalent to the suppression threshold for the delay variation ratio.
¡ The absolute value of the difference between two consecutive minimum delays is larger than or equivalent to the suppression threshold for the absolute value of the delay variation.
This command takes effect only after you execute the metric-delay advertisement enable command.
As a best practice, the suppression timer you specified should not be less than the NQA measurement interval. For more information about NQA, see NQA configuration in Network Management and Monitoring Configuration Guide.
Examples
# Enable IS-IS process 1 to suppress link delay information advertisement and configure the suppression settings.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] metric-delay suppression timer 100 percent-threshold 50 absolute-threshold 200
Related commands
metric-delay advertisement enable
metric-type
Use metric-type to configure the metric type of a flexible algorithm.
Use undo metric-type to restore the default.
Syntax
metric-type { delay | te-cost }
undo metric-type
Default
The flexible algorithm uses IS-IS link cost for path calculation.
Views
Flexible algorithm view
Predefined user roles
network-admin
Parameters
delay: Configures the metric type as link delay.
te-cost: Configures the metric type as TE cost.
Usage guidelines
By default, the flexible algorithm uses IS-IS link cost for optimal path calculation. In some scenarios, the paths calculated by the flexible algorithm might not be optimal. To resolve this issue, configure the flexible algorithm to use another metric type for optimal path calculation.
Flexible algorithm supports the following metric types:
· IS-IS link cost.
· Link delay. The minimum link delay is used for optimal path calculation.
· TE cost.
You can use this feature only when the link cost style is wide, compatible, or wide-compatible.
Examples
# Configure the metric type of flexible algorithm 128 as TE cost.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] flex-algo 128
[Sysname-isis-1-flex-algo-128] metric-type te-cost
Related commands
cost-style
isis link-delay
metric-delay advertisement enable
mpls enable (MPLS Command Reference)
mpls te enable (MPLS Command Reference)
multi-instance enable
Use multi-instance enable to enable the IS-IS multi-instance process and specify an instance ID for the process.
Use undo multi-instance enable to disable the IS-IS multi-instance process.
Syntax
multi-instance enable iid iid-value
undo multi-instance enable
Default
IS-IS multi-instance process is disabled.
Views
IS-IS view
Predefined user roles
network-admin
Parameters
iid iid-value: Specifies an instance ID for the IS-IS process, in the range of 1 to 65535.
Usage guidelines
IS-IS processes not enabled with the multi-instance process feature are called traditional IS-IS processes. IS-IS processes enabled with the multi-instance process feature are called IS-IS multi-instance processes.
By default, an interface supports only one IS-IS process. To configure multiple IS-IS processes on a device, you must add more interfaces to the device and configure the interfaces manually. To simplify configuration, use the IS-IS multi-instance process feature to configure multiple IS-IS multi-instance processes as well as a traditional IS-IS process on an interface.
After you enable the IS-IS multi-instance process feature, two devices can establish a neighbor relationship only when you configure the same instance ID for the multi-instance processes on the devices.
When you configure IS-IS multi-instance processes or disable the IS-IS multi-instance process feature, follow these restrictions and guidelines:
· You cannot specify the same instance ID for different IS-IS processes.
· Before enabling or disabling the IS-IS multi-instance process feature on an interface that has been configured with an IS-IS process, disable IS-IS on the interface.
Examples
# Enable IS-IS multi-instance process on IS-IS process 1 and set the instance ID to 3.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] multi-instance enable iid 3
Related commands
isis enable
multi-topology
Use multi-topology to enable IPv6 IS-IS MTR.
Use undo multiple-topology to disable IPv6 IS-IS MTR.
Syntax
multi-topology [ compatible ]
undo multi-topology
Default
IPv6 IS-IS MTR is disabled.
Views
IS-IS IPv6 address family view
Predefined user roles
network-admin
Parameters
compatible: Specifies the compatible mode to advertise IPv6 prefixes to both IPv4 and IPv6 topologies. If you do not specify this keyword, the command advertises IPv6 prefixes only to the IPv6 topology.
Usage guidelines
This command enables separate route calculation in IPv4 and IPv6 topologies.
This command is available when the link cost style is wide, compatible, or wide-compatible.
Examples
# Enable IPv6 IS-IS MTR.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] address-family ipv6
[Sysname-isis-1-ipv6] multi-topology
Related commands
cost-style
network-entity
Use network-entity to configure the Network Entity Title (NET) for an IS-IS process.
Use undo network-entity to delete a NET.
Syntax
network-entity net
undo network-entity net
Default
No NET is configured.
Views
IS-IS view
Predefined user roles
network-admin
Parameters
Usage guidelines
CAUTION: When you execute the network-entity command together with the cost-style and is-level commands for the same IS-IS process, execute the network-entity command at last. Incorrect configuration order might cause data loss because the IS-IS process will restart. |
A NET is a special NSAP address with the SEL being 0. The length of the NET is in the range of 8 to 20 bytes.
A NET comprises the following parts:
· Area ID—With a length of 1 to 13 bytes.
· System ID—A system ID uniquely identifies a host or router in the area and has a fixed 6-byte length.
· SEL—It has a value of 0 and a fixed 1-byte length.
For example, a NET of ab.cdef.1234.5678.9abc.00 specifies the area ID ab.cdef, the system ID 1234.5678.9abc, and the SEL 00.
Examples
# Set the NET to 10.0001.1010.1020.1030.00, of which 10.0001 is the area ID and 1010.1020.1030 is the system ID.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] network-entity 10.0001.1010.1020.1030.00
Related commands
cost-style
isis
isis enable
is-level
non-stop-routing
Use non-stop-routing to enable IS-IS NSR.
Use undo non-stop-routing to disable IS-IS NSR.
Syntax
non-stop-routing
undo non-stop-routing
Default
IS-IS NSR is disabled.
Views
IS-IS view
Predefined user roles
network-admin
Usage guidelines
IS-IS NSR takes effect on a per-process basis. As a best practice, enable NSR for each IS-IS process.
IS-IS NSR and IS-IS GR are mutually exclusive. Therefore, do not configure the non-stop-routing command and the graceful-restart command at the same time.
Examples
# Enable NSR for IS-IS process 1.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] non-stop-routing
overload adjust-cost
Use overload adjust-cost to set the cost for all IS-IS interfaces when the device enters the overload state.
Use undo overload adjust-cost to restore the default.
Syntax
overload adjust-cost { cost-offset | max }
undo overload adjust-cost
Default
The device does not change the cost for any IS-IS interfaces when it enters the overload state.
Views
IS-IS view
IS-IS IPv6 unicast address family view
Predefined user roles
network-admin
Parameters
cost-offset: Sets the cost offset in the range of 1 to 16777213. When the device enters the overload state, the cost of each IS-IS interface changes to the original interface cost plus the specified cost offset value. The new cost does not exceed the maximum cost value of the interface.
max: Sets the maximum cost value. The value range varies by cost style.
· For styles narrow, narrow-compatible, and compatible, the maximum cost value is 63.
· For styles wide and wide-compatible, the maximum cost value is 16777214.
Usage guidelines
Upon entering the overload state, the device sends an LSP with the OL bit set to its neighbors. The neighbor that receives the LSP performs path calculation and forwards packets as follows:
· For packets destined to a network not directly connected to the overloaded device, the neighbor device does not forward the packets to the overloaded device.
· For packets destined to the network directly connected to the overloaded device, the neighbor device forwards the packets to the overloaded device.
These processing methods might cause problems in an anycast scenario where the destination address of packets is an anycast address. The neighbor device will send such packets to the anycast node with the smallest cost, and that node might have already entered the overload state. To avoid such problems, use this command to enable an overloaded device to increase its cost. Neighbors will not select the device during path calculation.
The command takes effect when the device enters the overload state as follows:
· When the device is in overload state, the system increases the cost of all IS-IS interfaces on the device. Neighbors will not select the device during path calculation.
· When the device exits the overload state or you execute the undo overload adjust-cost command, the IS-IS interfaces resume their original costs.
Examples
# Increase the cost for all IS-IS interfaces by 50 when IS-IS process 1 enters the overload state.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] overload adjust-cost 50
pic
Use pic to enable IS-IS PIC.
Use undo pic to disable IS-IS PIC.
Syntax
pic [ additional-path-always ]
undo pic
Default
IS-IS PIC is enabled.
Views
IS-IS view
Predefined user roles
network-admin
Parameters
additional-path-always: Allows the indirect suboptimal route as the backup route.
Usage guidelines
Prefix Independent Convergence (PIC) enables the device to speed up network convergence by ignoring the number of prefixes. PIC applies only to indirect routes.
When both IS-IS PIC and IS-IS FRR are configured, only IS-IS FRR takes effect.
Examples
# Configure IS-IS PIC to support the indirect suboptimal route as the backup route.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] pic additional-path-always
preference
Use preference to configure the preference for IS-IS.
Use undo preference to restore the default.
Syntax
preference { preference | route-policy route-policy-name } *
undo preference
Default
IS-IS preference is 15.
Views
IS-IS IPv4 unicast address family view
IS-IS IPv6 unicast address family view
Predefined user roles
network-admin
Parameters
preference: Specifies an IS-IS protocol preference in the range of 1 to 255.
route-policy route-policy-name: Specifies a routing policy by its name, a case-sensitive string of 1 to 63 characters, to assign a priority to the matching routes.
Usage guidelines
If multiple routing protocols find routes to the same destination, the route found by the routing protocol with the highest preference is selected as the optimal route.
If a routing policy is specified in this command, the preference set by the routing policy applies to the matching routes. Other routes use the preference set by the preference command.
Examples
# Set the preference for IS-IS to 25.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] address-family ipv4
[Sysname-isis-1-ipv4] preference 25
prefix-priority
Use prefix-priority to assign convergence priorities to specific IS-IS routes.
Use undo prefix-priority to remove the configuration.
Syntax
prefix-priority { critical | high | medium } { prefix-list prefix-list-name | tag tag-value }
prefix-priority route-policy route-policy-name
undo prefix-priority { critical | high | medium } [ prefix-list | tag ]
undo prefix-priority route-policy
Default
IS-IS routes have the lowest convergence priority.
Views
IS-IS IPv4 unicast address family view
IS-IS IPv6 unicast address family view
Predefined user roles
network-admin
Parameters
critical: Specifies the highest convergence priority.
high: Specifies the high convergence priority.
medium: Specifies the medium convergence priority.
prefix-list prefix-list-name: Specifies a prefix list by its name, a case-sensitive string of 1 to 63 characters.
tag tag-value: Specifies a tag value in the range of 1 to 4294967295.
route-policy route-policy-name: Specifies a routing policy by its name, a case-sensitive string of 1 to 63 characters.
Usage guidelines
The higher the convergence priority, the faster the convergence speed.
IS-IS host routes have a medium convergence priority.
Examples
# Assign the high convergence priority to IS-IS routes permitted by IP prefix list standtest.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] address-family ipv4
[Sysname-isis-1-ipv4] prefix-priority high prefix-list standtest
priority
Use priority to set the priority of a flexible algorithm.
Use undo priority to restore the default.
Syntax
priority priority-value
undo priority
Default
The priority of a flexible algorithm is 128.
Views
Flexible algorithm view
Predefined user roles
network-admin
Parameters
priority-value: Specifies a priority value in the range of 0 to 255. A higher value indicates a higher priority.
Usage guidelines
All nodes that participate in the path calculation for a flexible algorithm can have a different FAD. To avoid routing loops in an FAD advertisement scope (IS-IS area), these nodes must use the same FAD. By convention, a node selects an FAD as follows:
· The FAD with the highest priority will be selected from the FADs advertised within the IS-IS routing domain. If the node does not advertise FADs, it selects the FAD with the highest priority from the received FADs.
· The FAD with the greatest system ID will be selected from the FADs that have the highest priority.
This feature is available when the link cost style is wide, compatible, or wide-compatible.
Examples
# Set the priority to 200 for flexible algorithm 128.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] flex-algo 128
[Sysname-isis-1-flex-algo-128] priority 200
Related commands
advertise-definition
cost-style
reset isis all
Use reset isis all to clear all IS-IS data structure information.
Syntax
reset isis all [ process-id ] [ graceful-restart ]
Views
User view
Predefined user roles
network-admin
Parameters
process-id: Specifies an IS-IS process by its ID in the range of 1 to 65535 to clear the data structure information for an IS-IS process.
graceful-restart: Recovers the data through graceful restart after the data is cleared.
Usage guidelines
Use this command when LSPs must be updated immediately.
Examples
# Clear all IS-IS data structure information.
<Sysname> reset isis all
reset isis event-log graceful-restart
Use reset isis event-log graceful-restart to clear IS-IS GR log information.
Syntax
reset isis event-log graceful-restart slot slot-number
Views
User view
Predefined user roles
network-admin
Parameters
slot slot-number: Specifies a card by its slot number.
# Clear IS-IS GR log information for the specified slot.
<Sysname> reset isis event-log graceful-restart slot 0
reset isis event-log hello
Use reset isis event-log hello to clear IS-IS log information about received or sent hello packets.
Syntax
reset isis event-log hello { peer-change | received-abnormal | received-dropped | sent-abnormal | sent-failed } [ process-id ]
Views
User view
Predefined user roles
network-admin
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 (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 clears IS-IS log information about received or sent hello packets for all processes.
Examples
# Clear IS-IS log information about received or sent hello packets for all processes.
<Sysname> reset isis event-log hello peer-change
Related commands
display isis event-log hello
reset isis event-log lsp
Use reset isis event-log lsp to clear IS-IS LSP log information.
Syntax
reset isis event-log lsp { purged | refreshed } [ process-id ]
Views
User view
Predefined user roles
network-admin
Parameters
purged: Clears log information about purged LSPs.
refreshed: Clears log information about refreshed LSPs.
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 clears LSP log information for all IS-IS processes.
Examples
# Clear log information about LSPs for IS-IS process 1.
<Sysname> reset isis event-log lsp 1
Related commands
display isis event-log lsp
reset isis event-log peer
Use reset isis event-log peer to clear log information about IS-IS neighbor state changes.
Syntax
reset isis event-log peer [ process-id ]
Views
User view
Predefined user roles
network-admin
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 clears neighbor state change log information for all IS-IS processes.
Examples
# Clear neighbor state change log information for all IS-IS processes.
<Sysname> reset isis event-log peer
Related commands
display isis event-log peer
reset isis event-log spf
Use reset isis event-log spf to clear IS-IS route calculation log information.
Syntax
reset isis event-log spf [ process-id ]
Views
User view
Predefined user roles
network-admin
Parameters
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 clears route calculation log information for all IS-IS processes.
Examples
# Clear route calculation log information for IS-IS process 1.
<Sysname> reset isis event-log spf 1
Related commands
display isis event-log spf
reset isis packet
Use reset isis packet to clear IS-IS packet statistics.
Syntax
reset isis packet [ csnp | hello | lsp | psnp ] [ interface-type interface-number ] [ process-id ]
Views
User view
Predefined user roles
network-admin
Parameters
csnp: Clears CSNP packet statistics.
hello: Clears hello packet statistics.
lsp: Clears LSP packet statistics.
psnp: Clears PSNP packet statistics.
interface-type interface-number: Specifies an interface by its type and number. If you do not specify this option, the command clears 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 clears IS-IS packet statistics for all IS-IS processes.
Examples
# Clear IS-IS packet statistics for all IS-IS processes.
<Sysname> reset isis packet
Related commands
display isis packet
reset isis peer
Use reset isis peer to clear data structure information for a specified IS-IS neighbor.
Syntax
reset isis peer system-id [ process-id ]
Views
User view
Predefined user roles
network-admin
Parameters
system-id: Specifies an IS-IS neighbor by its system ID.
process-id: Specifies an IS-IS process by its ID in the range of 1 to 65535 to clear data structure information for the neighbor in the specified IS-IS process.
Usage guidelines
Use this command when you re-establish an IS-IS neighbor relationship.
Examples
# Clear the data structure information of the neighbor with the system ID 0000.0c11.1111.
<Sysname> reset isis peer 0000.0c11.1111
reset isis troubleshooting
Use reset isis troubleshooting to clear IS-IS neighbor relationship troubleshooting information.
Syntax
reset isis troubleshooting
Views
User view
Predefined user roles
network-admin
Examples
# Clear IS-IS neighbor relationship troubleshooting information.
<Sysname> reset isis troubleshooting
Related commands
display isis troubleshooting
reset osi statistics
Use reset osi statistics to clear OSI packet statistics.
Syntax
reset osi statistics
Views
User view
Predefined user roles
network-admin
Usage guidelines
To obtain OSI packet statistics from the specified time point, first clear the existing statistics.
Examples
# Clear OSI packet statistics.
<Sysname> reset osi statistics
Related commands
display osi statistics
segment-routing microloop-avoidance enable
Use segment-routing microloop-avoidance enable to enable SR microloop avoidance for a flexible algorithm.
Use undo segment-routing microloop-avoidance enable to disable SR microloop avoidance for a flexible algorithm.
Syntax
segment-routing microloop-avoidance enable
undo segment-routing microloop-avoidance enable
Default
SR microloop avoidance is enabled for a flexible algorithm.
Views
Flexible algorithm view
Predefined user roles
network-admin
Usage guidelines
After a network failure occurs or recovers, route convergence occurs on relevant network devices. Because of non-simultaneous convergence on network devices, microloops might be formed. After you configure SR microloop avoidance, the devices will forward traffic along the specified path before route convergence is finished on all the relevant network devices. Because the forwarding path is independent of route convergence, microloops are avoided.
Examples
# Enable SR microloop avoidance for flexible algorithm 128.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] flex-algo 128
[System-isis-1-flex-algo-128] segment-routing microloop-avoidance enable
Related commands
segment-routing microloop-avoidance rib-update-delay
segment-routing microloop-avoidance strict-sid-only
segment-routing microloop-avoidance rib-update-delay
Use segment-routing microloop-avoidance rib-update-delay to set the SR microloop avoidance delay timer for a flexible algorithm.
Use undo segment-routing microloop-avoidance rib-update-delay to restore the default.
Syntax
segment-routing microloop-avoidance rib-update-delay delay-time [ level-1 | level-2 ]
undo segment-routing microloop-avoidance rib-update-delay [ level-1 | level-2 ]
Default
The SR microloop avoidance delay timer for a flexible algorithm is 5000 milliseconds.
Views
Flexible algorithm view
Predefined user roles
network-admin
Parameters
delay-time: Specifies the SR microloop avoidance delay timer for the flexible algorithm, in the range of 1 to 60000 milliseconds.
level-1: Applies the SR microloop avoidance delay timer to Level-1 IS-IS.
level-2: Applies the SR microloop avoidance delay timer to Level-2 IS-IS.
Usage guidelines
To leave sufficient time for IS-IS to finish route convergence, specify a proper value for the SR microloop avoidance delay timer. Before the timer expires, failure relevant devices will forward traffic along the specified path. After the timer expires, traffic will traverse the usual path.
The SR microloop avoidance delay timer takes effect only after you enable SR microloop avoidance.
If you do not specify the level-1 or level-2 keyword, this command sets the SR microloop avoidance delay timer for all IS-IS levels.
Examples
# Set the SR microloop avoidance delay timer to 6000 milliseconds for flexible algorithm 128.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] flex-algo 128
[System-isis-1-flex-algo-128] segment-routing microloop-avoidance rib-update-delay 6000
Related commands
segment-routing microloop-avoidance enable
segment-routing microloop-avoidance strict-sid-only
segment-routing microloop-avoidance strict-sid-only
Use segment-routing microloop-avoidance strict-sid-only to configure SR microloop avoidance to encapsulate only strict SIDs in the SID list.
Use undo segment-routing microloop-avoidance strict-sid-only to restore the default.
Syntax
segment-routing microloop-avoidance strict-sid-only
undo segment-routing microloop-avoidance strict-sid-only
Default
The strict-SID-only feature is not configured for SR microloop avoidance.
Views
Flexible algorithm view
Predefined user roles
network-admin
Usage guidelines
By default, SR microloop avoidance first calculates the End SID to the P node, and then calculates the End.X SIDs from the P node to the destination node. These SIDs form an SID list and SR microloop avoidance then encapsulates the list into the packet.
If multi-point failure exists and the forwarding path is frequently switched, there might be a microloop on the path to the P node identified by the End SID. To avoid the microloop, you can strictly constrain the path to the P node. This command strictly constrains the path to the P node by calculating an End.X SID to reach the P node. Then, the SID list encapsulated into the packet consists of the End.X SID to the P node and End.X SIDs from the P node to the destination node.
Examples
# Configure SR microloop avoidance to encapsulate strict SIDs in the SID list.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] flex-algo 128
[System-isis-1-flex-algo-128] segment-routing microloop-avoidance strict-sid-only
Related commands
segment-routing microloop-avoidance enable
segment-routing microloop-avoidance rib-update-delay
set-att
Use set-att to set the ATT bit of Level-1 LSPs.
Use undo set-att to restore the default.
Syntax
set-att { always | never }
undo set-att
Default
The Level-1-2 router sets the ATT bit for Level-1 LSPs in accordance with the default ATT bit setting rule.
Views
IS-IS view
IS-IS IPv6 unicast address family view
Predefined user roles
network-admin
Parameters
always: Sets the ATT bit of Level-1 LSPs.
never: Keeps the ATT bit of Level-1 LSPs not set.
Usage guidelines
The ATT bit is used to identify the connection status between a Level-1 area and other areas. By default, a Level-1-2 router sets the ATT bit for Level-1 LSPs as follows:
· The Level-1-2 router sets the ATT bit in Level-1 LSPs to inform the Level-1 routers that it can reach other areas. After a Level-1 router receives a Level-1 LSP with the ATT bit set, it generates a default route destined for the Level-1-2 router.
· The Level-1-2 router does not set the ATT bit in Level-1 LSPs if it can reach only one area.
To edit the default ATT bit setting rule for a Level-1-2 router, perform the following tasks as needed:
· To enable ATT bit setting for all Level-1 LSPs, execute the set-att always command on the Level-1-2 router.
· To disable a Level-1 router from generating a default route upon receiving an ATT-bit-set Level-1 LSP from the Level-1-2 router, you can perform one of the following tasks:
¡ Execute the ignore-att command on the Level-1 router.
¡ Execute the set-att never command on the Level-1-2 router.
The set-att command is applicable to only Level-1-2 routers.
Examples
# Set the ATT bit of Level-1 LSPs.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] set-att always
set-overload
Use set-overload to set the overload bit.
Use undo set-overload to restore the default.
Syntax
In IS-IS view:
set-overload [ on-startup [ [ start-from-nbr system-id [ timeout1 [ nbr-timeout ] ] ] | timeout2 | wait-for-bgp [ timeout3 ] ] ] [ allow { external | interlevel } * ]
undo set-overload
In IS-IS IPv6 unicast address family view:
set-overload [ on-startup [ [ start-from-nbr system-id [ timeout1 [ nbr-timeout ] ] ] | timeout2 | wait-for-bgp4+ [ timeout3 ] ] ] [ allow { external | interlevel } * ]
undo set-overload
Default
The overload bit is not set.
Views
IS-IS view
IS-IS IPv6 unicast address family view
Predefined user roles
network-admin
Parameters
on-startup: Sets the overload bit upon system startup.
start-from-nbr system-id [ timeout1 [ nbr-timeout ] ]: Starts the nbr-timeout timer when the router begins to establish the neighbor relationship with the neighbor after system startup. If the neighbor relationship is formed within the nbr-timeout interval, IS-IS keeps the overload bit set. If not, the bit is cleared. IS-IS keeps the overload bit set within the timeout1 interval after the neighbor relationship is formed within the nbr-timeout interval.
· system-id—Specifies the neighbor.
· timeout1—The timeout1 interval is in the range of 5 to 86400 seconds, and the default is 600 seconds.
· nbr-timeout—The timer has an interval from 5 to 86400 seconds. The default is 1200 seconds.
timeout2: Sets the overload bit within the timeout2 interval after system startup. The interval is in the range of 5 to 86400 seconds, and the default is 600 seconds.
wait-for-bgp [ timeout3 ]: Starts the timeout3 timer for BGP convergence after system startup. If BGP is not converged within the timeout3 interval, IS-IS clears the overload bit. The value range for the timeout3 argument is 5 to 86400 seconds, and the default is 600 seconds.
wait-for-bgp4+ [ timeout3 ]: Starts the timeout3 timer for IPv6 BGP convergence after system startup. If IPv6 BGP is not converged within the timeout3 interval, IPv6 IS-IS clears the overload bit. The value range for the timeout3 argument is 5 to 86400 seconds, and the default is 600 seconds.
allow: Allows advertising address prefixes. By default, no address prefixes are allowed to be advertised when the overload bit is set.
external: Allows advertising IP address prefixes redistributed from other routing protocols with the allow keyword specified.
interlevel: Allows advertising IP address prefixes learned from different IS-IS levels with the allow keyword specified.
Usage guidelines
If the on-startup keyword is not specified, the command sets the overload bit immediately until the undo set-overload command is executed.
If the on-startup keyword is specified, IS-IS sets the overload bit upon system startup and keeps it set within the timeout2 interval.
Examples
# Set overload flag on the current router.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] set-overload
shutdown process
Use shutdown process to shut down an IS-IS process.
Use undo shutdown process to restart an IS-IS process.
Syntax
shutdown process
undo shutdown process
Default
IS-IS process is not shut down.
Views
IS-IS view
Predefined user roles
network-admin
Usage guidelines
Both this feature and IS-IS isolation can be used for IS-IS maintenance.
After you execute the shutdown process command for an IS-IS process, the process performs the following operations:
· Changes the state of all neighbors to down.
· Stops receiving and sending IS-IS packets.
· Clears its neighbor, LSDB, and IS-IS route information.
If the neighbors do not receive any hello packets from the IS-IS process within the hold time, they consider the process down and recalculate the routes.
After maintenance, you can use the undo shutdown process command to restart the IS-IS process for neighbor relationship re-establishment.
Examples
# Shut down IS-IS process 1.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] shutdown process
Related commands
isolate enable
snmp context-name
Use snmp context-name to set the context name for the SNMP object for managing IS-IS.
Use undo snmp context-name to restore the default.
Syntax
snmp context-name context-name
undo snmp context-name
Default
No context name is set for the SNMP object for managing IS-IS.
Views
IS-IS view
Predefined user roles
network-admin
Parameters
context-name: Specifies a context name, a case-sensitive string of 1 to 32 characters.
Examples
# Configure the context name as isis for the SNMP object for managing IS-IS process 1.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] snmp context-name isis
snmp-agent trap enable isis
Use snmp-agent trap enable isis to enable IS-IS SNMP notifications.
Use undo snmp-agent trap enable isis to disable IS-IS SNMP notifications.
Syntax
snmp-agent trap enable isis [ adjacency-state-change | area-mismatch | authentication | authentication-type | buffsize-mismatch | id-length-mismatch | lsdboverload-state-change | lsp-corrupt | lsp-parse-error | lsp-size-exceeded | manual-address-drop | max-seq-exceeded | maxarea-mismatch | own-lsp-purge | protocol-support | rejected-adjacency | skip-sequence-number | system-id-conflict | version-skew ] *
undo snmp-agent trap enable isis [ adjacency-state-change | area-mismatch | authentication | authentication-type | buffsize-mismatch | id-length-mismatch | lsdboverload-state-change | lsp-corrupt | lsp-parse-error | lsp-size-exceeded | manual-address-drop | max-seq-exceeded | maxarea-mismatch | own-lsp-purge | protocol-support | rejected-adjacency | skip-sequence-number | system-id-conflict | version-skew ] *
Default
IS-IS SNMP notifications are enabled.
Views
System view
Predefined user roles
network-admin
Parameters
adjacency-state-change: Specifies notifications about IS-IS adjacency status changes.
area-mismatch: Specifies notifications about area address mismatches between hello packets.
authentication: Specifies notifications about authentication failures of IS-IS packets.
authentication-type: Specifies notifications about authentication type errors of IS-IS packets.
buffsize-mismatch: Specifies notifications about buffer size mismatches for LSPs.
id-length-mismatch: Specifies notifications about system ID length mismatches of IS-IS packets.
lsdboverload-state-change: Specifies notifications about LSDB overload state changes.
lsp-corrupt: Specifies notifications about LSP checksum errors in the LSDB.
lsp-parse-error: Specifies notifications about LSP packet parse failures.
lsp-size-exceeded: Specifies notifications about propagation failures caused by oversized LSPs.
manual-address-drop: Specifies notifications about manually configured area addresses that have been dropped.
max-seq-exceeded: Specifies notifications about attempts to exceed the maximum LSP sequence number.
maxarea-mismatch: Specifies notifications about maximum area address mismatches of hello packets.
own-lsp-purge: Specifies notifications about attempts to remove the local LSP.
protocol-support: Specifies notifications about supported-protocol mismatches.
rejected-adjacency: Specifies notifications about adjacency creation failures.
skip-sequence-number: Specifies notifications about LSP sequence number duplications.
system-id-conflict: Specifies notifications about system ID conflicts.
version-skew: Specifies notifications about hello packet version mismatches.
Usage guidelines
If you do not specify a notification, this command enables all IS-IS SNMP notifications.
If no IS-IS process exists, the configuration is not allowed.
This function does not take effect if all configured IS-IS processes are deleted.
Examples
# Disable IS-IS SNMP notifications.
<Sysname> system-view
[Sysname] undo snmp-agent trap enable isis
summary
Use summary to configure a summary route.
Use undo summary to remove a summary route.
Syntax
In IS-IS IPv4 unicast address family view:
summary ip-address { mask-length | mask } [ avoid-feedback | generate_null0_route | [ level-1 | level-1-2 | level-2 ] | tag tag ] *
undo summary ip-address { mask-length | mask } [ level-1 | level-1-2 | level-2 ]
In IS-IS IPv6 unicast address family view:
summary ipv6-prefix prefix-length [ avoid-feedback | generate_null0_route | [ level-1 | level-1-2 | level-2 ] | tag tag ] *
undo summary ipv6-prefix prefix-length [ level-1 | level-1-2 | level-2 ]
Default
No summary route is configured.
Views
IS-IS IPv4 unicast address family view
IS-IS IPv6 unicast address family view
Predefined user roles
network-admin
Parameters
ip-address: Specifies the destination IP address of the summary route.
mask-length: Specifies the mask length of the summary route, in the range of 0 to 32.
mask: Specifies the mask of the destination IP address, in dotted decimal notation.
ipv6-prefix: Specifies an IPv6 prefix for the summary route.
prefix-length: Specifies the length of the IPv6 prefix, in the range of 0 to 128.
avoid-feedback: Avoids learning summary routes by route calculation.
generate_null0_route: Generates the Null 0 route to avoid routing loops.
level-1: Summarizes only the routes redistributed to Level-1.
level-1-2: Summarizes the routes redistributed to both Level-1 and Level-2.
level-2: Summarizes only the routes redistributed to Level-2.
tag tag: Specifies a management tag in the range of 1 to 4294967295.
Usage guidelines
To reduce the size of the routing table, as well as the size of LSP and LSDB generated by the router, summarize multiple contiguous networks into a single network. You can summarize native IS-IS routes and redistributed routes. After summarization, the cost of the summary route is the smallest cost of the summarized routes.
If no level is specified, only level-2 routes are summarized.
The router summarizes only routes generated from local LSPs.
Examples
# Configure a summary route of 202.0.0.0/8.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] address-family ipv4
[Sysname-isis-1-ipv4] summary 202.0.0.0 255.0.0.0
te attribute enable
Use te attribute enable to enable TE attribute advertisement for an IS-IS process.
Use undo te attribute enable to disable TE attribute advertisement for an IS-IS process.
Syntax
te attribute enable [ level-1 | level-2 ]
undo attribute enable [ level-1 | level-2 ]
Default
IS-IS does not advertise TE attributes.
Views
IS-IS view
Predefined user roles
network-admin
Parameters
level-1: Advertises TE attributes at Level-1 areas.
level-2: Advertises TE attributes at the Level-2 area.
Usage guidelines
This feature enables IS-IS to advertise TE attributes in the sub-TLVs of extended IS reachability TLVs (TLV type 22) for use by MPLS TE, SR TE, and SRv6 TE.
To enable TE attribute advertisement for an IS-IS process, you can also use the mpls te enable command. Only TE and SR-TE can use the advertised TE attribute information.
If you execute this command multiple times, the most recent configuration takes effect. For example, if you execute the te attribute enable command and then the te attribute enable level-1 command, TE attribute advertisement is enabled at Level-1 areas and is disabled at the Level-2 area.
If you do not specify a level, this command enables IS-IS to advertise TE attributes at Level-1 and Level-2 areas. In this case, executing the undo te attribute enable level-1 command disables TE attribute advertisement at Level-1 areas. TE attribute advertisement is still enabled at the Level-2 area. Similarly, the undo te attribute enable level-2 command only disables TE attribute advertisement at the Level-2 area.
You can enable TE attribute advertisement only when the IS-IS cost style is wide, compatible, or wide-compatible.
Examples
# Enable TE attribute advertisement for IS-IS process 1.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] cost-style wide-compatible
[Sysname-isis-1] te attribute enable
Related commands
cost-style
mpls te enable (MPLS Command Reference)
timer aging-lsp-lifetime
Use timer aging-lsp-lifetime to set the lifetime for expired LSPs in the LSDB.
Use undo timer aging-lsp-lifetime to restore the default.
Syntax
timer aging-lsp-lifetime { non-self-originate | self-originate } lifetime
undo timer aging-lsp-lifetime { non-self-originate | self-originate }
Default
The lifetime for an expired LSP varies by the source of this LSP as follows:
· If this LSP is generated by the local device, the lifetime is 1200 seconds.
· If this LSP is received from another device, the lifetime is 60 seconds.
Views
IS-IS view
Predefined user roles
network-admin
Parameters
non-self-originate: Specifies the LSPs generated by the local device.
self-originate: Specifies the LSPs received from other devices.
lifetime: Sets the lifetime for expired LSPs in seconds. The value range for this argument is 1 to 65535. An expired LSP will be deleted from the LSDB after its lifetime elapses.
Usage guidelines
Each IS-IS LSP has a maximum lifetime. After a device receives an LSP, the lifetime of this LSP starts decreasing. The LSP will expire if the following conditions exist:
· The device does not receive any update for the LSP.
· The lifetime of the LSP has decreased to 0.
If the device still does not receive any update for the expired LSP within a specific period of time, it will delete the LSP from its LSDB.
Some LSPs might expire before flooding and are deleted from the LSDB, especially when IS-IS has multiple neighbors and the LSDB contains a large number of LSPs. As a result, IS-IS might take a long time to complete route learning, if the LSP advertisement sources cannot update LSPs in time.
To resolve this issue, increase the lifetime for expired LSPs by using this command. Then, IS-IS can flood out the expired LSPs before they are deleted, which ensures the LSP advertisement sources can update LSPs in time.
Examples
# Allow received LSPs to exist in the LSDB for 1000 seconds after they expire.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] timer aging-lsp-lifetime non-self-originate 1000
Related commands
timer lsp-refresh
timer lsp-max-age
timer lsp-arrival
Use timer lsp-arrival to set the LSP receiving interval.
Use undo timer lsp-arrival to remove the configuration.
Syntax
timer lsp-arrival maximum-interval [ minimum-interval [ incremental-interval ] ] [ level-1 | level-2 ]
undo timer lsp-arrival [ level-1 | level-2 ]
Default
The LSP receiving interval is not set.
Views
IS-IS view
Predefined user roles
network-admin
Parameters
maximum-interval: Specifies the maximum LSP receiving interval in the range of 1 to 120 seconds.
minimum-interval: Specifies the minimum LSP receiving interval in the range of 10 to 60000 milliseconds.
incremental-interval: Specifies the incremental interval in the range of 10 to 60000 milliseconds.
level-1: Applies the intervals to Level-1.
level-2: Applies the intervals to Level-2.
Usage guidelines
When the network is stable, IS-IS uses the minimum receiving interval. When network changes become frequent, the receiving interval increases by the incremental interval each time the same LSP is received until the maximum receiving interval is reached.
The minimum LSP receiving interval and the incremental interval cannot be greater than the maximum LSP receiving interval.
If no level is specified, the specified intervals apply to both Level-1 and Level-2.
Examples
# Set the maximum receiving interval, minimum receiving interval, and incremental interval for Level-1 LSPs to 10 seconds, 100 milliseconds, and 200 milliseconds, respectively.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] timer lsp-arrival 10 100 200 level-1
timer lsp-flood suppress-flapping
Use timer lsp-flood suppress-flapping to suppress LSP flooding when route flapping occurs.
Use undo timer lsp-flood suppress-flapping to remove the configuration.
Syntax
timer lsp-flood suppress-flapping delay-interval [ threshold threshold-value ] [ level-1 | level-2 ]
undo timer lsp-flood suppress-flapping [ level-1 | level-2 ]
Default
IS-IS does not suppress LSP flooding.
Views
IS-IS view
Predefined user roles
network-admin
Parameters
delay-interval: Specifies the delay time in the range of 0 to 65535 seconds.
threshold threshold-value: Specifies the number of route flaps that trigger the delay timer, in the range of 3 to 100. The default number is 5.
level-1: Applies the configuration to Level-1.
level-2: Applies the configuration to Level-2.
Usage guidelines
If no level is specified, the configuration applies to both Level-1 and Level-2.
Examples
# Suppress Level-1 LSP flooding for 5 seconds after the number of route flaps reaches 10.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] timer lsp-flood suppress-flapping 5 threshold 10 level-1
timer lsp-generation
Use timer lsp-generation to set the LSP generation interval.
Use undo timer lsp-generation to remove the configuration.
Syntax
timer lsp-generation maximum-interval [ minimum-interval [ incremental-interval ] ] [ level-1 | level-2 ]
undo timer lsp-generation [ level-1 | level-2 ]
Default
The maximum interval is 5 seconds, the minimum interval is 50 milliseconds, and the incremental interval is 200 milliseconds.
Views
IS-IS view
Predefined user roles
network-admin
Parameters
maximum-interval: Specifies the maximum interval in the range of 1 to 120 seconds.
minimum-interval: Specifies the minimum interval in the range of 10 to 60000 milliseconds.
incremental-interval: Specifies the incremental interval in the range of 10 to 60000 milliseconds.
level-1: Applies the intervals to Level-1.
level-2: Applies the intervals to Level-2. If no level is specified, the specified intervals apply to both Level-1 and Level-2.
Usage guidelines
By adjusting the LSP generation interval, you can prevent bandwidth and router resources from being over consumed due to frequent topology changes.
If you specify only the maximum-interval argument, the LSP generation interval is maximum-interval.
If you do not specify the incremental-interval argument, the LSP generation interval is in the range of minimum-interval to maximum-interval.
If you specify the incremental-interval argument, the LSP generation interval is as follows:
· When network changes are not frequent, the minimum-interval is adopted.
· When network changes are frequent, the LSP generation interval increases by incremental-interval × 2n-2 (n is the number of calculation times) each time a generation occurs until the maximum-interval is reached.
The minimum interval and the incremental interval cannot be greater than the maximum interval.
Examples
# Set the maximum interval, minimum interval, and incremental interval to 10 seconds, 100 milliseconds, and 200 milliseconds, respectively.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1]timer lsp-generation 10 100 200
timer lsp-generation suppress-flapping
Use timer lsp-generation suppress-flapping to suppress LSP generation when route flapping occurs.
Use undo timer lsp-generation suppress-flapping to remove the configuration.
Syntax
timer lsp-generation suppress-flapping delay-interval [ threshold threshold-value] [ level-1 | level-2 ]
undo timer lsp-generation suppress-flapping [ level-1 | level-2 ]
Default
IS-IS does not suppress LSP generation.
Views
IS-IS view
Predefined user roles
network-admin
Parameters
delay-interval: Specifies the delay time in the range of 0 to 65535 seconds.
threshold threshold-value: Specifies the number of route flaps that trigger the delay timer, in the range of 3 to 100. The default number is 5.
level-1: Applies the configuration to Level-1.
level-2: Applies the configuration to Level-2.
Usage guidelines
If no level is specified, the configuration applies to both Level-1 and Level-2.
Examples
# Suppress Level-1 LSP generation for 3 seconds after the number of route flaps reaches 10.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] timer lsp-generation suppress-flapping 3 threshold 10 level-1
timer lsp-max-age
Use timer lsp-max-age to set the LSP maximum age in the LSDB.
Use undo timer lsp-max-age to restore the default.
Syntax
timer lsp-max-age seconds
undo timer lsp-max-age
Default
The LSP maximum age in the LSDB is 1200 seconds.
Views
IS-IS view
Predefined user roles
network-admin
Parameters
seconds: Specifies the LSP maximum aging time in the range of 1 to 65535 seconds.
Usage guidelines
Each LSP has an age that decreases in the LSDB. Any LSP with an age of 0 is deleted from the LSDB. You can adjust the age value based on the scale of a network.
Examples
# Set the maximum LSP age to 1500 seconds.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] timer lsp-max-age 1500
Related commands
timer lsp-refresh
timer lsp-refresh
Use timer lsp-refresh to set the LSP refresh interval.
Use undo timer lsp-refresh to restore the default.
Syntax
timer lsp-refresh seconds
undo timer lsp-refresh
Default
The default LSP refresh interval is 900 seconds.
Views
IS-IS view
Predefined user roles
network-admin
Parameters
seconds: Specifies the LSP refresh interval in the range of 1 to 65534 seconds.
Usage guidelines
Each router refreshes its LSPs at a configurable interval and sends them to other routers to achieve the following purposes:
· Prevent valid routes from aging out.
· Synchronize LSPs in the network.
A smaller refresh interval speeds up network convergence but consumes more bandwidth.
To refresh LSPs before they are aged out, the interval configured by the timer lsp-refresh command must be smaller than that configured by the timer lsp-max-age command.
Examples
# Set the LSP refresh interval to 1500 seconds.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] timer lsp-refresh 1500
Related commands
timer lsp-max-age
timer purge-zero-lsp route-calculate-delay
Use timer purge-zero-lsp route-calculate-delay to suppress route calculation after fragment 0 of a purge LSP is received.
Use undo timer purge-zero-lsp route-calculate-delay to remove the configuration.
Syntax
timer purge-zero-lsp route-calculate-delay delay-interval [ level-1 | level-2 ]
undo timer purge-zero-lsp route-calculate-delay [ level-1 | level-2 ]
Default
IS-IS suppresses route calculation for 10 seconds after fragment 0 of a purge LSP is received.
Views
IS-IS view
Predefined user roles
network-admin
Parameters
delay-interval: Specifies the delay time in the range of 0 to 65535 seconds.
level-1: Applies the delay time to Level-1.
level-2: Applies the delay time to Level-2.
Usage guidelines
If no level is specified, the delay time applies to both Level-1 and Level-2.
Examples
# Suppress route calculation for 15 seconds after fragment 0 of a purge LSP is received.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] timer purge-zero-lsp route-calculate-delay 15 level-1
timer route-calculate suppress-flapping
Use timer route-calculate suppress-flapping to suppress route calculation when route flapping occurs.
Use undo timer route-calculate suppress-flapping to remove the configuration.
Syntax
timer route-calculate suppress-flapping delay-interval [ threshold threshold-value ] [ level-1 | level-2 ]
undo timer route-calculate suppress-flapping [ level-1 | level-2 ]
Default
IS-IS does not suppress route calculation.
Views
IS-IS view
Predefined user roles
network-admin
Parameters
delay-interval: Specifies the delay time in the range of 0 to 65535 seconds.
threshold threshold-value: Specifies the number of route flaps that trigger the delay timer, in the range of 3 to 100. The default number is 5.
level-1: Applies the configuration to Level-1.
level-2: Applies the configuration to Level-2.
Usage guidelines
If no level is specified, the configuration applies to both Level-1 and Level-2.
Examples
# Suppress route calculation for 5 seconds after the number of route flaps reaches 10.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] timer route-calculate suppress-flapping 5 threshold 10 level-1
timer spf
Use timer spf to set the SPF calculation interval.
Use undo timer spf to restore the default.
Syntax
timer spf { maximum-interval [ minimum-interval [ incremental-interval [ conservative ] ] ] | millisecond millisecond-interval } [ exclude-prc ]
undo timer spf
Default
The maximum SPF calculation interval is 5 seconds, the minimum interval is 50 milliseconds, and the incremental interval is 200 milliseconds.
Views
IS-IS view
IS-IS IPv6 unicast address family view
Predefined user roles
network-admin
Parameters
maximum-interval: Specifies the maximum SPF calculation interval in the range of 1 to 120 seconds.
minimum-interval: Specifies the minimum SPF calculation interval in the range of 10 to 60000 milliseconds.
incremental-interval: Specifies the incremental SPF calculation interval in the range of 10 to 60000 milliseconds.
conservative: Keeps the maximum interval when route flapping occurs. If you do not specify this keyword, the minimum interval is used after SPF calculation is performed at the maximum interval for three consecutive times.
millisecond millisecond-interval: Specifies the fixed SPF calculation interval in the range of 0 to 10000 milliseconds.
exclude-prc: Configures IS-IS to perform SPF calculation immediately upon route prefix changes.
Usage guidelines
Based on the LSDB, an IS-IS router uses the SPF algorithm to calculate a shortest path tree with itself being the root, and uses the shortest path tree to determine the next hop to a destination network. By adjusting the SPF calculation interval, you can prevent bandwidth and router resources from being overused due to frequent topology changes.
When network changes are not frequent, the minimum-interval is adopted. If network changes become frequent, the SPF calculation interval increases by the incremental-interval each time a generation happens until the maximum-interval is reached.
The minimum interval and the incremental interval cannot be greater than the maximum interval.
As a best practice to speed up route convergence triggered by route prefix changes, specify the exclude-prc keyword for the timer spf command.
Examples
# Set the maximum interval to 10 seconds, the minimum interval to 100 milliseconds, and the incremental interval to 300 milliseconds, respectively.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] timer spf 10 100 300
virtual-system
Use virtual-system to configure a virtual system ID for the IS-IS process.
Use undo virtual-system to remove a virtual system ID.
Syntax
virtual-system virtual-system-id
undo virtual-system virtual-system-id
Default
No virtual system ID is configured.
Views
IS-IS view
Predefined user roles
network-admin
Parameters
virtual-system-id: Specifies a virtual system ID for the IS-IS process.
Examples
# Set a virtual system ID of 2222.2222.2222 for IS-IS process 1.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] virtual-system 2222.2222.2222