[c-nsp] How to access cisco remotely when cpu 100%
cchurch at netcogov.com
Sat Oct 2 19:23:55 EDT 2004
If you can stand a brief outage, you can have someone at the remote site
pull out the interface cable(s) that isn't/aren't facing you (IP
route-wise). Unless you're a victim of a DOS, that'll probably drop the
CPU immediately. Telnet in, grab a sh tech, and then have them put the
cable(s) back. Might only be 15-30 seconds outage. With this info, you
should be able to figure out the cause of the CPU issue. I don't think
sh tech includes a sh log, so you might want to add that also. A
scheduler allocate setting will probably help as well.
Lead Design Engineer
CCIE #8776, MCNE, MCSE
Netco Government Services - Design & Implementation Team
1210 N. Parker Rd.
Greenville, SC 29609
Home office: 864-335-9473
cchurch at netcogov.com <-note new address!
PGP key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x4371A48D
From: cisco-nsp-bounces at puck.nether.net
[mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Jay Hennigan
Sent: Saturday, October 02, 2004 5:42 PM
To: Prit Patel
Cc: NSP List
Subject: Re: [c-nsp] How to access cisco remotely when cpu 100%
On Sat, 2 Oct 2004, Prit Patel wrote:
> Hello All,
> How can i access my cisco box remotely via telnet when CPU reached
> 100% for that box.
Very slowly, patiently, and painfully.
If it is responding at all, turning on service nagle may help.
If there is another box at the remote site that is responding, a
rollover cable between the aux port of box A to the console of box B
with reverse telnet can be a lifesaver.
Jay Hennigan - CCIE #7880 - Network Administration - jay at west.net
WestNet: Connecting you to the planet. 805 884-6323 WB6RDV
NetLojix Communications, Inc. - http://www.netlojix.com/
cisco-nsp mailing list cisco-nsp at puck.nether.net
archive at http://puck.nether.net/pipermail/cisco-nsp/
More information about the cisco-nsp