HP StorageWorks 2/16V Brocade Web Tools Administrator's Guide (53-0000194-01, - Page 111

Using the FCIP Tunneling Service

Page 111 highlights

Using the FCIP Tunneling Service Chapter 7 This chapter describes the Fibre Channel over IP (FCIP) Tunneling Service. It contains the following sections: • "About the FCIP Tunneling Service" on page 7-1 • "Configuring an FCIP Interswitch/Interfabric Link" on page 7-7 • "Managing the FCIP Tunneling Service" on page 7-11 About the FCIP Tunneling Service The FCIP Tunneling Service is an optional feature that enables you to use Fibre Channel "tunnels" to connect SANs over IP-based networks. An FCIP tunnel transports data between a pair of Fibre Channel switches, and can have more than one TCP connection between the pair of IP nodes. However, from the Fibre Channel fabric point of view, the FCIP tunnel is just a connection between switches, and all the IP network and protocols remain invisible. Fabric OS supports FCIP interswitch links (ISLs) between the SilkWorm 7500 or SilkWorm 48000 (with an FR4-18i blade) or AP7420 with a VE_Port on each end. Fabric OS also supports FCIP interfabric links (IFLs) between two SilkWorm switches (SilkWorm 7500 or SilkWorm 48000 with an FR4-18i blade) or routers with a VE_Port on one end and a VEX_Port on the other to support a routed fiber channel storage area network, also known as a MetaSAN topology. The GbE ports on the FC4-16IP do not support FCIP tunneling. Note You must have an FCIP license installed on the switch to use the FCIP Tunneling Service. GbE ports configured for FCIP are called "virtual E_Ports" (VE_Ports) or "virtual EX_Ports" (VEX_Ports). An FCIP tunnel between two VE_Ports is considered an FCIP ISL and will merge the two fabrics. An FCIP tunnel between a VE_Port and a VEX_Port is considered an FCIP IFL and will not merge the fabrics. FCIP tunnels between two VEX_Ports are not supported. Fabric OS supports up to eight virtual FCIP tunnels and up to eight logical VE_Ports or eight logical VEX_Ports on a single physical GbE port. The first physical GbE port, ge0, contains logical ports 16- 23; and the second physical GbE port, ge1, contains logical ports 24-31. The FCIP tunnels on each GbE port are numbered 0 through 7, and each tunnel is logically mapped to a physical GbE port. For example, tunnel 0 on GbE port 0 corresponds to logical FC port 16; tunnel 1 on GbE port 1 corresponds to logical FC port 25. At either end of the tunnel is a VE_Port or VEX_Port. After you configure a VE_Port on one end and a VEX_Port on the other, an FCIP IFL connection is established between them. Web Tools Administrator's Guide 7-1 Publication Number: 53-0000194-01

  • 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

Web Tools Administrator’s Guide
7-1
Publication Number: 53-0000194-01
Chapter
7
Using the FCIP Tunneling Service
This chapter describes the Fibre Channel over IP (FCIP) Tunneling Service. It contains the following
sections:
“About the FCIP Tunneling Service”
on page 7-1
“Configuring an FCIP Interswitch/Interfabric Link”
on page 7-7
“Managing the FCIP Tunneling Service”
on page 7-11
About the FCIP Tunneling Service
The FCIP Tunneling Service is an optional feature that enables you to use Fibre Channel “tunnels” to
connect SANs over IP-based networks. An FCIP tunnel transports data between a pair of Fibre Channel
switches, and can have more than one TCP connection between the pair of IP nodes. However, from the
Fibre Channel fabric point of view, the FCIP tunnel is just a connection between switches, and all the IP
network and protocols remain invisible.
Fabric OS supports FCIP interswitch links (ISLs) between the SilkWorm 7500 or SilkWorm 48000
(with an FR4-18i blade) or AP7420 with a VE_Port on each end. Fabric OS also supports FCIP
interfabric links (IFLs) between two SilkWorm switches (SilkWorm 7500 or SilkWorm 48000 with an
FR4-18i blade) or routers with a VE_Port on one end and a VEX_Port on the other to support a routed
fiber channel storage area network, also known as a MetaSAN topology.
The GbE ports on the FC4-16IP do not support FCIP tunneling.
GbE ports configured for FCIP are called “virtual E_Ports” (VE_Ports) or “virtual EX_Ports”
(VEX_Ports). An FCIP tunnel between two VE_Ports is considered an FCIP ISL and will merge the
two fabrics. An FCIP tunnel between a VE_Port and a VEX_Port is considered an FCIP IFL and
will
not merge the fabrics
. FCIP tunnels between two VEX_Ports are not supported.
Fabric OS supports up to eight virtual FCIP tunnels and up to eight logical VE_Ports or eight logical
VEX_Ports on a single physical GbE port. The first physical GbE port, ge0, contains logical ports 16–
23; and the second physical GbE port, ge1, contains logical ports 24–31.
The FCIP tunnels on each GbE port are numbered 0 through 7, and each tunnel is logically mapped to a
physical GbE port. For example, tunnel 0 on GbE port 0 corresponds to logical FC port 16; tunnel 1 on
GbE port 1 corresponds to logical FC port 25.
At either end of the tunnel is a VE_Port or VEX_Port. After you configure a VE_Port on one end and a
VEX_Port on the other, an FCIP IFL connection is established between them.
Note
You must have an FCIP license installed on the switch to use the FCIP Tunneling Service.