The use-case is not very clear to me ; did the customer add other ESX hosts to the Cluster in between ?

If yes, why would you like a host not to see the same volumes as all hosts in the cluster ?

if not, why not removing the volume to the ExportGroup "SHARED", which only contains the single ESX ?

An option is to remove the ESX host from the cluster in the vCenter, and (after forcing a vCenter discovery in VIPR or wait 24h by default) this will trigger an Event in VIPR 3.5+, that you can approve/decline. If approved, your ESX host will lose access to the volume(s) exported to the Cluster.

Hi Julien, unfortunally, the Customer has discovered the ESX directly, not through the vCenter, and he has created and Export Group for the whole Cluster, so I think that we would not have the trigger if he removes the ESX from Cluster, correct?

He has provisioned some Volumes as SHARED as Storage Type to the whole Cluster (10 hosts), but now he would like to remove one of these 10 from the Cluster....

What would you suggest to do?

Thanks a lot!
Andrea

so there is no vCenter discovery at all ?

having a "Shared" export means he manually built a cluster in VIPR, can you confirm ?

Then he can directly remove the host from the cluster in VIPR and the host will be removed the shared volumes automatically.

Yes, no vCenter discovered at all; he has discovered the ESX directly via IP and he has created an Export Group named as the Cluster, provisioning Volumes as SHARED when he select the Storage Type.

What do you suggest in this situation?

OK. Then I suggest he can directly remove the host from the cluster in VIPR and the host will be removed the shared volumes automatically

if your customer is running VIPR 3.5 (as you said firstly), there is no more "Auto-Export" flags on Clusters in VIPR, but Events. I think Events does not "work" without vCenter discovery !

It could be a way....but, because of the auto-export enabled on the Cluster, if also the vCenter is discovered, could it be possible to remove the ESX host from the Cluster on the vCenter, and then rediscover the vCenter? Could be the ESX removed also in ViPR side, in your opinion?

I do not remember if the Customer has discovered the vCenter also...I'm only sure about the fact that he has discovered the ESX directly via IP..

Ah ok, I thought that the flag is available also on 3.5, because the Customer started with 2.4 and then the env was upgraded to 3.0 and after to 3.5....I have to verify that the Customer has discovered vCenter also.

If vCenter is not discovered but only ESX are, I can try to remove, in ViPR, the single ESX from the Export Group where SHARED Volumes are exported?

The Customer said that vCenter are discovered into ViPR....I'm asking him if auto-export flag is enabled, on Cluster...if so, the procedure could be:

. Remove ESX host from Cluster, on vCenter

. Rediscover vCenter in ViPR

In this case, the ESX host will be automatically removed from the Export Group?

Thanks!

Andrea

Again, there is no more "auto-export" in VIPR 3.5.

You have the right procedure ; this will trigger an Event that you will have to accept (or decline).