01.01.2021

Hp Msa2012i Firmware

4reenurse.netlify.app › ▀ ▀ Hp Msa2012i Firmware

Hp Msa2012i Firmware 8,4/10 7417 votes

Hp Msa2012i Firmware
Hp Storageworks Msa2012i Firmware
Hp Msa 2012 Firmware

Printable version

Hewlett Packard StorageWorks MSA2012i information, specs and pricing, along with reviews and troubleshooting tips written by IT pros. Configurazione hp msa2012i storage presentation. This feature is not available right now. Please try again later. HP uses Microsoft MPIO drivers for multipathing, not IBM SDDSM drivers. Windows 2008 & 2012 come with MPIO drivers built in. The time I've wasted on technology. Hewlett Packard Enterprise's MSA storage provides best-in-class performance with more capacity for your investment. Integrate compute and software-defined storage.

* RECOMMENDED * Online ROM Flash Component for Windows - HP Modular Smart Array 2000i Controller

By downloading, you agree to the terms and conditions of the Hewlett Packard Enterprise Software License Agreement.
Note: Some software requires a valid warranty, current Hewlett Packard Enterprise support contract, or a license fee.

Type:

Firmware (Entitlement Required) - Storage Controller

Version:

J212P01(A)(15 Aug 2014)

Operating System(s):

Microsoft Windows Server 2003 64-Bit Edition

Microsoft Windows Server 2003 for 64-bit Extended Systems

Microsoft Windows Server 2008 Itanium

Microsoft Windows Server 2008 R2

Microsoft Windows Server 2008 W32

Microsoft Windows Server 2008 x64

Microsoft Windows Server 2003

File name:

cp024308.exe (12 MB)

This package contains the firmware upgrade for the HP Modular Smart Array 2000i Controllers. The firmware update can be performed on any Server, Desktop or Laptop running Microsoft Windows (2003/2008) that has Ethernet connection to the MSA2012i Storage Array system.

The following enhancements were incorporated in J202P01, J212P01, and J302P01:

In the CLI, for the set advanced-settings command, the single-controller on parameter was added to set Single Controller redundancy mode for a single installed controller.

Please refer the Release Notes for a complete listing of fixes, known issues and work-arounds and installation instructions.

Prerequisites:

CAUTION: Updating Array controller firmware with only one Array controller will require the MSA2000 system to go offline to complete the firmware update.

IMPORTANT: In a single-controller system, updating firmware causes all disks to be temporarily inaccessible. Stop I/O to vdisks before performing this operation.

NOTE: It takes approximately 10 minutes for the firmware to load and for the automatic restart to complete with the first controller. If there is a second controller then the full process time is about 30 mintues. All firmware flash progress messages are logged to %systemdrive%CPQSYSTEMLogcpqsetup.log. A final completion message will be displayed. The Smart Component will manage the FTP and Partner Firmware Update (PFU) enable / disable settings.

NOTE: This Firmware Smart Component will not interoperate with HP Smart Update Manager (HP SUM) nor with the HP Firmware Maintenance CD.

To ensure the integrity of your download, HPE recommends verifying your results with this SHA-256 Checksum value:

41e79118f7bcf52dd7185ab481a8bbecdf3b4d2c3eeda735b2fe87b2e6208233

cp024308.exe

Reboot Requirement:
Reboot is not required after installation for updates to take effect and hardware stability to be maintained.

Installation:

IMPORTANT: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 the controller firmware, ensure that the storage system configuration is stable and is not being reconfigured or changed in any way. If any configurations changes are in progress, monitor them using the SMU and wait until they are completed before proceeding with the upgrade.

IMPORTANT: As with any other firmware upgrade it is a recommended best practice to ensure that you have a full backup prior to the upgrade.

Smart Component Installation Instructions

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 firmware 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 <ip_address> /user <username> /passwd <password> /s
where:
• ip_address is the management IP address of the array controller
• username is the username account with management rights
• password is the password for username
Instead of command line parameters you can use the following DOS environment variables:
• ao_address: set this variable for the IP address of array controller
• oa_username : set this variable for the username of array controller
• oa_password : set this variable for the password of array controller
NOTE: When prompted for logon information, enter credentials for an account with management access rights.

End User License Agreements:
Hewlett-Packard End User License Agreement

Upgrade Requirement:
Recommended - HPE recommends users update to this version at their earliest convenience.
Upgrade to controller firmware version J212P01 (A) is not necessary if the controllers are currently running J212P01.

Important:

CAUTION: Updating Array controller firmware with only one Array controller will require the MSA2000 system to go offline to complete the firmware update.

IMPORTANT: In a single-controller system, updating firmware causes all disks to be temporarily inaccessible. Stop I/O to vdisks before performing this operation.

NOTE: It takes approximately 10 minutes for the firmware to load and for the automatic restart to complete with the first controller. If there is a second controller then the full process time is about 30 mintues. All firmware flash progress messages are logged to %systemdrive%CPQSYSTEMLogcpqsetup.log. A final completion message will be displayed. The Smart Component will manage the FTP & Partner Firmware Update (PFU) enable / disable settings.

NOTE: This Firmware Smart Component will not interoperate with HP Smart Update Manager (HP SUM) nor with the HP Firmware Maintenance CD.

Notes:

J212P01build includes the following:

Storage Controller:J212P01
Memory Controller FPGA: F300R22
Storage Controller Loader: 15.010
MC Loader: 12.013
Management Controller: W421R46
CPLD: B110J27
Expander Controller: I320B18

Please refer the Release Notes for a complete listing of fixes, known issues and work-arounds and installation instructions.

Supported Devices and Features:

MSA2012i

The following fixes were incorporated in J202P01, J212P01, and J302P01:

In a Windows cluster environment, there was a possibility that a scrub, reconstruction, or volume creation could cause a controller to crash.
In the Windows Server 2008 R2 environment, cluster validation failed during the cluster creation.
iSCSI IQN/host mapping failed when uppercase characters were used in the IQN string.
Enclosure ID numbers were not updated when an additional drive enclosure was added to an array running on a single controller.
In the SMU, the enclosure status displayed a false red alert status following a firmware update when the status was actually OK.

Please refer the Release Notes for a complete listing of fixes, known issues and work-arounds and installation instructions.

CAUTION: Updating Array controller firmware with only one Array controller will require the MSA2000 system to go offline to complete the firmware update.

IMPORTANT: In a single-controller system, updating firmware causes all disks to be temporarily inaccessible. Stop I/O to vdisks before performing this operation.

NOTE: This Firmware Smart Component will not interoperate with HP Smart Update Manager (HP SUM) nor with the HP Firmware Maintenance CD.

Version:J212P01(A) (15 Aug 2014)

The following fixes were incorporated in J202P01, J212P01, and J302P01:

In a Windows cluster environment, there was a possibility that a scrub, reconstruction, or volume creation could cause a controller to crash.
In the Windows Server 2008 R2 environment, cluster validation failed during the cluster creation.
iSCSI IQN/host mapping failed when uppercase characters were used in the IQN string.
Enclosure ID numbers were not updated when an additional drive enclosure was added to an array running on a single controller.
In the SMU, the enclosure status displayed a false red alert status following a firmware update when the status was actually OK.

Please refer the Release Notes for a complete listing of fixes, known issues and work-arounds and installation instructions.

The following enhancements were incorporated in J202P01, J212P01, and J302P01:

In the CLI, for the set advanced-settings command, the single-controller on parameter was added to set Single Controller redundancy mode for a single installed controller.

Please refer the Release Notes for a complete listing of fixes, known issues and work-arounds and installation instructions.

Version:J212R10-03 (22 Dec 2011)

Upgrade Requirement:
Critical - HPE requires users update to this version immediately.
An issue exists on HP 2000 Modular Smart Array products running firmware versions J200P46, J210P22, or J300P22 that eventually causes controller configuration information to be lost, with subsequent loss of management capability from that controller. Array management, event messaging, and logging cease functioning, but host I/O continues to operate normally. This issue affects the ability to manage the array only from the affected controller; if a partner controller is available, the array can be managed through the partner controller. Because configuration information is stored in non-volatile memory, resetting or powering off the controller does not clear this error. If the issue occurs, the controller must be replaced. This failure mode is time sensitive and HP recommends immediately upgrading firmware on all MSA2000 controllers. This is not a hardware issue and proactive replacement of a controller is not a solution. To avoid this condition, you must upgrade your controller to the latest version of firmware.
Versions of firmware that resolve this issue are in the following table.

Product	Corrected Firmware	Affected Firmware
MSA2000 FC	J202R10, J201R12, J201R09, J200P50	J200P46
MSA2000 iSCSI	J212R10, J211R09, J210P23	J210P22
MSA2000 SAS	J302R10, J301R09, J300P23	J300P22

Some of the key fixes incorporated in J201R10, J212R10 and J302R10 are:

Scrub caused controllers to halt.
Identical vdisks created through the CLI and SMU report different volume sizes.
Power Supply and I/O module statuses were reported differently on Controller A and Controller B.
Controller halted when a vdisk expansion started.
In dual-controller configurations, if one controller halted, the Fibre Channel host links did not failover to the surviving controller.
Medium errors on drives in a RAID 6 vdisk caused another vdisk to report a critical state.
The controller halted when clearing metadata of a leftover disk.
Due to loss of heartbeat between the two controllers, one of the controllers halted.
The event log was not updated when a drive was removed (or marked as “down”) while a utility, such as verify, was running.
RAID 6 reconstruct caused partner controller to halt.
Volumes became unaccessible when converting a master volume to a standard volume.
Drives in non fault-tolerant vdisks did not report unrecovered media error as a warning.
Heavy RSR load caused a controller to halt.
Added “year” to the critical error log.
Controller halted when utility timing was in conflict.
Controller halted when, under heavy I/O loads, a RAID 6 vdisk had one or more failed drives.
There were verification errors after an internal error recovery process completed.
After a failover, an incorrect vdisk utility status was reported in the CLI and SMU.
Host lost access when a large vdisk was being rebuilt.
The spare drive was not activated when the vdisk passed into a critical state.
Updated scrub utility for improved behavior.
RAID 6 reconstruct reported incorrectly when an additional failure occurred.
Drive LED behavior was inconsistent.

Please refer to the Release Notes for a complete list of fixes, known issues and work-arounds and installation instructions.

The smart component now supports live logging of the installation progress on the Smart Component GUI.

Type:

Firmware (Entitlement Required) - Storage Controller

Version:

J212P01(A)(15 Aug 2014)

Operating System(s):

Microsoft Windows Server 2003

Microsoft Windows Server 2003 64-Bit Edition

Microsoft Windows Server 2003 for 64-bit Extended Systems

Microsoft Windows Server 2008 Itanium

Microsoft Windows Server 2008 R2

Microsoft Windows Server 2008 W32

Microsoft Windows Server 2008 x64

Description

Enhancements

The following enhancements were incorporated in J202P01, J212P01, and J302P01:

In the CLI, for the set advanced-settings command, the single-controller on parameter was added to set Single Controller redundancy mode for a single installed controller.

Please refer the Release Notes for a complete listing of fixes, known issues and work-arounds and installation instructions.

Installation Instructions

Prerequisites:

CAUTION: Updating Array controller firmware with only one Array controller will require the MSA2000 system to go offline to complete the firmware update.

IMPORTANT: In a single-controller system, updating firmware causes all disks to be temporarily inaccessible. Stop I/O to vdisks before performing this operation.

NOTE: This Firmware Smart Component will not interoperate with HP Smart Update Manager (HP SUM) nor with the HP Firmware Maintenance CD.

To ensure the integrity of your download, HPE recommends verifying your results with this SHA-256 Checksum value:

41e79118f7bcf52dd7185ab481a8bbecdf3b4d2c3eeda735b2fe87b2e6208233

cp024308.exe

Reboot Requirement:
Reboot is not required after installation for updates to take effect and hardware stability to be maintained.

Installation:

IMPORTANT: As with any other firmware upgrade it is a recommended best practice to ensure that you have a full backup prior to the upgrade.

Smart Component Installation Instructions

Release Notes

End User License Agreements:
Hewlett-Packard End User License Agreement

Important:

CAUTION: Updating Array controller firmware with only one Array controller will require the MSA2000 system to go offline to complete the firmware update.

IMPORTANT: In a single-controller system, updating firmware causes all disks to be temporarily inaccessible. Stop I/O to vdisks before performing this operation.

NOTE: This Firmware Smart Component will not interoperate with HP Smart Update Manager (HP SUM) nor with the HP Firmware Maintenance CD.

Notes:

J212P01build includes the following:

Storage Controller:J212P01
Memory Controller FPGA: F300R22
Storage Controller Loader: 15.010
MC Loader: 12.013
Management Controller: W421R46
CPLD: B110J27
Expander Controller: I320B18

Please refer the Release Notes for a complete listing of fixes, known issues and work-arounds and installation instructions.

Supported Devices and Features:

MSA2012i

Fixes

The following fixes were incorporated in J202P01, J212P01, and J302P01:

In a Windows cluster environment, there was a possibility that a scrub, reconstruction, or volume creation could cause a controller to crash.
In the Windows Server 2008 R2 environment, cluster validation failed during the cluster creation.
iSCSI IQN/host mapping failed when uppercase characters were used in the IQN string.
Enclosure ID numbers were not updated when an additional drive enclosure was added to an array running on a single controller.
In the SMU, the enclosure status displayed a false red alert status following a firmware update when the status was actually OK.

Please refer the Release Notes for a complete listing of fixes, known issues and work-arounds and installation instructions.

Important

CAUTION: Updating Array controller firmware with only one Array controller will require the MSA2000 system to go offline to complete the firmware update.

IMPORTANT: In a single-controller system, updating firmware causes all disks to be temporarily inaccessible. Stop I/O to vdisks before performing this operation. kodi download for apple mac

NOTE: This Firmware Smart Component will not interoperate with HP Smart Update Manager (HP SUM) nor with the HP Firmware Maintenance CD.

Revision History

Version:J212P01(A) (15 Aug 2014)

The following fixes were incorporated in J202P01, J212P01, and J302P01:
Driver epson esc/p standard 3.

In a Windows cluster environment, there was a possibility that a scrub, reconstruction, or volume creation could cause a controller to crash.
In the Windows Server 2008 R2 environment, cluster validation failed during the cluster creation.
iSCSI IQN/host mapping failed when uppercase characters were used in the IQN string.
Enclosure ID numbers were not updated when an additional drive enclosure was added to an array running on a single controller.
In the SMU, the enclosure status displayed a false red alert status following a firmware update when the status was actually OK.

Please refer the Release Notes for a complete listing of fixes, known issues and work-arounds and installation instructions.

The following enhancements were incorporated in J202P01, J212P01, and J302P01:

In the CLI, for the set advanced-settings command, the single-controller on parameter was added to set Single Controller redundancy mode for a single installed controller.

Please refer the Release Notes for a complete listing of fixes, known issues and work-arounds and installation instructions.

Version:J212R10-03 (22 Dec 2011)

Product	Corrected Firmware	Affected Firmware
MSA2000 FC	J202R10, J201R12, J201R09, J200P50	J200P46
MSA2000 iSCSI	J212R10, J211R09, J210P23	J210P22
MSA2000 SAS	J302R10, J301R09, J300P23	J300P22

Some of the key fixes incorporated in J201R10, J212R10 and J302R10 are:

Scrub caused controllers to halt.
Identical vdisks created through the CLI and SMU report different volume sizes.
Power Supply and I/O module statuses were reported differently on Controller A and Controller B.
Controller halted when a vdisk expansion started.
In dual-controller configurations, if one controller halted, the Fibre Channel host links did not failover to the surviving controller.
Medium errors on drives in a RAID 6 vdisk caused another vdisk to report a critical state.
The controller halted when clearing metadata of a leftover disk.
Due to loss of heartbeat between the two controllers, one of the controllers halted.
The event log was not updated when a drive was removed (or marked as “down”) while a utility, such as verify, was running.
RAID 6 reconstruct caused partner controller to halt.
Volumes became unaccessible when converting a master volume to a standard volume.
Drives in non fault-tolerant vdisks did not report unrecovered media error as a warning.
Heavy RSR load caused a controller to halt.
Added “year” to the critical error log.
Controller halted when utility timing was in conflict.
Controller halted when, under heavy I/O loads, a RAID 6 vdisk had one or more failed drives.
There were verification errors after an internal error recovery process completed.
After a failover, an incorrect vdisk utility status was reported in the CLI and SMU.
Host lost access when a large vdisk was being rebuilt.
The spare drive was not activated when the vdisk passed into a critical state.
Updated scrub utility for improved behavior.
RAID 6 reconstruct reported incorrectly when an additional failure occurred.
Drive LED behavior was inconsistent.

Please refer to the Release Notes for a complete list of fixes, known issues and work-arounds and installation instructions.

The smart component now supports live logging of the installation progress on the Smart Component GUI.

When setting a new firmware baseline for an enclosure, you have the option to update the: Enclosure only (OA firmware) Enclosure, logical interconnect, and the server profiles (OA, interconnect, and server firmware, including iLO, for servers with server profiles). AJ747A - HP StorageWorks MSA2012i Dual Controller Array. What's in the box. Software: Compatible operating systems: Microsoft Windows 2003 R2; Microsoft Windows 2003 X64; Red Hat Linux 5; SUSE Linux 10; VMware 3.5. Hewlett Packard specifically disclaims the implied warranty of merchantability and fitness for a.

Legal Disclaimer: Products sold prior to the November 1, 2015 separation of Hewlett-Packard Company into Hewlett Packard Enterprise Company and HP Inc. may have older product names and model numbers that differ from current models.

Hi gurus,
I'm interested in buying my first SAN (iSCSI) for use with VMware vSphere. My company is small so cost is very important.Through various inquiries, it seems that the HP MSA2012i Server is a recommended choice.
Can anyone give me more details on the server:
1) does it come with it's on SAN software or do I need to install one, ie. OpenFiler
2) I need an explanation on single controller versus dual controller.

Hp Msa2012i Firmware

3) I'm virtualizing Exchange and SQL primarly for clustering/redundancy, will regular SATA drives suffice or will SAS drives provide better performance given the price difference.

Hp Storageworks Msa2012i Firmware

Hp Msa 2012 Firmware

4) any other tips/guides and what to shop for will be greatly appreciated.