FW 6.4.0.06.00 McDATA 4Gb SAN Switch for HP p-Class BladeSystem Release Notes (AA-RW1ZD-TE, November 2006)

When using the McDATA Web Server application, ensure that the switch has been removed from
the Selected Individual Addresses list in Discover Setup in HAFM, or alternatively that HAFM has
been closed and all services stopped prior to attempting the upgrade.
When using the CLI, verify that the McDATA Web Server application is not open, and that the
switch has been removed from the Selected Individual Addresses list in Discover Setup in HAFM,
or that HAFM applications are closed and HAFM services stopped.
This single session limit is no longer an issue once you have loaded the rmware version 5.2.2.15.00
or later and attempted an NDCLA to a later release. Due to this limitation in the previous rmware
versions, HP recommends that the switch rmware be upgraded to 5.2.2.15.00 or later prior to upgrading
the management applications.
Prior to upgrading rmware, HP recommends that you back up the switch conguration in the event that
a failure should occur. Refer to “Backing up and restoring switch congurations” in the McDATA 4Gb
SAN Switch for HP p-Class BladeSystem user guide for more details.
If you attempt to perform a non-disruptive activation without satisfying the following conditions, the switch
may perform a disruptive activation:
The current rmware version is a version that supports upgrading to the new version
No changes are being made to switches in the fabric including powering up, powering down,
disconnecting or connecting ISLs, nameserver queries, and switch conguration changes
No port in the fabric is in the diagnostic state
No zoning changes are being made in the fabric
No changes are being made to attached devices including powering up, powering down,
disconnecting, connecting, and HBA conguration changes
Ports that are stable when the non-disruptive activation begins and then change states, will be reset.
When the non-disruptive activation is complete, McDATA Web Server sessions reconnect automatically.
However, Telnet sessions must be restarted manually.
After upgrading rmware from 5.x.x.xx.xx to 6.4.0.06.00, any open Element Manager or McDATA Web
Server session will indicate that the rmware is not supported. This is simply an indication that the new
rmware is not supported by the current management session. To correct this, close the McDATA Web
Browser session and the browser window, or the Element Manager session. The unsupported rmware
message will not reoccur in subsequent McDATA Web Server or Element Manager sessions.
Installing rmware involves loading, unpacking, and activating the rmware image on the switch.
Activation of the rmware involves a hot reset to the switch, which is non-disruptive to attached devices.
During a hot reset operation, fabric services will be unavailable for a short period (30—75 seconds).
To ensure that a non-disruptive activation is successful, verify that all administrative changes to the
fabric (if any) are complete. When you need to upgrade rmware on multiple switches, only perform
the rmware upgrade on one switch at a time, and allow a 75 second wait prior to performing the
rmware upgrade on the next switch.
Con
siderations for downgrading the version of rmware
Dow
ngrading the version of rmware to previous rmware releases is a disruptive operation. Prior
to
downgrading rmware, attached devices should be prepared for disruption during the rmware
do
wngrade. Firmware on the McDATA 4Gb SAN Switch for HP p-Class BladeSystem cannot be
do
wngraded to a version earlier than 5.2.0.29.00. Prior to downgrading rmware,itisrecommended
t
hat you back up the switch conguration in the event that a failure should occur. Refer to “Backing
u
p and restoring switch congurations” in the McDATA 4Gb SAN Switch for HP p-Class BladeSystem
u
ser guide for more details.
8