HP 3PAR OS 3.1.3 Release Notes

DescriptionItemIssue ID
version 3.1.3 and later, base volumes are not preserved if only its
snapspace LDs are affected.
preserved if only its snapspace LDs
are affected.
On iSCSI ports, failover/failback might not be fast and multipathing
messages might be seen in host logs. Host multipathing may temporarily
On iSCSI ports, failover/failback
might not be fast and multipathing
78419
marks paths as failed but they are quickly re-instated. This behavior ismessages might be seen in host
logs. observed on Windows 2008 and Windows 2012 hosts. However, it
might be observed on other hosts depending on how heavily the
StoreServ interface is loaded. This is resolved by optimizing the failover
operation.
If the source array in a Peer Motion configuration becomes unavailable
for an extended period of time, the Peer PD is marked as failed. When
Peer Motion PDs could appear
failed but continue to work.
78798
the issue with the source array is resolved, the PD still appears as failed
though it is functioning correctly. This is resolved so that the state of
the peer PD is displayed correctly.
The showport –ids command displays incorrect iSCSI I/P address
and iSCSI name for failover partner port. This is resolved.
IMC displays wrong iSCSI I/P
address and iSCSI name for failover
partner port.
78842
For the CLI showport command, the Partner column must show only
dash ('-') if there is no valid failover partner. However, in some cases,
For the CLI showport command,
the Partner column must show only
78937
the Partner column displays an actual node:slot:port value. This is
resolved.
dash ('-') if there is no valid failover
partner. However, in some cases,
the Partner column is incorrectly
populated with an actual
node:slot:port value.
Sysmgr becomes unresponsive during execution of the showspace
command because an issue with the operating system creates core
dumps. This is resolved and core dumps are not generated.
Sysmgr becomes unresponsive
during execution of the showspace
command.
79772
Data miscompares between the primary and target might happen when
-createvv option is used with the admitrcopyvv command. This
is resolved.
Data miscompares between the
primary and target might happen
when -createvv option is used
with the admitrcopyvv command.
79933
The following error might occur in HP 3PAR OS versions earlier than
3.1.3:
The startao command ensures
that the aomover log file is created.
80249
When startao is executed, the file logging process (LOGFILEMGR)
checks the status of the log file /var/log/tpd/aomover. However,
This avoids early exit of the
startao command.
since startao never explicitly creates the aomover log file, on the very
first execution of startao the aomover log file does not exist. When
LOGFILEMGR process notices that the log file does not exist, it writes
an error message to the aomover log file and to the task detail, creates
/var/log/tpd/aomover, and returns an error status to startao
which causes startao to exit early. The time when startao exits
might vary depending on the time when LOGFILEMGR notices that the
aomover log file does not exist. As LOGFILEMGR process ensures that
the aomover log file is created, every subsequent startao works
normally. Only the first execution of startao encounters this issue.
With HP 3PAR OS 3.1.3, this is resolved. It ensures that /var/log/
tpd/aomover exists at the beginning of startao.
The aomover log file is currently not used to report the status of
startao and so it will be always empty. The status of the startao
command is reported via the task manager, or directly to the command
line.
Starting with HP 3PAR OS 3.1.3, a new path management policy can
be applied to synchronous remote copy groups. The policy influences
New path management policy is
provided for setrcopygroup.
80777
the status of exported volumes of the group. The secondary volumes
are in standby mode and volumes in the primary group are active.
Volumes in groups with no path management are active on both
primary systems and secondary systems. Active volumes are available
Modifications to the OS 13