 | Copyright © 2009, Juniper Networks, Inc. All rights reserved. Trademark Notice. | |
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 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.
To disable adjacency down notification in IS-IS, include the no-adjacency-down-notification statement:
-
no-adjacency-down-notification;
You can include this statement at the following hierarchy levels:
To disable neighbor down notification in OSPF, include the no-neighbor-down-notification statement:
-
no-neighbor-down-notification;
You can include this statement at the following hierarchy levels:
| Copyright © 2009, Juniper Networks, Inc. All rights reserved. Trademark Notice. | |