Hi,
Then, this is likely that you'll have to go on site, remove/insert the faulty
RE, log onto the RE console port and check boot sequence ('sysctl -a | grep
bootdevs' in shell. Normally, you should have pcmcia, CF and disk), then
eventually check/replace CF, etc.
If you have a valid contract with Juniper, it's maybe worth opening a case with
JTAC (in this case, be sure to take at least 'request support info', 'sh log
messages' and 'sh log chassisd' at the time of the issue - RE moved to
"present" state - before doing anything on the node).
Besides, if someone here knows a method to remotely recover from this "present"
state, I would be (very) happy to learn how :)
Julien.
> -----Message d'origine-----
> De : [EMAIL PROTECTED] [mailto:juniper-nsp-
> [EMAIL PROTECTED] De la part de Phil Bedard
> Envoyé : mardi 8 janvier 2008 05:32
> À : [EMAIL PROTECTED]
> Cc : juniper-nsp@puck.nether.net; Guy Davies
> Objet : Re: [j-nsp] Juniper M10i n00b question
>
> To give some background on Chris' problem, the backup RE is only in a
> "Present" state and not "Backup" so I believe it is probably dead in
> some way or in a non-booted state. I didn't know of a way to reset
> the power to that slot via JunOS and console was unresponsive.
>
> Phil
>
> On Jan 7, 2008, at 5:01 PM, [EMAIL PROTECTED] wrote:
>
> > Or just log into the cli of the other one and reboot it.
> >
> > RE0> request routing-engine login other-routing-engine
> >
> > (Doing this little part always makes me feel better to make sure I'm
> > not rebooting the active one):
> >
> > RE1> show route
> > error: the routing subsystem is not running
> >
> > RE1> request system reboot
> >
> >
> >
> >
> >
> > On Jan 7, 2008 3:08 PM, Guy Davies <[EMAIL PROTECTED]> wrote:
> >> request system reboot other-routing-engine
> >>
> >> http://www.juniper.net/techpubs/software/junos/junos83/swcmdref83-
> basics-services/request-system-reboot-command.html#request-system-
> reboot-command
> >>
> >> regards,
> >>
> >> Guy
> >>
> >>
> >> On 07/01/2008, Scott Weeks <[EMAIL PROTECTED]> wrote:
> >>>
> >>>
> >>> --- [EMAIL PROTECTED] wrote:
> >>> From: Chris <[EMAIL PROTECTED]>
> >>>
> >>> Is it possible to reboot a routing engine without having to pull
> and
> >>> reinsert it (e.g. via the JunOS CLI)? Can't seem to find anything
> >>> that would
> >>> suggest so.
> >>> -----------------------------------------
> >>>
> >>> RE0> request system reboot
> >>>
> >>> scott
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>> -----------------------------
> >>> _______________________________________________
> >>> juniper-nsp mailing list juniper-nsp@puck.nether.net
> >>> https://puck.nether.net/mailman/listinfo/juniper-nsp
> >>>
> >> _______________________________________________
> >> juniper-nsp mailing list juniper-nsp@puck.nether.net
> >> https://puck.nether.net/mailman/listinfo/juniper-nsp
> >>
> > _______________________________________________
> > juniper-nsp mailing list juniper-nsp@puck.nether.net
> > https://puck.nether.net/mailman/listinfo/juniper-nsp
>
> _______________________________________________
> juniper-nsp mailing list juniper-nsp@puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
