Delete hidden firmware from NVRAM on C2
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎02-06-2014 01:12 PM
One of our C2s still has a test firmware hidden in NVRAM. Because the firmware does not show up in "dir", I cannot delete it from the CLI. There was a KB article detailing the process of going into the Administrator menu at boot-up and choosing a hidden menu option to delete the file directly from the NVRAM. (I've followed it before with great success.) However, I cannot find the article now. I need to provide instructions to my local support to go clear the file out so we can upgrade it. Can someone please refresh me?
5 REPLIES 5
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎02-18-2014 06:33 PM
For what it's worth, I did find the hidden boot menu option and the options to delete the test firmware. We were able to delete the test file successfully and upgrade the stack to 05.02.18.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎02-06-2014 02:53 PM
And oh-by-the-way; if you have not already done this, prior to any upgrade operation you can delete the backup firmware image ('
code:
', 'dir
code:
<delete
filename>') to free up directory space.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎02-06-2014 02:45 PM
OK, the extra context is making more sense.
Painful though it may be, I'm thinking that the XModem upgrade (which directly replaces the operational code) is the most probable path to resolution. The procedure is documented here:
KB 5605, "
Also note the additional cautions at the top of that article; in particular, KB 11617, regarding a possible problem with direct upgrade of 5.00.xx firmware to 5.02 or higher - with a stated solution.
Painful though it may be, I'm thinking that the XModem upgrade (which directly replaces the operational code) is the most probable path to resolution. The procedure is documented here:
KB 5605, "
code:
" (http://gsfn.us/t/49n93).Firmware Upgrading a SecureStack via TFTP or XModem
Also note the additional cautions at the top of that article; in particular, KB 11617, regarding a possible problem with direct upgrade of 5.00.xx firmware to 5.02 or higher - with a stated solution.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎02-06-2014 02:23 PM
Yep. This switch is mounted up a column on a staging floor, and it is running 05.00.59. Now that they're wanting to add a third switch into stack, we need to look into this again. It's been a while since we addressed all the older ones.
We corrected this using a hidden option in the boot menu before, because the only other option was to delete the operational code and upload the newer code by XMODEM, which takes quite some time.
We corrected this using a hidden option in the boot menu before, because the only other option was to delete the operational code and upload the newer code by XMODEM, which takes quite some time.
