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

Device Locality, Configuring Zones, Principal, Default, Never Principal, Switch Priority

Page 107 highlights

Planning Considerations for Fibre Channel Topologies 3 When balancing a load across multiple ISLs, a director or switch attempts to avoid assigning multiple ports attached to a device to the same ISL. This minimizes the probability that failure of a single ISL will affect all paths to the device. However, because port assignments are made incrementally as devices log into the fabric and ISLs become available, optimal results are not guaranteed. Special consideration must also be given to applications with high data transfer rates or devices that participate in frequent or critical data transfer operations. For example, in Figure 3-11, suppose device D7 is a server and device D9 is a storage unit and both devices participate in a critical nightly backup operation. It is recommended that such a connection be routed directly through director S2 (rather than the entire fabric) through zoned port connections, WWN-bound port connections, or a preferred path. For additional information, refer to Device Locality. • Zoning - For multiswitch fabrics, zoning is configured on a fabric-wide basis. Changes to the zoning configuration apply to all directors and switches in the fabric. To ensure the zoning configuration is maintained, certain rules are enforced when two or more elements are connected through ISLs to form a fabric or when two or more fabrics are joined. For additional information, refer to Configuring Zones. After directors and fabric switches are defined and cabled, they automatically join to form a single fabric through a user-transparent process. However, the user should be aware of the following fabric concepts, configuration characteristics, and operational characteristics: • Principal switch selection - Setting this value determines the principal switch for the multiswitch fabric. Select either Principal (highest priority), Default, or Never Principal (lowest priority) from the Switch Priority drop-down list. If all fabric elements are set to Principal or Default, the director or fabric switch with the highest priority and the lowest WWN becomes the principal switch. Following are some examples of principal switch selection when fabric elements have these settings. - If you have three fabric elements and set all to Default, the director or switch with the lowest WWN becomes the principal switch. Planning Considerations for Fibre Channel Topologies 3-23

  • 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
Planning Considerations for Fibre Channel Topologies
3-23
Planning Considerations for Fibre Channel Topologies
When balancing a load across multiple ISLs, a director or switch
attempts to avoid assigning multiple ports attached to a device to
the same ISL. This minimizes the probability that failure of a
single ISL will affect all paths to the device. However, because
port assignments are made incrementally as devices log into the
fabric and ISLs become available, optimal results are not
guaranteed.
Special consideration must also be given to applications with
high data transfer rates or devices that participate in frequent or
critical data transfer operations. For example, in
Figure 3-11
,
suppose device
D
7
is a server and device
D
9
is a storage unit and
both devices participate in a critical nightly backup operation. It
is recommended that such a connection be routed directly
through director
S
2
(rather than the entire fabric) through zoned
port connections, WWN-bound port connections, or a preferred
path. For additional information, refer to
Device Locality
.
Zoning -
For multiswitch fabrics, zoning is configured on a
fabric-wide basis. Changes to the zoning configuration apply to
all directors and switches in the fabric. To ensure the zoning
configuration is maintained, certain rules are enforced when two
or more elements are connected through ISLs to form a fabric or
when two or more fabrics are joined. For additional information,
refer to
Configuring Zones
.
After directors and fabric switches are defined and cabled, they
automatically join to form a single fabric through a user-transparent
process. However, the user should be aware of the following fabric
concepts, configuration characteristics, and operational
characteristics:
Principal switch selection -
Setting this value determines the
principal switch for the multiswitch fabric. Select either
Principal
(highest priority),
Default
, or
Never Principal
(lowest priority) from
the
Switch Priority
drop-down list.
If all fabric elements are set to
Principal
or
Default
, the director or
fabric switch with the highest priority and the lowest WWN
becomes the principal switch. Following are some examples of
principal switch selection when fabric elements have these
settings.
If you have three fabric elements and set all to
Default
, the
director or switch with the lowest WWN becomes the
principal switch.