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

2.30
3PAR InForm Operating System Release Notes InForm OS Version 2.3.1
2.8.17 Complex Upgrade to 2.3.1 Reverts when more than 756 Initiators
Attached (Bug 45907)
A complex upgrade to InForm OS 2.3.1 may fail and revert when over 756 initiators are a
attached to the InServ Storage Server via a Fabric. This is due to the fact that some of the host
initiator ports do not log into the InServ Storage Server when the expedition controller nodes
come back online. This problem can be seen on Brocade, McData, Cisco, and QLogic fabrics.
This occurs as a result of the hosts not being notified via RSCNs and therefore, do not log in.
 Workaround - Limit the number of initiators to 756 when performing a complex upgrade
to 2.3.1
.
2.8.18 showtask for updatevv Displays Incorrect Completion Time (Bug
46328)
showtask for updatevv displays the incorrect completion time.
 Workaround - In these cases updatevv did complete for all virtual volumes in the set,
however the completion time is incorrect. The actual completion time can found by
gathering the creation time of the new snapshots.
2.8.19 Tasks Become Active after a Failed Upgrade (Bug 46418)
There are certain situations after a failed upgrade when tasks that were scheduled and
suspended become active.
 Workaround - Following the failed upgrade using the showsched command to determine
which scheduled tasks need to be suspended again. Use the setsched -suspend
<schedule_name> command.