Wednesday, March 14, 2012

How to map iSCSI interface of XenServer 6.0.2 to EMC VNX 5500

I am starting series of blog with hastag "DellEMCXEN "which will talks about integrating XenServer with EMC VNX 5500. XenServer is installed on Dell Power Edgem710 HD with Chassis M1000e connected via Nexus 5500 and Dell switch M8024.

First define storage interface on XenServer and for that choose configure under "Management Interface " and then select "New Interface" . Now specify the name and then choose the NIC which will be configure for storage traffic. Supply IP address. This needs to be repeated for all the interface which is connected to the storage.


Once this is done then perform discovery of the nic for the logging into EMC. This can be perform via CLI as well as via XenCenter. To perform via XenCenter select new storage and choose "Software iSCSI". Choose "Name" and then under location provide information as follows :

Target host: This will be IP address of target Storage Processor or controller . Specify all the IP address with ,

Target IQN: Here you will find IQN of the target storage processor . If it has 4 ports then you will see 4 IQN. We need to choose the one which is highlighted (*)

This will log all the targets on the EMC VNX box to mapped .


From the command line following  needs to be run from the host in order to login.


Once all the message says successfully login , open EMC Unixshpere and select "Connectivity status "  on left hand side under "Hosts ". This will popup Host initiators window. You will find one name with just IQN as shown below. This is the new targets which has logged in . Select "Edit " from bottom and then provide information about "host name" "IP address" . IP address is of  XenServer  management IP . Make sure you choose initiator type as "clarion open " and Fail Over mode as "ALUA 4". ALUA is the latest fail over mode as per EMC and other storage vendors.image

With this host will be connected to to EMC storage. In the next series , I will explain process of creating lun and attaching it to the storage group.

No comments: