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

Duplicate Domain_IDs, E_Port segmentation

Page 111 highlights

Planning Considerations for Fibre Channel Topologies 3 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. A rerouting delay parameter can be enabled at the Element Manager application to ensure a director or switch provides correct frame order delivery. The delay period is equal to the error detect time out value (E_D_TOV) specified in the Element Manager application. Class 2 frames transmitted into the fabric during this delay period are rejected; Class 3 frames are discarded without notification. By default, the rerouting delay parameter is disabled. NOTE: To prevent E_Port segmentation, the same E_D_TOV and resource allocation time out value (R_A_TOV) must be specified for each fabric element. • E_Port segmentation - When an ISL activates, the two fabric elements exchange operating parameters to determine if they are compatible and can join to form a single fabric. If the elements are incompatible, the connecting E_Port at each director or switch segments to prevent the creation of a single fabric. A segmented link transmits only Class F traffic; the link does not transmit Class 2 or Class 3 traffic. The following conditions cause E_Ports to segment: - Incompatible operating parameters - Either the R_A_TOV or E_D_TOV is inconsistent between the two fabric elements. - Duplicate Domain_IDs - One or more Domain_ID conflicts are detected. - Incompatible zoning configurations - Zoning configurations for the two fabric elements are not compatible. For an explanation, refer to Configuring Zones. - Build fabric protocol error - A protocol error is detected during the process of forming the fabric. - No principal switch - No director or switch in the fabric is capable of becoming the principal switch. Planning Considerations for Fibre Channel Topologies 3-27

  • 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-27
Planning Considerations for Fibre Channel Topologies
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.
A rerouting delay parameter can be enabled at the Element
Manager application to ensure a director or switch provides
correct frame order delivery. The delay period is equal to the error
detect time out value (E_D_TOV) specified in the Element
Manager application. Class 2 frames transmitted into the fabric
during this delay period are rejected; Class 3 frames are discarded
without notification. By default, the rerouting delay parameter is
disabled.
NOTE:
To prevent E_Port segmentation, the same E_D_TOV and
resource allocation time out value (R_A_TOV) must be specified for each
fabric element.
E_Port segmentation
- When an ISL activates, the two fabric
elements exchange operating parameters to determine if they are
compatible and can join to form a single fabric. If the elements are
incompatible, the connecting E_Port at each director or switch
segments to prevent the creation of a single fabric. A segmented
link transmits only Class F traffic; the link does not transmit Class
2 or Class 3 traffic. The following conditions cause E_Ports to
segment:
Incompatible operating parameters
- Either the R_A_TOV or
E_D_TOV is inconsistent between the two fabric elements.
Duplicate Domain_IDs
- One or more Domain_ID conflicts
are detected.
Incompatible zoning configurations
- Zoning configurations
for the two fabric elements are not compatible. For an
explanation, refer to
Configuring Zones
.
Build fabric protocol error
- A protocol error is detected
during the process of forming the fabric.
No principal switch
- No director or switch in the fabric is
capable of becoming the principal switch.