iSCSI & FCIP
IP Interface of MDS
• The IP Interface of the MDS are not like Ethernet Interfaces but rather
like a Server Interface.
• We can configure Physical as well as Sub-Interface.
• We also have a concept of Native Vlan, as any untagged traffic going
to the Physical Interface and Tagged Traffic to the Sub-Interface.
• If we create Sub-Interface e.g.
#interface g1/1.<Nos> The Nos here represents the VLAN no that
is used for sending traffic out
iSCSI
• Internet Small Computer System Interface (iSCSI)
• We are carrying SCSI over TCP/IP.
• This is a completely different Protocol Stack than Fibre Channel.
• Is used typically for small to mid-range SAN environment
• Advantage of using this is that we don’t require dedicated SAN
switches and dedicated adapter from the Initiator side.
iSCSI
• iSCSI is not to be confused with SAN Switching as the end hosts,
Storage Array just can run in IP, and the Transport in between can be
anything i.e. IP.
• MDS here acts as an iSCSI to FC Gateway.
MDS as iSCSI Gateway
• MDS is acting like a Translation bridge between Fibre Channel & iSCSI.
• The iSCSI Gateway works in the following way :-
• FC Targets FLOGI as usually to the FC Fabric.
• iSCSI Initiators sends Discovery to the IP enabled interface of MDS.
• MDS applies Zoning.
• iSCSI Initiator thinks FC Target is an iSCSI Target.
• FC Target thinks iSCSI Initiator is an FC Initiator.
MDS iSCSI Gateway Configuration
1. Configure FC to Targets.
2. Configure IP to Initiators.
3. Enable iSCSI
4. Configure Zoning
5. Point Server at MDS IP address.
iSCSI Access Control
• The Zoning can be based on :-
Normal pWWN, FCID , alias, etc.
Initiator’s IP add
Initiator’s IQN
Configuration : We will set the Storage side with FC already
!
(config)# int gigabitethernet 2/1
ip add … {should be pinging Initiators IPs}
no shut
!
(config)# feature iscsi
!
(config)# iscsi enable module <no> [1] {Runs on Module with IPS}
!
(config)# int iscsi 2/1 {Logical Interface of iSCSI that represents Physical int g2/1}
no shut
!
(config)# iscsi import target fc
The Initialization of the Protocol from Initiator is only like IP the rest of them is FC Routing till the
SAN Extension Technologies
TCP 3221
Initiates 2 TCP Session
1. Control Plane.
2. Data Plane.
This helps us provide different QoS Treatment for Control Plane and Data Plane.
We can Control which one Initiates the TCP connection and become TCP Client.
FCIP Overhead
• This adds 94 bytes including new CRC=4 bytes will be adding 98
bytes overhead.
• So we are gonna transport 2112 bytes FC Frame + 98 bytes FCIP
Header i.e. total MTU of around > 2200 bytes.
• Although Fragmentation is supported in IP Network still it is
recommended to have an MTU of 2300 bytes in the IP + Ethernet
Transport Network to support FCIP.
FCIP Commands :-
--------------
!Turn the feature of FCIP
feature fcip
!Make sure IP rechability is there between Sites.
int g1/1
ip address <on same subnet as other side>
!Turn on the FCIP Profile and bind it to the IP add of the Local Interface
fcip profile <1-255>
ip add <ip add of local interface>
!Create FCIP Interface and bind it to a profile
int fcip <1-255>
use-profile <1-255>
peer-info ipaddr <IP add of the Peer>
no shut
!To never Initiate a TCP Connection and always be a TCP Server
int fcip 1
passive-mode
!Setting QoS for Control and Data Stream by setting the DSCP value
int fcip 1
qos control <DSCP value> data <DSCP value>
!Turn on write acceleration such that the MDS switch will Reply to the Request
!sent by the Initiator to the Target thus not waiting for the Receive_Ready
!and making the Process faster. This is needed in both side otherwise Tunnel
!will go Down.
int fcip 1
write-accelerator
!Modifying Trunk Allowed VSANs
int fcip 1
switchport trunk allowed vsan 1
switchport trunk allowed vsan add 10
switchport trunk allowed vsan add 20
!Modifying FSPF cost
int fcip 1
fspf cost <COST> vsan <NO>
!Modifying TCP parameters and RTT
fcip profile 1
tcp max-bandwidth-mbps 1000 min-available-bandwidth-mbps 500
round-trip-time-<Millisec/Microsec>
Verification :-
=============
#sh int fcip <1-255>
#sh fcns database {to see the two Fabric of diff DC merge}
#sh fcdomain vsan 10 {Shows Principal Switch info}
#sh fcip summary
