HP StorageWorks MSA2012i HP 2000 Modular Smart Array Controller Firmware J202P - Page 4
Product models, Operating systems, Fixes and enhancements
View all HP StorageWorks MSA2012i manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 4 highlights
Product models • HP 2012fc Modular Smart Array (HP MSA2012fc) • HP 2212fc Modular Smart Array (HP MSA2212fc) • HP 2012i Modular Smart Array (HP MSA2012i) • HP 2012sa Modular Smart Array (HP MSA2012sa) Operating systems Operating systems supported for use with HP MSA2000 G1 Controllers (and when installing the binary firmware package): • Microsoft Windows Server 2008 x64 - All Editions • Microsoft Windows Server 2008 W32 - All Editions • Microsoft Windows Server 2003 x64 Edition (Including R2 & Base Edition) • Microsoft Windows Server 2003 - All Editions (Including R2 & Base Edition) • Red Hat Enterprise Linux 5 Server (x86-64) • Red Hat Enterprise Linux 5 Server (x86) • SUSE LINUX Enterprise Server 10 (AMD64/EM64T) • SUSE LINUX Enterprise Server 10 (x86) • VMware ESX/ESXi 4.1 • VMware ESX/ESXi 4.0 • VMware ESX/ESXi Server 3.5 • VMware ESX Server 3.0 Operating systems supported for use when installing the Smart Component firmware package: • Microsoft Windows Server 2008 x64 - All Editions • Microsoft Windows Server 2008 W32 - All Editions • Microsoft Windows Server 2008 Itanium • Microsoft Windows Server 2003 x64 Edition (Including R2 & Base Edition) • Microsoft Windows Server 2003 - All Editions (Including R2 & Base Edition) • Microsoft Windows Server 2003 64-Bit Edition (Itanium) • Red Hat Enterprise Linux 5 Server (x86-64) • Red Hat Enterprise Linux 5 Server (x86) • SUSE LINUX Enterprise Server 10 (AMD64/EM64T) • SUSE LINUX Enterprise Server 10 (x86) Fixes and enhancements The following enhancements and 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. 4 Product models