Mertol Ozyoney
2008-Apr-07 17:25 UTC
[zfs-discuss] iSCSI targets mapped to a VMWare ESX server
Hi All ;
We are running latest Solaris 10 a X4500 Thumper. We defined a test iSCSI
Lun. Out put below
Target: AkhanTemp/VM
iSCSI Name: iqn.1986-03.com.sun:02:72406bf8-2f5f-635a-f64c-cb664935f3d1
Alias: AkhanTemp/VM
Connections: 0
ACL list:
TPGT list:
LUN information:
LUN: 0
GUID: 010000144fa7093000002a0047fa50e6
VID: SUN
PID: SOLARIS
Type: disk
Size: 100G
Backing store: /dev/zvol/rdsk/AkhanTemp/VM
Status: online
We tried to access the LUN from a windows laptop, and it worked without any
problems. However VMWare ESX 3,2 Server is unable to access the LUN''s.
We
checked that the virtual interface can ping X4500.
Sometimes it sees the Lun , but 200+ Lun''s with the same proporties are
listed and we cant add them as storage. Then after a rescan they vanish.
Any help appraciated
Mertol
<http://www.sun.com/> http://www.sun.com/emrkt/sigs/6g_top.gif
Mertol Ozyoney
Storage Practice - Sales Manager
Sun Microsystems, TR
Istanbul TR
Phone +902123352200
Mobile +905339310752
Fax +902123352222
Email <mailto:Ayca.Yalcin at Sun.COM> mertol.ozyoney at Sun.COM
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20080407/b1df32b7/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.gif
Type: image/gif
Size: 1257 bytes
Desc: not available
URL:
<http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20080407/b1df32b7/attachment.gif>
Jim Dunham
2008-Apr-07 17:41 UTC
[zfs-discuss] iSCSI targets mapped to a VMWare ESX server
Mertol Ozyoney wrote:> Hi All ;There are a set of issues being looked at that prevent the VMWare ESX server from working with the Solaris iSCSI Target. http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6597310 At this time there is no target date when this issues will be resolved. Jim> > We are running latest Solaris 10 a X4500 Thumper. We defined a test > iSCSI Lun. Out put below > > Target: AkhanTemp/VM > iSCSI Name: iqn.1986-03.com.sun:02:72406bf8-2f5f-635a-f64c- > cb664935f3d1 > Alias: AkhanTemp/VM > Connections: 0 > ACL list: > TPGT list: > LUN information: > LUN: 0 > GUID: 010000144fa7093000002a0047fa50e6 > VID: SUN > PID: SOLARIS > Type: disk > Size: 100G > Backing store: /dev/zvol/rdsk/AkhanTemp/VM > Status: online > > We tried to access the LUN from a windows laptop, and it worked > without any problems. However VMWare ESX 3,2 Server is unable to > access the LUN?s. We checked that the virtual interface can ping > X4500. > Sometimes it sees the Lun , but 200+ Lun?s with the same proporties > are listed and we cant add them as storage. Then after a rescan they > vanish. > > Any help appraciated > > > Mertol > > <image001.gif> > Mertol Ozyoney > Storage Practice - Sales Manager > > Sun Microsystems, TR > Istanbul TR > Phone +902123352200 > Mobile +905339310752 > Fax +902123352222 > Email mertol.ozyoney at Sun.COM > > > _______________________________________________ > zfs-discuss mailing list > zfs-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20080407/b690e705/attachment.html>
Mertol Ozyoney
2008-Apr-07 18:54 UTC
[zfs-discuss] iSCSI targets mapped to a VMWare ESX server
Thanks James ;
The problem is nearly identical with mine.
When we had 2 LUN''s vmware tried to multipath over them . I think this
is a
bug inside VMWare as it thinks that two LUN 0 are same. I think I can fool
it setting up targets with different LUN numbers.
After I figured out this, I switched to a single LUN , cleaned a few things
and reinitialized . For some reason VM found 200+ LUN''s again but all
with
single active path.
I started formatting the first one. (100 GB) It''s been going one for
the
last 20 minutes. I hope it will ever finish. Zpool iostat shows small
activity over disk.
I think that vmware 3,02 have a severe bug. I will try to open a case at
vmware . But there seems to be a lot of people on the web who had no
problems with the exact same setup.
Mertol
<http://www.sun.com/> http://www.sun.com/emrkt/sigs/6g_top.gif
Mertol Ozyoney
Storage Practice - Sales Manager
Sun Microsystems, TR
Istanbul TR
Phone +902123352200
Mobile +905339310752
Fax +902123352222
Email mertol.ozyoney at Sun.COM <mailto:Ayca.Yalcin at Sun.COM>
From: James.Dunham at Sun.COM [mailto:James.Dunham at Sun.COM]
Sent: 07 Nisan 2008 Pazartesi 20:42
To: Mertol.Ozyoney at Sun.COM
Cc: zfs-discuss at opensolaris.org; erdal.koroglu at servus.com.tr
Subject: Re: [zfs-discuss] iSCSI targets mapped to a VMWare ESX server
Mertol Ozyoney wrote:
Hi All ;
There are a set of issues being looked at that prevent the VMWare ESX server
from working with the Solaris iSCSI Target.
http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6597310
At this time there is no target date when this issues will be resolved.
Jim
We are running latest Solaris 10 a X4500 Thumper. We defined a test iSCSI
Lun. Out put below
Target: AkhanTemp/VM
iSCSI Name: iqn.1986-03.com.sun:02:72406bf8-2f5f-635a-f64c-cb664935f3d1
Alias: AkhanTemp/VM
Connections: 0
ACL list:
TPGT list:
LUN information:
LUN: 0
GUID: 010000144fa7093000002a0047fa50e6
VID: SUN
PID: SOLARIS
Type: disk
Size: 100G
Backing store: /dev/zvol/rdsk/AkhanTemp/VM
Status: online
We tried to access the LUN from a windows laptop, and it worked without any
problems. However VMWare ESX 3,2 Server is unable to access the LUN''s.
We
checked that the virtual interface can ping X4500.
Sometimes it sees the Lun , but 200+ Lun''s with the same proporties are
listed and we cant add them as storage. Then after a rescan they vanish.
Any help appraciated
Mertol
<http://www.sun.com/> <image001.gif>
Mertol Ozyoney
Storage Practice - Sales Manager
Sun Microsystems, TR
Istanbul TR
Phone +902123352200
Mobile +905339310752
Fax +902123352222
Email mertol.ozyoney at Sun.COM <mailto:Ayca.Yalcin at Sun.COM>
_______________________________________________
zfs-discuss mailing list
zfs-discuss at opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20080407/fa8db2b8/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.gif
Type: image/gif
Size: 1257 bytes
Desc: not available
URL:
<http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20080407/fa8db2b8/attachment.gif>
Some time ago I experienced the same issue. Only 1 target could be connected from an esx host. Others were shown as alternative paths to that target. If I''m reminding correctly I thought I read on a forum it has something to do with the disks serial number. Normally every single (i)scsi disk is represented with a serial number, but when we create zvols on zfs and share them via iscsi, there is no unique serial number. Somebody explained the ciscso unique initiator (built-in to esx) is using this serial to differentiate between multiple targets. But since the serial is empty esx thinks all those targets are the same disk. If it''s true I don''t understand why they use this serial, since the iqn is a unique name for a target. Or shouldn''t (open)solaris set a unique serial number for every zvol? K This message posted from opensolaris.org
Henk Langeveld
2008-Apr-10 21:17 UTC
[zfs-discuss] iSCSI targets mapped to a VMWare ESX server
kristof wrote:> Some time ago I experienced the same issue. > > Only 1 target could be connected from an esx host. Others were shown as alternative paths to that target. > > If I''m reminding correctly I thought I read on a forum it has something to do with the disks serial number.Steffen Plotner summarised this well in http://communities.vmware.com/thread/60452 An optional VPD is exposed, and esx ignores the ''blank'' serial/no, intended to tell the host that no s/n exists. >>VMware Communities > VMTN > Archives > >> VMware Infrastructure Archives > >> ESX Server 3.x Configuration Archives > Discussions >> Nov 1, 2006>> Why does vmware think that 2 different LUNs are actually the same >> disk? Simple, they both have the same serial number. I have >> researched the problem and found that the SCSI specification >> exposes VPD (vital product data). One of those VPD is 0x83 which is >> the unit identification which IET implements and the specification >> requires it. The other page is 0x80 which is the disk serial number >> page, the specification says that this is optional, and IET sends >> back 4 0x20 codes which are spaces, the spec clearly says that''s >> the way to tell the initiator that there is no serial number.
thanks for pointing me to that article. I see there is a solution (patch) for ietd. Is there any solution for zfs zvols ? Is Sun plannig any action to solve this issue? K This message posted from opensolaris.org
Mertol Ozyoney
2008-Apr-11 09:43 UTC
[zfs-discuss] iSCSI targets mapped to a VMWare ESX server
That''s excellent news for me. I think Sun should think about a solution as everything today is somewhat linked to VMWare. I am no expert about Linux and VMWare, can someone tell me step by step (assuming that I do not know anything which is kinda true) How to apply the path mentioned at http://communities.vmware.com/thread/60452 ? Best regards Mertol Mertol Ozyoney Storage Practice - Sales Manager Sun Microsystems, TR Istanbul TR Phone +902123352200 Mobile +905339310752 Fax +902123352222 Email mertol.ozyoney at Sun.COM -----Original Message----- From: zfs-discuss-bounces at opensolaris.org [mailto:zfs-discuss-bounces at opensolaris.org] On Behalf Of kristof Sent: 11 Nisan 2008 Cuma 01:19 To: zfs-discuss at opensolaris.org Subject: Re: [zfs-discuss] iSCSI targets mapped to a VMWare ESX server thanks for pointing me to that article. I see there is a solution (patch) for ietd. Is there any solution for zfs zvols ? Is Sun plannig any action to solve this issue? K This message posted from opensolaris.org _______________________________________________ zfs-discuss mailing list zfs-discuss at opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
A colleague told me IET is not longer an ongoing project, so it''s obsoleted. There''s another new linux iscsi target: ISCSI-SCST is a forked (with all respects) version of IET with updates to work over SCST as well as with many improvements and bugfixes. see http://scst.sourceforge.net/ This message posted from opensolaris.org
Brandon High
2008-Apr-14 22:37 UTC
[zfs-discuss] iSCSI targets mapped to a VMWare ESX server
On Fri, Apr 11, 2008 at 12:36 PM, kristof <kristof at aserver.com> wrote:> A colleague told me IET is not longer an ongoing project, so it''s obsoleted.The latest release in Sourceforge was Mar 17, 2008. I think IET is still alive.> see http://scst.sourceforge.net/iSCSI-SCST is a fork of the IET code to work with SCST. The SCST project *claims* their code is better. I haven''t used either, and it may very well be a better solution, but I''d recommend testing both to see. -B -- Brandon High bhigh at freaks.com "The good is the enemy of the best." - Nietzsche