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

2.29
InForm OS Version 2.3.1 3PAR InForm Operating System Release Notes
2.8.13 controlport Configuration Gives Warning after Being Taken Offline
(Bug 44989)
Using the -f option with controlport config, the system responded with a confirmation
request, or refused to force the mode change.
 Workaround - If the -f flag was used and the system still prompts for confirmation,
respond to the prompt. If there are other messages, they need to be resolved (e.g. take
port offline), or possibly reissue the command.
2.8.14 createvvcopy Issues with Halt (Bug 45142)
When a virtual volume copy is halted, the detailed status of the target virtual volume indicates
copy_failed. The detailed status of the target virtual volume continues to show this state even
if the virtual volume copy is restarted and the virtual volume copy is going on.
 Workaround - The virtual volume detailed status is cleared once the restarted virtual
volume copy completes. No user intervention is required.
2.8.15 Disk Failure Alert has Invalid/Incorrect Magazine Information (Bug
45224)
A disk drive failure alert may not correctly identify its corresponding drive magazine location.
When a disk is considered "missing" by the system, the alert will identify the Drive Magazine
as "N/A" (Not Available). For example, "Message : Magazine N/A, Physical Disk 104 Failed."
 Workaround - The Physical Disk drive number is correctly displayed in the alert and in the
InServ Storage Server's event log. Examine the CLI output of the showpd and showpd -s
commands to determine the cage/magazine location of the failed disk.
2.8.16 Some Messages Not Clear During upgradecage (Bug 45229)
Messages displayed during an upgrade of a drive cage are not clear if the drive cage is actually
being upgraded.
 Workaround - Run the showcage and showcage -d command to see if a firmware upgrade
is still required. Verify there are no other instances of upgradecage running, then run
upgradecage again.
NOTE: This was observed when multiple upgradecage commands were run. Do
not run multiple upgradecage commands.