Actually one refinement that might save you some time. After you saved the configuration file, you could open it with a text editor and look at it. You can edit the file manually and see if you can see any VLAN configuration that might cause the problem. This way you can load the test configuration back to the switch after you upgrade the FW again and test it that way so you don't have to reconfigure everything manually.
If you post the configuration here maybe we can help you figure out what in this file might be causing the problem.
Looks like backward compatibility issue with the configuration. Something on your configuration is causing a problem on the new FW. Maybe some maximum ranges have changed between the versions. It might be something in your configuration (maybe VLAN setup) that's doing it.
It is not going to be a nice procedure but you might try this:
connect to the serial interface using hyperterm or something like that.
reboot the switch then hit escape (esc) pretty soon after it restarts which will drop you into the boot prompt and allow you to elect to reboot from the network.
choose to boot from the net and select your older version of FW.
once you get it running again then go to the "system manager->configuration" menu and first save your old configuration in case you have not done so and then you might need to reset your configuration to factory default first and reboot.
now load the new FW and finally try to reconfigure your switch and see what operation is failing.
Sorry about the problem you experience. I don't know of a better solution right now - but I will check with my colleagues to see if anyone has a better idea.
Which version do you need? It should still be there on the support web site but if you let me know which version you need I can try to find it for you.
There might be a problem restoring the old firmware. The version was so old that I could not save the file before updating. Where could I get an older firmware version for the 3024 switch?
Here are the options I am presented with after rebooting the switch and pressing Esc...
Available commands:
C - Show current cache information DW StartAddr [#bytes] - Display memory S - Go to S record download mode, ESC exits G [addr] - Go execute routine at 'addr', if 'addr' is not specified use start address from last 'S' record download, G, or @ command V - Show version numbers HE - Help ? - Help
Note: All numeric values are in hexadecimal format
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.
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...
That's very strange. I don't see those options at all. When I boot my 3024, I see the following:
Boot from flash...
Boot Mode (F)lash or (N)et:
I'm not sure why you should see the other menu. Can you just boot normally and capture the entire boot sequence and post that information? I'm not sure where the other menu comes from. The 3024 doesn't show that menu to me in any of my boot sequence.
This is very strange. Can you confirm for me that you are running the 3024? There are several things on your bootup that seems strange to me. First is the boot messages are a bit different from what I'm seeing and the CPU type is completely different - you show R4650 and mine (shipping switch) shows RC32332. Anyway the other thing I see different is your version of boot code is older then the shipping version. I will have to see if I can find the older version of boot code and try to load it on my switch to see if I see what you are seeing. I actually already looked at the online archive and do not see this boot code so I may have to find some other of my colleagues who might know.
I still cannot find the boot code/HW version that you are running. It looks like this switch went through a version change at some point and the CPU and boot code were updated. I'm actually using different HW and boot code on my test switch. I'm trying to find a version of the switch you are running without luck so far. I'm sure it's in a lab somewhere but no one has responded yet with one.
DELL-Cuong N.
1017 Posts
459
0
Posted March 30th, 2006 19:00
Actually one refinement that might save you some time. After you saved the configuration file, you could open it with a text editor and look at it. You can edit the file manually and see if you can see any VLAN configuration that might cause the problem. This way you can load the test configuration back to the switch after you upgrade the FW again and test it that way so you don't have to reconfigure everything manually.
If you post the configuration here maybe we can help you figure out what in this file might be causing the problem.
Cuong.