HP P4000 9.0 HP StorageWorks P4000 SAN Solution User Guide - Page 300

iSNS server, iSCSI load balancing, Requirements, Compliant iSCSI initiators, Authentication (CHAP)

Page 300 highlights

iSNS server An iSNS server simplifies the discovery of iSCSI targets on multiple clusters on a network. If you use an iSNS server, configure your cluster to register the iSCSI target with the iSNS server. You can use up to 3 iSNS servers, but none are required. iSCSI load balancing Use iSCSI load balancing to improve iSCSI performance and scalability by distributing iSCSI sessions for different volumes evenly across storage systems in a cluster. iSCSI load balancing uses iSCSI Login-Redirect. Only initiators that support Login-Redirect should be used. When using VIP and load balancing, one iSCSI session acts as the gateway session. All I/O goes through this iSCSI session. You can determine which iSCSI session is the gateway by selecting the cluster, then clicking the iSCSI Sessions tab. The Gateway Connection column displays the IP address of the storage system hosting the load balancing iSCSI session. Configure iSCSI load balancing when setting up servers. See Chapter 19 on page 299. Requirements • Cluster configured with a virtual IP address. See "Virtual IP addresses" on page 299. • A compliant iSCSI initiator. Compliant iSCSI initiators A compliant initiator supports iSCSI Login-Redirect AND has passed HP' test criteria for iSCSI failover in a load balanced configuration. Find information about which iSCSI initiators are compliant by clicking the link in the New or Edit Server window. The link opens to the http://www.hp.com/go/P4000compatibility where you log in and search for the HP StorageWorks P4000 SAN Solutions Compatibility Matrix. If your initiator is not on the list, do not enable load balancing. Authentication (CHAP) Server access with iSCSI can use the following authentication methods: • Initiator node name (single host) • CHAP (Challenge-Handshake Authentication Protocol), which can support single or multiple hosts. NOTE: The iSCSI terminology in this discussion is based on the Microsoft iSCSI Initiator terminology. For the terms used in other common operating systems, see "iSCSI and CHAP terminology" on page 302. CHAP is a standard authentication protocol. The SAN/iQ software supports the following configurations: 300 iSCSI and the HP P4000 SAN Solution

  • 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
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308
  • 309
  • 310
  • 311
  • 312
  • 313
  • 314
  • 315
  • 316
  • 317
  • 318
  • 319
  • 320
  • 321
  • 322
  • 323
  • 324
  • 325
  • 326
  • 327
  • 328
  • 329
  • 330
  • 331
  • 332
  • 333
  • 334
  • 335
  • 336
  • 337
  • 338
  • 339
  • 340
  • 341
  • 342
  • 343
  • 344
  • 345
  • 346
  • 347
  • 348
  • 349
  • 350

iSNS server
An iSNS server simplifies the discovery of iSCSI targets on multiple clusters on a network. If you use
an iSNS server, configure your cluster to register the iSCSI target with the iSNS server. You can use
up to 3 iSNS servers, but none are required.
iSCSI load balancing
Use iSCSI load balancing to improve iSCSI performance and scalability by distributing iSCSI sessions
for different volumes evenly across storage systems in a cluster. iSCSI load balancing uses iSCSI
Login-Redirect. Only initiators that support Login-Redirect should be used.
When using VIP and load balancing, one iSCSI session acts as the gateway session. All I/O goes
through this iSCSI session. You can determine which iSCSI session is the gateway by selecting the
cluster, then clicking the iSCSI Sessions tab. The Gateway Connection column displays the IP address
of the storage system hosting the load balancing iSCSI session.
Configure iSCSI load balancing when setting up servers. See
Chapter 19
on page 299.
Requirements
Cluster configured with a virtual IP address. See
Virtual IP addresses
on page 299.
A compliant iSCSI initiator.
Compliant iSCSI initiators
A compliant initiator supports iSCSI Login-Redirect AND has passed HP
test criteria for iSCSI failover
in a load balanced configuration.
Find information about which iSCSI initiators are compliant by clicking the link in the New or Edit
Server window.
The link opens to the
h
t
tp://w
w
w
.hp
.co
m/go/P4
000co
m
patib
ilit
y
where you log in and search for
the
HP StorageWorks P4000 SAN Solutions Compatibility Matrix
.
If your initiator is not on the list, do not enable load balancing.
Authentication (CHAP)
Server access with iSCSI can use the following authentication methods:
Initiator node name (single host)
CHAP (Challenge-Handshake Authentication Protocol), which can support single or multiple hosts.
NOTE:
The iSCSI terminology in this discussion is based on the Microsoft iSCSI Initiator terminology. For the
terms used in other common operating systems, see
iSCSI and CHAP terminology
on page 302.
CHAP is a standard authentication protocol. The SAN/iQ software supports the following
configurations:
iSCSI and the HP P4000 SAN Solution
300