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

Task 15: Plan a Multiswitch Fabric (Optional), Fabric Topologies

Page 277 highlights

Configuration Planning Tasks 6 Task 15: Plan a Multiswitch Fabric (Optional) If a multiswitch fabric topology is to be implemented, carefully plan the physical characteristics and performance objectives of the topology, including the proposed number of fabric elements, characteristics of attached devices, cost, nondisruptive growth requirements, and service requirements. Refer to Fabric Topologies, Planning for Multiswitch Fabric Support, and General Fabric Design Considerations for detailed information. When two or more fabric elements are connected through ISLs to form a fabric, the elements must have compatible operating parameters, compatible name server zoning configurations, and unique domain identifications (IDs). Planning for a fabric must be carefully coordinated with planning for zoned configurations. The following factors should be considered when planning for a multiswitch fabric: • Fabric topology limits - Consider the practical number of fabric elements (theoretical maximum of 31, practical limit of 24), number of ISLs per element, hop count (maximum of three), and distance limitations (limited by port type and cable availability). • Multiple ISLs for bandwidth and load balancing - Consider using multiple ISLs to increase the total bandwidth available between two fabric elements. If heavy traffic between devices is expected, also consider multiple ISLs to create multiple minimum-hop paths for load balancing. If multiple ISL connections are planned, ensure the OpenTrunking feature key is ordered with the Element Manager application. This feature automatically provides dynamic load balancing across multiple ISLs in a fabric environment. • Principal switch selection - If required, plan which fabric element is to be assigned principal switch duties for the fabric. • Critical operations - Consider routing paths that transfer data for critical operations directly through one director or fabric switch and not through the fabric. Planning and implementing a multiswitch fabric is a complex and difficult task. Obtain planning assistance from McDATA's professional services organization before implementing a fabric topology. Configuration Planning Tasks 6-29

  • 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

6
Configuration Planning Tasks
6-29
Configuration Planning Tasks
Task 15: Plan a Multiswitch Fabric (Optional)
If a multiswitch fabric topology is to be implemented, carefully plan
the physical characteristics and performance objectives of the
topology, including the proposed number of fabric elements,
characteristics of attached devices, cost, nondisruptive growth
requirements, and service requirements. Refer to
Fabric Topologies
,
Planning for Multiswitch Fabric Support
, and
General Fabric Design
Considerations
for detailed information.
When two or more fabric elements are connected through ISLs to
form a fabric, the elements must have compatible operating
parameters, compatible name server zoning configurations, and
unique domain identifications (IDs). Planning for a fabric must be
carefully coordinated with planning for zoned configurations. The
following factors should be considered when planning for a
multiswitch fabric:
Fabric topology limits -
Consider the practical number of fabric
elements (theoretical maximum of 31, practical limit of 24),
number of ISLs per element, hop count (maximum of three), and
distance limitations (limited by port type and cable availability).
Multiple ISLs for bandwidth and load balancing -
Consider
using multiple ISLs to increase the total bandwidth available
between two fabric elements. If heavy traffic between devices is
expected, also consider multiple ISLs to create multiple
minimum-hop paths for load balancing.
If multiple ISL connections are planned, ensure the
OpenTrunking feature key is ordered with the Element Manager
application. This feature automatically provides dynamic load
balancing across multiple ISLs in a fabric environment.
Principal switch selection -
If required, plan which fabric
element is to be assigned principal switch duties for the fabric.
Critical operations -
Consider routing paths that transfer data for
critical operations directly through one director or fabric switch
and not through the fabric.
Planning and implementing a multiswitch fabric is a complex and
difficult task. Obtain planning assistance from McDATA’s
professional services organization before implementing a fabric
topology.