Sunday, July 7, 2013

iSCSI - (Storage Series Part-7)


+ iSCSI ( Internet Small Computer System Interface )
####################################################

- Completely separate protocol stack from Fibre channel

- Typically used in small to mid range SANs

- No dedicated SAN switches required which implies no SAN switching knowledge required

- 1/10 GigE iSCSI hardware offload cards available

- End host/Storage Array just runs IP

- Transport supports IP and can be of any IP Transport type like Ethernet, Frame Relay or Token Ring

- MDS is an iSCSI to FC Gateway, so MDS is a translational bridge for Fiber Channel & iSCSI

=====================================

+ iSCSI Gateway Operation
########################

- FC Targets FLOGI to FC Fabric

- iSCSI initiators send Discovery to MDS using Ethernet for example

- MDS applies zoning/Access Lists

- iSCSI initiator things FC target is iSCSI target 

- FC Target thinks iSCSI initiator is a FC initiator

=====================================

+ MDS iSCSI Gateway Configuration Steps
#######################################

- Configure FC to Targets

- Configure IP to Initiators

- Enable iSCSI

- Configure ZONING/ Access Control

- Point Server at MDS's IP Address

=====================================

+ Access Control in iSCSI
##########################

- Access Control can be enforced as Zoning based upon :

> pwwn, fcid, alias

> Initiator's IP Address

> Initiator's iSCSI qualified name (IQN),IQNs are generated automatically by initiator
    but can be configured manually.

> iSCI based virtual target to present LUN based on IQN or IP Address/Subnet

=====================================

sh int fc1/20 trunk vsan

feature iscsi
iscsi enable module 1

int iscsi 1/1
 no sh
inc iscsi 1/2
 no sh

iscsi import target fc

sh iscsi global

sh iscsi initiator

HTH...
Deepak Arora
Evil CCIE

No comments: