how to change the access of luns from single host to multi host on VC?

[stephanie]

Hi all,

We have added new LUNs to an ESX server and VCB proxy server and now have two sets of LUN connection (new and current), we are configuring ESX servers to connect to new LUNs.

We found the new LUNs in Virtual center access is Single Host, and original LUNs is Multi Host. How can we change the Access for new LUNs?

Thanks.

ESX server 3.0.0, VC 2.0.0

[MR-T · Accepted solution]

Double check the zoneing of these LUNs.

Also try performing a rescan on the ESX server which isn't currently seeing the LUNS.

[stephanie]

sorry, I would like to make a correction, the Access status was found in the New Virtual Machine Wizard, when 'Choose a Datastore for the Virtual Machine'.

The access of the datastores is either 'Single host' or 'Multiple Hosts'.

The question is how to change the access of 'Single host' to 'Multiple Hosts'?

[aldin]

stephani,

If you have 2 esx that have access to one lun and only one of those esx server is added to VC, when you start New Virtual Machine Wizard, in Choose Datastore you will see Single Host access. If you add both of esx servers in VC you will see Multiple Host access, if your zoning is correct.

When you connect with VIC directly to esx you will always see Single Host access.

[MR-T]

This 'multiple hosts' message is only available if the correct zoning has been configured and the LUN is visable from more than 1 ESX host.

[stephanie]

thanks to all for your responses.

Will this issue be related to VMFS datastores are not created on the new luns? We only found 'Single host' for the newly added LUNs.

vmhba1:1:x are new LUNs, and vmhba1:0:x are current (old) LUNs.

# esxcfg-vmhbadevs -qm

Skipping dir: /vmfs/volumes/47c7835f-56ca8792-72c8-00187174c662. Cannot open volume: /vmfs/volumes/47c7835f-56ca8792-72c8-00187174c662

Skipping dir: /vmfs/volumes/47c7831e-2fee43fa-8a83-00187174c662. Cannot open volume: /vmfs/volumes/47c7831e-2fee43fa-8a83-00187174c662

Skipping dir: /vmfs/volumes/47c7839d-603cceb8-4ed9-00187174c662. Cannot open volume: /vmfs/volumes/47c7839d-603cceb8-4ed9-00187174c662

Skipping dir: /vmfs/volumes/47c783e1-ff6e7908-5c3d-00187174c662. Cannot open volume: /vmfs/volumes/47c783e1-ff6e7908-5c3d-00187174c662

Skipping dir: /vmfs/volumes/47c782eb-a776cd10-ebe5-00187174c662. Cannot open volume: /vmfs/volumes/47c782eb-a776cd10-ebe5-00187174c662

Skipping dir: /vmfs/volumes/47c78419-372f4700-09b7-00187174c662. Cannot open volume: /vmfs/volumes/47c78419-372f4700-09b7-00187174c662

vmhba1:0:1:1 /dev/sda1 45226546-c6e99d90-d6ca-00187174c662

vmhba1:0:4:1 /dev/sdd1 45226578-1db90716-19fd-00187174c662

vmhba0:0:0:3 /dev/cciss/c0d0p3 451d383a-85042584-d672-00187174c662

vmhba1:0:2:1 /dev/sdb1 4522659c-d19f9924-6eb2-00187174c662

vmhba1:0:3:1 /dev/sdc1 45226562-04522b8e-fe4d-00187174c662

vmhba1:0:5:1 /dev/sde1 452263f9-0daeefca-cca5-00187174c66e

# esxcfg-vmhbadevs -q

vmhba0:0:0 /dev/cciss/c0d0

vmhba1:0:1 /dev/sda

vmhba1:0:2 /dev/sdb

vmhba1:0:3 /dev/sdc

vmhba1:0:4 /dev/sdd

vmhba1:0:5 /dev/sde

vmhba1:0:6 /dev/sdf

vmhba1:1:1 /dev/sdg

vmhba1:1:2 /dev/sdh

vmhba1:1:3 /dev/sdi

vmhba1:1:4 /dev/sdj

vmhba1:1:5 /dev/sdk

vmhba1:1:6 /dev/sdl

Thanks.