LUN0 message in iSCSI v6 Beta

[budy]

From my own experience there're several iSCSI initiators that will not see any LUN of a target if LUN0 of that particular target is present.

Oops… of course thats should read "isn't present".

Btw, it would be really nice if one could edit one's post afterwards…

Cheers,
Budy

[beng]

G'day Budy,
Thanks for the confirmation. We have seen the same thing here, VMware likes different LUNs, while Windows didn't care.
Took us hours to work it out when first trying to get iSCSI working, ie created a second LUN and could get the MS Initiator to see it (from within a VM too!) while ESX refused to play ball until we incremented the LUN.

Our V6Beta testing so far has shown that our previous methods (Not using 0 or reusing LUNS) works, so we will stick with that for the moment. although it may become an issue with Multipathing, Replication or Bonding, as we have not tried any of these yet.

RE Editing post, yeah I agree, it's a real pain when you write something at 1AM, and then read the mistakes at 9AM

Rgds Ben

[symm]

Hey beng

here is a link about not using tha same lun numbers globaly with vmware
http://communities.vmware.com/message/701181#701181