Contents

Dell EMC VMAX 100K V9.2.1 Storage Product Guide PDF

1 of 18
1 of 18

Summary of Content for Dell EMC VMAX 100K V9.2.1 Storage Product Guide PDF

Product Guide

Dell EMC VASA Provider and Embedded VASA Provider for PowerMax 9.2.1

Rev. 02 September 2021

This product guide contains supplemental information about the external Dell EMC VASA Provider and Embedded VASA Provider for PowerMax. Topics include:

Overview.....................................................................................................................................................................................................................2

VASA Provider...........................................................................................................................................................................................................2

Embedded VASA Provider..................................................................................................................................................................................... 9

Serviceability............................................................................................................................................................................................................ 13

Certificates............................................................................................................................................................................................................... 16

Overview

This document describes both VASA Provider (external) and Embedded VASA (eVASA) Provider, concepts, and theory of operation for the Dell EMC PowerMax array.

NOTE: VASA Provider (external) and eVASA Provider cannot run on the same array.

NOTE: The external VASA Provider only supports VASA 2.0 and the embedded VASA Provider (eVASA) only supports VASA

3.0.

VASA Provider

A VASA (vSphere APIs for Storage Awareness) Provider is a storage-side software component that acts as a storage awareness service for vSphere. VASA Provider is responsible for storage orchestration between VMware vSphere components and the Dell EMC PowerMax system.

The VASA Provider is delivered as a virtual appliance which orchestrates the life cycle of VMware Virtual Volumes (vVols) and their derivatives: snapshots, clones, and fast-clones. It also provides storage topology, capabilities, and status information to the vCenter and the ESXi hosts.

vVols are a storage abstraction, designed by VMware with the collaboration of Dell EMC. vVols provide storage arrays with visibility at a virtual disk level and enables them to fulfill the application's storage requirements. vVols are PowerMax devices that store application data, virtual machine configuration, swap space, and memory state. vVols offer more granular control to users and increased scale.

Environment and system requirements

Dell EMC VASA Provider for PowerMax has the following system requirements:

Two virtual disks with a minimum size of 10 GB and 15 GB each 8 GB of RAM and two Virtual Central Processing Units (vCPU) A 4 GB device that is to be used as a database LUN, must be presented to ESXi host and mounted on the Virtual Appliance

using the vApp Interface. VMware vSphere 6.5 or higher The ESXi host running VASA Provider must have a Fibre Channel connection. A redundant TCP/IP network A minimum of five gatekeepers that are mapped to the virtual appliance

See the Dell EMC Virtual Appliance Manager Installation Guide on the Dell EMC support site for more details.

Compatibility matrix

Table 1 lists the software version numbers compatible with VASA Provider.

Table 1. Compatibility matrix

VASA Provider vApp Manager Solutions Enabler PowerMaxOS vCenter Server ESX/ESXi Server

9.2.1 9.2.1 9.2.1 5978.669.669 and above

6.5, 6.7 ,7.0 6.5, 6.7 ,7.0

2

Deploy and configure the Virtual Appliance

About this task

To deploy and configure the Virtual Appliance:

Steps

1. Download the OVF archive file (*.ova) containing the installation program from Dell EMC Support to a temporary directory.

2. Start the vSphere Client and log in to the vCenter Server instance through which you install the Virtual Appliance.

3. From the navigation tree, select the ESXi host on which you install the Virtual Appliance.

4. Right-click the ESXi host and select Deploy OVF Template.

5. Browse to the OVF archive file, which is located in the temporary directory you created earlier. Select the OVF archive file and click Next.

6. On the Review details page, verify the details about the appliance and click Next.

7. On the Accept License Agreements page, select Accept and click Next.

8. On the Name and Location page, specify a name and location for the appliance and click Next.

9. On the Disk Format, select the format in which to store the virtual machine virtual drives and click Next.

10. On the Network Mapping page, select the networks that the deployed template should use and click Next.

11. On the Customize template page, provide valid values for the following OVF Tool properties and then click Next:

a. IP Address Netmask Gateway DNS Server 1 DNS Server 2

NOTE:

The Virtual Appliance uses the IP address to query the DNS server and get its hostname. Therefore, you must ensure

that the IP address has a hostname mapping in the DNS server. The VASA protocol does not work correctly without

a properly configured DNS service.

b. Optionally, provide or select valid values for the following OVF properties:

Proxy Server: Enter the IP address of the proxy server and port. For example:

ProxyServer-IP:Port ESXi Server Name: Enter the fully qualified ESXi hostname. ESXi Server Password: Enter the ESXi password in base64 encryption format.

12. On the Ready to Complete page, verify the information and click Finish.

NOTE: The Target setting on the Ready to Complete page must be the same as the ESXi Server Name value.

13. When the Completed Successfully message is displayed, click Close.

3

Launching vApp Manager

About this task

After the vApp is deployed, complete the following the steps to launch vApp Manager:

Steps

1. Type one of the following URLs in a browser:

https://appliance_ip:5480

Or

https://appliance_host_name:5480

2. On the log in panel, type vpconfig for both the User Name and Password, and then click Login.

NOTE: You are required to change the password from vApp Manager on first login. Also, vApp Manager can be

configured to use LDAP for user authentication. For more information about LDAP, see the vApp Manager online help.

Adding an ESXi host

About this task

Fibre Channel gatekeeper mapping features are unavailable until an ESXi host is validated once and then attached to the appliance. Manually add a new ESXi host by selecting the new gatekeeper devices to map (see the "Mapping Fibre Channel gatekeeper devices" section).

Steps

1. Log in to the vApp Manager and select Manage > Gatekeepers.

If the ESXi has been validated, this view shows the unmapped and mapped Fibre Channel gatekeeper devices. If there is no ESXi host attached to the appliance, no devices are shown. All gatekeeper configuration features are unavailable until an ESXi host is added.

2. Click Add ESXi, and then add details in the following fields: ESX server where the VASA Provider VM is deployed (fully qualified server name)

NOTE: If you enter anything other than an FQDN, for example, an IP address, an error message is displayed.

User name Password Confirm password

3. Click Add.

Results

The ESXi hostname is displayed next to the text Host ESXi attached.

Adding an array

About this task

To list devices available for mapping, you can add an array to the ESXi host.

Steps

1. Log in to the vApp Manager and select Manage > Gatekeepers.

2. Next to the host ESXi name, click Add Array.

3. The Select Array dialog box opens. Select the radio button next to the required array ID and then click Add Array.

4

The Devices attached to the Host ESXi list shows the devices that are available for mapping to the Virtual Appliance. The devices are listed in ascending order, and based on size.

Mapping Fibre Channel gatekeeper devices

Prerequisites

If no ESXi host is attached to the appliance, mapping features are unavailable. See Adding an ESXi server.

Fibre Channel gatekeeper devices are mapped to the appliance through the ESXi host that is attached to the appliance. If no ESXi host is attached to the appliance, you can add one.

Steps

1. Log in to the vApp Manager and select Manage > Gatekeepers.

This view shows the unmapped and mapped Fibre Channel and iSCSI gatekeeper devices.

2. In the Gatekeeper devices attached to the Host ESX list, click the checkbox next to the devices you want to map and then click Map Gatekeepers.

NOTE: A warning message is displayed when mapping devices that are equal to or greater than 1 GB: The selected devices might be formatted during mount process and data will not be recoverable. Please ensure they are not part of any datastore. Do you want to continue mapping these devices?

Mounting the database LUN

About this task

Dell EMC VASA Provider for PowerMax requires that a separate TDEV device is mapped to host the database. The recommended size is 4 GB.

Steps

1. Log in to the vApp Manager and select Manage > Gatekeepers.

2. In the Devices attached to the Host ESXi list, select the device and click Map Gatekeepers.

The device is moved from the Gatekeeper Devices attached to the Host ESXi list to the Devices attached to Virtual Appliance Host list.

3. In the Devices attached to Virtual Appliance Host list, select the device and click MountDB. An information dialog box confirms that the device has been successfully mounted.

Viewing Dell EMC VASA Provider for PowerMax configuration

Steps

1. Log in to vApp Manager and select Configure > VP Configuration.

The following settings are displayed:

VP log file size (MB)

Default value is 64.

VP log level Default value is DEBUG.

Number of log files to be retained

Default value is 10.

Max concurrent connections per session

Default value is 4.

5

Retain VP certificate

Default value is False. NOTE: For self-signed certificates on multiple vCenter Server appliances, this setting must be set

to True.

SYMAPI debug log Default value is Disabled.

2. To update a configuration value, select a new value and click Set.

NOTE: After updating a configuration value, you must restart ECOM.

Registering Dell EMC VASA Provider for PowerMax with the vSphere Web Client or vSphere Client

About this task

The default Dell EMC VASA Provider for PowerMax credentials for registration are admin for username and #1Password for password. For security, Dell Technologies recommends changing the default values. The default registration credentials can be changed by going to https://appliance_IP:5989/ecomconfig and selecting Change Password.

NOTE: Dell Technologies recommends that users do not change other options within the ECOMConfig portal.

NOTE: NTP must be configured,

Steps

1. From the Navigator panel of the VMware vSphere Web Client for vCenter Server, select the vCenter Server virtual machine in the Hosts and Clusters view.

2. In the Configure tab, select Storage Providers and click the + symbol. The New Storage Provider dialog box opens.

3. Type the name, username, password, and URL and click OK.

NOTE: The VASA Provider URL is https://vApp_host_name:5989/vasa-providers.xml

A Security Alert dialog box is displayed, asking if you trust the host.

4. Click Yes. Select the User storage provider certificate check box if required.

5. To verify the registration, refresh the view in the vSphere Web Client. The Dell EMC VASA Provider for PowerMax and its details should be listed.

NOTE: Users must rescan from vCenter Server to discover the newly created storage containers.

Accessing Dell EMC VASA Provider for PowerMax using SSH

Prerequisites

The default username and password to log in to Dell EMC VASA Provider for PowerMax through SSH is cseadmin.

Steps

1. Log in to the vApp Manager and select Configure > Host.

2. If the link shows as Disable SSH, the SSH port is already in the enabled state, otherwise, click Enable SSH to enable the SSH port.

6

Workflow overview

This section defines different workflows that are required for creating vVol-based Virtual Machines (VM).

Policy Management

About this task

During the creation of a VM, the VM should be associated with a VMware policy. The VMware policy translates into the underlying storage profile that is associated with the VM. The user defines a VMware policy with storage profile values, for example, the service level.

Based on what kind of storage is available in the vVol datastore, it is marked compatible with the VMware profile.

When you select a VMware policy for a VM during creation time, the user interface displays a list of compatible datastores for the VM. You can select any datastore from this list to create a VM.

This section below describes the workflows that are related to VMware policies.

Creation

Steps

1. In the VMware vSphere Web Client or vSphere Client, select Menu > Policies and Profiles.

2. Select VM Storage Policy.

3. Set the name of the policy and the corresponding descriptions.

4. Select VmaxVVolProvider from the drop-down menu next to Rules based on data services.

NOTE: Selecting VmaxVvolProvider creates a VASA 2.0 policy using the VMware VASA 2.0 specification. Selecting

VmaxVvolVasaProvider VASA 1.0 configures the policy under the VMware VASA 1.0 specification.

5. Select the relevant Service Level. The list of compatible Datastores is listed for the newly created policy.

6. Select the Workload.

NOTE: Workloads are supported only for backwards compatibility. Storage policies should include the Workload attribute

for compliance calculations. Workload should be set to "None."

7. Select Finish to create the policy.

Association

About this task

See the VM creation section to see how the policy is associated with a virtual machine.

Update Profile

About this task

The storage profile that is associated with the VMware policy can be updated when required.

Steps

1. Select the policy that must be updated.

2. Click Edit Settings.

3. Select the relevant section, and update the corresponding values.

4. Click OK to confirm.

7

Storage configuration

Prerequisites

Before creating the VMware vVol datastore, ensure that there are vVol storage containers that are created on the array. The steps to create a vVol storage container on the array can be found in the Unisphere for PowerMax Online Help at https:// support.emc.com.

vVol datastore creation

About this task

Most of the workflow to create a vVol datastore is similar to that when creating a VMFS datastore. On the screen where the user selects the VMFS type, for a vVol datastore you should select the vVol type. See the VMware documentation on datastore creation for further details.

Steps

1. Go to the Storage tab to create a Datastore.

2. Select vVol as the Datastore type.

3. Enter the Datastore name and select the storage container from the Backing Storage Container table.

4. Select the host from the list.

5. Click Finish.

VM Creation

About this task

The VM creation procedure for vVol-based VMs is similar to that for non-vVol-based VMs. In a vVol-based VM, the VM should be associated with the vVol policy. This decides the underlying storage on which the VM is hosted. See the VMware documentation on VM creation for further details.

Steps

1. Select the VM policy and the compatible datastore for the policy.

2. Complete the wizard to create a vVol-based VM.

VM Policy update

About this task

For a VM on the vVol datastore, you have the option of changing the policy at VM level and at individual disk level (VMDK).

The VM control and provisioning operations for a VM on a vVol datastore are the same as for the VMs on a VMFS datastore.

8

Embedded VASA Provider

Embedded VASA Provider (VP) is available for new PowerMax 2000 and PowerMax 8000 arrays running PowerMaxOS 5978.669.669 and above eliminating the need for a user to manage it on a host . VP high availability (HA) is offered as part of embedded VP with two copies of the VP required on each array. The HA functionality enables users to seamlessly recover from VP failures. VASA 3.0 supports SRDF/A replication between two PowerMax arrays. Note: Upgrades to existing PowerMax arrays are supported for arrays running PowerMaxOS 5978.711.711 with embedded VASA(eVASA) Provider 9.2.1. Contact your local Dell EMC representative for more information. .

Compatibility matrix

The table below lists the software version numbers compatible with eVASA Provider.

Table 2. Compatibility matrix

VASA Provider

vApp Manager

Solutions Enabler

PowerMax OS

Array Models vCenter Server

ESX/ESXi Server

SRM VASA

9.2.1 9.2.1 9.2.1 5978 PowerMax 2000

PowerMax 8000

6.5, 6.7 ,7.0 6.5, 6.7 ,7.0

8.3 3.0

NOTE:

Adding eVASA to existing PowerMax arrays is supported for arrays running PowerMaxOS 5978.711.711 with eVASA

Provider 9.2.1.Contact your local Dell EMC representative for more information.

vVol remote replication is supported using PowerMax SRDF.

vVol remote replication is supported for vSphere 7.0 and above

Replication support includes the replication of Data vVols, Clones, and FAST clones. Snapshot replication is not

supported.

Only Async SRDF replication is supported.

Only two-site replication is supported.

Both fan-in and fan-out array configurations are supported.

Bi-Direction Remote Replication between Fault Domains (arrays) is supported.

Configuring an eVASA container

See Unisphere Online Help for detailed instructions on how to configure and enable an eVASA container on the PowerMax array.

Viewing Dell EMC eVASA Provider for PowerMax configuration

Steps

1. Log in to vApp Manager and select Configure > VP Configuration.

The following settings are displayed:

VP log file size (MB)

Default value is 64.

VP log level Default value is INFO.

Number of log files to be retained

Default value is 10.

9

Max concurrent connections per session

Default value is 8.

Retain VP certificate

Default value is False. NOTE: For self-signed certificates on multiple vCenter Server appliances, this setting must be set

to True.

SYMAPI debug log Default value is Disabled.

2. To update a configuration value, select a new value and click Set.

NOTE: After updating a configuration value, you must restart ECOM.

eVASA Provider registration

eVASA Provider 9.2.1 supports High Availability using VMware's active-passive HA model. The VASA Provider service running on each guest is independently registered with vCenter. The vCenter uses VASA APIs to configure one of the VASA Provider services as an active provider and the other as a standby provider.

Follow Registering Dell EMC VASA Provider for PowerMax with the vSphere Web Client or vSphere Client to register eVASA Provider.

NOTE:

The VASA Provider URL is https://vApp_host_name:5989/vasa-providers.xml.

This link is also available from the vApp Manager home page of VASA-0 and VASA-1.

The priority value of the Dell EMC VASA Provider for PowerMax is set to 255 and is not configurable.

The VASA Provider must be re-registered if the NAT/Appliance IP is changed or if a C&I, Verify VMAX, or VTOC is

performed on the PowerMax array.

VASA Provider goes offline during a VASA container upgrade.

vVol workflow overview

VASA Provider 9.2.1 supports vVol replication, the array-based replication is policy driven.

A storage container must be created on the primary and secondary site to create a VM with a remote replication policy profile. The primary site container requires that the VASA replication groups are paired with the replication groups that are associated with the secondary site container.

The following topics define different workflows that are required when creating vVol-based replicated Virtual Machines (VM):

Policy Management

About this task

During the creation of a VM, the VM must be associated with a VMware policy. The VMware policy translates into the underlying storage profile that is associated with the VM. The user defines a VMware policy with storage profile values, for example, the service level.

Based on what kind of storage is available in the vVol datastore, it is marked compatible with the VMware profile.

When you select a VMware policy for a VM during creation time, the GUI displays a list of compatible datastores for the VM. You can select any datastore from this list to create a VM.

This section below describes the workflows that are related to VMware policies.

10

Creating a VM Storage Policy

Steps

1. Click Menu > Policies and Profiles > VM Storage Policies.

2. Select Create VM Storage Policy.

3. Enable rules for VMAXvVolProvider storage by selecting:

Policy structure > Datastore specific rules

4. Select the Persistence Capability by selecting the Service Level and Workload NOTE: Workloads are only supported for backwards compatibility. Storage policies should include the Workload attribute

for compliance calculations and should be set to None.

5. Select the Replication tab, choose the Target Fault Domain where the vVols are replicated. Replication Type (Asynchronous) and RPO (300 seconds) are pre-configured and cannot be modified.

6. Click Next, the Storage compatibility page displays the list of policy datastores.

NOTE: Containers or datastores are listed as compatible if the configured vRGs are in either a SOURCE or FAILEDOVER

or INTEST state.

7. Click Next. The Review and finish page is displayed.

8. Select Finish to create the policy.

Storage Policy Component

About this task

A storage policy component describes a single data service, such as replication, that must be provided for the virtual machine.

Steps

1. Click Menu > Policies and Profiles > Storage Policy Components.

2. Click Create Storage Policy Components.

3. Select the vCenter Server instance.

4. Enter a name and description for the policy component.

5. For Category select Replication.

6. Select the Target Fault Domain where the vVols are replicated. Replication Type(Asynchronous) and RPO (300 seconds) are pre-configured and cannot be modified.

7. Click OK.

8. To use this component, add it to the VM Storage Policy under the Replication Tab as described in the Creating a VM Storage Policy section above.

Association

About this task

See the VM creation section on how a policy is associated with a virtual machine.

Update Profile

About this task

The storage profile that is associated with the VMware policy can be updated when required.

Steps

1. Select the policy that must be updated.

2. Click Edit Settings.

11

3. Select the relevant section and update the corresponding values.

4. Click OK to confirm.

VM Creation using the Replication Profile

About this task

A VM storage policy can be assigned to a VM during initial deployment, post deployment, or while performing other VM operations such as cloning or migrating. See the VMware documentation on VM creation for further details.

Steps

1. In the Select storage screen, select the storage policy containing replication capabilities from the VM Storage Policy drop down list.

2. Select the required datastore from the list.

3. Select a Replication Group from the drop drown list.

4. In the Customize Hardware screen under Virtual Hardware expand the New Hard Disk pane and validate the VM storage policy and Replication Group.

5. Complete the wizard to create a replicated vVol VM.

6. After the VM is created, the Summary tab displays Storage policy, Compliance status, and VM Replication Groups.

NOTE: The compliance status for newly created VMs automatically report as compliant once the valid Point-in-Times

are created at the target site. See the VMware guide for more information about compliance, https://docs.vmware.com.

Edit the Storage Policy of a VM

About this task

You can edit the storage policy that was originally applied to VM and apply a newly created policy with replication capabilities and choose a replication group. You can edit the storage policy of the VM to remove the replication and make it non-replicated by applying the storage profile with just persistence capabilities. Refer the VMware documentation on editing the storage policies for a virtual machine.

You can select a single replication group for all objects or select different replication groups for each storage object.

Steps

1. Select the Virtual Machine whose policy requires editing.

2. Select VM Policies > Edit VM Storage Policies. Apply the same storage policy to all the objects of the selected virtual machine or choose Configure per disk to apply a different VM Storage Policy to the VM home object and virtual disks objects.

3. Click CONFIGURE and select the required Replication Group in the Configure VM Replication Groups to apply the same replication to all the objects . Enable the Configure per disk option to choose different Replication Groups for the VM home objects and virtual disks objects.

SRM 8.3 for vVols

About this task

See the VMware documentation on Site Recovery Manager 8.3, https://docs.vmware.com/.

12

Storage configuration

About this task

Before creating the VMware vVol datastore, ensure that there are vVol storage containers that are created on the array. To Create vVol storage containers and Create VASA Replication Groups see the Dell EMC Unisphere for PowerMax Online Help 9.2.1 at https://support.emc.com.

Serviceability

This section contains information about serviceability issues.

Call Homes

In certain scenarios, the VASA Provider issues a Call Home. The table below describes the different Call Home codes, their causes, and possible resolutions.

Table 3. VASA Provider and eVASA Provider Call Homes

Code Description Reason

0x01 VASA Info: VASA Provider started. Generated every time the VP is started.

0x02 VASA Info: VASA Provider shutdown Generated every time the VP is shut down cleanly.

0x03 VASA Error: Postgres server is down. Generated when the postgres server becomes inaccessible.

0x04 VASA Error: Database LUN failed to mount. Generated when the postgres server fails to find the mounted database path.

Possible corrective action: Check whether the DB LUN has been mounted. If not, mount a DB LUN using the vApp Manager UI.

0x05 VASA Error: Database initialization failed due to some unknown error.

Generated when the database server has started but the initialization failed.

Possible corrective action: Check if another process is using port 5432. Try to restart the VP if the error in the udb.log suggests a timeout.

0x06 VASA Error: Gate keeper devices not found. Generated when the VP fails to find mapped gate keepers.

Possible corrective action: Add gate keepers from the vApp Manager.

0x07 VASA Error: VASA Provider initialization failed. Generated when the VP failed during initialization.

Possible Corrective action: See the Error Code 0x07 Resolution Table below for more details.

0x08 VASA Error: VASA Provider restarted after crash.

Generated when the VP restarts after an unclean shutdown. If the core file is generated, it must be analyzed to understand the reason for the unclean shutdown.

0x09 VASA Error: Database LUN Error. Generated when there is a problem that is associated with access to the mounted DB LUN. This could be a device error or a loss of access.

0x0A VASA Info: Database recovery initiated. Generated when VP information is being recovered from the array.

0x0B VASA Error: Database recovery failed. Generated when there is a failure during recovery of VP information from the array.

13

Table 3. VASA Provider and eVASA Provider Call Homes (continued)

Code Description Reason

0X0C VASA Info: Database recovery completed. Generated when VP information is successfully recovered from the array.

0x0D VASA Warning: Database partially recovered. Generated when VP information is recovered from the array but there was a problem when storing it into the VP DB.

0x0E VASA Error: SFS I/O Failed. Generated when there is a failure while reading or writing metadata to the array.

0X0F VASA Error: MDP I/O failed. Generated when the saving of vVol metadata fails.

0X10 VASA Info: Snapshot operation timed out. Generated when a snapshot operation fails because it exceeded the timeout.

Possible corrective action: Retry the snapshot operation.

0x11 VASA Info: Number of snapshots exceeded for a vVol.

Generated when the snapshot limit for a virtual volume has been exceeded.

0x12 VASA Info: Number of fast clones exceeded for a vVol.

Generated when the fast clone limit for a virtual volume has been exceeded.

0x13 VASA Error: Disk going out of space. Generated when the disk usage on the VP goes beyond the threshold.

0x14 VASA Error: VASA Provider VM running on low memory.

Generated when the memory usage on the VP goes beyond the threshold.

Possible corrective action: Restart VP.

See SFA 488138: https://support.emc.com/kb/488138

0x15 VASA Error: VASA Provider is offline. The VASA Provider keeps sending a heartbeat to the uCode. When the uCode detects a missed heartbeat from the VASA Provider for two iterations, it generates the call home error 7A5A.15.

0x15 VASA Error: VASA Replication Group partitioned.

Generated when the Replication Group is in a partitioned state as VMs are not protected.

0x16 VASA Info: Replication Group RDF session activated.

Generated when the Replication Group is activated. Indicates an RDF session is running between the R1 and R2.

0x17 VASA Info: VASA Provider is activated. Generated when VASA Provider is activated.

Table 4. Error Code 0x07 Resolutions

Possible cause Possible corrective action

Failure to discover the array. Map GK devices using vApp UI and restart VP.

Invalid/empty array ID. Map GK devices using vApp UI and restart VP.

Failure to initialize Provider object in Database. Check disk usage. Restart VP.

Failure to initialize threads. Restart VP.

Failure to initialize capability metadata. Restart VP.

Failure to initialize capability profiles. Restart VP.

Failure to create event subjects . Restart VP.

14

Knowledge Base articles

The full list of Knowledge Base articles for VASA Provider for PowerMax is available on www.dell.com. The latest articles are listed below:

000521733 - Describes the removal of workloads in PowerMaxOS 5978. 000519712 - Describes the failure to authenticate a request from the vCenter when the request is signed by the intermediate

CA in the list of certificates. 000511602 - Describes a possible security vulnerability in some VP versions.

Configuration options

ECOM is the web server that is used by the PowerMax VP. This section describes the configuration options available to you when using the ECOM configuration page to manage the VP appliance. Only those configuration options that are relevant to the VP are described.

ECOMConfig options

Launch the ECOM configuration page by using the URL https:// :5989/ECOMConfig/ The default user credentials are admin/#1Password.

On successful login, the main page is displayed. You can use this page to go to the area you are interested in. This section covers some of the most frequently used options.

Multi-vCenter configuration

VASA Provider can be configured with multiple vCenters as follows: 1. Enable the VASA Provider setting RETAIN_VP_CERTIFICATE in the vApp Manager by setting the value to TRUE.

2. Generate the self-signed certificate as per the Self-Signed Certificate section of this document. 3. Register the VASA Provider with all the vCenters that are going to use the storage array the VASA Provider is managing.

NOTE: If the VASA provider is already registered with one vCenter and the user intends to register it multiple

vCenters, the VASA Provider must be de-registered from the first vCenter and follow the above steps to complete

the configuration.

Logging

This section allows you to view the VP logs and to change the log levels for the VP appliance.

The log settings have the following meanings:

CIMOMLOG: Logs the messages from the ECOM server SECURITYLOG: Logs authentication messages from the ECOM server HTTP_TRACE_LOG: Logs the HTTP traffic to and from the ECOM server

Security settings:

User management

The following settings are used to manage ECOM users:

Add User: Allows creation of a new user Modify User: Allows changes to be made to an existing user Change Password: Allows a password change for an existing user Set Password Quality: Allows setting the parameters for the user password Delete User: Allows deletion of a user List Users: Allows listing of the users in the system

15

SSL certificate management

This option can be used to create an ECOM certificate and allows you to perform the following actions:

Generate a CSR. Import a signed certificate. Generate a self-signed certificate. Import a CA certificate file.

Certificates

This section describes the different types of certificates that the VP supports.

By default the VP has a self-signed certificate that is overwritten by a VMCA certificate during the registration process. This behavior is defined by the RETAIN_VP_CERTIFICATE flag that is defined in the vApp Manager configuration. RETAIN_VP_CERTIFICATE is FALSE by default. When enabled, the existing VASA Provider certificate is not overwritten. For more information, see the Virtual Appliance Manager Installation Guide on https://support.emc.com.

Self-signed certificate

The default self-signed certificate that is created by ECOM cannot be used when the RETAIN_VP_CERTIFICATE flag is set to TRUE. IN order to use self-signed certificate, the ESXi servers require the extension CertificateSign to be present in the keyUsage for the self-signed certificate.

Set this flag in the KeyUsage while creating the self-signed certificate. Follow the steps below to create and use the self-signed certificate.

1. Change RETAIN_VP_CERTIFICATE to TRUE in VASA Provider.

2. Log in to the ECOM Config page (https:// :5989 for ecomconfig), go to SSL Certificate Management and then click Option #2 Generate Self-Signed Certificate.

3. The Self-Signed Certificate page is displayed, enter the following details: Common Name : Country : State: Locality: Organization name: Organization Unit name: Serial Number: SAN Email Address: SAN IP: SAN URI: Key Usage: DigitalSignature;NonRepudiation;KeyEncipherment;KeyAgreement;EncipherOnly;DecipherOnly;CertificateSign CA

4. Click Generate a Self-Signed Certificate. 5. Restart ECOM. 6. Register VASA Provider. If it is already registered, unregister and register it again.

The ECOM default value for the Key Usage field is: DigitalSignature;NonRepudiation;KeyEncipherment;DataEncipherment;KeyAgreement;CertificateSi gn;CRLSign;EncipherOnly;DecipherOnly.

The VASA default value for the Key Usage field is: DigitalSignature;NonRepudiation;KeyEncipherment;KeyAgreement;EncipherOnly;DecipherOnly.

CA certificate

To use the CA certificate in the VP environment, the RETAIN_VP_CERTIFICATE flag should be unset (marked FALSE).

In this scenario, at VP registration time, the vCenter ignores the certificate that is sent by the VP and sends the vCenter certificate as the new certificate. This certificate is stored by the VP for all future handshakes.

16

Self-Signed Certificate on multiple vCenter appliances

When a VASA Provider is registered with a vCenter, the following actions take place: 1. VASA Provider presents the vCenter with a self-signed certificate. The vSphere user validates the thumbprint and accepts

the certificate. 2. After the validation, VASA Provider sends a CSR with its public key. 3. vCenter responds with a VMCA signed certificate that is stored in the VASA Provider trust store.

NOTE: The above steps are only applicable when using a VMCA as certificate authority.

VASA Provider uses VMCA signed certificates to communicate with ESX and vCenter servers. This works because all the

components (vCenter/ESX/VP) use VMCA signed certificates.

In a multi-vCenter environment, when a VP is registered with the first vCenter the steps mentioned above are performed and VP receives a VMCA certificate from the first vCenter. When the same VASA Provider is registered again with second vCenter, and if the RETAIN_VP_CERTIFICATE flag is set to false (not enabled) then the certificate is overwritten and the communication with the first vCenter is broken and only second vCenter communicates with VASA Provider.

If the RETAIN VP CERTIFICATE flag is set to true, this makes sure that the VP trust store is not overwritten, hence the communication with first vCenter is not broken, but communication with second vCenter will not be established.

If user wants to use both vCenters, there are two options: 1. A common VMCA is required, where both vCenters are part of a common VMCA. 2. Use Self Signed Certificate along with the extension CertificateSign to be present in the keyUsage (In this case the RETAIN

VP CERTIFICATE flag must be set to true).

The VMCA can be deployed as a standalone or as a subordinate to another CA. If both vCenters use a standalone VMCA, the configuration is not supported because they are two different CA instances and the VP can retain only one.

17

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

Manualsnet FAQs

If you want to find out how the EMC Dell works, you can view and download the Dell EMC VMAX 100K V9.2.1 Storage Product Guide on the Manualsnet website.

Yes, we have the Product Guide for Dell EMC as well as other Dell manuals. All you need to do is to use our search bar and find the user manual that you are looking for.

The Product Guide should include all the details that are needed to use a Dell EMC. Full manuals and user guide PDFs can be downloaded from Manualsnet.com.

The best way to navigate the Dell EMC VMAX 100K V9.2.1 Storage Product Guide is by checking the Table of Contents at the top of the page where available. This allows you to navigate a manual by jumping to the section you are looking for.

This Dell EMC VMAX 100K V9.2.1 Storage Product Guide consists of sections like Table of Contents, to name a few. For easier navigation, use the Table of Contents in the upper left corner.

You can download Dell EMC VMAX 100K V9.2.1 Storage Product Guide free of charge simply by clicking the “download” button in the upper right corner of any manuals page. This feature allows you to download any manual in a couple of seconds and is generally in PDF format. You can also save a manual for later by adding it to your saved documents in the user profile.

To be able to print Dell EMC VMAX 100K V9.2.1 Storage Product Guide, simply download the document to your computer. Once downloaded, open the PDF file and print the Dell EMC VMAX 100K V9.2.1 Storage Product Guide as you would any other document. This can usually be achieved by clicking on “File” and then “Print” from the menu bar.