DELL PowerMax 2500 Enterprise NVMe Storage User Guide

DELL PowerMax 2500 Enterprise NVMe Storage

Product Information

Specifications

• Product Name: Dell Unisphere for PowerMax
• Version: 10.0.0
• Release Type: Major (MA)
• Supported Storage Systems:
  • PowerMax 2500, PowerMax 8500 running PowerMaxOS 10 (6079)
  • PowerMax 2000, PowerMax 8000 running PowerMaxOS 5978
  • VMAX100K, VMAX200K, VMAX400K, VMAX 250F, VMAX 450F, VMAX 850F, VMAX 950F running HYPERMAX OS 5977.1131.1131
• REST API available for diagnostic, performance, configuration data access and provisioning operations

FAQ

• Q: What new features are introduced in Unisphere for PowerMax 10.0.0?
  • A: New features include CKD Compression, LREP Feature Deprecations, 32Gb FICON Support, and Platform Support Deprecation.
• Q: What storage systems are supported by Unisphere for PowerMax 10.0.0?
  • A: Supported storage systems include PowerMax 2500, PowerMax 8500 running PowerMaxOS 10, PowerMax 2000, PowerMax 8000 running PowerMaxOS 5978, and various VMAX models running HYPERMAX OS.

Information

Dell Unisphere for PowerMax 10.0.0 Release Notes

This document describes the new features, changed features, resolved issues, known issues, and limitations in Unisphere for PowerMax.

• Current Release Version: 10.0.0
• Release Type: Major (MA)

This document provides information about this release of Unisphere for PowerMax.

Revision history

This section provides a description of document changes.

Table 1. Document Revision history

embedded container restart.

Unisphere for PowerMax product description

Unisphere is a HTML5 web-based application that enables you to provision, operate and maintain PowerMax, VMAX All Flash, and VMAX storage systems.

Unisphere for PowerMax 10.0.0 supports:

• Storage systems (PowerMax 2500, PowerMax 8500) running PowerMaxOS 10 (6079)
• Storage systems (PowerMax 2000, PowerMax 8000) running PowerMaxOS 5978
• Storage systems (VMAX100K, VMAX200K, VMAX400K, VMAX 250F, VMAX 450F, VMAX 850F, VMAX 950F) running HYPERMAX OS 5977.1131.1131

A Unisphere Representational State Transfer (REST) API is also available. The API enables you to access diagnostic, performance and configuration data, and also enables you to perform provisioning operations on the storage system.

Rather than using a browser refresh, it is recommended that you click the (Refresh selected system) icon that is available from the home dashboard view for a specific storage system.
These Release Notes incorporate eVASA release information.

VASA Provider 10.0.0 is compatible with:

• Unisphere 10.0
• Solutions Enabler 10.0
• PowerMaxOS 10 (6079)
• PowerMax 2500 and 8500
• vCenter Server 6.7, 7.0
• ESXi Server 6.7, 7.0
• SRM Server 8.3, 8.4, 8.5

vVol remote replication is supported for vSphere 7.0 and above.
When both VASA providers are not registered in vCenter , the initial state of VASA in the U4P UI is standby-standby for both VPs.

New features

The following table describes the features that are introduced in Unisphere for PowerMax 10.0.0.

Table 2. New features

running PowerMaxOS 10 (6079), Unisphere supports the enabling of data reduction on CKD storage group creation, the enabling or disabling of data reduction when modifying a CKD storage group, and the viewing of the data reduction state for a CKD storage group.
LREP Feature Deprecations| TimeFinder SNAP is not supported on storage systems running HYPERMAX OS 5977, PowerMaxOS 5978, and PowerMaxOS 10 (6079). TimeFinder VP SNAP and TimeFinder/Mirror are not supported on storage systems running PowerMaxOS 10 (6079). TimeFinder SnapVX provides the equivalent support.
2K SRDF groups| For storage systems running PowerMaxOS 10 (6079), 2,000 SRDF groups are supported.
Illuminated Bezels| The system bay LED state can be configured on one or more selected bays, in order to aid in locating them.
FlexRAID – Flexible Drive Protection Scheme| The storage systems running PowerMaxOS 10 (6079) support the use of a flexible RAID protection scheme that supports capacity expansion in increments of a single drive. New properties have been added for the Disk Group, SRP, and System and a new alert policy has also been added.
32Gb FICON Support| For storage systems running PowerMaxOS 10 (6079), a new OR emulation has been added to replace all previous Open System Front End and SRDF emulations. The system hardware view displays an OR directors tab, a BE directors tab, an EF directors tab, and an EM directors tab.
Platform Support Deprecation| This feature supports the removal of Unisphere management support for storage system running Enginuity OS 5876. The feature also supports the removal of Unisphere management support for storage systems running HYPERMAX OS 5977 at a version lower than HYPERMAX OS 5977.1131.1131.
Customer driven Software Staging, Install, and Upgrade| This feature provides customers with the capability to update applications on embedded management guests. The feature allows them to stage the management guest software and install it at their own convenience, without the involvement of remote services.
---|---
Deprecate Write pacing| Write-pacing is not supported for storage systems running PowerMaxOS 10 (6079).
Backend Emulation| On storage systems running PowerMaxOS 10 (6079) spindles are not associated with a specific DA (Director), Interface,

or SCSI ID (TID). They are, instead, uniquely identified by the Spindle ID and grouped according to Disk Group. There is no relationship between DA directors and disks for storage systems running PowerMaxOS 10 (6079).

Embedded Management Serviceability -vApp Manager Removal| The standalone vApp Manager has been removed and its functionality has been added to Unisphere (embedded option) and SymmWin.
Integrate Open Replicator into NDM| This feature provides migration support for migrations from storage systems running Enginuity OS 5876, XtremeIO, VNX, Unity, DMX, and other array vendors to a storage system running PowerMaxOS 10 (6079).
Support for 25 GbE NVMeoF via TCP on V4| Unisphere supports both iSCSI and NVMe/TCP protocols for storage systems running PowerMaxOS 10 (6079).
Converged Emulation| For storage systems running PowerMaxOS 10 (6079), a new OR emulation has been added to replace all previous Open System Front End and SRDF emulations.
e-Licensing Updates| For storage systems running PowerMaxOS 10 (6079), XML format is required when loading a license file.
SAN Health Reporting and Troubleshooting| For storage systems running PowerMaxOS 10 (6079), a new SAN Health Report view is added to aid the user to determine the current health of their storage network.
Array Metrics Review, Reduction, Deprecation| This feature supports the removal of Unisphere management support for PM metrics that are associated with storage systems running Enginuity OS 5876.
TDev Creation with User Specified Start Number| User specified numbering allows a user during TDEV volume creation to input a custom starting device number from which they would like volume numbers to start.
PowerMax Multi System Provisioning & Migration Workload Suitability Validation| The Unisphere multi-array Provisioning Wizard and the multi- array Migration Wizard have been enhanced to support remote arrays, provided that data is being collected for the remote array on one or more U4P instances.
PowerMax Software System Profiles and Compliance| This feature allows customers to set up and configure their software settings on one or more arrays in a scalable manner. In addition, compliance can be monitored against a PowerMax Profile configuration to ensure a consistent setup of arrays and allow notifications to be sent when settings are changed that deviate from the PowerMax Profiles.
ACL Deprecation| Symmetrix ACLs are not supported for storage systems running PowerMaxOS 10 (6079).
SRS Gen4 API for Unisphere| Unisphere uses Secure Remote Services (SRS) to send and receive data to and from CloudIQ. The SRS API has updated to a new generation (Gen 4) and Unisphere has been updated to use the Gen4 version.
Unisphere Angular 7 (includes DSA removal)| Unisphere is keeping up to date with the versions of Angular. Angular provides built-in features for animation, http service, and materials which in turn have features such as auto-complete, navigation, toolbar, and menus. Database Storage Analyzer (DSA) functionality has been removed from Unisphere for PowerMax.
---|---
Multi-Factor Authentication| This feature provides support for Multi-Factor Authentication (RSA SecurID(R) token) for Unisphere for PowerMax.
SRDF Feature Usage Collection| This feature supports the collection of activity-based SRDF feature usage statistics from the field.
ORS Usage Stat Collection| This feature supports the collection of activity- based Open Replicator (OR) feature usage statistics from the field.
Resource Usage Monitoring and Reporting| This feature provides an intuitive view of capacity utilization on the array throughout its life cycle. Alerting on and monitoring of resources is focused on assisting the customer decision making around remaining capacity.
Audit Log Enhancements| This feature supports audit log enhancements in the areas of filtering, additions to audit log message catalog, and combination of records that were written as part of a single sequence.
Cloudiq Cybersecurity| Unisphere provides certain system and array-based security attributes to CyberSecIQ using REST API. Additional attributes have been added for this new version including the multifactor authentication enablement status, the version of TLS used by remote syslog, and information about the DARE remote storage system.
Support for 25 GbE via SRDF on V4| This feature supports 25 GbE via SRDF on storage systems running PowerMaxOS 10 (6079).
Show Realtime Capacity of Directors| Unisphere supports the display of real- time performance capacity for directors on storage systems running PowerMaxOS 10 (6079).
Support for Dell Service Tags| Dell Service Tags are displayed in the system properties page for each array.
Optimization Number of Gatekeepers – Control Host| This feature allows a customer to add a new control host in one step and also supports the reduction in the number of gatekeepers .
U4P Support of SRM| REST API support is provided for SRM.
Support of AppSync| REST API support is provided for AppSync
V4 Support of VMware Plugins – ESA, vRO, BSI| REST API support is provided for VMware plugins
Support of Ansible Modules and CSI Driver| REST API support is provided for Ansible Modules and CSI Driver
V4 Support for Splunk TA| REST API support is provided for Splunk TA
Day 1 support of CloudIQ| This feature is supported in this release.
Support of 3rd Party Certifications and Solutions – SAP| REST API support is provided for 3rd Party Certifications and Solutions – SAP
U4P Installer changes for Dell Standard Versioning| This feature addresses the changes that are required to the U4P installer for Dell standard versioning
Recover cloud snapshots to another PowerMax| This feature supports the restore of cloud snapshots to another PowerMax.
Unisphere ISG Telemetry Notice Update for CloudIQ SRS connection setup| The text in the Unisphere settings for the SRS dialog has been replaced with the new ISG Telemetry Notice text .
---|---
StFS Integration with NVMe-oFTCP| This feature provides support for Storage Fabric Services (StFS), that can automate the establishment of connectivity, between NVMe over Fabrics (NVMe-oF) hosts and PowerMax front-end port(s) running the NVMe-oF TCP protocol on storage systems running PowerMaxOS 10 (6079).
U4P Add Drive Capacity Support| For storage systems running PowerMaxOS 10 (6079), additional reporting has been added to allow monitoring of the add drive capacity process. Changes have been added to report the state of adding drive capacity, the target capacities, and the estimated remaining time to completion.
SG support for Clones| Support for TimeFinder/Clone has been added for reporting and management at the Storage Group level.
Inclusive Language Initiative| Unisphere for PowerMax has added preferred substitutes for any non-inclusive terminology based on inclusive language terminology.
PowerMax File| Network-attached storage (NAS) is a file-level storage architecture that makes stored data more accessible to networked devices. A storage system running PowerMaxOS 10 (6079) with embedded Unisphere supports software- defined NAS (also known as PowerMax File). PowerMax File provides a reliable, highly available, scale-out, high performance, and 64-bit file system. PowerMax File runs as a container instance inside each file guest offering based on the customer configuration. Unisphere in the Embedded Element Manger (EEM) manages a single instance of file that is present locally. The Unisphere that is installed on an external host does not manage any file instances.
Day 1 support of PowerPath| This feature is supported in this release.
REST API – LUN Level Diagnostics Stats| REST API support is provided for LUN level diagnostics statistics.
Provide Unisphere online help in Japanese| This feature relates to the provision of Unisphere online help in the Japanese language.

Changed features

In Unisphere for PowerMax 10.0.0, LDAPS configuration requires the import of the trust anchor, that is, the root CA certificate of the LDAP server’s certificate issuer.

In Unisphere for PowerMax 10.0.0, the following changes have occurred in the Performance Management (PM) area:

The following PM Metric categories are no longer supported:

• Composite Group
• Database
• Database by Pool
• Disk Group Tier
• DSE Pool
• Fast Storage Resource
• FAST VP Policy
• Meta
• Other-Pool Bound Volume
• SAVE Volume
• Snap Pool
• Spare Disk
• Storage Group by Tier
• Tier by Storage Group
• Thin Tier
• Tier by Storage Group

The PM category iSCSI Target has been renamed to Endpoint.

The following PM Metrics are no longer supported:

• BE Director (DA): % Busy Logical Core 0
• BE Director (DA): % Busy Logical Core 1
• BE Director (DA): % Compressed Write Reqs
• BE Director (DA): % Compressed MBs
• BE Director (DA): % Compressed Read MBs
• BE Director (DA): % Compressed Write MBs
• BE Director (DA): % Compressed Read Reqs
• BE Director (DA): % Compressed Reqs
• BE Director (DA): % Idle Logical Core 0
• BE Director (DA): % Idle Logical Core 1
• BE Director (DA): % Non-IO Busy
• BE Director (DA): % Non-IO Busy Logical Core 0
• BE Director (DA): % Non-IO Busy Logical Core 1
• BE Director (DA): Compressed MBs/sec
• BE Director (DA): Compressed Read MBs/sec
• BE Director (DA): Compressed Write MBs/sec
• BE Director (DA): Compressed Read Reqs/sec
• BE Director (DA): Compressed Reqs/sec
• BE Director (DA): Compressed Write Reqs/sec
• DATA Volume: BE Disk Read RT (ms)
• DATA Volume: BE Prefetched Tracks/sec
• DATA Volume: BE Reads For VLUN Migration (KB)
• DATA Volume: BE Reads For VLUN Migration
• DATA Volume: BE Writes For VLUN Migration (KB)
• DATA Volume: BE Writes For VLUN Migration
• DATA Volume: BE XOR Reads (KB)
• DATA Volume: BE XOR Reads
• Device Group: BE Disk Read RT (ms)
• Device Group: BE Reads For VLUN Migration (KB)
• Device Group: BE Reads For VLUN Migration
• Device Group: BE Read Request Time (ms)
• Device Group: BE Read Task Time (ms)
• Device Group: BE Task Time/sec
• Device Group: BE Writes For VLUN Migration (KB)
• Device Group: BE Writes For VLUN Migration
• Device Group: BE XOR Read (KB)
• Device Group: BE XOR Reads
• Device Group: Random Hits/sec
• Disk: Avg Hypers per Seek
• External Director: % Busy Logical Core 0
• External Director: % Busy Logical Core 1
• External Director: % Compressed MBs
• External Director: % Compressed Read MBs
• External Director: % Compressed Read Reqs
• External Director: % Compressed Reqs
• External Director: % Compressed Write MBs
• External Director: % Compressed Write Reqs
• External Director: % Idle Logical Core 0
• External Director: % Idle Logical Core 1
• External Director: % Non-IO Busy
• External Director: % Non-IO Busy Logical Core 0
• External Director: % Non-IO Busy Logical Core 1
• External Director: Compressed MBs/sec
• External Director: Compressed Read MBs/sec
• External Director: Compressed Read Reqs/sec
• External Director: Compressed Reqs/sec
• External Director: Compressed Write MBs/sec
• External Director: Compressed Write Reqs/sec
• FE Director: % Busy Logical Core 0
• FE Director: % Busy Logical Core 1
• Pool By Storage Group: % Compressed Tracks
• Pool By Storage Group: Compressed Tracks
• Pool By Storage Resource: % Compressed Tracks
• Pool By Storage Resource: Compressed Tracks
• RDFA Group: Duration of Last Cycle
• RDFA Group: System WP Count
• RDFA Group: System WP Limit
• RDFS Group: BE Reads For VLUN Migration (KB)
• RDFS Group: BE Reads For VLUN Migration
• RDFS Group: BE Writes For VLUN Migration (KB)
• RDFS Group: BE Writes For VLUN Migration
• RDFS Group: BE XOR Read (KB)
• RDFS Group: BE XOR Reads
• RDFS Group: RDF Read Hits/sec
• RDF Director: Rewrites/sec
• Storage Container: % Compressed Tracks
• Storage Container: BE Disk Read RT (ms)
• Storage Container: BE Read Request Time (ms)
• Storage Container: BE Read Task Time (ms)
• Storage Container: BE Reads For VLUN Migration (KB)
• Storage Container: BE Reads For VLUN Migration
• Storage Container: BE Writes For VLUN Migration (KB)
• Storage Container: BE Writes For VLUN Migration
• Storage Container: BE XOR Reads (KB)
• Storage Container: BE XOR Read s
• Storage Container: Compressed Tracks
• Storage Group: % Compressed Tracks
• Storage Group: BE Disk Read RT (ms)
• Storage Group: BE XOR Reads (KB)
• Storage Group: BE XOR Reads
• Storage Group: BE Reads For VLUN Migration (KB)
• Storage Group: BE Reads For VLUN Migration
• Storage Group: BE Read Request Time (ms)
• Storage Group: BE Read Task Time (ms)
• Storage Group: BE Writes For VLUN Migration (KB)
• Storage Group: BE Writes For VLUN Migration
• Storage Group: Compressed Tracks
• Storage Group by Pool: % Compressed Tracks
• Storage Group by Pool: Compressed Tracks
• Storage Resource: % Compressed Tracks
• Storage Resource: BE Reads For VLUN Migration (KB)
• Storage Resource: BE Reads For VLUN Migration
• Storage Resource: BE Read Request Time (ms)
• Storage Resource: BE Read Task Time (ms)
• Storage Resource: BE Writes For VLUN Migration (KB)
• Storage Resource: BE Writes For VLUN Migration
• Storage Resource: BE XOR Reads (KB)
• Storage Resource: BE XOR Reads
• Storage Resource: Compressed Tracks
• Storage Resource by Pool: % Compressed Tracks
• Storage Resource by Pool: Compressed Tracks
• Thin Pool: % Compressed Tracks
• Thin Pool: BE Blocks Read For VLUN Migration
• Thin Pool: BE Blocks Written For VLUN Migration
• Thin Pool: BE Reads For VLUN Migration
• Thin Pool: BE Writes For VLUN Migration
• Thin Pool: BE XOR Reads (KB)
• Thin Pool: BE XOR Reads
• Thin Pool: Compressed Tracks
• Thin Volume: BE RDF Copy (MB)
• Thin Volume: BE RDF Copy
• vVol: BE RDF Copy (MB)
• vVol: BE RDF Copy

Resolved issues

The problems that are resolved in Unisphere for PowerMax 10.0.0 are listed in the following table:

Table 3. Resolved issues

displays only 512 devices, even when there are 700 devices in the storage group (SG).
575727| Performance Management| Save as PDF – Charts & Data is not working for real-time traces.
578240| REST API| Some REST API calls that are taking too long to return a response, and this delay causes VSS timeout errors in AppSync.
580130| SRDF management| Establishing an SRDF Metro pair in Unisphere automatically defaults to Bias even if vWitness is available.
584127| SRDF management| When creating an SRDF pair, Unisphere cannot find the correct number of devices.
584192| Capacity management| Unisphere supports the enhancement of the user visibility of the SRP percentage usage effective capacity.
588092| SRDF management| The removal of the MetroDR environment may result in the removal of the wrong DR leg when DR_RDFG has the same number on both the Metro R1 & Metro R2 sites.
591959| Performance Management| Unisphere supports memory DIMM metrics.
592082| Device group management| When a device group (DG) is used as the construct for the SRDF device, REST API is not making a direct call to the array for the status of the pair relationship.
593105| SRDF management| When attempting to expand an SRDF SG, the UI displays an error indicating that the pair states are mixed for the SRDF group.
594351| Email notification| A scheduled dashboard report create/email fails intermittently.
596246| Alert management| An exception error occurs when attempting to set threshold alerts to email.
597064| REST API| When using REST API with the Accept: application/xml header, the response appears corrupted.

Known issues

The known issues in Unisphere for PowerMax 10.0.0 are listed in the following table:

Table 4. Known issues

Issue ID| Functional area| Description| Workaround/Resolution
---|---|---|---
594041| Upgrade| if the customer had any LocalDir account with ‘£’ or ‘€’ character in the password, they must change the password first before proceeding with the upgrade to Juniper.| Change the password before the upgrade ensuring that the ‘£’ or ‘€’ characters are not in the new password.
598501| Serviceability| Occasionally when a user refreshes the browser while in the Serviceability tab, the data on the particular page may not be updated.| The user must log in to Unisphere application again with their credentials and go to the Serviceability tab.
600196| Serviceability| When one node is offline and the user tries to set a value in SE settings tab, the value gets set in the

active node, but synchronization with the other nodes fails because it is offline.

| When the other node comes online, the user can set the values and the nodes synchronize with each other.
600263| Serviceability| When MGMT-0 is offline, nethost does not display any values on the UI.| The nethost entries can be found or updated in /var/symapi/ config/nethost file when MGMT-0 is down. This update must be done with the help of CS using the backend by logging into the SSH session of both the SE- MGMT containers.
–| Serviceability| The ability to restart the embedded container (previously supported by the now deprecated vApp manager) has been removed.| The embedded container can be restarted using MMCS/SymmWin and a call logged with Technical Support.
601077| Authentication| Clarification is required for “Configure authentication authorities” Unisphere for PowerMax help topic – there is an invalid reference to port 389 support for LDAP (no longer supported), and a missing reference for port 3269 support for LDAP-SSL (in addition to port 636 support for LDAP-SSL). The help topic will be updated in the next release.| Document the corrected information (see Description) in the Release Notes for this

release and update the help topic in the next release.

595131| eVASA| Storage vMotion or migration to vVol datastore fails if the virtual machine uses RDM. You will see a similar error in the vCenter – “Storage vMotion failed to create the destination disk. The requested size is not a multiple of 1MB”. For more information about this issue, see Cannot place any Virtual disk file whose size is not an integral multiple of 1024KB (1MB) on the VVOL Datastore (52674).| To resolve the issue:

1.      Resize the RDM volume capacity with CYL in Unisphere. Contact storage admin to ensure that the capacity with cylinder can be converted to multiples of 1 MB.

2.      Remove/Unmap the RDM from the virtual machine

3.      Rescan all the ESXi Hosts that this LUN is visible to

4.      Add/ Re-Map the RDM back to the virtual machine

5.      Perform rescan from the guest operating system

6.      Perform the Storage vMotion or Migration

For more information about expanding the RDM that is in use by virtual machine, see Expanding
the size of a Raw Device
Mapping (RDM) (1007021).

596181| eVASA| If the failover of the VASA provider occurs in an environment where the VASA Provider is registered on multiple vCenters, datastores are accessible on the first vCenter, however are inaccessible on the second vCenter.| See the workaround documented in Adding an ESXi host to vCenter Server after upgrade to ESXi 6.7 Update 3 and later versions fail (78017).
---|---|---|---
–| eVASA| If the VASA IP address is changed for any reason, then user must re- register the VASA Provider.| See description.
–| eVASA| VASA registration issues:

●    If the status of the VASA Provider is set to “No Storage System” in the vCenter, then the user can attempt a “Rescan” to bring the VASA Provider back to an active state.

●    If the status of the VASA Provider in vCenter shows “Rescan Error” and the datastores are inaccessible, then the user has to restart the VASA Provider through the U4P->Serviceability-

Applications->VASA for resolution.

| See description.
597839| Install| On Windows, after login, a directory that is called Program FilesEMCSMASjbossdomainserversserver-0d ata or a similar name is created under

%SMAS_HOME%/jboss. This directory and its content can be safely ignored.

| See description.
597941| viClient| Unisphere container crashes during the registration or discovery workflow.| See the resolution documented in Unisphere container crashes during the registration or discovery workflow (000200542).

Limitations

The limitations in Unisphere for PowerMax 10.0.0 are listed in the following table:

Table 5. Limitations

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| 600002 – Snapshot capacity dashboard is updated only after a new snapshot is taken.
Serviceability| 600264 – In the Unisphere SE settings page, syslog port field description says the default value as

514. However the value is displayed as 0 on the UI.

eVASA| VASA Provider 10.0 does not support:

●    More than two vCenters

●    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 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:

●    Depth of Fast Clone virtual machine (VM) creation is 32.

●    Number of Snapshots in VM is 12

●    Number of Storage Containers per array is 16

●    Number of Protocol Endpoints per ESXi server is 1

●    Maximum vVol size is 16 TB

Environment and system requirements

• This topic outlines the environmental and system requirements for Unisphere for PowerMax.
• For information about the environmental and system requirements for Unisphere for PowerMax, see the Dell Unisphere for PowerMax Installation Guide.

Support deprecation

• The Cloud Mobility feature is deprecated and requires an approved Request for Product Qualification (RPQ). Contact your sales team for more information.
• Virtual Appliance (vApp) is deprecated in Unisphere for PowerMax V10.0.
• Virtual Appliance (vApp) Manager is deprecated in the PowerMax V10.0 release.
• Unisphere 360 is deprecated in the PowerMax V10.0 release.
• Database Storage Analyzer (DSA) is deprecated in Unisphere for PowerMax V10.0.

Installation and upgrade considerations

• This topic outlines the Installation and upgrade considerations for Unisphere for PowerMax.
• For instructions on installing, upgrading, or downgrading Unisphere for PowerMax, see the Dell Unisphere for PowerMax Installation Guide.

Where to get help

• The Dell Technologies Support site (https://www.dell.com/support) contains important information about products and services including drivers, installation packages, product documentation, knowledge base articles, and advisories.
• A valid support contract and account might be required to access all the available information about a specific Dell Technologies product or service.

Your comments

• Your suggestions help continue to improve the accuracy, organization, and overall quality of the user publications. Send your feedback to content feedback.

Notes, cautions, and warnings

• NOTE: A NOTE indicates important information that helps you make better use of your product.
• CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the problem.
• WARNING: A WARNING indicates a potential for property damage, personal injury, or death.

© 2024 Dell Inc. or its subsidiaries. All rights reserved. Dell Technologies, Dell, and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other trademarks may be trademarks of their respective owners.

Read User Manual Online (PDF format)

Read User Manual Online (PDF format)  >>

Download This Manual (PDF format)

Download this manual  >>