FCIP Fibre Channel over IP (FCIP) SCSI over FCP over TCP over IP Same protocol stack as Fibre Channel Similar IPv6 over IPv4 GRE tunnel Initiators and Targets are still Native FC (or FCOE) Used for FC SAN Extension Data replication over long distances Native FC is sensitive to latency and drops TCP already has built in congestion management, retransmission, and so on FCIP and CCIE DC Extend the SAN over the DCI E.g. FC SAN over OTV SCSI over FCP over TCP over IP over Ethernet over MPLE over GRE over IP over Ethernet MDS will act as a FCIP Gateway FCIE Gateway Configuration Configure normal FC to Initiators and Targets Configure IP connectivity between MDS's Configure FCIP Tunnel Tunnel Counts as a TE_port Normal FC switching design now applies Zoning, FCSPF , FCNS is all going to be the same as in a Fabric locally at the same location FCIP Topology  All FC and IP connectivity are already setup in the network. You should be able to ping MDS2 form MDS1. MDS1 conf t feature fcip fcip profile 1 ip address 10.0.0.53 (Tunnel Source Local Address) interface fcip1 use-profile 1 peer-info ipaddr 10.0.0.54 (Remote Tunnel address) no shut MDS2 conf t feature fcip fcip profile 1 ip address 10.0.0.54 (Tunnel Source Local Address) interface fcip1 use-profile 1 peer-info ipaddr 10.0.0.53 (Tunnel Source Local Address) no shut show int fcip1 brief (MDS1)  show fcip summary  show fcns database vsan 100 (N5K2)  Configure a Zone Zoneset N5K1 (because it's an end to end fabric you can configure zoning aware) Make sure enhanced zoning is on for VSAN 100 conf t zone mode enhanced vsan 100 zoneset VSAN100 vsan 100 zone name SERVER3 member device-alias JBOD2_PORT1_DISK1 member device-alias SERVER3 zone name SERVER2 member device-alias JBOD1_PORT0_DISK0 member device-alias SERVER2_SANB zoneset activate name VSAN100 vsan 100 zone commit vsan 100 |
Blog >