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

FL_Port Connectivity, Planning for Private Arbitrated Loop Connectivity

Page 96 highlights

Planning Considerations for Fibre Channel Topologies 3 FL_Port Connectivity Sphereon 4300 and 4500 Fabric Switches provide loop connectivity through GX ports that are active as FL_Ports. The ports provide port addressing, physical connectivity, and Fibre Channel frame routing. Each FL_Port (and the embedded FL_Port) has a 24-bit address identifier. The address identifier is expressed in hexadecimal format as DD AA PP, where: • DD is the domain identifier. This identifier is assigned one of 31 values (60 through 7F). • AA is the area identifier. Each physical FL_Port (12 or 24 ports) is assigned one of up to 24 values (04 through 1B). • PP is the port identifier. Each device (node) attached to an FL_Port is assigned one of 126 AL_PA values (01 through EF). The embedded FL_Port is assigned an AL_PA of 00. Planning for Private Arbitrated Loop Connectivity Private arbitrated loop topology supports the clustering of isolated servers and storage subsystems into workgroup or departmental SANs. This topology is well-suited to small and mid-sized configurations where modest connectivity levels and high data transmission speeds are required. The topology also supports low-cost switching and connectivity in environments where the per-port cost of a switched fabric director is prohibitive. Private arbitrated loop topology: • Supports the connection of up to 126 NL devices per loop plus the switch's embedded FL_Port (127 connections). • Reduces connection costs by distributing the routing function through each loop port (loop functionality is a small addition to normal Fibre Channel port functionality). • Provides a fully-blocking architecture that allows a single connection between any pair of loop ports. Connections between a third loop port and busy ports are blocked until communication between the first connection pair ends. 3-10 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-10
McDATA Products in a SAN Environment - Planning Manual
Planning Considerations for Fibre Channel Topologies
FL_Port Connectivity
Sphereon
4300 and 4500 Fabric Switches
provide loop connectivity
through GX ports that are active as FL_Ports. The ports provide port
addressing, physical connectivity, and Fibre Channel frame routing.
Each FL_Port (and the embedded FL_Port) has a 24-bit address
identifier. The address identifier is expressed in hexadecimal format
as
DD AA PP
, where:
DD
is the domain identifier. This identifier is assigned one of 31
values (
60
through
7F
).
AA
is the area identifier. Each physical FL_Port (12 or 24 ports) is
assigned one of up to 24 values (
04
through
1B
).
PP
is the port identifier. Each device (node) attached to an
FL_Port is assigned one of 126 AL_PA values (
01
through
EF
). The
embedded FL_Port is assigned an AL_PA of
00
.
Planning for Private Arbitrated Loop Connectivity
Private arbitrated loop topology supports the clustering of isolated
servers and storage subsystems into workgroup or departmental
SANs. This topology is well-suited to small and mid-sized
configurations where modest connectivity levels and high data
transmission speeds are required. The topology also supports
low-cost switching and connectivity in environments where the
per-port cost of a switched fabric director is prohibitive. Private
arbitrated loop topology:
Supports the connection of up to 126 NL devices per loop plus the
switch’s embedded FL_Port (127 connections).
Reduces connection costs by distributing the routing function
through each loop port (loop functionality is a small addition to
normal Fibre Channel port functionality).
Provides a fully-blocking architecture that allows a single
connection between any pair of loop ports. Connections between
a third loop port and busy ports are blocked until communication
between the first connection pair ends.