Supported Platforms
Related Documentation
Configuring Nonstop Active Routing on EX Series Switches (CLI Procedure)
Nonstop active routing (NSR) provides a mechanism for transparent switchover of the Routing Engines without necessitating restart of supported routing protocols. Both Routing Engines are fully active in processing protocol sessions, and so each can take over for the other. The switchover is transparent to neighbors.
You can configure nonstop active routing on an EX Series switch with redundant Routing Engines to enable the transparent switchover of the Routing Engines in the event that the Routing Engines switch over. You can also disable nonstop active routing after you have enabled it.
To configure nonstop active routing:
- Enable graceful Routing Engine switchover (GRES):
[edit chassis redundancy]
user@switch# set graceful-switchover - Enable nonstop active routing (by default, nonstop active
routing is disabled):
[edit routing-options]
user@switch# set nonstop-routing - Synchronize configuration changes between the Routing
Engines:
[edit system]
user@switch# set commit synchronizeIf you try to commit the nonstop active routing configuration without including the commit synchronize statement, the commit fails.
 | Note: There is no requirement to start the two Routing Engines simultaneously. If the backup Routing Engine is not up when you commit synchronize, the candidate configuration is committed in the master Routing Engine and when the backup Routing Engine is inserted or comes online, its configuration is automatically synchronized with that of the master. |
 | Best Practice: After a graceful Routing Engine switchover, we recommend that you issue the clear interface statistics (interface-name | all) command to reset the cumulative values for local statistics on the new master Routing Engine. |
To disable nonstop active routing:
[edit routing-options]
user@switch# delete nonstop-routing
