HP StorageWorks 2000fc - G2 Modular Smart Array Bedienungsanleitung

HP StorageWorks MSA2000 G2

Firmware Release Notes

Part number: 508849–004

Fourth edition: December 2009

Version: M110R25

Description

This smart component provides firmware for MSA2000 G2 Storage Array Controllers. The firmware

update can be performed on any computer running a supported operating system that has an Ethernet

connection to the MSA2000 G2 Storage Array system. For supported operating systems, see Operating

systems.

Update recommendation Optional

Supersedes This firmware is an update for all previously released firmware for the HP StorageWorks

MSA2000 G2 family of products.

Product models

•HP StorageWorks MSA2312fc G2

•HP StorageWorks MSA2312i G2

•HP StorageWorks MSA2312sa G2

•HP StorageWorks MSA2324fc G2

•HP StorageWorks MSA2324i G2

•HP StorageWorks MSA2324sa G2

Operating systems

•Microsoft Windows 2003 x64 Edition

•Microsoft Windows 2003 x64 Edition (Itanium)

•Microsoft Windows 2008

•Microsoft Windows 2008 x64

•Microsoft Windows 2008 Itanium

•Red Hat Enterprise Linux 4

•Red Hat Enterprise Linux 5

•SUSE Linux Enterprise Server 10

Enhancements

•Made general improvements to the logging feature.

•Added disk firmware update support for future versions of 2TB SATA disk drives.

•Added some optimizations for snapshots.

•Improved the integration with Common Information Model (CIM) by adding support for single

ported drive reporting.

•Added an analyze function to the background scrub utility that provides information to help isolate

issues.

•Improved the dynamic sparing feature so that it will use a free disk even when there is metadata

from a previous vdisk on the disk.

HP StorageWorks MSA2000 G2 Firmware Release Notes 3

•Improved ability to communicate with a controller after it has been shut down, to improve restart

behavior.

•Enhanced the SNMP community string to support strings that contain dash and underscore char-

acters.

•Improved the SNMP Notification page in internationalized systems that uses non-ASCI characters,

such as Japanese.

Fixes

•Fixed a problem detecting the number of disk drive bays in an expansion enclosure.

•Fixed the issue that all drives spun up concurrently when a single power supply was in use. If only

a single power supply is functioning, disk drives now spin up in a staggered manner.

•Fixed a situation where a SATA disk drive may be dropped from a vdisk during a firmware up-

grade.

•Fixed a problem where user credentials were reset to default values when controller A was replaced.

•Fixed an issue where the vdisk number was mis-reported.

•Fixed an issue where a firmware upgrade did not error out when an invalid package was used.

•Fixed an issue that allowed a user to set the independent cache mode to an unsupported config-

uration.

•Fixed an issue that a reconstructing vdisk would report as completed when just beginning the re-

build.

•Fixed an issue where a failed disk drive might cause a controller to stall.

•Fixed an issue where correctable ECC errors caused a scrub failure.

•Fixed a problem where a scrub error was reported when, in fact, the background scrub was

manually stopped.

•Fixed an issue where an offline vdisk might not be appropriately quarantined when an array is

powered up.

•Fixed an issue where the array did not correctly report all supported persistent reservation types.

•Fixed an issue where deleting a vdisk failed.

•Fixed an issue that, while deleting a snapshot, could lead to an error and cause the snapshot to

not be deleted.

•Fixed an issue where a quarantine event caused a scrub error.

•Fixed an issue where media errors were not leading to a disk drive being removed from service.

•Fixed a situation where IO requests during a failover would fail out with the following error message:

“Request not supported”.

•Fixed a problem where failover did not occur, even when a component failed.

•Fixed a situation where reconstruction progress stuck at 0%.

•Fixed a rare timing issue that lead to a drive enclosure not being discovered on a reboot.

•Fixed an issue that lead to drive enclosure firmware update failure.

•Fixed a problem where a LUN reset did not clear same sector reads.

•Fixed an issue where a controller failover lead to IP settings being lost.

•Fixed an issue where a Windows OS might see a volume that does not exist at LUN 0.

•Fixed an issue where both storage controllers became unresponsive when a disk issue caused a

general protection fault to be delivered to both controllers.

•Fixed an issue that could cause a storage controller to crash while I/O is being written to a RAID

6 vdisk that is in a critical state.

•Fixed a timing issue that lead to a controller becoming unresponsive.

•Fixed an issue where SAS port values were reported incorrectly.

•Fixed issues with cold temperature monitoring.

•Fixed an issue where a drive that reports a SMART error may not be downed appropriately.

•Fixed a problem where a drive failure during initialization could cause a controller to crash.

•Fixed a problem where a controller was brought down by a disk reset from the partner controller.

•Fixed the licensing engine to prevent an invalid license from loading.

•Fixed an issue where an uncorrectable ECC error caused a controller to crash.

•Fixed an issue where a controller would stop responding when disks with media errors are in the

system.

•Fixed an issue that lead to a vdisk faulting when controller A was replaced.

•Fixed an issue where a vdisk using mirroring would fail to initialize when the maximum size was

requested.

•Fixed a problem where a controller crash could be triggered by switching the owning controller

of a vdisk when snapshot volumes were resident on the vdisk.

•Fixed an issue where the controller would stop responding when a snapshot with a duplicate name

was requested.

•Fixed an issue where a RAID 10 vdisk in quarantine had a utility would fix a parity error even

though there was a missing member of the vdisk.

•Fixed a problem where an erroneous SuperCap failure was reported.

•Fixed a rare issue where controller temperature was displayed incorrectly .

•Fixed an issue where the default LUN was not released for reuse when the owning volume was

deleted in a single controller array.

•Fixed an issue of inconsistent behavior when moving drives from one drive enclosure to another

drive enclosure.

•Fixed an issue on RAID 10 and RAID 50 vdisks that kept spares from being deleted.

•Fixed an issue that lead the enclosure health status to be reported incorrectly.

•Improved the initialization time for RAID 1 and RAID 10 vdisks.

•Fixed an error on the iSCSI controller where a controller pair would lose connection and force

one of the controllers to shut the other down.

•Fixed an issue where LUNs were presented in both PDA (Peripheral Device Addressing) and VSA

(Volume Set Addressing) modes.

•Fixed an issue with SNMP incorrectly reporting certain traps.

•Fixed a problem where the loop IDs of the controllers were not properly displayed.

•Fixed an issue where part and serial number were not displayed correctly.

•Fixed a problem where online help was formatting incorrectly (CLI).

•Added a function to allow SNMP test traps to be sent (CLI).

•Fixed a problem that caused enabling NTP to fail because of an improper condition (CLI).

•Fixed an issue where set disk-parameters was not accepting valid input (CLI). (Example:

set disk-parameters smart off)

•Fixed an issue where a set job-parameters utility-priority command returned an

error of "Error: Invalid FC topology" (CLI).

•Fixed an issue that lead to inconsistent vdisk status reporting (CLI).

•Fixed various cosmetic issues (GUI).

•Fixed an issue where changing volume names allowed the user to change the name to a volume

that is already in use (GUI).

•Fixed Help to provide the correct location for Save Logs feature (GUI).

HP StorageWorks MSA2000 G2 Firmware Release Notes 5

•Fixed some issues in the Japanese version of the GUI.

•Fixed an issue where the SMU page was not updating after creating volumes (GUI).

•Fixed an issue where the user inactivity timeout was not working properly (GUI).

Important notes

WARNING!

Do not power cycle or restart during the firmware update. This can result in loss of capabilities for

the unit.

CAUTION:

Updating Array controller firmware with only one Array controller requires the MSA2000 system to

be offline. In a single-controller system, updating firmware causes all disks to be temporarily

inaccessible. Stop I/O to vdisks before updating the firmware.

IMPORTANT:

Reverting the firmware version back to M100R18-05 from the M110 code branch requires HP technical

support.

NOTE:

•Smart Components are available for this firmware. These are located on the Windows and Linux

software deliverables page for this storage product.

•It takes approximately 10 minutes for the firmware to load and for the automatic restart to complete

with the first controller. With a second controller, the full process time is approximately 25 minutes.

•All firmware flash progress messages are logged to \CPQSYSTEM\Log\cpqsetup.log on

the system drive in Windows and /var/cpq/Component.log in Linux.

•The Smart Component manages the FTP & Partner Firmware Update (PFU) enable / disable settings.

•Updating array controller firmware may result in receiving new event messages that are not de-

scribed in earlier versions of documentation. For comprehensive event message documentation,

see the most current version of the

HP StorageWorks 2000 G2 Modular Smart Array Reference

Guide

Installation instructions

When planning for a firmware upgrade, select and schedule an appropriate time to perform an online

upgrade. For redundant controller systems, to ensure the success of an online upgrade, selecting the

appropriate time is essential. Because the online firmware upgrade is performed while host I/Os are

being serviced, the I/O load can impact the upgrade process. Selecting a period of low I/O activity

will ensure the upgrade completes as quickly as possible, and will avoid disruptions to hosts and

applications due to timeouts.

CAUTION:

Before upgrading controller firmware, ensure that the storage system configuration is stable and is

not being reconfigured or changed in any way. If configurations changes are in progress, monitor

them and wait until they are completed before proceeding with the upgrade.

IMPORTANT:

As with any firmware upgrade, it is a recommended best practice to ensure that you have a full

backup prior to the upgrade.

NOTE:

To download this module from the HP website, right-click the link and save the file to your local

filesystem. You cannot double-click the link.

Smart Component installation instructions for Windows environments

This is a self-extracting executable module. You can execute this module from the Windows graphical

user interface (GUI) or the command line console (CLI).

GUI option

1. Place the downloaded Smart Component package in a temporary directory.

2. Using Windows Explorer, navigate to the directory containing the download.

3. Double click the executeable file.

4. Follow onscreen instructions.

NOTE:

When prompted for logon information, enter credentials for an account with management

access rights.

CLI option

The following syntax can be used to invoke at the command line:

cpxxxxxxx.exe /target <MSA2300_IP> /user <USER_NAME> /passwd <PASSWORD>

where:

•MSA2000_IP is the management IP address of the MSA2300 controller

•USER_NAME is the username account with manage rights

•PASSWORD is the password for username

Instead of command line parameters you can use the following DOS environment variables:

HP StorageWorks MSA2000 G2 Firmware Release Notes 7

•OA_ADDRESS: set this variable for the IP address of MSA2300 controller

•OA_USERNAME : set this variable for the username of MSA2300 controller

•OA_PASSWORD : set this variable for the password of MSA2300 controller

NOTE:

When prompted for logon information, enter credentials for an account with management access

rights.

Smart Component installation instructions for Linux environments

1. Place the Smart Component in a temporary directory.

2. Open a Linux command console.

3. From the directory containing the downloaded file, enable execute access to this model by typing

chmod +x CPxxxxxx.scexe, where CPxxxxxx.scexe represents the downloaded file.

4. Execute the Smart Component by entering a command similar to the following: ./

CPxxxxxx.scexe --target <ip_address> --user <manage_username> --passwd

If the user name or password contains an exclamation mark (!), enclose the string in single quotes

or enter a backslash (\) before the exclamation point. For example, '!manage' or \!manage.

5. Follow onscreen instructions.

NOTE:

When prompted for logon information, enter credentials for an account with management

access rights.

Smart Component installation instructions using Storage Management Utility

(SMU)

WARNING!

Do not cycle power or restart the controller during a firmware update. If the update is interrupted or

there is a power failure, the module could become inoperative. If this occurs, contact technical support.

The module may need to be returned to the factory for reprogramming.

1. Extract the contents of the smart component.

In Windows —Select the Extract button on the first screen of the smart component.

In Linux —./CPXXXXXX.scexe --unpack=<folder name> extracts the contents of the smart

component to <folder name> folder. For example,./CP001123.scexe –unpack=extract_here

2. Locate the firmware file in the extracted folder. The firmware filename is in the following format:

mercurysw-M110R25-01.bin

3. If the system has a single controller, stop I/O to vdisks before starting the firmware update.

4. In the MANAGE section, under UPDATE SOFTWARE > controller software. The tables titled Load

Software to RAID Controller A show the currently installed versions.

5. Click Browse and then select the firmware file to install.

6. Click Load Software Package File. It takes approximately 10 minutes for the firmware to load

and for the automatic restart to complete on the controller you are connected to. Wait for the

progress messages to specify that the update has completed. If Partner Firmware Update

is enabled, allow an additional 20 minutes for the partner controller to be updated.

7. Verify that the proper firmware version appears for each controller module.

Smart Component installation instructions using FTP

NOTE:

It takes approximately 10 minutes for the firmware to load and for the automatic restart to complete.

Progress messages are displayed in the FTP interface during that time. Wait for the progress messages

to specify that the firmware load has completed. If the system Partner Firmware Update (PFU)

option is enabled, allow an additional 20 minutes for the partner controller to be updated. No

messages are displayed in the FTP interface during PFU.

1. Extract the contents of the smart component.

In Windows —Select the Extract button on the first screen of the smart component.

In Linux —./CPXXXXXX.scexe --unpack=<folder name> extracts the contents of the smart

component to <folder name> folder. For example,./CP001123.scexe –unpack=extract_here

2. Locate the firmware file in the extracted folder. The firmware file name is as follows:

: mercurysw-M110R25-01.bin

3. Using the MSA2000 SMU, prepare to use FTP:

a. Determine the network-port IP addresses of the system controllers.

b. Verify that the system FTP service is enabled.

c. Verify that the user you will log in as has permission to use the FTP interface and has manage

access rights.

4. Open a command prompt (Windows) or a terminal window (UNIX), and navigate to the directory

containing the firmware file to load.

a. Enter ftp <controller-network-address>For example: ftp 10.1.0.9

b. Log in as an FTP user (user = ftp, password = flash).

c. Enter put <firmware-file> flashFor example: put J210P19-02.bin flash

Binary file installation instructions using Storage Management Utility (SMU)

WARNING!

Do not perform a power cycle or controller restart during a firmware update. If the update is interrupted

or there is a power failure, the module might become inoperative. If this occurs, contact technical

support. The module might need to be returned to the factory for reprogramming.

HP StorageWorks MSA2000 G2 Firmware Release Notes 9

1. Obtain the appropriate firmware file and download it to your computer or network.

2. If the system has a single controller, stop I/O to vdisks before starting the firmware update.

3. In the Configuration View panel, right-click the system and select Tools > Update Firmware. The

tables titled Current Versions of Controller Module A and Current Versions of Controller Module

B show the currently installed versions.

4. Click Browse and select the firmware file to install.

5. Click Install Controller-Module Firmware File. It takes approximately 10 minutes for the firmware

to load and for the automatic restart to complete on the controller you are connected to. Wait

for the progress messages to specify that the update has completed. If Partner Firmware Update

is enabled, allow an additional 20 minutes for the partner controller to be updated.

6. Verify that the proper firmware version appears for each controller module.

Binary file installation instructions using FTP

NOTE:

It takes approximately 10 minutes for the firmware to load and for the automatic restart to complete.

Progress messages are displayed in the FTP interface during that time. Wait for the progress messages

to specify that the firmware load has completed. If the system Partner Firmware Update (PFU) option

is enabled, allow an additional 20 minutes for the partner controller to be updated. No messages

are displayed in the FTP interface during PFU.

1. Download the firmware file to your computer or network.

2. Using the MSA2000 G2 SMU, prepare to use FTP:

a. Determine the network-port IP addresses of the system controllers.

b. Verify that the system FTP service is enabled.

c. Verify that the user you will log in as has permission to use the FTP interface and has manage

access rights.

3. Open a command prompt (Windows) or a terminal window (UNIX), and navigate to the directory

containing the firmware file to load.

a. Enter ftp <controller-network-address>For example: ftp 10.1.0.9

b. Log in as an FTP user (user = ftp, password = flash).

c. Enter put <firmware-file> flash. For example: put M110R25–01.bin flash

Known issues and workarounds

This is a cumulative list of known issues and workarounds for this release.

•Issue: Installing a firmware image that is not supported for the array in the Storage Management Utility

(SMU) Update Firmware page may cause issues in the SMU.

•Workaround: Ensure that the correct array firmware image is used when upgrading firmware. If an incorrect

firmware image is loaded, the SMU may display a status of loading firmware or updating firmware for a

long period, and then display a status of the controller is unresponsive, which is normal during rebooting.

If the SMU stays in this cycle, restart the controller. The SMU may report that the firmware as been updated

successfully, but it has not been updated because the firmware is not actually supported.

Andere Handbücher für StorageWorks 2000fc - G2 Modular Smart Array

Dieses Handbuch passt für folgende Modelle

Inhaltsverzeichnis

Andere HP Lagerung Handbücher

HP STORAGEWORKS ALL-IN-ONE STORAGE SYSTEM Bedienungsanleitung

HP LTO-3 HH Bedienungsanleitung

HP 7906 Bedienungsanleitung

HP STORAGEWORKS ALL-IN-ONE STORAGE SYSTEM Bedienungsanleitung

HP 6400/8400 Bedienungsanleitung

HP StorageWorks D2700 Bedienungsanleitung

HP 3PAR StoreServ 7000 Bedienungsanleitung

HP StorageWorks TL895 Bedienungsanleitung

HP 705 Kurzanleitung

HP Pavilion p6000 - Desktop PC Bedienungsanleitung

HP Surestore Disk Array 12h - And FC60 Bedienungsanleitung

HP 624192-B21 Gebrauchsanweisung

HP LeftHand P4000 - SAN Solutions Bedienungsanleitung

HP 705 Workstation Bedienungsanleitung

HP Open View Produkthandbuch

HP 500 G2 Installationsanleitung

HP StorageWorks DAT 72 Bedienungsanleitung

HP P9000 Bedienungsanleitung

HP Surestore 5200ex - Optical Disk Drives Bedienungsanleitung

HP Data Vault Technisches Datenblatt

HP EVA P6000 Service-Handbuch

HP Ultrium Drive Produkthandbuch

HP StorageWorks 8000 - NAS Bedienungsanleitung

HP StorageWorks 4000/6000/8000 - Enterprise Virtual... Bedienungsanleitung

Beliebte Lagerung Handbücher anderer Marken

QNAP

QNAP TS 32PXU Series Bedienungsanleitung

LaCie

LaCie RUGGED RAID Bedienungsanleitung

Freecom

Freecom CLS DOCK Bedienungsanleitung

PNY

PNY Attache P-FD64MBATT3 Bedienungsanleitung

OLT

OLT 6x6 Maximizer Bedienungsanleitung

Transcend

Transcend JetFlash 160 Bedienungsanleitung

LaCie

LaCie RUGGED MINI Bedienungsanleitung

Thunderbolt

Thunderbolt 600 Bedienungsanleitung

Panasonic

Panasonic LB-DH8 series Handbuch

Intel

Intel RAID High Availability Bedienungsanleitung

LaCie

LaCie 12big Thunderbolt 3 Bedienungsanleitung

Spectra Logic

Spectra Logic T-Series Spectra T50e Bedienungsanleitung

Panasonic

Panasonic LKM-F931-1 Bedienungsanleitung

Tabernus

Tabernus Enterprise Erase E2400 Bedienungsanleitung

Rocstor

Rocstor COMMANDER 3F series Bedienungsanleitung

Western Digital

Western Digital Ultrastar Data60 Bedienungsanleitung

Dell

Dell PowerVault MD3600f Series Bedienungsanleitung

CFI

CFI TERA STOR SATA RAID IV Bedienungsanleitung