Dell PowerEdge M710 Web Tools Administrator’s Guide - Page 213

Administering the iSCSI Target Gateway, In this iSCSI service overview

Page 213 highlights

DRAFT: BROCADE CONFIDENTIAL Administering the iSCSI Target Gateway Chapter 15 In this chapter •iSCSI service overview 185 •Setting up iSCSI Target Gateway services 188 •Discovery Domain management 193 •Discovery domain sets 195 •CHAP configuration 195 •Connection redirection 197 •iSCSI Fibre Channel zone configuration 197 •Managing and troubleshooting accessibility 199 iSCSI service overview Through the iSCSI Target Gateway Admin module, you can perform iSCSI target gateway-related management tasks, such as creating and managing iSCSI virtual targets, managing iSCSI sessions and iSCSI authentications, and editing discovery domain sets, that enforce iSCSI device access control. The iSCSI port configuration is available to both the iSCSI Target Gateway Admin module and the port management module. Although iSCSI service is fabric-wide, you can manage the iSCSI target gateway service through any iSCSI-capable switch in a fabric. Any applied iSCSI target gateway change is propagated and enforced to the whole fabric. Web Tools can recognize and manage all Fibre Channel ports and GbE ports on the supported blades. When a GbE port is configured to support iSCSI, it can transport SCSI traffic over an IP network. Each GbE port has a unique IP address called an "iSCSI target portal" and each port supports 64 iSCSI sessions. The TCP/IP stack at the port provides support for multiple TCP connections over a single GbE port. In Web Tools, ports are addressed using slot number and port number notation (for example, 2,16): • For Fibre Channel ports on the FC4-16IP blade, the range of ports is 0 through 7. • For GbE ports on the FC4-16IP blade, the port numbers range from ge0 through ge7. The FC4-16IP blade does not support FCIP functionality. The iSCSI standard defines several naming conventions to enable location-independent device identification of storage resources. The FC4-16IP blade recognizes the IQN (iSCSI Qualified Name) formatted iSCSI initiator node name. For example, an iSCSI target name of "iSCSI tgt" is presented as follows: iqn.2002-12.com.brocade:ISCSItgt After an IQN is defined, you can map a LUN device to the IQN name. Web Tools Administrator's Guide 185 53-1001772-01

  • 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

Web Tools Administrator’s Guide
185
53-1001772-01
DRAFT: BROCADE CONFIDENTIAL
Chapter
15
Administering the iSCSI Target Gateway
In this chapter
iSCSI service overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
Setting up iSCSI Target Gateway services . . . . . . . . . . . . . . . . . . . . . . . . . . 188
Discovery Domain management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
Discovery domain sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
CHAP configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
Connection redirection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
iSCSI Fibre Channel zone configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
Managing and troubleshooting accessibility . . . . . . . . . . . . . . . . . . . . . . . . 199
iSCSI service overview
Through the iSCSI Target Gateway Admin module, you can perform iSCSI target gateway-related
management tasks, such as creating and managing iSCSI virtual targets, managing iSCSI sessions
and iSCSI authentications, and editing discovery domain sets, that enforce iSCSI device access
control. The iSCSI port configuration is available to both the iSCSI Target Gateway Admin module
and the port management module.
Although iSCSI service is fabric-wide, you can manage the iSCSI target gateway service through any
iSCSI-capable switch in a fabric. Any applied iSCSI target gateway change is propagated and
enforced to the whole fabric.
Web Tools can recognize and manage all Fibre Channel ports and GbE ports on the supported
blades. When a GbE port is configured to support iSCSI, it can transport SCSI traffic over an IP
network. Each GbE port has a unique IP address called an “iSCSI target portal” and each port
supports 64 iSCSI sessions. The TCP/IP stack at the port provides support for multiple TCP
connections over a single GbE port.
In Web Tools, ports are addressed using slot number and port number notation (for example, 2,16):
For Fibre Channel ports on the FC4-16IP blade, the range of ports is 0 through 7.
For GbE ports on the FC4-16IP blade, the port numbers range from ge0 through ge7. The
FC4-16IP blade does not support FCIP functionality.
The iSCSI standard defines several naming conventions to enable location-independent device
identification of storage resources. The FC4-16IP blade recognizes the IQN (iSCSI Qualified Name)
formatted iSCSI initiator node name. For example, an iSCSI target name of “iSCSI tgt” is presented
as follows:
iqn.2002-12.com.brocade:ISCSItgt
After an IQN is defined, you can map a LUN device to the IQN name.