Dell Unisphere for PowerMax 10.1.0.1 Release Notes

PDF

Limitations

This topic outlines the limitations for Unisphere for PowerMax.

The limitations in this release are listed in the following table:

Table 1. LimitationsThis table outlines the limitations.
Functional area	Limitation
System management	PMUNI-16264: FPIN Alerts are being displayed on the iSCSI dashboard. The issue is planned to be addressed in the next release.
System management	PMUNI-14828: The system attributes Hot Swap Policy and PAV are deprecated and attempts to set values for these attributes from Unisphere fails.
VMware management	PMUNI-15024 JPN: VMware > vCenters and ESXi In the Japanese build, registering a vCenter fails specifying "Failed to retrieve service content" error.
Secure Remote Services/Secure Connect Gateway	Registering Secure Remote Services/Secure Connect Gateway a second time using REST API does not require correct credentials. If the user enters incorrect credentials, Secure Remote Services is successfully registered and no error is posted.
Storage management	Sometimes effective used capacity for devices and Storage Groups may be reported larger than expected, and can occur for a device or devices which were SnapVX link targets or clone targets. The issue is planned to be addressed in the next release.
Capacity management	Unisphere version 10.0.1 reports Effective Used and Unreducible Capacity at storage group level for arrays running on PowerMaxOS 5978 Q121 SR and later, with the following exception: These values are not being updated in C/S mode, if the Client is lower than 10.0.1.
eVASA	VASA Provider 10.0.1 does not support: More than two vCenters without an RPQ Storage systems running HYPERMAX OS 5977 or PowerMaxOS 5978 IPv6 Workload capability (starting from microcode version 5978) - to maintain backwards compatibility, the VASA Provider continues to advertise Workloads as part of its capability schema. Adding more than one Protocol Endpoint to the same Storage Group XCOPY (host copy is used instead). Custom Certificate Authority (CA) signed certificates for multiple vCenters, self-signed certificates are supported.
eVASA	Protocol Endpoints are only supported through ACLX-enabled ports.
eVASA	Management VASA Provider 10.0.1 manages only one PowerMax. The management of the life cycle of derivatives including snapshots of vVols can only be performed through vCenter.
eVASA	VMware After upgrading the VASA Provider, vCenter does not show the upgraded version number. VMware expects users to unregister and re-register the VASA Provider to see the upgraded version. vCenter does not support the creation and migration of Fast Clone Virtual Machines. It can only be carried out through the VMware view.
eVASA	The VASA Provider supports a maximum of 12 snapshots per virtual machine. However, the VASA Provider revert workflow only supports a maximum of 11 snapshots. It is possible to revert the snapshot once one of the snapshots is deleted.
eVASA	The vVol Datastore space may take some time to update after a Virtual Machine deletion.
eVASA	Operation limits: The depth of Fast Clone virtual machine (VM) creation is 32. The number of Snapshots in the VM is 12. The number of Storage Containers per array is 16. The number of Protocol Endpoints per ESXi server is 1. The maximum vVol size is 16 TB.