Производитель: HP
Размер: 255.88 kb
Название файла:
|
К этому устройству также есть другие инструкции:
Фрагмент инструкции
NOTE:
To allow a Non-disruptive Code Load and Activation (NDCLA) with firmware versions earlier than
5.2.2.15.00, only one of the management applications (Element Manager, McDATA Web Server, or the
CLI) can be running during the upgrade process.
• 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 firmware version 5.2.2.15.00 or
later and attempted an NDCLA to a later release. Due to this limitation in the previous firmware versions,
HP recommends that the switch firmware be upgraded to 5.2.2.15.00 or later prior to upgrading
the management applications.
Prior to upgrading firmware, HP recommends that you back up the switch configuration in the event that
a failure should occur. Refer to “Backing up and restoring switch configurations” in the McDATA 4Gb
SAN Switch for HP p-Class BladeSystem user guide for more details.
You can upgrade to firmware version 6.4.0.13.00 from the previously released versions on an operating
switch without disrupting data traffic or having to re-initialize attached devices. The switch is not required
to be offline before performing an upgrade operation. For a successful non-disruptive activation, first
ensure that the following conditions are satisfied:
• No changes are being made to switches in the fabric including powering up, powering down,
disconnecting or connecting ISLs, nameserver queries, and switch configuration 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 configuration 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.
When upgrading firmware from 5.x.x.xx.xx to 6.4.0.06.00 or later, any open Element Manager
or McDATA Web Server session will indicate that the firmware is not supported. This is simply an
indication that the new firmware 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 firmware message will not recur in subsequent McDATA Web Server or Element
Manager sessions.
Installing firmware involves loading, unpacking, and activating the firmware image on the switch.
Activation of the firmware involves a hot reset to the switch, which is non-disruptive to at ached 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 firmware on multiple switches, only perform
the firmware upgrade on one switch at a time, and allow a 75 second wait prior to performing the
firmware upgrade on the next switch.
Considerations for downgrading the version of firmware
Downgrading the version of firmware to previous firmware releases is a disruptive operation. Prior
to downgrading firmware, at ached devices should be prepared for disruption during the firmware
downgrade. Firmware on the McDATA 4Gb SAN Switch for HP p-Class BladeSystem cannot be
downgraded to a version earlier than 5.2.0.29.00. Prior to downgrading firmware, it is recommended
that you back up the switch configuration in the event that a failure should occur. See “Backing up
8
...