I suppose that synchronizes them, but gives re0 & re1 the same host-name &
fxp0 inet address ?
Interesting.
N.
-----Original Message-----
From: Wilson, Michael [mailto:mkwilson@uslec.com]
Sent: 09 January 2002 18:14
To: Stirling, Neil [MOP:4625:EXCH]
Subject: RE: [j-nsp] Commit attribute to back-up RE
This feature is in release 5.1R2.4 : commit synchronize.
It is supposed to copy and commit the config to the backup re.
-----Original Message-----
From: Neil Stirling [mailto:neil.stirling@nortelnetworks.com]
Sent: Wednesday, January 09, 2002 1:06 PM
To: juniper-nsp@puck.nether.net
Subject: [j-nsp] Commit attribute to back-up RE
All,
A general question regarding the ability to quick-copy config's to the
backup re;
Currently to copy config's across to a back-up re I use the command 'file
copy <filename> re1:<path><filename>'.
However, this still needs me to login to the re and edit, load override,
change hostname & management fxp0 address & commit.
1. I'm trying to find out if there is a shorter way of committing to re0,
and then being able to commit to re1 as well (without actually going into
the re) ?
2. Failing that, can you specify 'commit override' but put in a set of
identifiers not to override host-name & fxp0 inet address (merge maybe) ?
Juniper guys - is there a planned release to allow a commit in re0: as well
as a tag to commit to re1:, but with a set of identifiers for changes, i.e.;
(from re0:)# commit re1 host-name
HMD_M160.1 fxp0 10.156.16.161 [enter]
Any help appreciated, not urgent, but interested nevertheless.
Cheers ;>).
Neil.
This archive was generated by hypermail 2b29 : Mon Aug 05 2002 - 10:42:38 EDT