HP 3PAR OS 3.1.3 Release Notes

DescriptionItemIssue ID
replaced, the iSCSI port might intermittently come up in config_wait
state following node reboot or node error. Resetting the port clears
might enter in config_wait state
intermittently.
the config_wait state. To resolve the inconsistency in the TOC, switch
the port to FCoE mode and then back to iSCSI mode.
An issue in rm_config_group_dr sets the target busy bit, but does not
clear the target busy bit after completing the restore command
An issue in rm_config_group_dr sets
the target busy bit, but does not
92831
when the restore command is issued from the secondary array with
target specified.
clear the target busy bit after
completing the restore command
Workaround: To work around this issue, the restore command must
be issued from the primary array instead of the secondary array.
when the restore command is issued
from the secondary array with
target specified.
A tunesys command can generate a large number of tune
commands during the analysis phase. If a CPG is subsequently
Renaming a CPG while tunesys is
running might cause tunes to fail.
101049
renamed before the generated tunes are executed, the tunes might
fail. The names of CPGs must not be swapped around while tunesys
is running as this might result in VVs being moved between CPGs
unexpectedly.
Downgrading an HP 3PAR StoreServ from a 3.1.3 release to an
earlier version can result in checkhealth warnings such as
Downgrading an HP 3PAR
StoreServ from version 3.1.3 to an
101859
Filesystems which are over 80% full and free node diskearlier release results in checkhealth
warnings and free node disk space
service alerts.
space service alerts. For version 3.1.3, the space requirements on
the local node drive is increased to the point where previously
monitored thresholds consider it as an issue. For the 3.1.3 release,
the monitoring code is modified with new threshold values to support
this increased usage.
If a StoreServ is subsequently downgraded to an earlier release such
as 3.1.2, the 3.1.3 filesystem is moved to an alternate boot path on
the local node drive while the primary path is installed with the target
version. This allows the StoreServ to be reverted to the 3.1.3 release,
if desired. Because this alternate filesystem is visible to the 3.1.2
monitoring software, the checkhealth warnings (Filesystem is over
80% full) and service alerts (Free node disk space) are triggered.
The chunklet cleaning display in tunesys always displays zero for the
number of chunklets cleaned in the last interval. The number of
chunklets remaining is displayed correctly.
The chunklet cleaning display in
tunesys always displays zero for the
number of chunklets cleaned in the
last interval.
102018
Known Issues with the OS 21