Supported Platforms
Understanding Backup Routers
If Junos OS is running on a routing device, you might want to specify a backup router. The purpose of the backup router is not to forward transit traffic. It is for local management of the routing device, by way of the out-of-band management interface (fxp0 or me0, for example). Traffic is not forwarded between the Packet Forwarding Engine and the management interface. You cannot route traffic between the management interface and the physical interfaces in the chassis.
The Junos OS process responsible for establishing routes is known as the routing protocol process (rpd). The backup router allows the routing device to install a route to a management network, before the routing protocol process is up and running. A backup router can be used during the initial boot process of Junos OS, before any routing protocols have converged. It allows the device to establish a Layer 3 connection quickly, thus keeping management unavailability to a minimum. In selecting a backup router, it is common practice to choose the default gateway of the management network that is directly connected to your routing device.
It is important to make sure that the specified backup router address is reachable and directly connected. The backup router address should be an address that is directly connected to the management interface.
 | Note: Router A can be the backup router for Router B, and Router B can be the backup router for Router A if the management interface of each router is connected to an interface on the other router, thus providing the necessary reachability. |
When the routing protocol process starts, the backup route (the route created by the backup router) is removed, and any default, static, or protocol-learned routes are installed.
If the routing device has a backup Routing Engine (usually RE1), the backup router remains active, unless nonstop active routing is configured.
