HP StorageWorks 2/16V Brocade Fabric Manager Administrator's Guide (53-1000019 - Page 286

About Fibre Channel Routing

Page 286 highlights

19 About Fibre Channel Routing About Fibre Channel Routing Fibre Channel routing provides connectivity to devices in different fabrics without merging the fabrics. For example, using Fibre Channel routing you can share tape drives across multiple fabrics without the administrative problems, such as change management, network management, scalability, reliability, availability, and serviceability, that might result from merging the fabrics. Fibre Channel routing allows you to create logical storage area networks (LSANs) that can span fabrics. These LSANs allow Fibre Channel zones to cross physical SAN boundaries without merging the fabrics and while maintaining the access controls of zones. Fibre Channel routing requires some additional terminology: FC Router A switch running FC-FC Routing Service. EX_Port A type of port that functions somewhat like an E_Port, but does not propagate fabric services or routing topology information from one fabric to another. A VEX_Port is similar to an EX_Port, but is a virtual port that enables routing functionality via an FCIP tunnel. Interfabric link (IFL) The link between an E_Port and an EX_Port, or a VE_Port and a VEX_Port. Edge fabric A standard Fibre Channel fabric with targets and initiators connected through an FC Router to another Fibre Channel fabric. Backbone fabric An FC Router can connect two edge fabrics; a backbone fabric connects FC Routers. The backbone fabric is the fabric to which the FC Router switch belongs. A backbone fabric consists of at least one FC Router and possibly a number of Fabric OS-based Fibre Channel switches. Initiators and targets in the edge fabric can communicate with devices in the backbone fabric through the FC Router. metaSAN The collection of all SANs interconnected with FC Routers. Note Devices on edge fabrics that are connected to a SilkWorm AP7420 Multiprotocol Router cannot communicate with devices in the backbone fabric. Figure 19-1 on page 19-3 shows a metaSAN with a backbone consisting of one SilkWorm 7500 connecting hosts in Edge Fabric 1 and 3 with storage in Edge Fabric 2 and the backbone fabric through the use of LSANs. A device is shared between: • The backbone fabric and Edge Fabric 1 • Edge Fabric 1 and Edge Fabric 2 • Edge Fabric 2 and Edge Fabric 3 19-2 Fabric Manager Administrator's Guide Publication Number: 53-1000196-01-HP

  • 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
  • 323
  • 324
  • 325
  • 326
  • 327
  • 328
  • 329
  • 330
  • 331
  • 332
  • 333
  • 334
  • 335
  • 336
  • 337
  • 338
  • 339
  • 340
  • 341
  • 342
  • 343
  • 344
  • 345
  • 346
  • 347
  • 348
  • 349
  • 350
  • 351
  • 352
  • 353
  • 354
  • 355
  • 356
  • 357
  • 358
  • 359
  • 360
  • 361
  • 362
  • 363
  • 364
  • 365
  • 366
  • 367
  • 368
  • 369
  • 370
  • 371
  • 372
  • 373
  • 374
  • 375
  • 376
  • 377
  • 378
  • 379
  • 380
  • 381
  • 382
  • 383
  • 384
  • 385
  • 386
  • 387
  • 388
  • 389
  • 390
  • 391
  • 392
  • 393
  • 394
  • 395
  • 396
  • 397
  • 398
  • 399
  • 400
  • 401
  • 402
  • 403
  • 404
  • 405
  • 406

19-2
Fabric Manager Administrator’s Guide
Publication Number: 53-1000196-01-HP
About Fibre Channel Routing
19
About Fibre Channel Routing
Fibre Channel routing provides connectivity to devices in different fabrics without merging the fabrics.
For example, using Fibre Channel routing you can share tape drives across multiple fabrics without the
administrative problems, such as change management, network management, scalability, reliability,
availability, and serviceability, that might result from merging the fabrics.
Fibre Channel routing allows you to create logical storage area networks (LSANs) that can span fabrics.
These LSANs allow Fibre Channel zones to cross physical SAN boundaries without merging the fabrics
and while maintaining the access controls of zones.
Fibre Channel routing requires some additional terminology:
Figure 19-1 on page 19-3
shows a metaSAN with a backbone consisting of one SilkWorm 7500
connecting hosts in Edge Fabric 1 and 3 with storage in Edge Fabric 2 and the backbone fabric through
the use of LSANs. A device is shared between:
The backbone fabric and Edge Fabric 1
Edge Fabric 1 and Edge Fabric 2
Edge Fabric 2 and Edge Fabric 3
FC Router
A switch running FC-FC Routing Service.
EX_Port
A type of port that functions somewhat like an E_Port, but does not propagate
fabric services or routing topology information from one fabric to another. A
VEX_Port
is similar to an EX_Port, but is a virtual port that enables routing
functionality via an FCIP tunnel.
Interfabric link (IFL)
The link between an E_Port and an EX_Port, or a VE_Port and a VEX_Port.
Edge fabric
A standard Fibre Channel fabric with targets and initiators connected through
an FC Router to another Fibre Channel fabric.
Backbone fabric
An FC Router can connect two edge fabrics; a
backbone fabric
connects FC
Routers. The backbone fabric is the fabric to which the FC Router switch
belongs. A backbone fabric consists of at least one FC Router and possibly a
number of Fabric OS-based Fibre Channel switches. Initiators and targets in
the edge fabric can communicate with devices in the backbone fabric through
the FC Router.
metaSAN
The collection of all SANs interconnected with FC Routers.
Note
Devices on edge fabrics that are connected to a SilkWorm AP7420 Multiprotocol Router cannot
communicate with devices in the backbone fabric.