HP 3PAR InForm OS 3.1.1 MU1 Release Notes

Limitations of the InForm OS
Unsupported Remote Copy Across InForm OS Levels
Remote Copy is only supported between adjacent HP 3PAR InForm OS release levels. HP 3PAR
Storage System running InForm OS 2.2.4.nnn may not be in a Remote Copy configuration with a
Storage System running InForm OS 3.1.1 GA or 3.1.1 MU1.
SupportSystem “B” InForm OS LevelSystem “A” InForm OS Level
Yes2.3.1.nnn2.2.4.nnn
Yes3.1.1.nnn2.3.1.nnn
No3.1.1.nnn2.2.4.nnn
Upgrades direct from all levels of InForm OS 2.2.4 to 3.1.1 GA or MU1 when remote copy is
configured will fail. This includes offline upgrades and when remote copy is simply stopped. For
these upgrades, you must first upgrade to InForm OS 2.3.1 MU5, then proceed to upgrade to
3.1.1 MU1.
Known Issues with the InForm OS
Sysmgr Failover During Group Snapshot Creation May Result in an Inconsistent Group
(57883)
If sysmgr failover occurs during group snapshot creation then the snapshot group may not be
consistent and some snapshots may be missing.
• Workaround: If sysmgr failover occurs during group snapshot creation then the group should
be removed and a new snapshot group created.
RCFC Link Issues When ISLs Are Removed (60936)
Under heavy remote copy traffic, adding or removing an ISL to the fabric may cause traffic delays
and congestion due to the dropping of FC frames.
• Workaround: FC fabrics with multiple ISL connections should be configured with these links
trunked together.
Multiple Large importvv Operations May Cause a Slowdown of Tune and Import
Operations (62592)
If too many importvv operations are running or scheduled, a slowdown may be experienced on
all tune and import operations.
• Workaround: No more than 160TB of importvv operations should be started or scheduled
(pending) on a single Storage System.
BIOS Log Entry Information is Incorrectly Raised as a Degraded Alert (62864)
For 3.1.1 MU1 and earlier: BIOS IDE log entry events can be safely ignored; a fix will be included
so that these events do not show up in the service logs in 3.1.2.
• Workaround: None.
Permanent Failure Alerts of a Backup Battery Unit (BBU) Are Not Cleared by NEMOE
(64033)
NEMOE issues an alert when a BBU has a fault but will also attempt to recover the BBU. In the
event when the BBU permanently fails, NEMOE will issue another alert. When a failed BBU is
Limitations of the InForm OS 35