...and if you are not on the backup RE it also could mean that your rpd
daemon was trashing and therefor not restarted anymore.. again all
details you will see in the message log.
Josef
Friday, January 7, 2005, 10:29:50 PM, you wrote:
SH> It may also mean you're executing the command from the standby
SH> routing-engine, assuming there is one.? :)? Without anything in your
SH> prompt informing you which RE you're logged into you could be on the
SH> wrong one.
SH> Sorry, I know it's a low-tech possibility, but one that can catch you if
SH> you're not paying attention.
-----Original Message-----
Sent: Friday, January 07, 2005 1:19 PM
To: kathy lee
Subject: Re: [j-nsp] error: routing subsystem is not running
This usually means that RPD is too busy to get the routing
information you requested with the show command.
Have any configuration changes been made recently? How long
has the router been this way? Can you issue the command 'run
show system processes extensive' and verify that RPD is high?
Are you seeing any other messages in the syslog like
scheduler slips or memory errors?
-Daniel Evans
On Fri, 7 Jan 2005 12:31:51 -0800 (PST), kathy lee
Post by kathy leeHi,
What does this error msg mean? It seems the only way to get routing
process going again is reboot the Juniper box.
root# run show ospf? neighbor
error: the routing subsystem is not running
Thanks.
Kathy
---------------------------------
Do you Yahoo!?
The all-new My Yahoo! - Get yours free!
_______________________________________________
http://puck.nether.net/mailman/listinfo/juniper-nsp
_______________________________________________
http://puck.nether.net/mailman/listinfo/junipe> r-nsp
SH> _______________________________________________
SH> juniper-nsp mailing list juniper-***@puck.nether.net
SH> http://puck.nether.net/mailman/listinfo/juniper-nsp