To manually set the LUN number for virtual volumes you are adding, or to view the LUN numbers of the virtual volumes already in the storage view, select the Manually set LUNs for added Virtual Volumes check box. You can select this check box before or after selecting the virtual volumes to add.
In regards to the "Manually set LUNs for added Virtual Volumes" option, our VPLEX is at v5.0.1 and if we try to use this option, the LUN # which is specified is passed to the background command as "undefined" so we can't use this option. However, the error dialog box shows the actual VPLEXCLI command which is used and so we do it like this, from VPLEXCLI instead:
We present both native VNX LUNs and VPLEX virtual volumes to the same ESXi clusters, so controlling the HLU (Host LUN ID #) is vital for us since we have room for error by accidentally presenting 2 of the same HLU to the hosts (nightmare! in VMware ESXi).
Jason_Zhou
1.2K 消息
0
2012年12月16日 21:00
我先把帖子移动至 存储系统 版块。
Anonymous
5 Practitioner
5 Practitioner
•
274.2K 消息
0
2012年12月17日 02:00
如果用GUI的话，在把virtual volume加到storage view给主机时，应该可以手动配置LUN ID的吧。
如果LUN ID真的变了，那么主机是不是需要重新配置啊？
JeremyTBradshaw
6 消息
0
2013年5月4日 07:00
Hello,
In regards to the "Manually set LUNs for added Virtual Volumes" option, our VPLEX is at v5.0.1 and if we try to use this option, the LUN # which is specified is passed to the background command as "undefined" so we can't use this option. However, the error dialog box shows the actual VPLEXCLI command which is used and so we do it like this, from VPLEXCLI instead:
export storage-view addvirtualvolume --view /clusters/cluster-1/exports/storage-views/%storage view name% --virtual-volumes (%HLU#%,%virtual volume name%) --force
e.g.
export storage-view addvirtualvolume --view /clusters/cluster-1/exports/storage-views/UCS_STJ_Production --virtual-volumes (5,device_VNX0038_LUN2002_1_vol) --force
We present both native VNX LUNs and VPLEX virtual volumes to the same ESXi clusters, so controlling the HLU (Host LUN ID #) is vital for us since we have room for error by accidentally presenting 2 of the same HLU to the hosts (nightmare! in VMware ESXi).