Fabric OS 6.2 administrator guide 221
5.
Use the
firmwareShow
command to check the current firmware version on connected switches.
Upgrade the firmware, if necessary, before proceeding with upgrading this switch.
See ”
Connected switches
” on page 216
6.
Enter the
haShow
command to confirm that the two CP blades are synchronized. In the following
example, the active CP blade is CP0 and the standby CP blade is CP1:
switch:admin>
hashow
Local CP (Slot 5, CP0): Active, Warm Recovered
Remote CP (Slot 6, CP1): Standby, Healthy
HA enabled, Heartbeat Up, HA State synchronized
CP blades must be synchronized and running Fabric OS 6.0.0 or later to provide a nondisruptive
download. If the two CP blades are not synchronized, enter the
haSyncStart
command to
synchronize them. If the CPs still are not synchronized, contact your switch service provider.
7.
Enter the
firmwareDownload
command.
8.
Respond to the prompts as follows:
9.
At the
Do you want to continue [y/n]
prompt, enter
y
.
The firmware is downloaded to one CP blade at a time, beginning with the standby CP blade. During
the process, the active CP blade fails over. After the firmware is downloaded, a firmware commit starts
on both CP blades. The entire firmware download and commit process takes approximately 15
minutes.
If an AP blade is present:
At the point of the failover an
autoleveling
process is activated. Autoleveling is
triggered when the active CP detects a blade that contains a different version of the firmware,
regardless of which version is older. Autoleveling downloads firmware to the AP blade, swaps
partitions, reboots the blade, and copies the new firmware from the primary partition to the secondary
partition. If you have multiple AP blades, they are updated simultaneously; however, the downloads
can occur at different rates.
Auto-leveling takes place in parallel with the firmware download being performed on the CPs, but does
not impact performance. Fibre Channel traffic is not disrupted during auto-leveling, but GbE traffic on
AP blades may be affected.
Server Name
or
IP Address
Enter the name or IP address of the FTP server, or SSH server for SCP, where the firmware
file is stored; for example, 192.1.2.3. IPv6 and DNS are supported by
firmwareDownload
in 5.3.0. If DNS is enabled and a server name instead of a server
IP address is specified in the command line,
firmwareDownload
determines whether
IPv4 or IPv6 should be used.
User name
Enter the user name of your account on the server; for example,
JaneDoe
.
File name
6.0.0 or later:
Specify the fully qualified path name of the firmware directory, for
example,
/pub/v6.0.0.
Absolute path names may be specified using forward slashes
(/).
Network
protocol
Specify the file transfer protocol used to download the firmware from the file server. Valid
values are FTP and SCP. The Values are not case-sensitive. If
-p
is not specified,
firmwareDownload
will determine the protocol automatically by checking the
config.security
parameter on the switch.
Password
Enter a password. This operand can be omitted if firmware is accessible through a local
directory, or if no password is required by the FTP server. This operand is required when
accessing an SSH server.
Summary of Contents for A7533A - Brocade 4Gb SAN Switch Base
Page 1: ...HP StorageWorks Fabric OS 6 2 administrator guide Part number 5697 0016 Edition May 2009 ...
Page 24: ...24 ...
Page 99: ...Fabric OS 6 2 administrator guide 99 ...
Page 100: ...100 Managing user accounts ...
Page 118: ...116 Configuring standard security features ...
Page 164: ...162 Configuring advanced security features ...
Page 234: ...232 Installing and maintaining firmware ...
Page 268: ...266 Administering advanced zoning ...
Page 284: ...282 Configuring Enterprise class platforms ...
Page 292: ...290 Routing traffic ...
Page 294: ...292 Interoperability for merged SANs ...
Page 302: ...300 Configuring the Distributed Management Server ...
Page 334: ...332 iSCSI gateway service ...
Page 340: ...338 Administering NPIV ...
Page 407: ...Fabric OS 6 2 administrator guide 405 ...
Page 408: ...406 Using the FC FC routing service ...
Page 438: ...434 Administering extended fabrics ...
Page 460: ...456 Administering ISL trunking ...
Page 516: ...512 FICON fabrics ...
Page 526: ...522 Configuring and monitoring FICON Extension Services ...
Page 540: ...536 Configuring the PID format ...
Page 544: ...540 Understanding legacy password behavior ...
Page 546: ...542 Mixed fabric configurations for non merge SANs ...
Page 550: ...546 Migrating from an MP Router to a 400 MP Router ...
Page 558: ...554 Inband Management ...
Page 572: ...568 ...