3PAR InForm Operating System 2.3.1 Release Notes (320-200178 Rev D, May 2010)

2.27
InForm OS Version 2.3.1 3PAR InForm Operating System Release Notes
2.8.6 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 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.8.7 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.8.8 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.
2.8.9 No Explicit Way to Reset the Default Value for Tunelinks (Bug 43579)
setrcopytarget tunelinks command can be used to adjust the performance value for the
target's links using the <bandwidth> and <latency> specifiers. After using this command,
there is no explicit way for the user to reset the tuning parameters back to its default values.
 Workaround - Reset the parameter to the default value by reissuing tunelinks with
bandwidth=128000 (or higher) and latency=100.