SecureStack C2 Firmware 1.x / 2.x / 3.x Migration procedures

  • 0
  • 1
  • Article
  • Updated 5 years ago
  • (Edited)
Article ID: 5707 

Products
SecureStack C2
Matrix C2 

Related to
Upgrade 

Goals
Recovery 

Changes
Upgraded from firmware version 1.x to 2.x or higher using standard procedures 

Symptoms
Won't boot
Stack failure 

Causes
Upgrade of a Standalone or Stack from 1.x to 2.x or higher without taking special precautions will cause the configurations to not be readable, with the result that the unit/stack will likely not boot up. 

Upgrade of a Stack from 2.x to 3.x or higher without taking special precautions will cause the firmware propagation to all stack member units to fail due to differing stack intercommunication protocols, with the result that the stack will not function properly for both (firmware & protocol) reasons. 

Upgrade of a Standalone or Stack from 3.x to 4.x or higher requires no special considerations or special procedures. 

Depending upon your current situation and your desired end point, you may wish to perform one or more of the procedures in this document, in the order listed. 

Solution 

To recover a Standalone or Stack from a 1.x to 2.x or higher "mis-upgrade": 

This first procedure states the simplest possible recovery process, as an alternative to completely clearing the NVRAM configuration from the boot menu (5628); and assumes that the Standalone or Stack is in the same condition it was in as of the initial failure. 

That is, the Standalone or Stack will not fully boot. 

  1. Use XModem to back-rev to the original version of 1.x firmware that was running prior to the failed 2.x or higher upgrade. Do this by following 5605, section "Downloading to a Standalone unit, via the Serial Port (XModem)", steps 1-14 only.
  2. The Standalone or Stack should now be fully booted onto 1.x firmware again.

Note1: For Stack recovery, it is important for the mis-upgraded Master to continue to recognize that it is Stacked, so that it will load the Stack configuration from NVRAM when it boots up. Otherwise, it will come up with defaulted Standalone configurations, and you will have more problems trying to recover the full configuration from the remaining units. This all assumes that the full Stack configuration is not easily duplicated, there is no recent copy of it that has been manually saved using the 'show config outfile' command (5533), and it is thus important to recover the NVRAM-based configurations. 

To recover a Stack from a 2.x to 3.x or higher "mis-upgrade": 

This second procedure states the simplest possible recovery process, as an alternative to temporarily unstacking and upgrading all units; and assumes that the Stack is in the same condition it was in as of the initial failure. 

That is, the Stack may or may not fully boot, but still has the same Master unit and the stack will not operate properly. 

  1. Use XModem to back-rev to the original version of 2.x firmware that was running prior to the failed 3.x or higher upgrade. Do this by following 5605, section "Downloading to a Standalone unit, via the Serial Port (XModem)", steps 1-14 only.
  2. The Stack should now be fully booted onto 2.x firmware again.

Note2: For Stack recovery, it is important for the mis-upgraded Master to continue to recognize that it is Stacked, so that it will load the Stack configuration from NVRAM when it boots up. Otherwise, it will come up with defaulted Standalone configurations, and you will have more problems trying to recover the full configuration from the remaining units. This all assumes that the full Stack configuration is not easily duplicated, there is no recent copy of it that has been manually saved using the 'show config outfile' command (5533), and it is thus important to recover the NVRAM-based configurations. 

To upgrade a Standalone or Stack from 1.x to 3.x or higher: 

This third procedure elaborates upon the process stated in firmware 2.00.48 release notes

  1. Save a local copy of your 1.x configuration ('show config outfile configs/myfile.cfg', per 5533.
  2. Download the new 3.x or higher firmware file (it is best to avoid 3.00.50) onto the Standalone or onto all units of the Stack, but don't boot onto it yet. For this purpose, follow 5605, section "Downloading to a Standalone unit or a Stack, via TFTP", steps 1-10 only.
  3. Reboot onto the new firmware while reloading the configuration using the new firmware's NVRAM storage rules ('configure configs/myfile.cfg', per 5533).
  4. The Standalone or Stack should now be fully booted onto 3.x or higher firmware.

Note3: If diffserv commands are present in the configuration, the cli (if monitored) will display an error message for each of these commands, stating that the command is unknown. These messages should be ignored. 

Note4: If GVRP was disabled per port with 1.x firmware (this is the default), it will be enabled in 2.x or higher firmware (this is also the default), and vice versa. If this is other than what you wish to happen, it will be necessary to review the port configurations and manually override the GVRP state of one or more ports, after the upgrade is complete. 

To upgrade a Standalone or Stack from 2.x to 3.x or higher: 

This fourth procedure elaborates upon the process stated in firmware 3.00.50 release notes. Since the 2.x-to-3.x concerns are about stack intercommunication protocols, the standard upgrade process (5605) is adequate, as desired, for Standalone unit upgrades from 2.x to 3.x or higher firmware. 

  1. Optionally, perform the "highly recommended" standard upgrade (5605) to firmware 2.01.37 to gain the "additional safeguards that check that proper code versions exist on all members of a stack" before moving on to firmware 3.x or higher. These same safeguards are present in all 2.01.37+ firmware versions.
  2. Download the new 3.x or higher firmware file (it is best to avoid 3.00.50) onto the Standalone or onto all units of the Stack, and then boot onto it. For this purpose, follow 5605, section "Downloading to a Standalone unit or a Stack, via TFTP", all steps 1-12.
  3. The Standalone or Stack should now be fully booted onto 3.x or higher firmware.

See also: 11493.
Photo of FAQ User

FAQ User, Official Rep

  • 13,610 Points 10k badge 2x thumb

Posted 5 years ago

  • 0
  • 1

There are no replies.

This conversation is no longer open for comments or replies.