3PAR InForm OS 2.3.1 MU2 Release Note (325-200142 Rev B, October 2010)

2.14
Known Issues with the InForm OS
3PAR InForm OS Release Notes InForm OS Version 2.3.1 MU2
3PAR Confidential
2.7.6 Firmware Core Dump from FC Adapter by LSI
(Bugs 24178, 30353, 32351)
Under certain error conditions, the firmware on a Fibre Channel Adapter from LSI may crash
resulting in a firmware core dump. The driver for the adapter resets the port pair after
collecting the firmware core dump.
Workaround - There is no workaround for this and no user action is required. After the
core dump is generated, the port pair is reset and comes online automatically after a few
seconds.
2.7.7 Windows 2003 Pop-Up
Client machines running the Windows 2003 operating systems receive an unknown device
pop-up from Windows Plug and Play security checking when connecting to a
2.3.1 MU2 InServ Storage Server system.
Workaround - To avoid this device pop-up message you can install NULL driver for 3PAR
SCSI Enclosure Service device located on DCS.
2.7.8 Cage Loop Down Alert is not Auto-Recovered (Bug 40274)
There are certain conditions during which a drive cage loop missing alert may not be auto-
resolved even though the drive cage loop comes back.
Workaround - Once it has been verified that the alert is indeed invalid, check showcage -
d and showpd to verify the loop is present. The alert can be removed by removealert or
setalert.
2.7.9 System Manager Could Crash During Rolling Upgrade if Remote Copy
Groups Running (Bug 40867)
When creating snapshots during the shutdown process there is a known race condition that
may result in a system manager crash. Therefore, the user is no longer permitted to manually
take snapshots during this process. However, this is not the case with snapshots that are taken
when a synchronous remote copy group is stopped.
During a rolling upgrade synchronous groups are normally not stopped. However, if there is a
target failure during the process any associated groups will automatically be stopped, and if
the group is synchronous a snapshot for each volume in the group will be taken. This leaves
the system open to hitting the race condition described above.
Workaround - Stop all remote copy groups before starting a rolling upgrade.