Mailing List Archive

I am afraid not. With later configurations using graceful-switchover
you will receive a warning telling you you should do a commit sync
(from 6.0).

You have to do the commit sync - even in the later case
Gary

On Feb 19, 2004, at 3:15 PM, Kashif.Khawaja@Broadwing.com wrote:

> Hi All,
>
> With redundant REs installed in 5.1, do you "have" to do a "commit
> sync" to update
> configuration on the inactive RE or is there a way you can incorporate
> this functionality
> (in other words making it a default behavior) in the configuration so
> that any time a user
> performs a commit he/she is essentially executing a "commit sync"?
>
> Thanks!
> -Kashif.
> +++The information transmitted is intended only for the person or
> entity to which it is
> addressed and may contain confidential and/or privileged material.
> Any review,
> retransmission, dissemination or other use of, or taking of any action
> in reliance upon,
> this information by persons or entities other than the intended
> recipient is prohibited.
> If you received this in error, please contact the sender and destroy
> any copies of this
> document.+++
> _______________________________________________
> juniper-nsp mailing list juniper-nsp@puck.nether.net
> http://puck.nether.net/mailman/listinfo/juniper-nsp
>

I don't think so. We have had this same discussion with our Juniper SE, as
we have a mix of J routers out in the network, and it would be nice to have
our provisioners just enter one command for all routers, regardless of
redundancy. As it stands now, we have to spell out which routers they need
to do a commit sync on...

Regards,
-Jeff

-----Original Message-----
From: Kashif.Khawaja@Broadwing.com [mailto:Kashif.Khawaja@Broadwing.com]
Sent: Thursday, February 19, 2004 3:15 PM
To: juniper-nsp@puck.nether.net
Subject: [j-nsp] RE Redundancy --- Configuration Update


Hi All,

With redundant REs installed in 5.1, do you "have" to do a "commit sync" to
update
configuration on the inactive RE or is there a way you can incorporate this
functionality
(in other words making it a default behavior) in the configuration so that
any time a user
performs a commit he/she is essentially executing a "commit sync"?

Thanks!
-Kashif.
+++The information transmitted is intended only for the person or entity to
which it is
addressed and may contain confidential and/or privileged material. Any
review,
retransmission, dissemination or other use of, or taking of any action in
reliance upon,
this information by persons or entities other than the intended recipient is
prohibited.
If you received this in error, please contact the sender and destroy any
copies of this
document.+++
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
http://puck.nether.net/mailman/listinfo/juniper-nsp