Jump to main content

# Understanding serviceability

Unisphere provides a serviceability application that supports the deployment of update packages for PowerMax OS and embedded applications.

The Unisphere for PowerMax Serviceability application integrates functionality that was previously supported by the stand-alone vApp manager application. The functionality enables the user to:

- View the version information and status of the PowerMax OS and embedded applications.
- Configure a NTP server.
- Modify external NAT IP addresses.
- Download logs that log the changes that the Serviceability applications make.
- Configure Solutions Enabler base and service settings.
- Set Symavoid on both instances on an embedded system.
- Control service access.
- Perform operations on VASA container.
- Configure VASA Provider settings for VASA containers.
- Manage certificates for SE/vWitness.
- Configure nethost entries.
- Manage certificates for Unisphere.
- Download performance reports, performance databases, and system databases.

Application -> VASA

- Provides and certifies VASA 5.0 support on the PowerMax 2500 and 8500 storage systems.
- Provides the ability to non-disruptively upgrade a VASA provider, running on a PowerMax 2500 or 8500 storage system, to a version that supports VASA 5.0. VASA Provider, when updated to version 5.0, requires VASA Provider to be unregistered and registered back to vCenter to build up the access control for the vCenter by running the registration steps again. This step is required since the VASA Provider would be building a database of trusted clients from scratch. VASA Provider expects that all provisioning operations arrive from the virtual host.
- Once a storage container is provisioned to a VASA 5.0 supported client, earlier clients (< VASA 5) are unable to access this storage container.
- In a Multi vCenter environment, it is recommended to unregister the standby Vasa Provider first. Expect Vasa Provider failover from vCenter if the active Vasa Provider is unregistered first.
- In a Multi vCenter setup, if the same storage container is shared across multiple vCenters, then once the VASA Provider is upgraded to 10.2.0, it is required that all vCenters in the data center be upgraded to the VASA 5.0 supported vSphere version in order to allow access to this storage container.
- After the VASA Provider upgrade to 10.2.0, for earlier client versions (< VASA 5.0) and VMCA certificate management, the VP_RETAIN_CERTIFICATE flag should be set to false.