HP StorageWorks 2/140 FW 08.01.00 McDATA Products in a SAN Environment Plannin - Page 106

OpenTrunking, General Fabric Design Considerations, Preferred Path, about the feature, refer

Page 106 highlights

Planning Considerations for Fibre Channel Topologies 3 • Bandwidth - ISL connections can be used to increase the total bandwidth available for data transfer between two directors or switches in a fabric. Increasing the number of ISLs between elements increases the corresponding total ISL bandwidth but decreases the number of port connections available to devices. • Load balancing - Planning consideration must be given to the amount of data traffic expected through the fabric or through a fabric element. Because the fabric automatically determines and uses the least cost (shortest) data transfer path between source and destination ports, some ISL connections may provide insufficient bandwidth while the bandwidth of other connections is unused. To optimize bandwidth use and automatically provide dynamic load balancing across multiple ISLs, consider purchasing and enabling the OpenTrunking feature key. For information about the feature and managing multiple ISLs, refer to OpenTrunking and General Fabric Design Considerations. • Preferred path - Preferred path is an option that allows a user to configure an ISL data path between multiple fabric elements (directors and fabric switches) by configuring the source and exit ports of the origination fabric element and the Domain_ID of the destination fabric element. Each participating director or switch must be configured as part of a desired path. For information about the feature, refer to Preferred Path. ATTENTION ! Activating a preferred path can result in receipt of out-oforder frames if the preferred path differs from the current path, if input and output (I/O) is active from the source port, and if congestion is present on the current path. In general, Fibre Channel frames are routed through fabric paths that implement the minimum possible hop count. For example, in Figure 3-11, all traffic between devices connected to director S1 and director S2 communicate directly through ISLs that connect the directors (one hop). No traffic is routed through director S3 (two hops). If heavy traffic between the devices is expected, multiple ISL connections should be configured to create multiple minimum-hop paths. With multiple paths, the directors balance the load by assigning traffic from different ports to different minimum-hop paths (ISLs). 3-22 McDATA Products in a SAN Environment - Planning Manual

  • 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

3
3-22
McDATA Products in a SAN Environment - Planning Manual
Planning Considerations for Fibre Channel Topologies
Bandwidth -
ISL connections can be used to increase the total
bandwidth available for data transfer between two directors or
switches in a fabric. Increasing the number of ISLs between
elements increases the corresponding total ISL bandwidth but
decreases the number of port connections available to devices.
Load balancing -
Planning consideration must be given to the
amount of data traffic expected through the fabric or through a
fabric element. Because the fabric automatically determines and
uses the least cost (shortest) data transfer path between source
and destination ports, some ISL connections may provide
insufficient bandwidth while the bandwidth of other connections
is unused.
To optimize bandwidth use and automatically provide dynamic
load balancing across multiple ISLs, consider purchasing and
enabling the OpenTrunking feature key. For information about
the feature and managing multiple ISLs, refer to
OpenTrunking
and
General Fabric Design Considerations
.
Preferred path -
Preferred path is an option that allows a user to
configure an ISL data path between multiple fabric elements
(directors and fabric switches) by configuring the source and exit
ports of the origination fabric element and the Domain_ID of the
destination fabric element. Each participating director or switch
must be configured as part of a desired path. For information
about the feature, refer to
Preferred Path
.
ATTENTION !
Activating a preferred path can result in receipt of out-of-
order frames if the preferred path differs from the current path, if input and
output (I/O) is active from the source port, and if congestion is present on the
current path.
In general, Fibre Channel frames are routed through fabric paths
that implement the minimum possible hop count. For example, in
Figure 3-11
, all traffic between devices connected to director
S
1
and director
S
2
communicate directly through ISLs that connect
the directors (one hop). No traffic is routed through director
S
3
(two hops). If heavy traffic between the devices is expected,
multiple ISL connections should be configured to create multiple
minimum-hop paths. With multiple paths, the directors balance
the load by assigning traffic from different ports to different
minimum-hop paths (ISLs).