Dell PowerConnect B-RX Multi-Service IronWare Software R02.7.02a Release Notes - Page 29

Rebooting the management module, Regenerating SSH v2 crypto key

Page 29 highlights

Rebooting the management module After upgrading one or more software images on the management or interface module, you must reboot the management module. After the management module reboots, it in turn reboots the interface modules. To reboot the management module, enter one of the following commands:  reload (this command boots from the default boot source, which is the primary code flash)  boot system flash primary | secondary During the management module reboot, the following synchronization events occur:  If you have a standby management module, the active management module compares the standby module's monitor, primary, and secondary images to its own. If you have updated these images on the active module, the active module automatically synchronizes the standby module's images with its own.  If you copied the primary and/or secondary IronWare image to all interface modules using the copy command with the all keyword, the management module made a copy of the image and stored it in its code flash under the names lp-primary-0 or lp-secondary-0. By default, the BigIron RX system checks the interface modules' IronWare images, which reside in the code flash of the interface modules and the management module to make sure they are the same in both locations. (These IronWare images are stored on the management module only and are not run by the management or interface modules.) If the IronWare images on the interface and management modules are different, the system prompts you to do the following:  If you want to update the IronWare images in the interface module's code flash with the images in the management module's code flash, enter the lp cont-boot sync command at the Privileged EXEC prompt.  If you want to retain the IronWare images in the interface module's code flash, enter the lp cont-boot no-sync command at the Privileged EXEC prompt. After the management module finishes booting, do the following:  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. IronWare Software Release 02.7.02a for Brocade BigIron RX Series Swtches Release Notes v 1.0 Page 29 of 46

  • 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
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46

IronWare Software Release 02.7.02a
for Brocade BigIron RX Series Swtches
Release Notes v 1.0
Page 29 of 46
Rebooting the management module
After upgrading one or more software images on the management or interface module, you must reboot
the management module. After the management module reboots, it in turn reboots the interface modules.
To reboot the management module, enter one of the following commands:
reload
(this command boots from the default boot source, which is the primary code flash)
boot system flash primary | secondary
During the management module reboot, the following synchronization events occur:
If you have a standby management module, the active management module compares the standby
module’s monitor, primary, and secondary images to its own. If you have updated these images on the
active module, the active module automatically synchronizes the standby module’s images with its
own.
If you copied the primary and/or secondary IronWare image to all interface modules using the
copy
command with the
all
keyword, the management module made a copy of the image and stored it in its
code flash under the names lp-primary-0 or lp-secondary-0. By default, the BigIron RX system
checks the interface modules’ IronWare images, which reside in the code flash of the interface
modules and the management module to make sure they are the same in both locations. (These
IronWare images are stored on the management module only and are not run by the management or
interface modules.) If the IronWare images on the interface and management modules are different,
the system prompts you to do the following:
If you want to update the IronWare images in the interface module’s code flash with the
images in the management module’s code flash, enter the
lp cont-boot sync
<slot-number>
command at the Privileged EXEC prompt.
If you want to retain the IronWare images in the interface module’s code flash, enter the
lp
cont-boot no-sync <slot-number>
command at the Privileged EXEC prompt.
After the management module finishes booting, do the following:
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.