Chapter 1 Before Configuring SN
FCIP Overview
Once configured, FCIP instances on each system become active and establish their connectivity via the IP network. The storage devices in one SAN access the storage devices in the connected SAN using FC frames, which are encapsulated in IP packets by the FCIP instance, and transmitted to the peer system. The peer FCIP instance strips the IP packet data and passes only the FC frames over the FC interfaces to the storage devices.
The peer systems deployed for FCIP must be configured to use the same protocol: TCP or raw. TCP protocol uses standard TCP flow control and error recovery algorithms, and should be used if you require
a
If the selected protocol is TCP, one FCIP instance must be configured as the TCP client; the other FCIP instance must be configured as the TCP server. The only difference between FCIP instances configured as TCP client and TCP server is which FCIP instance initiates the connection: the TCP client initiates the connection.
FCIP transports FC frames between SANs by performing the following actions (Figure
•Transporting FC frames between a SAN and an SN
•Encapsulating FC frames in IP packets and transporting the IP packets to a peer SN
•Receiving IP packets and transporting as FC frames between the peer SN
Note that FC traffic is carried over the IP network in such a way that the FC fabric and all FC devices on the fabric are unaware of the presence of the IP Network.
Figure 1-15 FCIP Actions
FC hosts and
storage devices
SAN
|
| FC hosts and |
SN | SN | storage devices |
|
IP | SAN |
Transporting FC frames between SAN and an SN
Encapsulating FC frames in IP packets and transporting IP packets to peer SN
Transporting FC frames between an SN
91008
FCIP Network Structures
This section describes typical FCIP network structures. In all of these examples, a management station (not shown) manages the storage routers through an IP network connected to the management interface and/or HA interface of each storage router.
Cisco SN
|
| |
|