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

Remote Copy Group Stop, On Brocade switches

Page 11 highlights

Issue ID Item Description coherent and let the battery charge level to set to normal. On releases before 2.3.1.MU5, there's no workaround that would fix the problem without interrupting system. On such system, the only way to get the system to work normally is to restart sysmgr. 65646 65663 65722 65775 65800 Deleting a very large and filled snapshot can lock up a CPU for a long time If we have a heavily loaded system and have snapshots with lots of data, the meta data tables of which are heavily populated, then on deleting some of these snapshots the meta data tables are traversed causing the cpu on occasions to be held for an excessive amount of time. This can cause the locking out other processes/tasks from running and can cause the background internode comms processing to be delayed resulting in the erroneous belief that one of the other nodes has died. This fix prevents the cpu from being held for an excessive amount of time while traversing the meta data tables during snapshot removal. This fix includes an enhancement to cover off the case where the meta data tables are being merged during snapshot removal. This enhancement fix is applied to 2.3.1.MU5, 3.1.1.MU1, and 3.1.2. Core dumps The firmware has a bug where it trashes its internal copy of scatter gather list which results in the fw trying to access invalid/incorrect addresses. This bug can be triggered only when fw is requiring to use DDR memory for BLP storage. If DDR memory was used at any time in the past, there is a potential of the fw polluting its internal memory (and thus using invalid/incorrect host memory addresses) till the port has been reset. Cluster goes offline following Synch When stopping a Synchronous Remote Copy Group in the middle of Remote Copy Group Stop re-sync phase following the admission of additional volumes into that group can cause the cluster to go offline. Cluster goes offline following Synch When stopping a Synchronous Remote Copy Group in the middle of Remote Copy Group Stop re-sync phase following the admission of additional volumes into that group can cause the cluster to go offline. Move AO configuration into the TOC Four new commands have been added to allow the creation, update, removal and display of Adaptive Optimization configurations via the CLI. These new commands are: • createaocfg - create a new AO configuration • setaocgg - modify an AO configuration • removeaocfg - remove an AO configuration • showaocfg - show AO configurations See the individual commands for usage & licensing information. 65906 node/port symbolic information Fibre Channel (FC) target ports will register new node and port symbolic information starting in 3.1.2. Node symbolic information is of the form: Legacy systems: HP_3PAR 7000 --fw: 7200 systems: HP_3PAR 7200 - -fw: 7400 systems: HP_3PAR 7400 - -fw: where is the legacy system model, such as V800; is the system serial number, e.g., 1499607; and is a four digit number representing the HP 3PAR OS release and MU, e.g., 3120 for 3.1.2 GA, 3121 for 3.1.2 MU1. Port symbolic information is of the form: - - where is the system serial number, e.g., 1499607; is the location of the port, e.g., 1:3:2; and is the type of the HBA, eg., LPe12004. Node and port symbolic information are registered with the FC fabric. On Brocade switches, nsshow will display this information. On Cisco Modifications to the OS 11

  • 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
coherent and let the battery charge level to set to normal. On releases
before 2.3.1.MU5, there's no workaround that would fix the problem
without interrupting system. On such system, the only way to get the
system to work normally is to restart sysmgr.
If we have a heavily loaded system and have snapshots with lots of
data, the meta data tables of which are heavily populated, then on
Deleting a very large and filled
snapshot can lock up a CPU for a
long time
65646
deleting some of these snapshots the meta data tables are traversed
causing the cpu on occasions to be held for an excessive amount of
time. This can cause the locking out other processes/tasks from running
and can cause the background internode comms processing to be
delayed resulting in the erroneous belief that one of the other nodes
has died. This fix prevents the cpu from being held for an excessive
amount of time while traversing the meta data tables during snapshot
removal. This fix includes an enhancement to cover off the case where
the meta data tables are being merged during snapshot removal. This
enhancement fix is applied to 2.3.1.MU5, 3.1.1.MU1, and 3.1.2.
The firmware has a bug where it trashes its internal copy of scatter
gather list which results in the fw trying to access invalid/incorrect
Core dumps
65663
addresses. This bug can be triggered only when fw is requiring to
use DDR memory for BLP storage. If DDR memory was used at any
time in the past, there is a potential of the fw polluting its internal
memory (and thus using invalid/incorrect host memory addresses) till
the port has been reset.
When stopping a Synchronous Remote Copy Group in the middle of
re-sync phase following the admission of additional volumes into that
group can cause the cluster to go offline.
Cluster goes offline following Synch
Remote Copy Group Stop
65722
When stopping a Synchronous Remote Copy Group in the middle of
re-sync phase following the admission of additional volumes into that
group can cause the cluster to go offline.
Cluster goes offline following Synch
Remote Copy Group Stop
65775
Four new commands have been added to allow the creation, update,
removal and display of Adaptive Optimization configurations via the
CLI. These new commands are:
Move AO configuration into the TOC
65800
createaocfg
- create a new AO configuration
setaocgg
- modify an AO configuration
removeaocfg
- remove an AO configuration
showaocfg
- show AO configurations
See the individual commands for usage & licensing information.
Fibre Channel (FC) target ports will register new node and port
symbolic information starting in 3.1.2.
node/port symbolic information
65906
Node symbolic information is of the form:
Legacy systems: HP_3PAR 7000 <model>-<serial>-fw:<release>
7200 systems: HP_3PAR 7200 - <serial>-fw:<release>
7400 systems: HP_3PAR 7400 - <serial>-fw:<release>
where <model> is the legacy system model, such as V800; <serial>
is the system serial number, e.g., 1499607; and <release> is a four
digit number representing the HP 3PAR OS release and MU, e.g.,
3120 for 3.1.2 GA, 3121 for 3.1.2 MU1.
Port symbolic information is of the form:
<serial> - <n:s:p> — <type>
where <serial> is the system serial number, e.g., 1499607; <n:s:p>
is the location of the port, e.g., 1:3:2; and <type> is the type of the
HBA, eg., LPe12004.
Node and port symbolic information are registered with the FC fabric.
On Brocade switches,
nsshow
will display this information. On Cisco
Modifications to the OS
11