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

Unified software image upgrade, Special instructions for using interface modules in a 32-slot

Page 22 highlights

• dir // (if the destination is slot 1 or 2) Check for the boot image, monitor image, and the date and time at which the new images were built. 4. If you want to upgrade other software images, go to the appropriate upgrade section for information. If you have completed upgrading the software images, you must reboot the management module to complete the upgrade process. Unified software image upgrade BigIron RX software release 02.6.00 and later can be upgraded using the Unified Software Image Upgrade procedure. When copying the image, you must load the lp-boot and mp-boot. You can set parameters to limit the images being copied and to direct images to be copied to the secondary image location to a later release by doing the following: Failure to load the lp-boot and mp-boot when copying the unified image will cause the LP to become stuck in an interactive mode. 1. Copy the unified software image (rx02702a.bin) from a TFTP server to the switch. For example, to copy the entire unified software image, the lp-boot and the mp-boot from a TFTP server at IP address 10.10.12.12, use the following command. BigIron RX#copy tftp image 10.10.12.12 rx02702a.bin lp-boot mp-boot Syntax: copy tftp image [lp-boot | lp-sec | mp-boot | mpsec | mbridge] The variable is the IP address for the TFTP server you are downloading the image from. The variable is the name of the unified software image you want to download to the switch. The lp-boot parameter specifies that you want to download the new interface module boot image. The lp-sec parameter specifies that interface image be copied to the secondary location in flash. The mbridge parameter tells the BigIron RX to copy the MBRIDGE image. It will now include two MBRIDGES; one for BigIron RX-16/8/4 (mbridge21.xsvf) and one for the BigIron RX32(mbridge32.xsvf). The mp-boot parameter specifies that you want to download the new management module boot image. The mp-sec parameter specifies that management image be copied to the secondary location in flash 2. Reboot the management module using the reload command. 3. If you are using SSH v2, you must clear the crypto key using the crypto key zeroize command after you upgrade. Then, regenerate a new crypto key using the crypto key generate command. Special instructions for using interface modules in a 32-slot chassis The BigIron RX-32 chassis introduced with this release can use interface modules in the BigIron RX series that have older versions of the Multi-Service IronWare software installed on them. There are however a couple of issues regarding older versions of the software that might be installed on interface IronWare Software Release 02.7.02a for Brocade BigIron RX Series Swtches Release Notes v 1.0 Page 22 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 22 of 46
dir /<path-name>/
(if the destination is slot 1 or 2)
Check for the boot image, monitor image, and the date and time at which the new images were
built.
4.
If you want to upgrade other software images, go to the appropriate upgrade section for
information. If you have completed upgrading the software images, you must reboot the
management module to complete the upgrade process.
Unified software image upgrade
BigIron RX software release 02.6.00 and later can be upgraded using the Unified Software Image
Upgrade procedure. When copying the image, you must load the
lp-boot
and
mp-boot
. You can set
parameters to limit the images being copied and to direct images to be copied to the secondary image
location to a later release by doing the following:
Failure to load the
lp-boot
and
mp-boot
when copying the unified image will cause the LP to become
stuck in an interactive mode.
1.
Copy the unified software image (rx02702a.bin) from a TFTP server to the switch.
For example, to copy the entire unified software image, the
lp-boot
and the
mp-boot
from a
TFTP server at IP address 10.10.12.12, use the following command.
BigIron RX#copy tftp image 10.10.12.12 rx02702a.bin lp-boot mp-boot
Syntax:
copy tftp image <TFTP-server-ip-addr> <image-name> [lp-boot | lp-sec | mp-boot | mp-
sec | mbridge]
The <TFTP-server-ip-addr> variable is the IP address for the TFTP server you are downloading
the image from.
The <image-name> variable is the name of the unified software image you want to download to
the switch.
The
lp-boot
parameter specifies that you want to download the new interface module boot image.
The
lp-sec
parameter specifies that interface image be copied to the secondary location in flash.
The
mbridge
parameter tells the BigIron RX to copy the MBRIDGE image. It will now include
two MBRIDGES; one for BigIron RX-16/8/4 (mbridge21.xsvf) and one for the BigIron RX-
32(mbridge32.xsvf).
The
mp-boot
parameter specifies that you want to download the new management module boot
image.
The
mp-sec
parameter specifies that management image be copied to the secondary location in
flash
2.
Reboot the management module using the
reload
command.
3.
If you are using SSH v2, you must clear the crypto key using the
crypto key zeroize
command
after you upgrade. Then, regenerate a new crypto key using the
crypto key generate
command.
Special instructions for using interface modules in a 32-slot chassis
The BigIron RX-32 chassis introduced with this release can use interface modules in the BigIron RX
series that have older versions of the Multi-Service IronWare software installed on them. There are
however a couple of issues regarding older versions of the software that might be installed on interface