no-adjacency-down-notification (Protocols IS-IS)
Syntax
no-adjacency-down-notification;
Hierarchy Level
[edit logical-systems logical-system-name protocols isis interface interface-name], [edit protocols isis interface interface-name]
Description
Disable adjacency down notification for IS-IS to allow for migration from IS-IS to OSPF without disruption of the RSVP neighbors and associated RSVP-signaled label-switched paths (LSPs).
Whenever IS-IS is deactivated, the IS-IS adjacencies are brought down. IS-IS signals to RSVP to bring down any RSVP neighbors associated with the IS-IS adjacencies, and this further causes the associated LSPs signaled by RSVP to go down as well.
A similar process occurs whenever OSPF is deactivated. The OSPF neighbors are brought down. OSPF signals to RSVP to bring down any of the RSVP neighbors associated with the OSPF neighbors, and this further causes the associated LSPs signaled by RSVP to go down as well.
If you need to migrate from IS-IS to OSPF or from OSPF to IS-IS,
the internal gateway protocol (IGP) notification to RSVP for an adjacency
or neighbor down event needs to be ignored. Using the no-adjacency-down-notification or no-neighbor-down-notification statements, you can disable IS-IS adjacency down notification
or OSPF neighbor down notification, respectively, until the migration
is complete. The network administrator is responsible for configuring
the statements before the migration, and then removing them from the
configuration afterward, so that IGP notification can function normally.
Required Privilege Level
routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Release Information
Statement introduced in Junos OS Release 8.0.