If a routing platform has dual Routing Engines, you must initially configure each routing platform independently. The sequence is irrelevant.
Configure the hostnames and addresses of the two Routing Engines using configuration groups at the [edit groups] hierarchy level. Use the reserved configuration group re0 for the Routing Engine in slot 0 and re1 for the Routing Engine in slot 1 to define properties specific to the individual Routing Engines. Configuring re0 and re1 groups enables both Routing Engines to use the same configuration file.
Use the apply-groups statement to reproduce the configuration group information in the main part of the configuration.
The commit synchronize command commits the same configuration on both Routing Engines. The command makes the active or applied configuration the same for both Routing Engines with the exception of the groups, re0 being applied to only RE0 and re1 being applied only to RE1. If you do not synchronize the configurations between two Routing Engines and one of them fails, the routing platform may not forward traffic correctly, because the backup Routing Engine may have a different configuration.
To initially configure a routing platform with dual Routing Engines, follow these steps:
- [edit]
- root@# edit groups
- [edit groups]
- root@# set re0 system host-name router1
- root@# set re0 interfaces fxp0 unit 0 family
inet address 10.10.10.1/24
- root@# set re0 system host-name router2
- root@# set re1 interfaces fxp0 unit 0 family
inet address 10.10.10.2/24
- [edit]
- root@# set system domain-name domain-name
- [edit groups]
- root@# set re0 interfaces lo0 unit 0 family
inet address 2.2.2.1/32
- root@# set re1 interfaces lo0 unit 0 family
inet address 2.2.2.2/32
- [edit groups]
- root@# top
- [edit]
- root@# set apply-groups [re0 re1]
- [edit]
- root@# set chassis redundancy routing-engine
0 master
- root@# set chassis redundancy routing-engine
1 backup
- root@# set chassis redundancy routing-engine
graceful-switchover
- [edit]
- user@host> commit synchronize
- root@#
- {master}
- user@host> request system snapshot
The root file system is backed up to /altroot, and /config is backed up to /altconfig. The root and /config file systems are on the routing platform’s CompactFlash card, and the /altroot and /altconfig file systems are on the routing platform’s hard disk.
![]() |
Note: After you issue the request system snapshot command, you cannot return to the previous version of the software, because the running copy and backup copy of the software are identical. |