f your router has two Routing Engines, you can manually direct one Routing Engine to synchronize its configuration with the other by issuing the
commit synchronize
command. The Routing Engine on which you execute this command (requesting Routing Engine) copies and loads its candidate configuration to the other (responding Routing Engine). Both Routing Engines then perform a syntax check on the candidate configuration file being committed. If no errors are found, the configuration is activated and becomes the current operational configuration on both Routing Engines. For example, if you are logged in to re1 (
requesting Routing Engine)
and you want re0
(responding Routing Engine) to have the same configuration as re1
, issue the commit synchronize
command on re1
. re1
copies and loads its candidate configuration to re0
. Both Routing Engines then perform a syntax check on the candidate configuration file being committed. If no errors are found, re1
's candidate configuration is activated and becomes the current operational configuration on both Routing Engines.Note - When you issue the
commit synchronize
command, you must use the apply groups re0
and re1.
For information about how to use the apply groups
statement, see Apply a Configuration Group. To synchronize a Routing Engine's current operational configuration file with the other, log in to the Routing Engine from which you want to synchronize and issue the
commit synchronize
command: [edit]
user@host#commit
synchronize
commit complete
[edit]
user@host#
Example: Apply Groups Re0 and Re1
The following example shows apply groups
re0
and re1
with some configuration data that might be different on re0
and re1
.re0 {
system {
host-name my_router_RE0;
}
interfaces {
fxp0 {
unit 0 {
family inet {
address 192.168.15.49/24;
}
family iso;
}
}
}
}
re1 {
system {
host-name my_router_RE1;
}
interfaces {
fxp0 {
unit 0 {
family inet {
address 192.168.15.50/24;
}
family iso;
}
}
}
}
Example: Set Apply Groups Re0 and Re1
[edit]
user@host# set apply-groups [re0 re1]
[edit]
user@host#
No comments:
Post a Comment