JUNOS Internet Software Network Operations Guide: Hardware
480 ! Manually Configuring Master and Backup Routing Engines
! Backup—If a Routing Engine is configured to be the backup, it does not
maintain routing tables or communicate with Packet Forwarding Engine or
chassis components. However, it runs through its memory check and boot
sequence to the point of displaying a login prompt. A backup Routing Engine
supports full management access through the Ethernet, console, and auxiliary
ports, and can communicate with the master Routing Engine. Additionally, a
backup Routing Engine responds to the Routing Engine
request chassis
routing-engine master switch command. The backup Routing Engine maintains a
connection with the master Routing Engine and monitors the master Routing
Engine. If the connection is broken, you can switch mastership by entering the
switchover command. If the master Routing Engine is hot-swapped out of the
system, the backup takes over control of the system as the new master Routing
Engine. Once a Routing Engine becomes master, it resets the switch plane and
downloads its own version of the microkernel to the Packet Forwarding Engine
components.
! Disabled—A disabled Routing Engine has progressed through its memory check
and boot sequence to the point of displaying a login prompt (similar to backup
state) but does not respond to a
request chassis routing-engine master switch
command. A Routing Engine in disabled state supports full management access
through the Ethernet, console, and auxiliary ports, and can communicate with
the master Routing Engine. A disabled Routing Engine does not participate in a
mastership election. To move from disabled state to backup state, the Routing
Engine must be reconfigured to be the backup Routing Engine.
Action To configure RE1 to be the default master, issue the following CLI command in
configuration mode at the [
edit] hierarchy level:
For slot 0:
[edit]
user@host# set chassis redundancy routing-engine 1 master
[edit]
user@host# commit
For slot 1:
[edit]
user@host# set chassis redundancy routing-engine 0 backup
[edit]
user@host# commit
Action To view the Routing Engine mastership/backup status, use the following CLI
command in operational mode:
user@host> show chassis routing-engine