I have been busy playing with Sun 7110 Virtual Simulator and have hit what is probably a complete newbie problem.
I have Cifs working fine so I decided to try connecting to it via iSCSI. Please note that as this was just a play, I was using the normal TCP/IP infrastructure which meant that the two devices were not on the same switch.
I have setup the 7110 to take iSCSI on a project and I have setup an initiator. My Initiator was planned to be one of our test Windows Server 2008 servers so I setup iSCSI initiator. This gave me the IQN for the initiator.
The problems come with the next steps. I set up the IP address of the 7110 as a Target Portal - I presume this is ok as if I put in the wrong IP address it tells me there is a connection problem. However, if I try to refresh the Target, it gets nothing.
I am not sure what to do next and how to debug - could anyone give me some starting pointers? I am not using CHAP names or secrets anywhere.
Many thanks for any help anyone can point at.
Last edited by ArchersIT; 14th May 2009 at 04:24 PM.
Reason: typing errors
I've just gone through this on our 7410 and an XP Pro box, hope it helps:
Click the + to add a LUN
Use the default project, unless you’ve configured another project with specific settings
Give it a name
Volume size – as much as you need for testing
Leave sparse un-ticked unless you know you need it
8k block size is fine
Mouseover the new LUN and hit the pencil (edit) icon on the right
Unless you’ve set up a project for something specific, untick ‘Inherit from project’
Click the + next to Initiator Access Control
Enter an Initiator Alias (name of the Windows server would make sense)
Enter the IQN from the Windows server (found via the iSCSI Initiator)
Back on the main protocols screen, untick 'Allow any Initiator Access' and tick 'Allow' for your Windows server entry
Okay - on the 7110 simulator the settings are slightly different, and when I look at the protocols for the new filesystem (lun) it does not list iSCSI, this is only listed at the project level - I wonder if I am doing something wrong here - I will have a read of the helpfile.
Has anyone got this working on ESXi then? or do you have to use Server/Player.
I tried a while back with an older version and didn't have any luck. Something about the way it was configured and the virtual machine image format it uses. I found a tool to convert between VM disk file formats but it never successfully converted them to something I could use in ESXi.
If I'm following you right then you should might want to make a pool of your Xen boxes then all you need to do is create one LUN on the S7000 and add it to the pool. All the Xen hosts can then see it as 'shared' storage and boot VMs from it. You'll need to know the initiators of all the Xen hosts if you're using initiator security so you can add and allow them on the S7000.
Oh ok I was trying to make a LUN for each physical box. I've now added them to the same pool so they should both be able to access it right. I remember reading that devices couldn't share iSCSI LUNs but the Xen pool must sort that then right?
Someone please confirm this or correct me if I'm wrong, but generally an iSCSI LUN can only be accessed by one device unless it has a filesystem that's designed to handle multiple access. So while NTFS wouldn't work, the Xen and VMware filesystems (I suppose they're not technically filesystems in the typical sense, but you know what I mean) are designed to handle multiple hosts accessing files on the same LUN. Can someone just confirm that makes sense?
Assuming you're using initiator security groups then your SAN will need to be told to allow all your Xen hosts iSCSI initiators to be able to access that LUN. After that (going by memory here as I've been playing with ESX more than Xen recently) you just add the LUN to the Xen pool, set it as the default storage, then put your virtual machines it in. If you have failover enabled then the pool will detect when one host goes down and automatically boot the VMs from the SAN on a different host.