FCR; Fibre Channel Routing; FC-FC Routing; etc; etc.
This has many names. FC-FC Routing service provides FCR (fibre channel routing).
Basically what it does is that it lets you zone devices in two separate fabrics without merging them.
These two separate fabrics are called ‘edge fabrics’ in Brocade lingo, they are otherwise known as SAN islands.
The edge fabric is connected to a backbone fabric (an FC router or at least an EX_Port).
Integrated Routing – is a licensed feature that lets you run FCR on a port that is in a normal port in a normal switch or port blade (so not in a dedicated router switch or router blade).
There’s a few things required to set up FCR:
- Verify that you have the proper setup (required licenses/hardware)
- Assign backbone FIDs (switchdisable; fosConfig –disable fcr; fcrconfigure; fosconfig –enable; switchenable)
- Configure FCIP tunnel (not required but: portcfg fciptunnel 8/ge0 create 2 184.108.40.206 220.127.116.11 0 -v 100 -p 3 -P 7 . Remote IP first, tunnel ID, vlan, Classes for layer2 control and data traffic)
- Configure IFLs – inter fabric links – links between edge and backbone fabrics (portcfgvexport, portcfgexport 7 -a 1 -f 30 . port 7, enable, fabric id 30)
- Modify cost on the EX_ports (not required; portdisable; portcfgexport 7 -a 1; fcrrouterportcost 7 10000; for default, set it to 0; fcrRouteShow also shows cost)
- Connect cables (if you do it before and they are configured as E_port you may get segmentation).
- Configure trunking on EX_ports (not required but if you have more than one link, please do, same commands as for E_port trunking)
- Configure LSAN zones (same as normal zoning; zonecreate “lsan_zone_fabric”, “wwn; wwn2; wwn3”; cfgadd “zone_cfg”, “lsan_zone_fabric”; cfgenable “zone_cfg”). Use lsanzoneshow -s. Shows imported/exist/configured/initializing.
fcrphydevshow, fcrproxydevshow are also useful.
- Confirm that it’s working (fcrfabricshow, switchshow, portcfgshow, portexport 7, portshow 7)
A little theory
Front domains -> always there
Translate domains (also xlate domains…). -> only there when devices are online and zoned
The FC router has a pool of wwns and proxy ids that it assigns to devices.
Basically a host that wants to communicate with a target in another fabric communicates with a proxy WWN in its own fabric (so the FC router is like a middle man that passes frames back n forth).
A little more information
There may be mistakes in here but that’s just how it is, I tried to keep it as factual as possible and used several sources.
There will most likely be more of these posts coming up.