This sample configuration is relevant for 1.2 and 1.3 releases of
SAN-OS. Some parameters change in the 2.0 release of SAN-OS. Reference the 2.0
SAN-OS configuration guide and release notes.

FCIP describes mechanisms that allow the interconnection of islands of
Fibre Channel (FC) storage area networks (SANs) over IP-based networks to form
a unified SAN in a single FC fabric. FCIP relies on IP-based network services
to provide the connectivity between the SAN islands over local area networks,
metropolitan area networks, or wide area networks.

The IP backbone must be operational and delivering the required
bandwidth to support the applications running across the FCIP link(s)- this
could be a Layer 2 (L2) or Layer 3 (L3) topology. If L3, the intermediate
routers or multilayer switches must be setup and configured to forward IP
traffic between source and destination IP addresses of the FCIP tunnels
appropriately. If Quality of Service (QoS) or traffic shaping is enforced at
any network device in the path between the FCIP peers, the network manager
administrating the IP infrastructure should be consulted to get the necessary
details before configuring any TCP related parameters and features on the MDS
FCIP profile(s) .

MDS 9216 with IPS service module (DS-X9308-SMIP) running version
1.2.(2a)

Win2003 Server (HPQ Pro-Liant-P4) with Emulex LP9K
HBA

IBM Storage Array (ESS-2105-F20)

The information in this document was created from the devices in a
specific lab environment. All of the devices used in this document started with
a cleared (default) configuration. If your network is live, make sure that you
understand the potential impact of any command.

ANSI T11

FC-SW-2 describes the operation and interaction of FC switches
including E_Port and fabric operation.

FC-BB-2 is a mapping that pertains to the extension of FC switched
networks across a TCP network backbone, and defines reference models that
support E_Port and B_Port.

IETF IPS Working Group

FC over TCP covers the TCP/IP requirements for transporting FC frames
over an IP network.

FC frame encapsulation defines the common fibre encapsulation
format.

An interconnection between two SAN switches or fabrics across FCIP is
called an FCIP link, and can contain one or more TCP connections. Each end of a
FCIP link is associated with a Virtual E port (VE_port) or a B_port, depending
on the implementation. FC-BB and FC-BB-2 are describing the differences between
both approaches. The IP Services module (DS-X9308-SMIP) supports both modes,
but defaults to the VE_Port, which is also the recommended mode to run if all
relevant peers are DS-X9308-SMIP modules. The VE_Port functionality on MDS
platforms also supports TE port functionality, which makes it capable of
trunking traffic from multiple VSANs across one FCIP instance.

This diagram shows a typical lab-setup where no additional networking
equipment is connected between both Gigabit Ethernet (GE) interfaces of both
MDS switches. This is the simplest form of an MDS FCIP install, and is
typically used in customer labs to verify basic functionality. In VSAN 600, the
Emulex LightPulse 9000 HBA connects the Windows 2003 server to the MDS9509
called Bison, and a IBM storage Array connected to MDS9216 called Canterbury,
where LUNs for the Windows 2003 server are configured.

The Agilent SAN test device is used as an emulator to populate VSAN 601
with two devices, as well as to generate substantial FC-2 non-FCP background
traffic. This peripheral equipment is added to make the configuration more
realistic and to have substantial entries in the distributed name server of
both participating switches. The focus of this document is not end-to-end
connectivity, and no screen shots of the server or storage array are included.
The peripheral equipment is not knowledgeable about the FCIP, and it behaves as
if the EISL link between both MDSs was running across a normal FC link.