[j-nsp] M10i commist sysc failed

[jjsyed at aol.com]

Phil,
 
  
Why is the redundant RE's status "present"? If it is working properly it generally says, "backup", right? If it is not working, it should show a state of "failed". When the RE is in this state is there a syslog/snmptrap sent indicating this? 
 
This is a big problem if one of the RE's is not functioning and the master RE knows nothing about it. We lose the redundancy when the master RE fails.
 
Please advice
 
js
 
-----Original Message-----
From: Phil Shafer <phil at juniper.net>
To: jjsyed at aol.com
Cc: juniper-nsp at puck.nether.net
Sent: Wed, 10 Aug 2005 11:37:46 -0400
Subject: Re: [j-nsp] M10i commist sysc failed 


jjsyed at aol.com writes:
>When we try to do "commit sync" on M10i's after making changes, the
>operation does not complete. It takes for ever.

The original timeouts were insanely large (hours).  Modern sw
versions (7.2) trim it to something reasonable (seconds).  This
was PR 55247.

This is assuming the other RE is up and working correctly, and
that the sw version difference between the REs isn't too big
a bump.

Thanks,
 Phil