HP StorageWorks 2/24 FW 07.00.00/HAFM SW 08.06.00 McDATA Products in a SAN Env - Page 119

Employ device locality, Install an additional ISL, Device Locality

Page 119 highlights

Planning Considerations for Fibre Channel Topologies 3 Storage TM 1 Gbps ISL 200 Bandwidth (MBps) TM 150 100 50 NT Server 1 NT Server 2 (100 MBps Max) (100 MBps Max) 0 15 1 Gbps ISL NT Server 1 NT Server 2 10 15 20 25 Time (Sec) Figure 3-12 ISL Oversubscription Two NT servers, each with maximum I/O of 100 MBps, are contending for the bandwidth of a single ISL operating at 1.0625 Gbps. In addition to data, the ISL must also transmit Class F traffic internal to the fabric. When operating at peak load, each NT server receives less than half the available ISL bandwidth. Depending on fabric performance requirements and cost, there are several options (best practices) to solve ISL oversubscription problems, including: • Employ device locality - NT Server 1 and its associated storage device can be connected through one director. NT Server 2 and its associated storage device can be connected through the other director. As a result, minimal traffic flows across the ISL between directors and the congestion problem is mitigated. For additional information, refer to Device Locality. • Install an additional ISL - A second ISL can be installed to balance the traffic load between fabric elements. Two ISLs are sufficient to support the bandwidth of both NT servers operating at peak load. Planning Considerations for Fibre Channel Topologies 3-33

  • 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

3
Planning Considerations for Fibre Channel Topologies
3-33
Planning Considerations for Fibre Channel Topologies
Figure 3-12
ISL Oversubscription
Two NT servers, each with maximum I/O of 100 MBps, are
contending for the bandwidth of a single ISL operating at 1.0625
Gbps. In addition to data, the ISL must also transmit Class F traffic
internal to the fabric. When operating at peak load, each NT server
receives less than half the available ISL bandwidth.
Depending on fabric performance requirements and cost, there are
several options (best practices) to solve ISL oversubscription
problems, including:
Employ device locality -
NT Server 1 and its associated storage
device can be connected through one director. NT Server 2 and its
associated storage device can be connected through the other
director. As a result, minimal traffic flows across the ISL between
directors and the congestion problem is mitigated. For additional
information, refer to
Device Locality
.
Install an additional ISL -
A second ISL can be installed to
balance the traffic load between fabric elements. Two ISLs are
sufficient to support the bandwidth of both NT servers operating
at peak load.
NT Server 1
(100 MBps Max)
1 Gbps ISL
Storage
NT Server 2
(100 MBps Max)
1
5
10
15
20
25
0
100
150
200
Time (Sec)
Bandwidth (MBps)
50
1 Gbps ISL
NT Server 1
NT Server 2