[c-nsp] Catalyst 6500 won't boot Ethernet Switching Modules
jc hall
jc.hall at cybertrails.net
Tue Sep 28 19:20:29 EDT 2004
I have 6 modules total. I've found 1 that seems to operate in a slot none others have. I of course haven't tried every possible combination of modules and slots. One of the modules that didn't work in this chassis did work in a chassis I have already in production...
So, I'll just continue troubleshooting until I find a pattern.
Thanks
-----Original Message-----
From: Dave Breiland [mailto:dave at opsource.net]
Sent: Tuesday, September 28, 2004 1:38 PM
To: jc hall; cisco-nsp at puck.nether.net
Subject: RE: [c-nsp] Catalyst 6500 won't boot Ethernet Switching Modules
My guess would be the SUP2 module or bad backplane...
Dave
-----Original Message-----
From: cisco-nsp-bounces at puck.nether.net
[mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of jc hall
Sent: Tuesday, September 28, 2004 1:20 PM
To: cisco-nsp at puck.nether.net
Subject: [c-nsp] Catalyst 6500 won't boot Ethernet Switching Modules
Can anybody provide some insight to this problem? I am piecing together a
Catalyst 6500 with a SUP2/MSFC2 and several Ethernet modules both 6248s and
6348s. All of this hardware was purchased gray market. The SUP2 will boot
the CatOS image when no other modules are installed in the chassis. After
it is loaded and running and I insert an Ethernet module, it does not boot
the blade nor is it recognized in any way.
If I boot the switch with an Ethernet module inserted, it never fully boots.
Here is an example of the last attempt with a ws-x6248 installed in Slot3:
rommon 2 > boot bootflash:cat6000-sup2k8.7-5-1.bin
Self decompressing the image :
############################################################################
############################################################################
############################################################################
############################################################################
############################################################################
############################################################################
############################################################################
############################################################################
############################################################################
#################################### [OK]
System Power On Diagnostics
DRAM Size ..........................512 MB
Testing DRAM .......................Passed
Verifying Text Segment .............Passed
NVRAM Size .........................512 KB
Level2 Cache .......................Present
Level3 Cache .......................Present
System Power On Diagnostics Complete
Currently running ROMMON from S (Gold) region
Boot image: bootflash:cat6000-sup2k8.7-5-1.bin
Bus Error Exception (data) occurred on Sep 28 2004 12:04:19
Software version = 7.5(1)
Process ID #b, Name = PortConfig-1
process stack top = 8ffee970, stack pointer = 8ffee680
cause = 0000001c
Bus Error Exception (data) exception happened
EPC: 80BE1088
Stack content:
sp+00: 8BD46900 00000000 00000000 809FA648
sp+10: A2E23FF0 82E1FCA4 00000000 00000000
sp+20: 00000000 809FA30C 000000CC 00000000
sp+30: 00000000 82E1FC84 00000000 00000000
sp+40: 809FC314 809FC2E8 00000010 00000000
sp+50: 00000000 00000000 80812980 8081294C
sp+60: 00000001 00000003 00000001 0000000C
sp+70: 00000000 00000066 00000000 000000ED
sp+80: 8FFEE708 8080D464 00000001 00000000
sp+90: 000493E0 808BCFD8 808BCFD8 808BCFD8
sp+A0: 00000000 00000001 00000000 000493E0
sp+B0: 808BCFD8 808BCFD8 808BCFD8 808BCFD8
sp+C0: 808BCFD8 808BCFD8 808BCFD8 808BCFD8
sp+D0: 808BCFD8 808BCFD8 808BCFD8 808BCFD8
sp+E0: 808BCFD8 808BCFD8 808BCFD8 808BCFD8
sp+F0: 808BCFD8 808BCFD8 808BCFD8 808BCFD8
Register content:
Status: FFFFFF83 Cause: 8100501C
AT: 81830000
V0: 00000000 V1: 00000000
A0: 8BD46928 A1: 00000000
A2: 00000050 A3: 00000000
T0: 8BD46914 T1: 34040021
T2: FFFFFFE0 T3: 00000003
T4: 00000000 T5: 00000000
T6: 01000000 T7: 0001C8D4
S0: 00000200 S1: 1FFFFFFF
S2: E0000000 S3: 00000000
S4: 00000000 S5: 00000000
S6: 00000000 S7: 00000000
T8: 00066EDE T9: FFFFFFFF
K0: A0000000 K1: A0EA0308
GP: 8152A9A0 SP: 8FFEE680
S8: 8FFEE6E0 RA: 809FAB04
HIGH: 00000EFC LOW: 00000063
BADVADDR: C189C8FA ERR EPC: 80BE1080
Call Trace(bottom of the stack to top):
0x809fa640: jal 0x809fd6cc
0x809fa304: jal 0x809fa97c
0x809fc30c: jal 0x809fa2a0
0x809fc2e0: jal 0x808c5b90
0x80812978: jal 0x809fc2c8
0x80812944: jal 0x805178bc
0x8080d45c: jal 0x808126f4
0x808bf14c: jalr r2ÿ
System Bootstrap, Version 7.1(1)
Copyright (c) 1994-2001 by cisco Systems, Inc.
*** Mistral Interrupt on line 2 ***
IO bus interrupt due to illegal addr, no ack, etc
PC = 0xbfc1234c, Cause = 0x1000, Status Reg = 0x30419003
ROM Monitor Can Not Recover From Exception
A Board Reset Is Issuedþ
Do I have a software problem, Ethernet module problem with all my blades or
a possible backplane issue?
Thanks,
________________________
J.C. Hall
Network Administrator
cybertrails
"providing internet solutions"
623.434.6066 Desk
623.764.8726 Mobile
jc.hall at cybertrails.net
http:// <http://www.cybertrails.com> www.cybertrails.com
________________________
_______________________________________________
cisco-nsp mailing list cisco-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
More information about the cisco-nsp
mailing list