HP 6100 HP 4x00/6x00/8x00 Enterprise Virtual Array User Guide (5697-0733, Marc - Page 151

Installation requirements, Recommended mitigations, Supported configurations

Page 151 highlights

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 2003 (32-bit), , Linux and IBM AIX operating systems, the zones consist of the single path HBA systems and one HSV controller port. • On OpenVMS and Tru64 UNIX operating systems, the zones consist of the single HBA systems and two HSV controller ports. This will result 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 multi-path software, high data availability and fault tolerance are achieved. In single path HBA server configurations, neither multi-path 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. Because of the risks of using servers with a single path HBA, HP recommends the following actions: • Use servers with a single path HBA that are not mission-critical or highly available. • Perform frequent backups of the single path server and its storage. Supported configurations All examples detail a small homogeneous Storage Area Network (SAN) for ease of explanation. Mixing of dual and single path HBA systems in a heterogeneous SAN is supported. In addition to this document, reference and adhere to the SAN Design Reference Guide for heterogeneous SANs, located at: http://h18006.www1.hp.com/products/storageworks/san/documentation.html General configuration components All configurations require the following components: • Enterprise VCS software • HBAs • Fibre Channel switches Connecting a single path HBA server to a switch in a fabric zone Each host must attach to one switch (fabric) using standard Fibre Channel cables. Each host has its single path HBA connected through switches on a SAN to one port of an EVA. Because a single path HBA server has no software to manage the connection and ensure that only one controller port is visible to the HBA, the fabric containing the single path HBA server, SAN switch, and EVA controller must be zoned. Configuring the single path by switch zoning and the LUNs by Selective Storage Presentation (SSP) allows for multiple single path HBAs to reside in the same server. A single path HBA server with OpenVMS or Tru64 UNIX operating system should be zoned with two EVA controllers. See the HP SAN Design Reference Guide at the following HP website for additional information about zoning: http://h18006.www1.hp.com/products/storageworks/san/documentation.html To connect a single path HBA server to a SAN switch: 1. Plug one end of the Fibre Channel cable into the HBA on the server. 2. Plug the other end of the cable into the switch. Installation requirements 151

  • 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

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 2003 (32-bit), , Linux and IBM AIX operating
systems, the zones consist of the single path HBA systems and one HSV controller port.
On OpenVMS and Tru64 UNIX operating systems, the zones consist of the single HBA systems
and two HSV controller ports. This will result 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 multi-path software,
high data availability and fault tolerance are achieved. In single path HBA server configurations,
neither multi-path 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.
Because of the risks of using servers with a single path HBA, HP recommends the following actions:
Use servers with a single path HBA that are not mission-critical or highly available.
Perform frequent backups of the single path server and its storage.
Supported configurations
All examples detail a small homogeneous Storage Area Network (SAN) for ease of explanation.
Mixing of dual and single path HBA systems in a heterogeneous SAN is supported. In addition to
this document, reference and adhere to the SAN Design Reference Guide for heterogeneous SANs,
located at:
h
t
tp://h1
8
006
.w
w
w1
.hp
.co
m/pr
odu
c
ts/s
t
o
r
age
w
o
r
ks/s
an/doc
ume
n
t
ati
o
n
.h
tml
General configuration components
All configurations require the following components:
Enterprise VCS software
HBAs
Fibre Channel switches
Connecting a single path HBA server to a switch in a fabric zone
Each host must attach to one switch (fabric) using standard Fibre Channel cables. Each host has
its single path HBA connected through switches on a SAN to one port of an EVA.
Because a single path HBA server has no software to manage the connection and ensure that only
one controller port is visible to the HBA, the fabric containing the single path HBA server, SAN
switch, and EVA controller must be zoned. Configuring the single path by switch zoning and the
LUNs by Selective Storage Presentation (SSP) allows for multiple single path HBAs to reside in the
same server. A single path HBA server with OpenVMS or Tru64 UNIX operating system should
be zoned with two EVA controllers. See the HP SAN Design Reference Guide at the following HP
website for additional information about zoning:
h
t
tp://h1
8
006
.w
w
w1
.hp
.co
m/pr
odu
c
ts/s
t
o
r
age
w
o
r
ks/s
an/doc
ume
n
t
ati
o
n
.h
tml
To connect a single path HBA server to a SAN switch:
1.
Plug one end of the Fibre Channel cable into the HBA on the server.
2.
Plug the other end of the cable into the switch.
Installation requirements
151