Considerations for NetSight upgrade of SecureStacks

  • 0
  • 1
  • Article
  • Updated 4 years ago
  • (Edited)
Article ID: 7513 

SecureStack C3
Firmware 1.00.37 and lower
SecureStack C2
Firmware 4.00.31 and lower
SecureStack B3
Firmware 1.00.31 and lower
SecureStack B2
Firmware 4.00.22 and lower
SecureStack A2
All firmware
Atlas Console
Inventory Manager 

Upgraded SecureStack firmware using NetSight 

Dir command shows wrong firmware version as Active and Boot
Cannot select new firmware version
Cannot delete new firmware version
'set boot system'
'show version'
"BackTrace-software version incompatible with running software" 

Normally in the process of upgrading firmware, the 'set boot system' command (step 11 of the TFTP procedure in 5605) is used to select the new firmware file for next boot and the system reboots onto it. It is typically not expected that a file will have been selected for the next boot but the reboot process has not yet occurred. 

Upgrading via NetSight Atlas Console or Inventory Manager, it is possible to select the new firmware file for next boot, without triggering an immediate reboot. If this is done, be aware that with older firmware the SecureStack's file directory management software is set up to consider a firmware file Active whenever it has been selected as the new Boot image - even though that image may not be what is presently running on the system. 

With older SecureStack firmware versions, this leaves the system in a state where
  • a 'show version' correctly describes the newly-selected image as BuFw (backup firmware);
  • a 'dir' incorrectly describes the newly-selected image as Active;
  • it is not possible to again select the new firmware version (because it is already Active);
  • it is not possible to delete the new firmware version (because it is Active); and
  • it is possible to delete the file directory copy of the currently-running-in-DRAM firmware version (because it is no longer considered Active).

Here is an example cli session executed after NetSight was used to upgrade a SecureStack C2 from firmware version 3.03.33 to 4.00.24: 
 C2(su)->set boot system c2-series_04.00.24
Error: invalid image specified
C2(su)->delete c2-series_04.00.24
Failed to remove c2-series_04.00.24
C2(su)->show version

Copyright (c) 2005 by Enterasys Networks, Inc.

Model Serial # Versions
-------------- ----------------- -------------------

C2G124-48 04430076900C Hw:BCM5695 REV 17

Filename: c2-series_03.03.33
Version: 03.03.33
Size: 6066176 (bytes)
Date: Tue Apr 4 11:03:56 2006
CheckSum: fa43940117f1519b54a3263fa5402074
Compatibility: C2G124-24, C2G124-48, C2H124-48, C2G124-48P, C2H124-48P
C2K122-24, C2G170-24, C2G134-24P

Filename: c2-series_04.00.24 (Active) (Boot)
Version: 04.00.24
Size: 6254592 (bytes)
Date: Mon Jul 10 13:29:10 2006
CheckSum: 00892c418c4ae418bfc31ea8fe582ce0
Compatibility: C2G124-24, C2G124-48, C2H124-48, C2G124-48P, C2H124-48P
C2K122-24, C2G170-24, C2G134-24P

Files: Size
================================ ========
my.cfg 4197
current.log 178705

There is a further possible issue resulting from a no-reboot stack upgrade: If one or more units are rebooted for any reason but at least one unit remains unrebooted, the stack firmware versions will be out of sync and a "BackTrace-software version incompatible with running software" error will indicate this in the current.log (5487). 

See also: 5455

For the C3, upgrade to firmware 1.00.40 or higher.
For the C2, upgrade to firmware 4.00.37 or higher.
For the B3, upgrade to firmware 1.00.34 or higher.
For the B2, upgrade to firmware 4.00.26 or higher.
For the A2, to be corrected in a future firmware release. 

Firmware release notes state: 
"The output of the 'dir' command will display the active and backup image loaded on the device when they are loaded via the CLI or SNMP." 

What this means is that the old, currently-running image is now properly described as Active. 

Post-upgrade, the remaining possibility of a "BackTrace-software version incompatible with running software" error condition is considered to be FAD (Functions as Designed). Regardless of SecureStack firmware version, a NetSight-invoked upgrade can by design still leave the stack unrebooted. This is not a problem per se, but it is useful to be aware of the possibility. 

This workaround applies to both older and newer firmware versions, after a no-reboot upgrade and either before or after the reboot of a subset of the stack units:
  • To bring the full stack up using the already-selected firmware, reboot the switch units that have not been rebooted since upgrade - or reboot all switches if you are not sure.

Are you sure you want to reload the stack? (y/n) y

Saving Configuration to stacking members
Reloading all switches.
  • Negate NetSight's selection of the new firmware file by re-selecting the original firmware file ('set boot system <filename>' - which will also trigger a stack reboot.

Note: With later SecureStack firmware, NetSight's ability to defer the post-upgrade system reboot is brought to the CLI as well. See 12399 for more about that.
Photo of FAQ User

FAQ User, Official Rep

  • 13,590 Points 10k badge 2x thumb

Posted 4 years ago

  • 0
  • 1

There are no replies.

This conversation is no longer open for comments or replies.