Skip to main content
Sign Out

Welcome to Dell

My Account
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.
Sign In Create an Account Dell Financial Services Premier Sign In Partner Program Sign In
Contact Us

Your Dell.com Carts

Unisphere and Unisphere Central 2020 R1 Administrator's Guide

PDF

Using Unisphere Central Certificates With VASA Provider

When you run the Register VASA Provider wizard, the URL of the VASA provider is automatically generated. This URL identifies the host on which the Data Collector is installed. The host is identified as either an IP address or fully qualified domain name (FQDN). Depending on how you installed or upgraded Unisphere Central or if you changed the host for the Data Collector, you might need to take additional steps to update the certificates.

New Installation of Dell Unisphere Central

If Unisphere Central is registered with a name lookup service such as DNS server or Active Directory server, Unisphere Central certificates are generated based on its FQDN. Any IP address changes do not affect certificates. If you change the FQDN, Unisphere Central must be manually restarted if it is a Windows-based installation. It is automatically rebooted for the Virtual Appliance installation. If you were using the VASA provider before the IP changes, you must unregister and then register VASA Provider manually.

Upgrade of Dell Unisphere Central

In Dell Unisphere Central, certificates are based on IP addresses. After an upgrade to Dell Unisphere Central, the existing certificates remain unchanged. If you need to modify the IP address of the host, the certificates need to be updated as described in the following table:

IP Change Action Required
IP changes on Windows-based Unisphere Central If Unisphere Central is not registered with a name lookup service such as DNS server or Active Directory, then Unisphere Central and VASA certificates are based on the IP address of the Windows host. Before the IP address of the Windows host is changed, you must first unregister the VASA Provider. Then modify the IP address of the Windows host. Then manually restart Unisphere Central to regenerate certificates based on the new IP address. After the restart, you must re-register the VASA Provider.
IP changes on the Virtual Appliance On a Dell Unisphere Central Virtual Appliance, network changes such as IP address happen through the Unisphere Central and hence Unisphere Central is aware of the changes. You must first unregister and the VASA Provider, then make the changes to the IP address. After the changes are done, Unisphere Central restarts itself to regenerate certificates based on the new IP address. You then must re-register the VASA Provider.
Switch from an IP Address to an FQDN on Dell Unisphere Central To switch the certificates to use the FQDN instead of the IP address of the host, you must first unregister and the VASA Provider. Then register the Unisphere Central host with a name lookup service. Then configure the networking properties on the host. Then follow the Dell Unisphere Central procedure for deleting existing certificates and restart the Unisphere Central. After the restart, re-register the VASA Provider.
FQDN changes on Windows or Virtual Appliance If certificates are already using FQDN and you want to change the FQDN, unregister VASA Provider first. Then make changes to the name lookup service or Unisphere Central host (or both) for the new FQDN. Then follow the old procedure for deleting certificates and restart Storage Manager. Re-register VASA Provider after Unisphere Central is running.
NOTE Failure to unregister the VASA Provider before making changes in name lookup service results in initialization errors on vCenter for certain services and causes VASA registration to fail.
Switching from FQDN to IP Address on DellUnisphere Central If you want to stop using FQDN and go back to using IP addresses, unregister the VASA Provider first. Then make changes to the name lookup service or Unisphere Central host (or both) to remove FQDN configuration. Restart Unisphere Central for the changes to take effect and register VASA Provider again.
NOTE Failure to unregister the VASA Provider before making changes in name lookup service results in initialization errors on vCenter for certain services and causes VASA registration to fail.

Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\