5510-48T Reboot issues

[paterson]

Hey guys,
I don't work with this product line much, but I do know how to connect and configure for some stuff.

My problem is that the unit keeps rebooting every 10-15 seconds or so. I connected with a serial cable to the console port and it shows the unit rebooting, then stops and reboots again.

Is this unit now a paper weight, or can I default it and start again? It was installed about 1-1/2 years ago. I suspect the software will be about 4.1 or 4.2.

Cheers!

**************************************
Insert Witty Signature Here.

 

[biv343]

I don't know if this is what you're experiencing, but I ran into this on a couple of 5510s a while back.

ANALYSIS
In some rare instances, a unit might become corrupted with its stored configuration and cause
the unit to hang after a power reset. What the customer might see can be seen in the example
below when the unit is powering up.

Test 102 ROM Config - PASSED
Test 104 FANs - PASSED
Test 207 NSXs Direct Registers - PASSED
Test 209 NSXs Indirect Reg/Mem - PASSED
Test 210 NSXs XRAM Adr/Data Lines - PASSED
Test 211 PHYs Register - PASSED
Test 212 NSXs Internal Loopback - PASSED
Test 213 CAM Interrupt - PASSED
Test 214 SNMP Interrupt - PASSED
Test 215 PHYs Interrupt - PASSED
Starting Agent Code..
Decompressing the image ... Software hangs
RECOMMENDATIONS
To correct this issue, the configuration flash needs to be erased.
NOTE - This will factory default the unit and potentially the stack configuration if it is the base
unit.
In order for the user to get the unit to boot up, the unit must be power cycled and Ctrl-C entered
from the console port after the power on self test (POST) has started to run. The POST has
started if "Testing main memory - " is displayed on the screen. Refer to the following screen
display.
When the "Press" menu is displayed on the console, enter 'i' to initialize the config area of flash.
Enter 'y' to confirm. When the "Press" menu is redisplayed, enter 'a' to run the agent code. The
unit should boot properly.
BayStack XXX Diagnostics X.X.X.X
Testing main memory - PASSED Enter Ctrl-C
>> Break Recognized - Wait.. Ctrl-C recognized
Resets: 58.
Initializing Flash..
Reading MAC Address..
MAC Address: 02:09:97:33:8A:60
Initializing Switch CBs,.......
Initializing Switch HW..
Press 'a' to run Agent code
Press 'd' to Download agent code
Press 'e' to display Errors
Press 'i' to Initialize config/log flash
Press 'p' to run POST tests.. Enter 'i'
Erase Config/Log Flash? y/N [ N ]: y Enter 'y'
Erasing - Wait 2 sec..


Press 'a' to run Agent code
Press 'd' to Download agent code
Press 'e' to display Errors
Press 'i' to Initialize config/log flash
Press 'p' to run POST tests.. Enter 'a'
Starting Agent Code..
1
Decompressing the image ...
diskFormat(): "NVRAM:" found unformatted..."NVRAM:" formatted.
Target Name: vxTarget
User: target
Attaching network interface idtip0... done.
Attaching network interface lo0... done.
Completing initialization...

 

[paterson]

Thanks for that, but I am unable to use the "Ctrl-C". Here is what is shown on the Terminal/console session.



Booting...

Testing Memory...............................

Starting..

Baystack 5510-48T

Hardware Rev : 4

CPU CLOCK :266000000
Resets: 32257.
Initializing Flash..
Reading MAC Address..
MAC Address: 00:0F:06:89:C4:00
Initializing Switch CBs
Attaching SOC unit 0... PCI device attached as unit 0.
Attaching SOC unit 1... PCI device attached as unit 1.
Attaching SOC unit 2... PCI device attached as unit 2.
Attaching SOC unit 3... PCI device attached as unit 3.
Attaching SOC unit 4... PCI device attached as unit 4.
}w#



After this, the unit reboots and starts again, showing the same thing on the screen. I have tried the Ctrl-C at every stage of this boot sequence but no love.


**************************************
Insert Witty Signature Here.

 

[Alainv]

If CTRL-C does not work anymore, I suggest changing it.
They have a LLT waranty, so contact you reseller or nortel.

 

[paterson]

Thank you both very much. It is not what I was hoping to hear, but it is what I expected to hear.

Cheers!

**************************************
Insert Witty Signature Here.

 

[Jynxx]

Dumb question but are you certain that the power cable is making a secure connection in the back of the switch?

If so and it is not even finishing boot before reloading again, it could be a corrupt image or config as mentioned.

 

[paterson]

Not a dumb question, but I would have been dumb not to check!! Ya, one of the first things I did was check the power source. This unit has been shipped back to Nortel, thanks everyone.

**************************************
Insert Witty Signature Here.