Avoiding Redundancy Problems ! 489
Chapter 36: Host Redundancy Overview
Step 3: Synchronize Configurations
Action Synchronize configurations between two Routing Engines using the synchronize
statement at the [edit] hierarchy level:
[edit]
user@host# commit synchronize
Sample Output
[edit]
root#
commit synchronize
re1: configuration check succeeds
re0: configuration check succeeds
re1: commit complete
re0: commit complete
What it Means When this statement is selected, the configuration file is copied to the other Routing
Engine, followed by a load override and a
commit. No user intervention is required.
Step 4: Copy a Configuration File from One Routing Engine to Another
Action You can copy a configuration file from one Routing Engine to another using the file
copy
command. The file is transferred through the internal Ethernet interface (FXP1
or
FXP2, depending on the router):
user@host> file copy <source> <destination>
Sample Output Copy a file on RE0 to RE1:
user@re0>
file copy /var/tmp/jinstall-6.0R3.3-domestic-signed.tgz
re1:/var/tmp1/
Check the result on RE1:
user@re1>
file list /var/tmp/
.pccardd=
jbundle-5.5R3.1-domestic.tgz*
jinstall-6.0R3.3-domestic-signed.tgz
sampled.pkts
What it Means The file jinstall-6.0R3.3-domestic-signed.tgz is copied from RE0 to RE1.
NOTE: Both Routing Engines must be running JUNOS software Release 5.1 or
higher. Use the
groups statement to ensure that differences in the configurations
for
RE0 and RE1 are applied.
NOTE: Both Routing Engines must have jbase version 4.1 or higher loaded.