Please enable javascript, or click here to visit my ecommerce web site powered by Shopify.

Community Forum > Can I set host LUN ID for each volume? [SOLVED v3.7.4]

I have briefly tested OS NEXUS and I figured out the OS NEXUS does not support to set host LUN ID for each volume.

Are there a way to set host LUN ID for each LUN?

Most of storages support to set host side LUN ID. (not storage side LUN ID)

September 23, 2013 | Registered CommenterDonghwan KAng

Hi Donghwan,
That's correct, QuantaStor automatically uses LUN 0 for all iSCSI targets. The system generates a unique IQN for each target which is then used to expose the associated storage volume at LUN 0. With FibreChannel it works a little differently. With FC we generate a "control device" similar to what you would see on a HP or EMC storage system and expose that at LUN 0 for each FC target port. Having an always present LUN 0 is important for some operating system support as skipping it can cause some devices to not be discovered. For each storage volume that is allocated an unused LUN number is selected an used to export the volume via FC. So with iSCSI the LUN is always 0, with FC the LUN number is auto-selected.
We've only had a couple of complaints about this and they were from VMware users that were using the LUN number to help them correlate from the host device back to the storage volume in the appliance. Is that the challenge you're having with our auto LUN selection? I was thinking that perhaps we should have a CLI script or utility that would make the correlation easy. QuantaStor storage volumes have the first 16 hex digits of their UUID stored in SCSI VDP 0x83 so that the device can be easily correlated back. A script could use a utility like sg_inq or scsi_id to show that information in a easy to read format.
Please share more info about your needs,

September 23, 2013 | Unregistered CommenterSteve

We need this information for exactly the example given. We need to be able to associate LUNS assigned to VMWare ESX servers in some way.
Please elaborate on how we might use sg tools to do this. Some examples would be great.


November 5, 2013 | Unregistered CommenterJim Medlin

Hi Jim,
Thanks for the feedback. We looked into this today and just added a new feature to solve this problem. You can now see your VMware EUI identifier for your storage volumes in the QuantaStor user interface so it's easy to correlate to VMware. We've just posted a screenshot of it here.

The VMware EUI is also shown in the properties on the left and note that the VMware EUI column doesn't show by default. You'll need to right-click on one of the columns to add it as it is initially hidden. This new feature will be in the 3.7.4 maintenance update and we're going to publish that soon.

November 5, 2013 | Registered CommenterSteve

Great Steve,
That just what we needed.

November 6, 2013 | Unregistered CommenterJim Medlin

Hi Steve,
We use CLI and we really need this output (VMWare EUI). When you look at one to three volumes the GUI is OK but when you need to correlate tens of them is really a no go. Could you share more details on how we can match those 16 hex digits with a standard block device which we can then sg_inq?

February 22, 2016 | Registered CommenterDACBARBOS Services

Hi Paul, we fixed this in the upcoming 3.17 release so that there is a formal 'eui' field on every Storage Volume. May be in 3.16 too, but I know we fixed it.

February 22, 2016 | Registered CommenterSteve

That's really great news Steve. Thanks a lot for taking the time to reply. We're all looking forward for it.

February 23, 2016 | Registered CommenterDACBARBOS Services

Here's some example output, the EUI field is the last one:

root@ceph-a-305-1-9:~# qs volume-get winrbd8

[Storage Volume]
ID: 814023f5-e58e-be40-4715-ab9bb9510689
Name: winrbd8
State: Normal
Type: 3
Created Time Stamp: Wed Mar 16 21:43:09 2016
Created By User ID: 437bb0da-549e-6619-ea0e-a91e05e6befb
Modified Time Stamp: Wed Mar 16 21:43:09 2016
Modified By User ID: 437bb0da-549e-6619-ea0e-a91e05e6befb
Is Remote: true
Object ID: 814023f5-e58e-be40-4715-ab9bb9510689
Object Type: volume
Owner ID: 437bb0da-549e-6619-ea0e-a91e05e6befb
Owner Type: 23
Access Level: 2
Reserved: 0
Storage Pool ID: c8361354-165c-404e-4cf9-71da612b2207
Remote Replica Flags: 0
Size: 1.0TiB
Is Snapshot: false
Lazy Clone Snapshot Path:
Snapshot Group ID:
Snapshot Parent:
Mount Path: /dev/rbd/qs-c8361354-165c-404e-4cf9-71da612b2207/814023f5-e58e-be40-4715-ab9bb9510689
Origination Pool ID: c8361354-165c-404e-4cf9-71da612b2207
Origination ID: 814023f5-e58e-be40-4715-ab9bb9510689
Origination Name: winrbd8
Origination Snapshot Parent:
Is Active Checkpoint: false
Created By Schedule:
Compression Ratio:
Compression Type:
Retention Tags: 0
Sync Policy: standard
Copies: 0
Access Mode: readwrite
Device Path:
Is Cloud Backup: false
Is Thin: true
Use Guid IQN: false
LUN: 8
Space Utilized: 0
Cloud Container ID:
Target: 25
Relative Target ID: 8
Volume Type: 9
CHAP Policy: 0
Block Size Kb: 0
CHAP Username:
Storage Link ID: OSNEXUS__QUANTASTOR__c8361354__814023f5
Device Descriptor: 814023f5e58ebe40c8361354
Enable Write Cache: false
Access Time Stamp: 1970-01-01T00:00:00Z
Qos Read IOPS: 0
Qos Write IOPS: 0
Qos Read Bandwidth: 0
Qos Write Bandwidth: 0
Qos Policy ID:
Space Reserved: 0
Eui: eui.3831343032336635

QuantaStor v4 shipped today in ISO form and we'll be updating the package servers so that 3.x systems can upgrade starting on Monday.

March 24, 2016 | Registered CommenterSteve