What you are witnessing is the router bypassing the timers for the sake
of efficiency. It knows there is no primary RE in the slot, or that you
requested mastership control on the secondary.
The timers are for times when the router is not as keenly aware of such
problems and is looking for keepalive messages to detect them. Keep in
mind that you can also increase granularity by monitoring individual
processes on the primary RE to cause a failover if a process fails 3
times in rapid succession.
-- steve
-----Original Message-----
From: Andrew Smith [mailto:as160@yahoo.com]
Sent: Thursday, October 18, 2001 12:53 AM
To: juniper-nsp@puck.nether.net
Subject: [j-nsp] Redundancy configurations
Hi, all
I am a bit confused about the RE redundancy.
It says in the doc that,
"
The sequence of events is as follows:
1. After 20 seconds of keepalive loss, a message is
logged.
2. After 300 seconds of keepalive loss (default
setting), the backup Routing Engine
attempts to assume mastership. An alarm is generated
whenever the backup is active
and the display is updated with status."
My confusion comes in because if I pulled Active RE or
use cli to do a master toggle. The back up RE seems
to start process to come online right away. So, which
situations the above timers are applied to?
Thanks for the explanations.
---andrew
__________________________________________________
Do You Yahoo!?
Make a great connection at Yahoo! Personals.
http://personals.yahoo.com
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
This archive was generated by hypermail 2b29 : Mon Aug 05 2002 - 10:42:37 EDT