3PAR InForm OS 2.3.1 MU4 Release Notes (QL226-96261, September 2011)

Supported Platforms
The 3PAR Configuration Matrix for InForm OS 2.3.1 contains information about supported hardware
and software platforms. To obtain a copy of this documentation, go to the Single Point of Connectivity
Knowledge for HP Storage Products (SPOCK) Web site at http://spock.corp.hp.com/index.aspx.
WARNING! If you are using the Thin Persistence feature and you are upgrading from InForm OS
2.3.1 GA to 2.3.1 MU4, you must install 2.3.1 P10 before installing 2.3.1 MU4.
If you are upgrading from InForm OS 2.3.1 MU1 to 2.3.1 MU4, you must install 2.3.1 MU1 P9 before
installing 2.3.1 MU4.
WARNING! When upgrading from HP 3PAR InForm OS 2.3.1 MU3 Patch 18 (P18) to 2.3.1 MU4,
you must also install Patch 20 (P20) before running the starttask admithw –ni command. Failure
to install the patch (P20) or issuing a starttask admithw –ni command before installing patch
(P20) may lead to unpredictable results.
Components
VersionComponent
2.3.1.330 (MU4)OS
2.3.1.330CLI
1.4.0SNMP Agent
What’s New in this Release
This release includes support for new 100 and 200 Gb Solid State Drives (SSD) on HP 3PAR T-Class
and F-Class Storage Systems.
Modifications to the InForm OS
The following items have been addressed in this release.
Table 1 Modifications to the InForm OS
DescriptionItemBug ID
When an initiator logged out or was disconnected while holding a SCSI-2 reservation
on an storage system LUN, the reservation would remain associated with the LUN
and had to be manually cleared for access by other initiators.
SCSI-2 LUN reservations
not properly cleared on
Fibre Channel
disconnects.
45951
The SCSI-2 reservation on a LUN is now cleared when the holder of the reservation
logs out or is disconnected from the array. The storage system also sets a
Power_on_Reset Unit Attention on the LUN indicating that the reservation has been
cleared for initiators accessing the LUN.
When a local host write was terminated with an error while a Remote Copy request
was scheduled for retransmission, the Remote Copy request was sometimes not
Node goes off-line due to
a Remote Copy request
46473
removed from the retransmit queue before it was canceled. This could result in thethat is not properly
retransmit queue retaining stale entries which could cause controller nodes to gocancelled from the
offline at a later stage. The most common situation for a local host write to be
terminated with an error was when a different controller node would go offline.
retransmit queue
following termination of a
local host write operation.
Remote Copy requests are now properly handled through the retransmit queue to
account for the termination of write operations by the local host.
If the removehost -rvl command was used to remove a WWN from a host when
the WWN was visible on multiple ports and a volume was exported to the host, the
Using removehost
-rvl to remove a WWN
46815
next reference to the list of VLUNs associated with that host, (e.g., issuing a
showvlun command), would cause System Manager to fail.
from a host can cause the
next reference to the
4 HP 3PAR InForm Operating System Release Notes