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

Factors to Consider When Implementing a Fabric Topology, Heterogeneous fabric, Number of ISLs

Page 106 highlights

Planning Considerations for Fibre Channel Topologies 3 • Heterogeneous fabric - Vendor interoperability in the fabric environment is supported; therefore, fabric elements can include directors, fabric switches, and open-fabric compliant products supplied by original equipment manufacturers (OEMs). To determine if interoperability is supported for a product or if communication restrictions apply, refer to the supporting publications for the product or contact McDATA. • Number of ISLs - The Intrepid 6064 Director supports 48 ISLs. The Intrepid 6140 Director supports 140 ISLs. The Intrepid 10000 Director supports seven ISLs per optical paddle pair. Sphereonclass switches support a maximum ISL count equal to half the number of Fibre Channel ports available on the product. For redundancy, at least two ISLs should connect any pair of director-class fabric elements. • Hop count - The Fibre Channel theoretical limit of ISL connections traversed (hop count) in a single path through the fabric is seven. The tested and verified hop count limit is three. NOTE: The hop count is equal to the number of ISL connections traversed in a single path, not the total number of ISL connections between devices. As shown in Figure 3-11, the number of ISL connections between switch S1 and S2 is four, while the number of hops is one. Factors to Consider When Implementing a Fabric Topology Director and switch-based fabrics offer scalable, high-performance, and high-availability connectivity solutions for the enterprise. To enable a multiswitch fabric, all fabric elements must be defined to the SAN management application (SANavigator 4.2 or EFCM 8.6) and must be physically cabled to form the requisite ISL connections. In addition, it is recommended that each director or switch in the fabric be assigned a unique preferred Domain_ID. When planning to implement a fabric topology, consider the following connectivity and cabling best practices: • Physical characteristics and performance objectives - Most enterprises have unique configurations determined by the characteristics of end devices, fabric elements, cost, and the installation's performance objectives (such as high data transfer rate or high availability). These factors, along with nondisruptive growth and service requirements, must be evaluated when planning an initial fabric. For additional information, refer to General Fabric Design Considerations on page 3-29. 3-20 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
  • 319
  • 320
  • 321
  • 322

3
3-20
McDATA Products in a SAN Environment - Planning Manual
Planning Considerations for Fibre Channel Topologies
Heterogeneous fabric -
Vendor interoperability in the fabric
environment is supported; therefore, fabric elements can include
directors, fabric switches, and open-fabric compliant products
supplied by original equipment manufacturers (OEMs). To
determine if interoperability is supported for a product or if
communication restrictions apply, refer to the supporting
publications for the product or contact McDATA.
Number of ISLs -
The Intrepid 6064 Director supports 48 ISLs.
The Intrepid 6140 Director supports 140 ISLs. The Intrepid 10000
Director supports seven ISLs per optical paddle pair. Sphereon-
class switches support a maximum ISL count equal to half the
number of Fibre Channel ports available on the product. For
redundancy, at least two ISLs should connect any pair of
director-class fabric elements.
Hop count -
The Fibre Channel theoretical limit of ISL
connections traversed (hop count) in a single path through the
fabric is seven. The tested and verified hop count limit is three.
NOTE:
The hop count is equal to the number of ISL connections
traversed in a single path, not the total number of ISL connections
between devices. As shown in
Figure 3-11
, the number of ISL connections
between switch
S1
and
S2
is four, while the number of hops is one.
Factors to Consider
When Implementing
a Fabric Topology
Director and switch-based fabrics offer scalable, high-performance,
and high-availability connectivity solutions for the enterprise. To
enable a multiswitch fabric, all fabric elements must be defined to the
SAN management application (SANavigator 4.2 or EFCM 8.6) and
must be physically cabled to form the requisite ISL connections. In
addition, it is recommended that each director or switch in the fabric
be assigned a unique preferred Domain_ID. When planning to
implement a fabric topology, consider the following connectivity and
cabling best practices:
Physical characteristics and performance objectives -
Most
enterprises have unique configurations determined by the
characteristics of end devices, fabric elements, cost, and the
installation’s performance objectives (such as high data transfer
rate or high availability). These factors, along with nondisruptive
growth and service requirements, must be evaluated when
planning an initial fabric. For additional information, refer to
General Fabric Design Considerations
on page 3-29.