Unity

Question

Hi, Is there a way to register more than one VASA provider under Access > VMware > vCenter? If I remove a vCenter thats VASA registered is this disruptive and cause an outage? Will this remove all of the associated ESXi Hosts that have access to the datastores? If I click on Remove vCenter, it prompts 'Deleting this object will also delete any associated objects'. I don't think I can register more than one VASA provider so I would like to remove the vCenter and add it back without registering as a VASA provider so all three vCenters are not VASA registered. Also, I noticed if you manually add the ESXi Hosts and later you try to add vCenter it doesn't allow you to complete the task. Seems like you have to remove all of the ESXi Hosts first then add the vCenter and that will detect all of the ESXi Hosts. By removing the ESXi Hosts would there be an outage and no access to the datastores? Seems like the Access > VMware is just for monitoring, but just want to confirm. Thanks

DELL-Sam L · Answer

6248304 Hello macyero,

Here is the link to Unisphere and Unisphere Central 2018 R1 Administrator’s Guide, & if you look on page 61 it list VASA Provider Restrictions. If you look on page 62 it explains how to unregister a VASA Provider. https://dell.to/2GhXa8y

macyero · Answer

Thank you Sam for the information. The document includes procedure for Unisphere Central which is a separate appliance from the the array's Unisphere. The steps go through Unisphere Central, but not through Unisphere from the array.

The instructions are as follows for Unisphere Central:

Unregister a VASA provider to remove it from vCenter.
Prerequisite
CAUTION: The VASA provider must be unregistered before you to initiate any of these tasks:
• Any action related to uninstallation, migration, upgrade, reinstalling of Unisphere Central on same host with same IP address

• Uninstalling Unisphere Central with the intention of reinstalling on another host
• Changing the Unisphere Central FQDN
• Changing the Unisphere Central IP address

- Unregistering VASA will affects control plane operations on virtual volume VMs and datastores which are in use. It does not affect data transfer between an ESXi host and the respective SAN storage.

- Unregistering the VASA provider results in powered-off VVol VMs being shown as inaccessible and datastores as inactive.

- To avoid prolonged control plane down time, minimize the period where the VASA provider remains unregistered. After re-registration, there could be a delay for powered-off VMs and datastores to recover from being inaccessible and inactive respectively.

I am on code 5.0.x. You would just go to ACCESS > VMware > vCenter and from there click on the trash can to delete the vCenter. Based on the document it seems to contradict whether this will be disruptive or not. In my opinion it shouldn't be disruptive, but since its production I want to make sure before proceeding.

Has anyone done this before in Unity or have a lab environment. I had asked a few EMC folks prior, but I couldn't get a confirmation. No one knows or had to do this.

Thanks,

Was this post helpful?