Вы находитесь на странице: 1из 4

How to configure FCIP on Brocade 7500s

Over Brocade Silkworm 7500s crossing an OC-12. This assumes you have prior
knowledge of the Brocade Fabric OS.
When using the Silkworm 7500, you have 32 ports available, 16 physical FC
ports, 2 GE ports, and 16 Virtual Ports
Backbone Fabric Silkworm 7500s connected together via VE-Ports or
Edge Fabric Normal switched fabric connected to the backbone via EPorts or EX-Ports
VE-Port FCIP interconnected E-Port/ISL, i.e. fabrics will merge
VEX-Port FCIP interconnected EX-Port, routing needed via lsan zoning to
connect initiator to a target.
E-Port Normal expansion connection between one switch to another.
EX-Port A connection that connects 2 fabrics together without merging
LSAN A special zone that allows 2 fabrics interconnected via EX-Ports to

Link Generation
1. On the Backbone/Edge ensure that interopmode is disabled
Check to ensure you arent running in Mcdata Compatibility Mode
2. On the Backbone/Edge ensure that secmode is disabled
Check to ensure Secure-Fabrics isnt enabled
3. On the Backbone ensure that msplatform DB is disabled
Check to ensure there is no external management to Brocade
4. Enable the FC Routing, by default its disabled on the backbone
Ensure its disabled first
>>fosConfig disable fcr
Set the Backbone Fabric ID
Ensure you use the same backbone id for all the routers in that
Enable the FC routing
>>fosconfig enable fcr
5. Perform these steps on all Routers in the Backbone Fabric
Creating FCIP Connections
1. Step to enabling FCIP is to turn on your EX-Port from the backbone fabric
(Routers) into the edge fabric (e.g. Tape SAN). On both sides of your WAN
Pick the same port for each backbone fabric i.e. port-4 on Source
Router and Destination Router, to keep things easy to manage, on
both sides
If plugging into the same switch types plug the router FC port into
the same port on the other side of the EX-Port/Edge Fabric
By default all ports on the routers are persistently disabled,
ensuring no-one can just plug in and go.

Here are the steps to configure the EX-Ports

>>portcfgexport 4 -a 1 -f 30 (fcrap14c001)
>>portcfgexport 4 a 1 f 31 (fcrap14c101)
This will configure port-4 to be an ex-port once its been
enabled, with (-a 1, enabling), (-f 30, defines the fabric id)
On the other side of the backbone, you simply flip the EX-port fabric
ids, other wise the backbone fabric router will not merge properly
>>portcfgexport 4 a 1 f 31 (fcrrp21001)
>>portcfgexport 4 a 1 f 30 (fcrrp21101)

3. Next you need to enable the port

>>portcfgpersistentenable 4 on all routers, you have configured EXports on.
This will enable the port, and assuming its plugged into the edge
fabric it will synch up, and you have a routable environment from
the FC-Side
On the backbone you will see:
EX-Port 10:00:00:05:1e:35:2c:9d "fcsap14c501" (fabric id = 30 )(Trunk master)
On the edge fabrics you will see:
E-Port 50:00:51:e3:81:2e:4e:1e "fcr_fd_160" (downstream)(Trunk
master) enables a tunnel for ge0
One thing to remember the main reason for configuration of an EXPort on the backbone, is so the fabrics will not merge themselves,
thus ensuring WAN link outages wont cause multi-fabric
6. IPSEC is supported on these routers, however this configuration uses
a PVC, not a internet based VPN.
You can configure only 1 tunnel per Ge port if IPSec is enabled, this
configuration takes advantage of multiple tunnels over the same
As well Tape Pipelining and Fast-Write arent supported over a
secure-tunnel, and we plan to use both of these items.
7. Next you need to ensure you enable the virtual ports on both routers
Ge0 16 23 correspond to Physical 0-8
Ge1 24 31 correspond to Physical 9-15
8. Go ahead and enable the virtual ports you need based on the number of
tunnels you are running across the ge-ports.

>>portcfgpersistentenable 16
>>portcfgpersistentenable 24 enables a tunnel for ge1
Ensure this is done on both sides of the WAN, and both set of

9. Create the IP Interfaces for the ge-ports on each router

LC-Router >>portcfg ipif ge0 create 2250
2250 is the MTU size (2148, is FC Frame size)
FC-Router >>portcfg ipif ge0 create 2250

In a flat subnet there is no need to configure a ip route, once

the tunnel is up the route will be generated for you
If you wish to enable tunnels on ge1 then you need to
perform the same procedure on those ports on each router.

10.Next are is to create the tunnels on both sides

LC-Router >>portcfg fciptunnel ge0 create 0
512000 -c
Tunnel ID = 0
Dest IP =
Src IP =
comm_rate = 512000 (500 mbps) (What Networks has given
-c (compression enable)
-t (enables tapepiplining)
-f (enables fastwrite)
**Note** HP Currently does not support the Fast Write option as it pertains to
Continuous Access Journaling, if this is enabled you will not be able to create the
needed pairs
FC-Router >>portcfg fciptunnel ge0 create 0
512000 -c
You will need to ensure that you create tunnels on the other
pais of routers as well.
12.Once this is complete the tunnels should come online, provided you have
done everything correctly
Online VE-Port 10:00:00:05:1e:37:f2:fc "fcrrp21001" (upstream)
Creating LSAN zones for FC Routing Communications
At this point you are ready to create some LSAN zones and start moving some
On the Edge Fabrics
Create an alias in the LC Fabric for the Target-Port on the FC
Storage Platform
aliCreate "Storage_1B_Alias","50:06:00:00:01:02:03:04"
Create a zone with the remote alias and the local one
zoneCreate "lsan_CAXP_Jrnl_Zone"," Storage_1B_Alias; XPAP14C001_1B_Alias"
Add the new zone into the Defined zone schema
cfgAdd "CFG_3"," lsan_CAXP_Jrnl_Zone"

Add the new zone into the Effective zone schema

cfgEnable "CFG_3"

FC- Edge Fabric

aliCreate "XPAP14C001_1B_Alias"," 50:06:0e:80:04:7e:69:01"

zoneCreate "lsan_CAXP_Jrnl_Zone"," XPAP14C001_1B_Alias;
Add the new zone into the Defined zone schema
cfgAdd "FC_CFG4"," lsan_CAXP_Jrnl_Zone"

Add the new zone into the Effective zone schema

cfgEnable "Fc_CFG4"

You will need to do the same process above for the other
sides of the XP
XPAP14C001_2B_Alias XPRP21001_2B_Alias (Initiator
RCU Target)
Since we are going both ways you will need to
configure another lsan zone coming back the other
way for the XPAP14C001_1D_Alias
XPRP21001_1D_Alias (RCU Target Initiator)
Must use LSAN or lsan in the beginning of any zone that will
be routed.