Log in to ask questions, share your expertise, or stay connected to content you value. Don’t have a login? Learn how to become a member.
See matching posts in thread - Upgrade routing engine
See matching posts in thread - Routing-Engine Replacement with...
Question On a router with multiple Routing Engines, should AI-Scripts be installed on all the Routing Engines? Answer Yes, install AI-Scripts on each Routing Engine running Junos OS Release 11.4 or later
However, we recommend having separate Routing Engine IDs configured for each Routing Engine, when using SNMPv3
P art 3 of 5 of Making Scripts Robust Previous Article: Making Scripts Robust: Checking Status Next Article: Making Scripts Robust: Recovering from Power Loss or Routing Engine Restart NOTE: This applies to SLAX version 1.0 and higher. Handling Routing Engine Switchovers “There is nothing permanent except change.” – Heraclitus If your script is running on a Junos device with multiple routing engines (REs), your device will very likely change operation from one RE to the other at some point
Coordinate XML RPC Data Between Routing Engines For SLAX version 1.0 and higher, you can get or set information between Routing Engines using a script. One example of this could be updating utility MIB information on both Routing Engines, since no utility MIB data synchronization is provided by Junos OS
Sometimes you need to get or set information between Routing Engines using a script. One example of this could be updating utility MIB information on both Routing Engines, since no utility MIB data synchronization is provided by Junos OS
Coordinate XML RPC Data Across Routing Engines in SLAX For SLAX version 1.0 and higher, there may be times when your Junos OS Automation script needs to share information with another script in the other Routing Engine, and you don't want to rely on connectivity between each Routing Engine's fxp0 interface
The document titled Coordinating XML RPC Data Across Routing Engines in SLAX has an example of sharing information with another script in the other Routing Engine that's done without relying on the connectivity between each Routing Engine's fxp0 interface
Part 4 of 5 of Making Scripts Robust Previous Article: Making Scripts Robust: Handling Routing Engine Switchovers Next Article: Making Scripts Robust: Managing Retries NOTE: This applies to SLAX version 1.0 and higher. Recovering from Power Loss or Routing Engine Restart “There is only one day left, always starting over: it is given to us at dawn and taken away from us at dusk.” -- Jean-Paul Sartre One thing is certain: every computerized device will either be rebooted or power-cycled