[j-nsp] M10i commist sysc failed

[Jake Bourgeois]

Not sure if you tried this but if "request routing-engine login 
other-routing-engine" does not work, have someone in your datacenter 
move the oob console port to the console for the re that is currently in 
"present", this way you can see if the re is waiting for user input to 
boot or is scrolling some error messages- if no OOB or this does 
nothing, prob have no other choice but to toggle manually.

Thanks and Regards,
Jake Bourgeois




jjsyed at aol.com wrote:

>is there anyway to login to the backup RE which is in present state. I am not able to login it seems liek i may have to send somebody to toggled the backup RE ? or else is there any other way. 
> 
> 
>javed 
> 
>-----Original Message-----
>From: Tim Thorne <tthorne at plus.net>
>To: jjsyed at aol.com
>Cc: juniper-nsp at puck.nether.net
>Sent: Wed, 10 Aug 2005 15:35:10 +0100
>Subject: Re: [j-nsp] M10i commist sysc failed
>
>
>jjsyed at aol.com wrote:
>
>Hello,
>
>  
>
>>When we try to do "commit sync" on M10i's after making changes, the operation 
>>    
>>
>does not
>  
>
>>complete. It takes for ever. We then have to kill it, log out, log in as root 
>>    
>>
>and kill
>  
>
>>the session based on pid or terminal.  This happens because the master RE 
>>    
>>
>detects the
>  
>
>>slave RE as "present" but the slave RE is not functioning at all.  
>>
>>Why is the slave RE in state "present" if it is not functioning?
>>    
>>
>
>The box detects that there is RE hardware present, but the software
>on the backup RE has not loaded thus you can't synch to it. It sounds
>like you need to recover the backup RE and reload the software.
>
>  
>
>>Should "commit sync" not time out and the slave RE be declared as being in a 
>>    
>>
>failed state.
>
>Why not just commit the config?
>
>Regards,
>Tim Thorne
>_______________________________________________
>juniper-nsp mailing list juniper-nsp at puck.nether.net
>http://puck.nether.net/mailman/listinfo/juniper-nsp
>
>  
>