HP Surestore Disk Array 12h Storage Manager 60-NT User’s Guide - Page 114

Restriction, Workaround, Access Volume Logical Unit number that is

Get HP Surestore Disk Array 12h - And FC60 PDF manuals and user guides View all HP Surestore Disk Array 12h manuals
Add to My Manuals
Save this manual to your list of manuals

Page 114 highlights

Restriction Workaround When controller failover occurs in an active/active controller pair and ownership of volumes transfers from the failed preferred owner to the other controller of the pair. The failed controller is replaced and brought online. Until the volume group ownership is transferred back to the preferred controller owner, you lose I/O path failover protection for the second controller. It may take 5 minutes after the failed controller is replaced and brought online for a rescan to detect and return ownership to the preferred controller. To ensure I/O path failover protection, immediately after replacing the controller select the option in the Array Management Window to transfer volume groups back to preferred controller owners. For more information, see the Array Management Window online Help system. After installing the Host-Agent software, you see an error message with "Service Error 100" on the host. Check these possible causes: The Host-Agent software does not find any controllers with firmware version 4.x. Controllers with firmware version 4.x have the Access Volume disabled with NVSRAM configuration settings. The NVSRAM on controllers in a Storage Array you are attempting to manage contains an Access Volume Logical Unit number that is already in use by another volume. The NVSRAM on controllers in a Storage Array you are attempting to manage contains an Access Volume Logical Unit number that is not supported by the operating system and installed patches. (For example, the Access Volume is configured at LUN 32, but the operating system and service packs only support 8 LUNs.) 114

  • 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
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
114
±±±±±±±±2SHUDWLQJ±/LPLWDWLRQV
When controller failover occurs in an
active/active controller pair and ownership of
volumes transfers from the failed preferred
owner to the other controller of the pair. The
failed controller is replaced and brought
online. Until the volume group ownership is
transferred back to the preferred controller
owner, you lose I/O path failover protection for
the second controller.
It may take 5 minutes after the failed controller is
replaced and brought online for a rescan to
detect and return ownership to the preferred
controller.
To ensure I/O path failover protection,
immediately after replacing the controller select
the
6WRUDJH±$UUD\±!!±5HGLVWULEXWH±9ROXPH±*URXSV
option in the Array Management Window to
transfer volume groups back to preferred
controller owners.
For more information, see the Array
Management Window online Help system.
After installing the Host-Agent software, you
see an error message with
“
Service Error
100
”
on the host.
Check these possible causes:
The Host-Agent software does not find any
controllers with firmware version 4.x.
Controllers with firmware version 4.x have the
Access Volume disabled with NVSRAM
configuration settings.
The NVSRAM on controllers in a Storage Array
you are attempting to manage contains an
Access Volume Logical Unit number that is
already in use by another volume.
The NVSRAM on controllers in a Storage Array
you are attempting to manage contains an
Access Volume Logical Unit number that is not
supported by the operating system and installed
patches. (For example, the Access Volume is
configured at LUN 32, but the operating system
and service packs only support 8 LUNs.)
7DEOH±¹³ ±
2SHUDWLQJ±/LPLWDWLRQV±IRU±WKH±:LQGRZV±17±Â6KHHW±¾±RI±ÄÃ
Restriction
Workaround