Unsolved
This post is more than 5 years old
2 Posts
0
8145
March 31st, 2004 08:00
5012 crashed on new firmware
Below is the output that I'm getting when I updated my 5012 switch's firmware. The test network boot went just fine off of my tftp server, so I swapped it to "Net & Save", rebooted, and now I get this through the console.
Anything that can be done? Or do I just call Tech Support?
---------------------------------------------------------------
RDU Product coming up...
CPU type is R4650 revision 0x00
DRAM found is 16MB
Testing DRAM...OK
Initializing FLASH Memory
Initializing PCI host bridge
...
Booting up... Ver 4.2 (20010802)
Reading non-volatile data...
Boot from flash...
Reading image from flash... Done.
Decompressing image... Done.
Expanded to 2827856 bytes, CRC 93210295
Loading image... Release 6.1.2.3291 (07210816)
Code Size............................6824K
Total Free Memory Size...............9560K
Start Address..................0x806aa000
End Address..................0x81000000
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California. All rights reserved.
Initializing...
0.06 GT-48304-B-0 (v2.00)
0.00 GT-48360-L-1 (v2.00)
1.01 GT-48360-L-1 (v2.00)
2.02 GT-48360-L-1 (v2.00)
3.03 GT-48360-L-1 (v2.00)
4.04 GT-48360-L-1 (v2.00)
5.05 GT-48360-L-1 (v2.00)
6.06 GT-48360-L-1 (v2.00)
7.07 GT-48360-L-1 (v2.00)
8.08 GT-48360-L-1 (v2.00)
9.09 GT-48360-L-1 (v2.00)
10.10 GT-48360-L-1 (v2.00)
11.11 GT-48360-L-1 (v2.00)
System Interface Attachments:
Device tty0 has been attached.
Device de0 has been attached.
Device nd0 has been attached.
Assertion "vlanId <= AM_VLAN_MAXID" in file vlan.c at line 305 failed.
Crashing the system...
Andrew_Hicks1
2 Intern
•
169 Posts
0
March 31st, 2004 12:00
You'll probably need to contact tech support, unfortunately. There is no back-door on the 5012 to allow us to reflash the firmware - so it's possible a faulty image may have been saved to flash. If the 5012 is still under warranty, Dell PowerConnect technical support should be able to issue a replacement.
If you are a customer in Canada or the United States, tech support can be reached at 1-800-822-8965. Choose the server option, then the PowerConnect option.
International customers should contact their regional tech support numbers.
apavely
2 Posts
0
March 31st, 2004 18:00
Thankfully, I actually did manage to get it working again, but not according to any Dell documentation.
I moved from firmware 5.2.5 to 6.1.2 on my 5012. Apparently there are issues I was previously unaware of that skipping a firmware revision, in my particular instance, would cause this type of error. I needed to fall back to the 6.0.4 firmware, then move up to the 6.1.2 again.
After digging around a bit, I came across a boot menu (hit when booting from the console), and used an otherwise-undocumented 'z' command, for wiping out certain segments of the NVRAM (this is not the flash, which is separate). This allowed me to force the switch to load firmware from a non-flash source (TFTP).
Note: don't do this unless you really really know what you're doing, otherwise you might mess up your switch seriously. Be very careful. I can't stress this enough. Having several spare switches helps, too.
Hit while booting the switch (through the console), which brings up the boot menu. Type 'z' . Type 'X' at the "Are you sure? (y/n)" prompt (note: not 'y', but 'X', there's reasons for this, that's why I said be careful!), then type 'g' to cause the switch to start booting.
You'll receive a timed-out prompt to elect where to obtain the firmware, pick 'N' for Network. Follow through specifying your IP settings/TFTP settings. This will cause the switch to load the firmware from your TFTP server, but remember, it will not save your firmware to the flash. You need to do this manually once the firmware is up and running.