HP P6000 HP P6300/P6500 Enterprise Virtual Array User Guide (593079-001, June - Page 132

Single path implementation, Installation requirements, Recommended mitigations, On HP-UX, Solaris

Page 132 highlights

6 Single path implementation This chapter provides guidance for connecting servers with a single path host bus adapter (HBA) to the Enterprise Virtual Array (EVA) storage system with no multipath software installed. A single path HBA is defined as: • A single HBA port to a switch with no multipathing software installed • A single HBA port to a switch with multipathing software installed HBA LUNs are not shared by any other HBA in the server or in the SAN. Failover action is different depending on which single path method is employed. The failure scenarios demonstrate behavior when recommended configurations are employed, as well as expected failover behavior if guidelines are not met. To implement single adapter servers into a multipath EVA environment, configurations should follow these recommendations. The purpose of single HBA configurations for non-mission critical storage access is to control costs. This chapter describes the configurations, limitations, and failover characteristics of single HBA servers under different operating systems. Several of the descriptions are based on a single HBA configuration resulting in a single path to the device, but OpenVMS has native multipath features by default. NOTE: Tru64 and NetWare are not supported with the P6300/P6500 EVA. With OpenVMS, a single HBA configuration will result in two paths to the device by having connections to both EVA controllers. Single HBA configurations are not single path configurations with these operating systems. In addition, cluster configurations for OpenVMS provide enhanced availability and security. To achieve availability within cluster configurations, configure each member with its own HBAs and connectivity to shared LUNs. For further information on cluster configurations and attributes, see the appropriate operating system guide and the HP SAN Design Reference Guide. NOTE: HP continually makes additions to its storage solution product line. For more information about the HP Fibre Channel product line, the latest drivers, and technical tips, and to view other documentation, see the HP website at: http://www.hp.com/country/us/eng/prodserv/storage.html Installation requirements • The host must be placed in a zone with any EVA worldwide IDs (WWIDs) that access storage devices presented by the hierarchical storage virtualization (HSV) controllers to the single path HBA host. The preferred method is to use HBA and HSV WWIDs in the zone configurations. • On HP-UX, Solaris, Microsoft Windows Server 2008, Microsoft Windows Server 2003 (32-bit), Windows 2000, Linux and IBM AIX operating systems, the zones consist of the single path HBA systems and one HSV controller port. • On OpenVMS, the zones consist of the single HBA systems and two HSV controller ports. This results in a configuration where there are two paths per device, or multiple paths. Recommended mitigations EVA is designed for the mission-critical enterprise environment. When used with multipath software, high data availability and fault tolerance are achieved. In single path HBA server configurations, neither multipath software nor redundant I/O paths are present. Server-based operating systems are not designed to inherently recover from unexpected failure events in the I/O path (for example, loss of connectivity between the server and the data storage). It is expected that most operating systems will experience undesirable behavior when configured in non-high-availability configurations. 132 Single path implementation

  • 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
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298

6 Single path implementation
This chapter provides guidance for connecting servers with a single path host bus adapter (HBA)
to the Enterprise Virtual Array (EVA) storage system with no multipath software installed. A single
path HBA is defined as:
A single HBA port to a switch with no multipathing software installed
A single HBA port to a switch with multipathing software installed
HBA LUNs are not shared by any other HBA in the server or in the SAN. Failover action is different
depending on which single path method is employed.
The failure scenarios demonstrate behavior when recommended configurations are employed, as
well as expected failover behavior if guidelines are not met. To implement single adapter servers
into a multipath EVA environment, configurations should follow these recommendations.
The purpose of single HBA configurations for non-mission critical storage access is to control costs.
This chapter describes the configurations, limitations, and failover characteristics of single HBA
servers under different operating systems. Several of the descriptions are based on a single HBA
configuration resulting in a single path to the device, but OpenVMS has native multipath features
by default.
NOTE:
Tru64 and NetWare are not supported with the P6300/P6500 EVA.
With OpenVMS, a single HBA configuration will result in two paths to the device by having
connections to both EVA controllers. Single HBA configurations are not single path configurations
with these operating systems.
In addition, cluster configurations for OpenVMS provide enhanced availability and security. To
achieve availability within cluster configurations, configure each member with its own HBAs and
connectivity to shared LUNs. For further information on cluster configurations and attributes, see
the appropriate operating system guide and the HP SAN Design Reference Guide.
NOTE:
HP continually makes additions to its storage solution product line. For more information
about the HP Fibre Channel product line, the latest drivers, and technical tips, and to view other
documentation, see the HP website at:
h
t
tp://w
w
w
.hp
.co
m/co
un
tr
y/u
s/e
ng/pr
ods
e
r
v/s
t
o
r
age
.h
tml
Installation requirements
The host must be placed in a zone with any EVA worldwide IDs (WWIDs) that access storage
devices presented by the hierarchical storage virtualization (HSV) controllers to the single path
HBA host. The preferred method is to use HBA and HSV WWIDs in the zone configurations.
On HP-UX, Solaris, Microsoft Windows Server 2008, Microsoft Windows Server 2003 (32-bit),
Windows 2000, Linux and IBM AIX operating systems, the zones consist of the single path
HBA systems and one HSV controller port.
On OpenVMS, the zones consist of the single HBA systems and two HSV controller ports. This
results in a configuration where there are two paths per device, or multiple paths.
Recommended mitigations
EVA is designed for the mission-critical enterprise environment. When used with multipath software,
high data availability and fault tolerance are achieved. In single path HBA server configurations,
neither multipath software nor redundant I/O paths are present. Server-based operating systems
are not designed to inherently recover from unexpected failure events in the I/O path (for example,
loss of connectivity between the server and the data storage). It is expected that most operating
systems will experience undesirable behavior when configured in non-high-availability configurations.
132
Single path implementation