JUNOS | Routing Engine Redundancy
Updated: Nov 29, 2019
Redundant Routing Engines are two Routing Engines that are installed in the same routing platform. One functions as the master, while the other stands by as a backup should the master Routing Engine fail. On routing platforms with dual Routing Engines, network reconvergence takes place more quickly than on routing platforms with a single Routing Engine.
When a Routing Engine is configured as master, it has full functionality. It receives and transmits routing information, builds and maintains routing tables, communicates with interfaces and Packet Forwarding Engine components, and has full control over the chassis. When a Routing Engine is configured to be the backup, it does not communicate with the Packet Forwarding Engine or chassis components.
For routers with two Routing Engines, you can configure which Routing Engine is the master and which is the backup. By default, the Routing Engine in slot 0 is the master (re0) and the one in slot 1 is the backup (re1)
#01) Check hardware status:
#02) Check both RE (routing-engine) current status:
In a router with two Routing Engines, one configuration should be shared between both Routing Engines. This ensures that both Routing Engine configurations are identical. Within this configuration, create two Routing Engine groups, one for each Routing Engine. Within these groups, you specify the Routing Engine–specific parameters.
#03) Apply commands below to synchronize both RE:
#04) The following configuration allows you to set the commit synchronize process by default. This allows you to do a "commit" command and by default it will synchronize the configuration on all members:
#05) Check replication: