The no form of this command administratively enables an entity.
In the config>router>isis context, the
shutdown command disables the IS-IS protocol instance. By default, the protocol is enabled,
no shutdown.
In the config>router>isis>interface context, the command disables the IS-IS interface. By default, the IS-IS interface is enabled,
no shutdown.
In the config>router>isis>interface ip-int-name>level context, the command disables the IS-IS interface for the level. By default, the IS-IS interface at the level is enabled,
no shutdown.
no shutdown — IS-IS entity is administratively enabled.
[no] isis
[isis-instance]
The IS-IS protocol instance is enabled with the no shutdown command in the
config>router>isis context. Alternatively, the IS-IS protocol instance is disabled with the
shutdown command in the
config>router>isis context.
The no form of the command deletes the IS-IS protocol instance. Deleting the protocol instance removes all configuration parameters for this IS-IS instance.
[no
] authentication-check
When no authentication-check is configured, authentication PDUs are generated and IS-IS PDUs are authenticated on receipt. However, mismatches cause an event to be generated and will not be rejected.
The no form of this command allows authentication mismatches to be accepted and generate a log event.
To configure authentication on the global level, configure this command in the config>router>isis context. When this parameter is configured on the global level, all PDUs are authenticated including the hello PDU.
To override the global setting for a specific level, configure the authentication-key command in the
config>router>isis>level context. When configured within the specific level, hello PDUs are not authenticated.
The no form of the command removes the authentication key.
Specifies the key is entered in a more complex encrypted form. If the
hash2 parameter is not used, the less encrypted
hash form is assumed.
The no form of the command disables authentication.
The no form of the command suppresses authentication of CSNP packets.
The no form of the command reverts to the default value.
csnp-interval 5 — CSN PDUs are sent every 5 seconds for point-to-point interfaces.
The no form of the command removes the description from the associated link-group.
[no
] member
interface-name
The no form of the command removes the specified interface from the associated link-group.
The no form of the command reverts the oper-members limit to 1.
The no form of the command reverts the revert-members threshold back to the default which is equal to the oper-member threshold value.
The no form of the command reverts the offset value to 0.
The no form of the command reverts the offset value to 0.
The no form of the command reverts the offset value to 0.
The no form of this command deletes the specified default metric and reverts to using the system default of 10.
The no form of this command deletes the specified default metric and reverts to using the system default of 10.
The no form of this command restores the default settings and re-enables IGP-LDP synchronization on all interfaces participating in the OSPF or IS-IS routing protocol and for which the ldp-sync-timer is configured.
[no
] export
policy-name [policy-name...up to 5 max]
If an aggregate command is also configured in the
config>router context, then the aggregation is applied before the export policy is applied.
Routing policies are created in the config>router>policy-options context.
The no form of the command removes the specified
policy-name or all policies from the configuration if no
policy-name is specified.
no export — No export policy name is specified.
The no form of the command removes the parameters from the configuration.
The external-preference command configures the preference level of either IS-IS level 1 or IS-IS level 2 external routes. By default, the preferences are as listed in the table below.
The no form of the command disables graceful restart and removes all graceful restart configurations in the IS-IS instance.
When graceful-restart is enabled, the router can be a helper (meaning that the router is helping a neighbor to restart) or be a restarting router or both. The router supports only helper mode. This facilitates the graceful restart of neighbors but will not act as a restarting router (meaning that the router will not help the neighbors to restart).
The no helper-disable command enables helper support and is the default when graceful-restart is enabled.
[no
] hello-authentication
The no form of the command suppresses authentication of HELLO packets.
[no
] hello-padding {adaptive | loose | strict}
The no form of the command disables IS-IS hello padding.
Specifies the loose padding option; the loose padding may not be able to detect certain situations such as asymmetrical
LSP MTUs between the routing devices.
Specifies the strict padding option; this option is the most overhead-intensive but detects LSP MTU issues on both sides of a link.
The no form of the command specifies that IS-IS will not ignore LSP errors.
[no
] ignore-narrow-metric
The no form of the command specifies that IS-IS will not ignore these links.
When enabled, each IS-IS instance marks its packets with the IID TLV containing its unique 16-bit IID for the routing domain. You should shut/no shut the isis instance to make the change operational.
[no
] interface
ip-int-name
The no form of the command removes IS-IS from the interface.
The shutdown command in the
config>router>isis>interface context administratively disables IS-IS on the interface without affecting the IS-IS configuration.
[no
] bfd-enable
{ipv4
| ipv6
} [include-bfd-tlv]
The no form of this command removes BFD from the associated adjacency.
The no form of this command disables the functionality so that the router can only establish adjacencies in the standard instance 0.
When the hello authentication key is configured in the config>router>isis>interface context, it applies to all levels configured for the interface.
The no form of the command removes the authentication-key from the configuration.
Specifies the key is entered in a more complex encrypted form. If the
hash2 parameter is not used, the less encrypted
hash form is assumed.
The no form of the command disables hello authentication.
The no form of the command to reverts to the default value.
3 — Hello interval default for the designated intersystem.
9 — Hello interval default for non-designated intersystems.
The no form of the command reverts to the default value.
3 — The router can miss up to 3 hello messages before declaring the adjacency down.
The no form of this command removes the metric from the configuration.
The no form of this command deletes the specified IS-IS topology.
The no form of the command reverts to the default value.
broadcast — For IP interfaces on Ethernet or unknown type physical interfaces.
The no ipv4-multicast-routing form of the command results in none of the IS-IS routes being populated in the IPv4 multicast RTM and would be used if multicast is configured to use the unicast RTM for the RPF check.
The no ipv6-multicast-routing form of the command results in none of the IS-IS routes being populated in the IPv4 multicast RTM and would be used if multicast is configured to use the unicast RTM for the RPF check.
The no form of the command disables IPv4 on the IS-IS instance.
[no
] ipv6-routing
{native | mt
}
The no form of the command disables support for IS-IS IPv6 TLVs for IPv6 routing.
The no form of the command disables LDP over RSVP processing.
The config>router>isis context configures default global parameters for both Level 1 and Level 2 interfaces.
The config>router>isis>interface context configures IS-IS operational characteristics of the interface at Level 1 and/or Level 2. A logical interface can be configured on one Level 1 and one Level 2. In this case, each level can be configured independently and parameters must be removed independently.
Table 10 displays configuration combinations and the potential adjacencies that can be formed.
The no form of the command removes the level capability from the configuration.
In the config>router>isis context, changing the
level-capability performs a restart on the IS-IS protocol instance.
In the config>router>isis>interface context, changing the
level-capability performs a restart of IS-IS on the interface.
The user enables the remote LFA next-hop calculation by the IGP LFA SPF by appending the remote-lfa option. When this option is enabled in an IGP instance, SPF performs the remote LFA additional computation following the regular LFA next-hop calculation when the latter resulted in no protection for one or more prefixes which are resolved to a given interface.
The default action of the loopfree-alternate-exclude command, when not explicitly specified by the user in the prefix policy, is a “reject”. Thus, regardless if the user did or did not explicitly add the statement “default-action reject” to the prefix policy, a prefix that did not match any entry in the policy will be accepted into LFA SPF.
The no form deletes the exclude prefix policy.
If the user excluded the interface from LFA using the command loopfree-alternate-exclude, the LFA policy, if applied to the interface, has no effect.
The no form deletes the mapping of a route next-hop policy template to an OSPF or IS-IS interface.
The no form of this command re-instates the default value for this command.
The no form of the command reverts to the default value.
100 — LSPs are sent in 100 millisecond intervals.
Each LSP received is maintained in an LSP database until the lsp-lifetime expires unless the originating router refreshes the LSP. By default, each router refreshes its LSPs every 20 minutes (1200 seconds) so other routers will not age out the LSP.
The no form of the command reverts to the default value.
1200 — LSPs originated by the router should be valid for 1200 seconds (20 minutes).
This command configures the LSP MTU size. If the size value is changed from the default using CLI or SNMP, then IS-IS must be restarted in order for the change to take effect. This can be done by performing a
shutdown command and then a
no shutdown command in the
config>router>isis context. Note: Using the
exec command to execute a configuration file to change the LSP MTU-size from its default value will automatically bounce IS-IS for the change to take effect.
The no form of the command reverts to the default value.
lsp-wait lsp-wait [lsp-initial-wait [lsp-second-wait]]
The no form of this command disables support for the IPv4 topology (MT3) within the associated IS-IS instance.
The no form of this command disables support for the IPv6 topology (MT4) within the associated IS-IS instance.
The no form of this command deletes the specified IS-IS topology.
The no form of the command disables the submission of routes into the multicast RTM.
To prevent an interface from flooding LSPs, the optional blocked parameter can be specified. Configure mesh groups carefully. It is easy to created isolated islands that do not receive updates as (other) links fail.
The no form of the command removes the interface from the mesh group.
[no
] ipv6-unicast-disable
The no form of the command enables IS-IS IPv6 unicast routing for the interface.
The no form of the command reverts to the default value.
10 — A metric of 10 for the level on the interface is used.
[no
] advertise-passive-only
The no form of this command, disables this capability.
[no
] area-id
area-address
This command was previously named the net network-entity-title command. The
area-id command allows you to configure the area ID portion of NSAP addresses which identifies a point of connection to the network, such as a router interface, and is called a Network Service Access Point (NSAP). Addresses in the IS-IS protocol are based on the ISO NSAP addresses and Network Entity Titles (NETs), not IP addresses.
A maximum of 3 area addresses can be configured.
If multiple area-id commands are entered, the system ID of all subsequent entries must match the first
area address.
The no form of the command removes the area address.
none — No area address is assigned.
The overload command is cleared from the configuration after a reboot if overload-on-boot is configured with or without a timeout value. To keep the IS-IS router in the overload state indefinitely after rebooting, configure overload-on-boot with no timeout value or configure the overload command with no overload-on-boot command.
The overload command can be useful in circumstances where the router is overloaded or used prior to executing a
shutdown command to divert traffic around the router.
The no form of the command causes the router to exit the overload state.
The no overload command does not affect the
overload-on-boot function.
This state can be cleared with the config>router>isis>no overload command.
The no form of the command removes the overload-on-boot functionality from the configuration.
Use the
show router isis status command to display the administrative and operational state as well as all timers.
The no form of the command removes the POI functionality from the configuration.
The no form of the command removes the passive attribute.
passive — Service interfaces are passive.
no passive — All other interfaces are not passive.
The no form of the command reverts to the default value.
If the pre-FEC error rate of the associated DWDM port crosses the configured sd-threshold, this offset-value is added to the IS-IS interface metric. This parameter is only effective if the interface is associated with a DWDM port and the
sd-threshold value is configured under that port.
The no form of the command reverts the offset value to 0.
If the pre-FEC error rate of the associated DWDM port crosses the configured sf-threshold, this offset-value is added to the IS-IS interface metric. This parameter is only effective if the interface is associated with a DWDM port and the
sf-threshold value is configured under that port.
The no form of the command reverts the offset value to 0.
The no form of the command suppresses authentication of PSNP packets.
If the reference bandwidth is configured as 10 Gigabits (10,000,000,000), a 100 M/bps interface has a default metric of 100. In order for metrics in excess of 63 to be configured, wide metrics must be deployed. (See wide-metrics-only in the
config>router>isis context.)
The no form of the command reverts to the default value.
When rsvp-shortcut is enabled at the IGP instance level, all RSVP LSPs originating on this node are eligible by default as long as the destination address of the LSP, as configured in configure>router>mpls>lsp>to, corresponds to a router-id of a remote node. RSVP LSPs with a destination corresponding to an interface address or any other loopback interface address of a remote node are automatically not considered by IS-IS or OSPF. The user can, however, exclude a specific RSVP LSP from being used as a shortcut for resolving IGP routes by entering the
config>router>mpls>lsp>no igp-shortcut command.
This feature provides IGP with the capability to populate the multicast RTM with the prefix IP next-hop when both the rsvp-shortcut and the
multicast-import options are enabled in IGP. The unicast RTM can still make use of the tunnel next-hop for the same prefix. This change is made possible with the enhancement by which SPF keeps track of both the direct first hop and the tunneled first hop of a node which is added to the Dijkstra tree.
The no form of this command disables the resolution of IGP routes using RSVP shortcuts.
There are two mutually exclusive modes of operation for the prefix SID range on the router. In the global mode of operation, the user configures the global value and this IGP instance will assume the start label value is the lowest label value in the SRGB and the prefix SID index range size equal to the range size of the SRGB. Once one IGP instance selected the global option for the prefix SID range, all IGP instances on the system will be restricted to do the same. The user must shutdown the segment routing context and delete the
prefix-sid-range command in all IGP instances in order to change the SRGB. Once the SRGB is changed, the user must re-enter the
prefix-sid-range command again. The SRGB range change will be failed if an already allocated SID index/label goes out of range.
Cfg_SR_MTU is the MTU configured by the user for all SR tunnels within a given IGP instance using the above CLI. If no value was configured by the user, the SR tunnel MTU will be fully determined by the IGP interface calculation explained next.
IGP_Tunnel_MTU is the minimum of the IS-IS or OSPF interface MTU among all the ECMP paths or among the primary and LFA backup paths of this SR tunnel.
[no
] advertise-tunnel-link
The forwarding adjacency feature can be enabled independently from the IGP shortcut feature in CLI. If both rsvp-shortcut and
advertise-tunnel-link options are enabled for a given IGP instance, then the
advertise-tunnel-link will win.
Note that the igp-shortcut option under the LSP name governs the use of the LSP with both the
rsvp-shortcut and the
advertise-tunnel-link options in IGP. In other words, the user can exclude a specific RSVP LSP from being used as a forwarding adjacency by entering the command
config>router>mpls>lsp>no igp-shortcut.
The no form of this command disables forwarding adjacency and hence disables the advertisement of RSVP LSP into IGP.
The no form of the command reverts to the default value.
[no]
spf-wait spf-wait [
spf-initial-wait [
spf-second-wait]]
This command defines the maximum interval between two consecutive SPF calculations in seconds. Timers that determine when to initiate the first, second and subsequent SPF calculations after a topology change occurs can be controlled with this command. Subsequent SPF runs (if required) will occur at exponentially increasing intervals of the spf-second-wait interval. For example, if the
spf-second-wait interval is 1000, then the next SPF will run after 2000 milliseconds, and then next SPF will run after 4000 milliseconds, etc., until it reaches the
spf-wait value. The SPF interval will stay at
spf-wait value until there are no more SPF runs scheduled in that interval. After a full interval without any SPF runs, the SPF interval will drop back to
spf-initial-wait.
[no
] strict-adjacency-check
When disabled (no strict-adjacency-check), both routers only need to have one common address family to establish the adjacency.
[no
] unicast-import-disable
The no form of the command reverts to the default value.
