vCenter

 View Only
  • 1.  Linux LUN not being exposed in vCenter

    Posted Sep 07, 2009 05:05 AM

    Am attempting to add an iSCSI LUN.

    It's a Linux box presenting itself as a target. I have already several of these used, although this particular one doesn't want to be seen by ESX.

    1. I add the box through Dynamic Discovery, and re-scan, the path comes up

    2. I go over to devices, and the LUN isn't being offered.

    3. Thought it might be an issue with it, so I checked if Windows will see it by means of an iSCSI initiator - which it does

    What can be done to track down the issue?

    I've checked on ESX the vmkiscsid.log and it contains:

    2009-09-07-14:08:38: iscsid: Login Success: iqn.2009-08.com.ibm._server_name_.store,default,_ip_address_,3260,1, 0x0

    2009-09-07-14:08:39: iscsid: connection1:0 is operational now

    Any ideas? Suggestions?

    Thank you.



  • 2.  RE: Linux LUN not being exposed in vCenter

    Posted Sep 08, 2009 02:03 AM

    After you add the path to the ESX host, what happens if you go to the Storage tab and click "Add Storage"? Are you able to create a VMFS partition from that new space?



  • 3.  RE: Linux LUN not being exposed in vCenter

    Posted Sep 08, 2009 09:23 AM

    No, unfortunately the "Add Storage" dialog, when I select Disk/Lun - comes up empty.



  • 4.  RE: Linux LUN not being exposed in vCenter

    Posted Sep 14, 2009 02:34 AM

    any more hints?



  • 5.  RE: Linux LUN not being exposed in vCenter

    Posted Sep 25, 2009 07:54 AM

    Solved.

    For those that someday will come across this problem.

    The fault was my own. If you see one the image I uploaded with paths to the LUN:

    Note that I have both LUN's exposed as LUN 0. This is because I merely copied the ietd.conf between the iSCSI targets, and didn't change the LUN id.

    Lesson learnt.