Dell PowerConnect B-RX Multi-Service IronWare Software R02.7.03a Release Notes - Page 24

Regenerating SSH v2 crypto key, Hitless Layer 2 OS Upgrade, show module, show version

Page 24 highlights

• Enter the show module command at any CLI level, and verify that the status of all interface modules is CARD_STATE_UP. • Enter the show version command at any CLI level, and verify that all management and interface modules are running the new software image version. If you find that an interface module is in a waiting state or is running an older software image, then you may have forgotten to enter the lp cont-boot sync command at the Privileged EXEC prompt. You also need to upgrade the MBRIDGE FPGA on the management module. Regenerating SSH v2 crypto key If you are using SSH v2, you must clear the crypto key using the crypto key zeroize command after you upgrade from any release 02.2.01 and later. Then, regenerate a new crypto key using the crypto key generate command. Hitless Layer 2 OS Upgrade Hitless OS upgrades are supported for Layer 2 switching and Layer 2 protocols only. See the Upgrading Software Images and Configuration Files chapter in the BigIron RX Installation Guide for additional information. The hitless OS Layer 2 upgrade allows for upgrading the software in a system between two patch releases of the operating system, which support this functionality and have compatible data structures. A hitless OS Layer 2 downgrade may also be supported if the current and target code releases have compatible data structures. Note: Hitless OS upgrade is not supported between major releases. It is supported only within a release. For example, Hitless OS Upgrade is available when upgrading from software release 02.7.00a to 02.7.00b. It is not available when upgrading from software release 02.6.00 to 02.7.00. From time to time, it may become necessary when enhancing the software or adding new features to change or add data structures making releases incompatible. In these cases, an upgrade or downgrade will not be hitless, and will fall back to using the regular Brocade upgrade process - relying on fast reboot. When performing a hitless O/S Layer 2 upgrade or downgrade, use the following guidance: • Hitless O/S Layer 2 upgrade or downgrade is not supported in 2.3.00 or earlier. • Hitless O/S Layer 2 upgrade support is in 2.3.00a and higher patch releases (unless indicated otherwise in the target software's release notes). • Hitless upgrade maintains forwarding states and control plane functionality of the active software from which you are upgrading (i.e. 2.3.00a to 2.3.00d would only maintain the functionality supported by 2.3.00a). • Hitless downgrades are recommended only between compatible patch releases of a feature release such as between 2.3.00b to 2.3.00a (to ensure the higher release has no conflicting functional enhancements that do not exist in the lower release). • Due to the PBIF change introduced in patch release version 02.3.00e and version 02.3.00f, users cannot perform hitless upgrades from earlier 02.3.00 versions or 02.3.00g or higher versions. For information on Hitless Upgrades refer to the "Hitless OS Upgrade" section in the BigIron RX Installation Guide. IronWare Software Release 02.7.03a for Brocade BigIron RX Series Swtches Release Notes v 1.0 Page 24 of 40

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40

IronWare Software Release 02.7.03a
for Brocade BigIron RX Series Swtches
Release Notes v 1.0
Page 24 of 40
Enter the
show module
command at any CLI level, and verify that the status of all interface modules
is CARD_STATE_UP.
Enter the
show version
command at any CLI level, and verify that all management and interface
modules are running the new software image version.
If you find that an interface module is in a waiting state or is running an older software image, then you
may have forgotten to enter the
lp cont-boot sync
<slot-number>
command at the Privileged EXEC
prompt.
You also need to upgrade the MBRIDGE FPGA on the management module.
Regenerating SSH v2 crypto key
If you are using SSH v2, you must clear the crypto key using the
crypto key zeroize
command after you
upgrade from any release 02.2.01 and later. Then, regenerate a new crypto key using the
crypto key
generate
command.
Hitless Layer 2 OS Upgrade
Hitless OS upgrades are supported for Layer 2 switching and Layer 2 protocols only. See the Upgrading
Software Images and Configuration Files chapter in the
BigIron RX Installation Guide
for additional
information. The hitless OS Layer 2 upgrade allows for upgrading the software in a system between two
patch releases of the operating system, which support this functionality and have compatible data
structures. A hitless OS Layer 2 downgrade may also be supported if the current and target code releases
have compatible data structures.
Note:
Hitless OS upgrade is not supported between major releases. It is supported only within a release.
For example, Hitless OS Upgrade is available when upgrading from software release 02.7.00a to
02.7.00b. It is not available when upgrading from software release 02.6.00 to 02.7.00.
From time to time, it may become necessary when enhancing the software or adding new features to
change or add data structures making releases incompatible. In these cases, an upgrade or downgrade will
not be hitless, and will fall back to using the regular Brocade upgrade process – relying on fast reboot.
When performing a hitless O/S Layer 2 upgrade or downgrade, use the following guidance:
Hitless O/S Layer 2 upgrade or downgrade is not supported in 2.3.00 or earlier.
Hitless O/S Layer 2 upgrade support is in 2.3.00a and higher patch releases (unless indicated
otherwise in the target software’s release notes).
Hitless upgrade maintains forwarding states and control plane functionality of the active software
from which you are upgrading (i.e. 2.3.00a to 2.3.00d would only maintain the functionality
supported by 2.3.00a).
Hitless downgrades are recommended only between compatible patch releases of a feature release
such as between 2.3.00b to 2.3.00a (to ensure the higher release has no conflicting functional
enhancements that do not exist in the lower release).
Due to the PBIF change introduced in patch release version 02.3.00e and version 02.3.00f, users
cannot perform hitless upgrades from earlier 02.3.00 versions or 02.3.00g or higher versions. For
information on Hitless Upgrades refer to the “Hitless OS Upgrade” section in the BigIron RX
Installation Guide.