HP 3PAR StoreServ 7450 4-node HP 3PAR OS 3.1.2 Release Notes - Page 41

systems Bug 86680, Kernel Core when performing online upgrade from 3.1.2.322 MU1 to 3.1.2.412

Page 41 highlights

Issue ID 86957 88271 88830 89948 Item Resolved AIX SCSI command timeouts on VV busy errors CIM API - NumberOfBlocks of a snapshot StorageVolume could be inaccurate srdata volume can be mounted on multiple nodes. CLI Client 3.1.2.278 Support Description while the system is powered-down, the alert still exists upon reboot. The alert is not cleared. The SCSI subsystem is not handling busy errors from the Volume Layer correctly and it can result in SCSI commands being timed out for AIX (NACA supported) hosts. AIX issues an ABORT when the command timeout occurs and then retry the command. To resolve this, return the BUSY status back to AIX so that AIX does not issue an ABORT prior to retrying the command. The NumberOfBlocks of a snapshot StorageVolume is inaccurate when the parent volume grows in size. This is resolved. Additional checks to make sure that the srdata volume is not mounted on another node before actually starting sampling rather than relying entirely on the srdatac process for management of the srdata volume. The CLI client version on the SP is 3.1.2.278 instead of 3.1.2.422 as with other components. This is expected. These CLI client versions are essentially the same. CLI client version 3.1.2.278 supports all connections on the storage system to the CLI server from version 3.1.x to 3.1.2 MU2. Known Issues with the OS Cannot downgrade from 3.1.2.422 (MU2) to an earlier release on specific storage systems (Bug 86680) Downgrading from HP 3PAR OS 3.1.2 MU2 to an earlier release is not possible on the 10000 and 7000 storage systems if the Virtual Volume IDs (VVIDs) exceed the earlier OS release's limit. The 3.1.2 MU2 version supports up to 32K OpenVMS VVIDs and the 3.1.2 MU1 and earlier releases support up to 12K VVIDs on the 10000 system and 8K VVIDs on the 7000 system. When downgrading from 3.1.2 MU2 to 3.1.2 MU1 or earlier releases, the VVID must be within the previously supported range for the system. A message similar to this appeas if VVIDs exceed the supported limit: One or more vv's exist with an id greater than 12287. This not supported by the target update version. Remove vv's with an id greater than 12287 and try again. Workaround: If the number of VVIDs is greater than 12K on the 10000 system and 8K on the 7000 system, reduce the number of VVIDs to less than the number supported and retry the downgrade. CAUTION: After the new features of HP 3PAR OS 3.1.2 MU2 are used, downgrading to an earlier version may not be possible. Kernel Core when performing online upgrade from 3.1.2.322 MU1 to 3.1.2.412 (Bug 89407) During an online upgrade from HP 3PAR OS 3.1.2.322 (MU1) to HP 3PAR OS 3.1.2.422 (MU2), a node running HP 3PAR OS 3.1.2.422 (MU2) causes data unavailability when rcopy transaction log is converted to the new format. Known Issues with the OS 41

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59

Description
Item
Issue ID
while the system is powered-down, the alert still
exists upon reboot. The alert is not cleared.
The SCSI subsystem is not handling busy errors
from the Volume Layer correctly and it can result
Resolved AIX SCSI command timeouts on VV
busy errors
86957
in SCSI commands being timed out for AIX (NACA
supported) hosts. AIX issues an ABORT when the
command timeout occurs and then retry the
command. To resolve this, return the BUSY status
back to AIX so that AIX does not issue an ABORT
prior to retrying the command.
The NumberOfBlocks of a snapshot StorageVolume
is inaccurate when the parent volume grows in
size. This is resolved.
CIM API - NumberOfBlocks of a snapshot
StorageVolume could be inaccurate
88271
Additional checks to make sure that the srdata
volume is not mounted on another node before
srdata volume can be mounted on multiple
nodes.
88830
actually starting sampling rather than relying
entirely on the srdatac process for management
of the srdata volume.
The CLI client version on the SP is 3.1.2.278
instead of 3.1.2.422 as with other components.
CLI Client 3.1.2.278 Support
89948
This is expected. These CLI client versions are
essentially the same. CLI client version 3.1.2.278
supports all connections on the storage system to
the CLI server from version 3.1.x to 3.1.2 MU2.
Known Issues with the OS
Cannot downgrade from 3.1.2.422 (MU2) to an earlier release on specific storage
systems (Bug 86680)
Downgrading from HP 3PAR OS 3.1.2 MU2 to an earlier release is not possible on the 10000
and 7000 storage systems if the Virtual Volume IDs (VVIDs) exceed the earlier OS release’s limit.
The 3.1.2 MU2 version supports up to 32K OpenVMS VVIDs and the 3.1.2 MU1 and earlier
releases support up to 12K VVIDs on the 10000 system and 8K VVIDs on the 7000 system. When
downgrading from 3.1.2 MU2 to 3.1.2 MU1 or earlier releases, the VVID must be within the
previously supported range for the system.
A message similar to this appeas if VVIDs exceed the supported limit:
One or more vv
s exist with an id greater than 12287. This not supported
by the target update version. Remove vv
s with an id greater than 12287
and try again.
Workaround
: If the number of VVIDs is greater than 12K on the 10000 system and 8K on the
7000 system, reduce the number of VVIDs to less than the number supported and retry the
downgrade.
CAUTION:
After the new features of HP 3PAR OS 3.1.2 MU2 are used, downgrading to an
earlier version may not be possible.
Kernel Core when performing online upgrade from 3.1.2.322 MU1 to 3.1.2.412
(Bug 89407)
During an online upgrade from HP 3PAR OS 3.1.2.322 (MU1) to HP 3PAR OS 3.1.2.422 (MU2),
a node running HP 3PAR OS 3.1.2.422 (MU2) causes data unavailability when rcopy transaction
log is converted to the new format.
Known Issues with the OS
41