VMware Communities: ESX 3.5 to 4.0 implications for using ...

VMware

Up to Discussions in vSphere SDK for Java

Sample Code
Tech Exchange

vSphere SDK for Java:

This Question is Possibly Answered

1 "correct" answer available (10 pts) 1 "helpful" answer available (6 pts)

1 Replies Last post: Nov 2, 2009 6:21 PM by AjayL

ESX 3.5 to 4.0 implications for using scsiLun.canonicalName() posted: Oct 20, 2009 12:03 AM

vmdeveloper

1 posts since
Nov 13, 2008

Hello,

Question

How would you recommend finding matching an hba, target, and lun to the corresponding scsiLun object in ESX 4.0?

Current Situation

I have some current code that has been working with ESX 3.5 when trying to find a datastore on a given LUN. The code breaks apart each scsiLun instance's canonical name for a comparision such as:

vmhba32:17:6 and vmhba1:0:0

When I retreive the canonical name in my ESX 4.0 environment I get a different result for the canonical name, sometimes a vmhba32:C0:T17:L6 for local SCSI devices, but for iSCSI attached storage I get something that is essentially the UUID from the scsiLun object.

Thank you in advance for your help.

Tags: vi_sdk_for_java_tech_preview, api, esx_4, java, scsilun, iscsi

Re: ESX 3.5 to 4.0 implications for using scsiLun.canonicalName()

1. Nov 2, 2009 6:23 PM

in response to: vmdeveloper

AjayL

16 posts since
Mar 13, 2006

Having same issue and also looking for an answer. in vSphere client there seems to be new column runtimeName, which provides needed information for ESX/i 4..0. However there does not seem to be way to get this runtimeName via VI SDK.

And this issue is there for SAN attached LUNs as well, in addition to iSCSI.