Can a bad console port connector crash a 4000 Router?

[terminaljunkie]

Hi,

I have a Router that looked ok before I shipped it to another site. The guy at the other end had a problem and plugged in a console cable (25 pin D Type) which was the only one he could find.....he says the cable is fine but the D type at the end is a bit iffy.

Anyway, the unit crashes repeatedly - but it seems to indicate memory errors which were certainly not there earlier.

My first though was that the Router has been damaged in transport, but he said he had seen something about a console connector being able to cause problems if the pinout was not making contacts or bad???

I have never heard of this, and just wanted to know if anyone else could confirm or refute this as a possibility before we get the unit shipped back?

Thanks in advance for any help!!!


Best Regards,

<*>terminaljunkie<*>

 

[tschouten]

I've seen bad cables cause enough errors to lock the interface up until you reboot the machine. Then slowly work back up to another interface lock-up. This may be what is happening. But a better way to check would be to see the actuall errors posted, it could very well have been damaged in transit. I had a switch once that was damaged during transit (new in the box it came in, we only opened it and configured then shipped it). What happened with that one was there was a severe freezing overnight, and some of the circuits just started falling off the boards. The fellow at the other site said he thought we were playing a joke on him when he opened the box and there were chips falling out onto the floor. Shrug...so it could be one or the other. My guess is it probably is the cable, try replacing it first then seeing if the problem clears up. Not to mention post the error messages would love to see what they are.

 

[terminaljunkie]

Thanks very much.

I must admit to being dubious when he mentioned the cable, but I will look into it further - I have just mailed him 2 new console cables with a selection of 9 & 25 way D Type ends.

I can't see then coming in wrong!

Probably won't know until Monday now, but I will certainly get him to mail me (and then post up) the error messages for your delectation


Best Regards,

<*>terminaljunkie<*>

 

[terminaljunkie]

Try 1
===================
System Bootstrap, Version 5.2(11a), RELEASE SOFTWARE
Copyright (c) 1986-1995 by cisco Systems
bad status on shared memory parity error, expected: 0x13, is: 0x17
location 0x6000000, phase 0, subtest 2, test: write
written 0x0, read 0x0 ... aborting
failed shared memory parity test ... aborting

Try 2
===================
System Bootstrap, Version 5.2(11a), RELEASE SOFTWARE
Copyright (c) 1986-1995 by cisco Systems

Shared Memory Parity Error
shared memory control register = 0x4dffff7
error caused by access in byte(s) 1

System Bootstrap, Version 5.2(11a), RELEASE SOFTWARE
Copyright (c) 1986-1995 by cisco Systems

Shared Memory Parity Error
shared memory control register = 0x4dffff7
error caused by access in byte(s) 1

System Bootstrap, Version 5.2(11a), RELEASE SOFTWARE
Copyright (c) 1986-1995 by cisco Systems
bad status on shared memory parity error, expected: 0x12, is: 0x16
location 0x6000000, phase 4, subtest 5, test: write
written 0xf, read 0xf ... aborting
failed shared memory parity test ... aborting


Try 3
==================

%Software-forced reload

Queued messages:
%HD-1-NOMEMORY: Unit 0, no memory for transmit ring
Exception: Software forced crash at 0x10f4c6c (PC)

System Bootstrap, Version 5.2(11a), RELEASE SOFTWARE
Copyright (c) 1986-1995 by cisco Systems
4000 processor with 16384 Kbytes of main memory


current memory block, bp = 0x60045BC,
memory pool type is I/O
bp(0x60045BC) allocator_pc = 0x0, pak->caller_pc = 0x0
paktype check, pak = 0x60045DC

next memory block, bp = 0x0,
memory pool type is I/O
bp(0x0) not in any mempool

previous memory block, bp = 0x6003F38,
memory pool type is I/O
bp(0x6003F38) allocator_pc = 0x1030E56, pak->caller_pc = 0x0
paktype check, pak = 0x6003F58
%SYS-3-BADBLOCK: Bad block pointer 60045BC
-Traceback= 103CAE8 103D076 102F788 1030E5E 1030F42 10F170A 10F15F4 1026C10
%SYS-6-MTRACE: malloc: addr,pc
87F1C,102F718 0,1030DC0 87F1C,102F718 0,1030DC0
87F1C,102F718 0,1030DC0 87F1C,102F718 0,1030DC0
%SYS-6-MTRACE: free: addr,pc
87F1C,102F858 87F1C,102F858 87F1C,102F858 87F1C,102F858
87F1C,102F858 87F1C,102F858 87F1C,102F858 87F1C,102F858
%SYS-6-BLKINFO: Freespace does not end at end of the pool blk 60045BC, words 2088210, alloc 0, Free, dealloc 0, rfcnt 0


%Software-forced reload

Queued messages:
validblock_diagnose, code = 8
Exception: Software forced crash at 0x10f4c6c (PC)

System Bootstrap, Version 5.2(11a), RELEASE SOFTWARE
Copyright (c) 1986-1995 by cisco Systems
4000 processor with 16384 Kbytes of main memory


current memory block, bp = 0x6000D90,
memory pool type is I/O
bp(0x6000D90) allocator_pc = 0x0, pak->caller_pc = 0x0
paktype check, pak = 0x6000DB0



Try 4
====================
See 3rd try

Try 5
====================
See 1st try


Best Regards,

<*>terminaljunkie<*>

 

[terminaljunkie]

Anybody any clues as to what all of that might mean?
Apart from the obvious *broken* Router?
Has anyone seen one behave like this?
Are the messages consistent with memory or Flash problems?

Thanks for any help!



Best Regards,

<*>terminaljunkie<*>

 

[wybnormal]

Given the different memory errors, I would guess a loose or crudy connection on one of the DIMMs.

Pull the memory cards out and clean the contacts.. use some contact cleaner in the DIMM connector and leave it wet when you reinsert the chips a couple of times. Wipe up extra and give it 30 minute reset to dry. Not that it's needed, the cleaner is non-conductive and I have used it and boot right away.

Worth a try with nothing to lose

MikeS

PS-- this trick works well on switch ports that have not been used in a long while or have been in a dirty enviroment




Find me at

http://www.packetattack.com

&quot;Take advantage of the enemy's unreadiness, make your way by unexpected routes, and attack unguarded spots.&quot;
Sun Tzu

 

[terminaljunkie]

No joy unfortunately.....looks like a dead Router []
I'll have to find something to replace it.


Best Regards,

<*>terminaljunkie<*>

 

[terminaljunkie]

Thanks for all help proffered though - we tried!!!


Best Regards,

<*>terminaljunkie<*>