Dell PowerMax

Application Version Details

Introduction

Dell EMC PowerMax is the platform, which offers massive scalability in every possible dimension — performance, capacity, connectivity, LUNs/devices and superior data services — all with a future-proof architecture featuring end-to-end non-volatile memory express (NVMe), storage class memory (SCM), built-in machine learning, seamless cloud mobility and deep VMware integration.

OpsRamp integrates with Dell PowerMax through REST APIs.

Prerequisites

• OpsRamp Classic Gateway 14.0.0 and above.
• OpsRamp Nextgen Gateway 14.0.0 and above.
  Note: OpsRamp recommends using the latest Gateway version for full coverage of Recent bug fixes, enhancements, etc.

Application Migration

1. Check for the gateway version as a prerequisite step - classic gateway-12.0.1 and above.
   Notes:

   • You only have to follow these steps when you want to migrate from sdk 1.0 to sdk 2.0.
   • For the first time installation below steps are not required.

2. Disable all configurations associated with sdk 1.0 adaptor integration application.

3. Install and Add the configuration to that sdk 2.0 application.
   Note: refer to Configure and Install the Dell PowerMax Integration & View the Dell Power Max Details sections of this document.

4. Once all discoveries are completed with the sdk 2.0 application, follow any one of the approaches.

   • Direct uninstallation of the sdk 1.0 adaptor application through the uninstall API with skipDeleteResources=true in the post request
     
     End-Point: https://{{host}}/api/v2/tenants/{tenantId}/integrations/installed/{installedIntgId}
     
     Request Body:

         {
         "uninstallReason": "Test",
         "skipDeleteResources": true
         }

     
     
     (OR)
     
     
   • Delete the configuration one by one through the Delete adaptor config API with the request parameter as skipDeleteResources=true
     
     End-Point: https://{{host}}/api/v2/tenants/{tenantId}/integrations/installed/config/{configId}?skipDeleteResources=true.
     
     
   • Finally, uninstall the adaptor application through API with skipDeleteResources=true in the post request.
     
     End-Point: https://{{host}}/api/v2/tenants/{tenantId}/integrations/installed/{installedIntgId}
     
     Request Body:

         {
         "uninstallReason": "Test",
         "skipDeleteResources": true
          }

Roles and Permissions

• Monitor role user is required to fetch discovery and monitoring related data.
• Symmetric Array has to be registered for statistics.

Hierarchy of Dell Power Max Resources

    • PowerMax Unisphere

           • PowerMax Storage Array

                  • PowerMax Storage Group
                  • PowerMax Storage Port Group
                  • PowerMax Storage Host
                  • PowerMax Storage Resource Pool
                  • PowerMax Storage FE Director
                           • PowerMax Storage FE Port
                  • PowerMax Storage BE Director
                           • PowerMax Storage BE Port
                  • PowerMax Storage RDF Director
                  • PowerMax Storage Disk Group
                  • PowerMax Array External Directors
                  • PowerMax Storage Container

Default Monitoring Configurations

Dell Power Max have default Global Device Management Policies, Global Templates, Global Monitors and Global metrics in OpsRamp. Users can customize these default monitoring configurations as per your business use cases by cloning respective Global Templates and Global Device Management Policies. OpsRamp recommends doing this activity before installing the application to avoid noise alerts and data.

1. Default Global Device Management Policies

   OpsRamp has a Global Device Management Policy for each Native Type of Power Max. You can find those Device Management Policies at Setup > Resources > Device Management Policies, search with suggested names in global scope. Each Device Management Policy follows below naming convention:

   {appName nativeType - version}

   Ex: dell-power-max PowerMax Unisphere - 2(i.e, appName = dell-power-max, nativeType = PowerMax Unisphere , version = 2)

2. Default Global Templates

   OpsRamp has a Global template for each Native Type of Power Max. You can find those templates at Setup > Monitoring > Templates, search with suggested names in global scope. Each template follows below naming convention:

   {appName nativeType 'Template' - version}

   Ex: dell-power-max PowerMax Unisphere Template - 2 (i.e, appName = dell-power-max, nativeType = PowerMax Unisphere, version = 2)

3. Default Global Monitors

   OpsRamp has a Global Monitors for each Native Type which has monitoring support. You can find those monitors at Setup > Monitoring > Monitors, search with suggested names in global scope. Each Monitors follows below naming convention:

   {monitorKey appName nativeType - version}

   Ex: PowerMax Storage Array Monitor dell-power-max PowerMax Storage Array - 2 (i.e, monitorKey =PowerMax Storage Array Monitor, appName = dell-power-max, nativeType = PowerMax Storage Array , version = 2)

Configure and Install the Dell PowerMax Integration

1. From All Clients, select a client.
2. Go to Setup > Integrations and Apps.
3. The INSTALLED INTEGRATIONS page, where all the installed applications are displayed.
   Note: If there are no installed applications, it will navigate to the ADD APP page.

4. Click + ADD on the INSTALLED INTEGRATIONS page. The AVAILABLE INTEGRATIONS AND APPS page displays all the available applications along with the newly created application with the version.
   Note: You can even search for the application using the search option available. Also you can use the All Categories option to search.

5. Click ADD in the Dell Power Max application.
6. In the Configurations page, click + ADD. The Add Configuration page appears.
7. Enter the below mentioned BASIC INFORMATION:

Notes:

• By default the Is Secure checkbox is selected.
• Ip Address/Host Name and Port should be accessible from Gateway.
• Select the following:
  • App Failure Notifications: if turned on, you will be notified in case of an application failure that is, Connectivity Exception, Authentication Exception.
  • Event Polling: enables integrating third party alerts into OpsRamp using further configurations.
    • Once Event Polling is enabled, we can see below fields with mentioned default values:
      • Alert Severity Filter: Provides alerts severity and gets integrated out of all possible alerts.
        • Default Values: NORMAL, INFORMATION, MINOR, WARNING, CRITICAL, FATAL.
        • Possible Values: FATAL, CRITICAL, MAJOR, MINOR, DEGRADED, INFORMATIONAL, DEBUG, UNKNOWN.
      • Alert Cleared Status: Provides alert cleared status. Default values for Event/Alert Cleared Status configuration property are “ACKNOWLEDGED”,“CLEARED”.
  • Alert On Root Resource: Checking this will generate event polling alerts on root resource.
    • Alert Severity Mapping: Provides alert severity mapping configuration. Default values for Alert Severity Mapping configuration are * \ {“NORMAL”:“Info”,“INFORMATION”:“Info”, “MINOR”:“Warning”,“WARNING”:“Warning”,“CRITICAL”:“Critical”,“FATAL”:“Critical”}*.
  • API Timeouts: These are the maximum API Timeouts that the application can use to connect and get responses from the end device.
    • Connection Timeout in Secs: a time period in which a client should establish a connection with a server.
      Note: By default, 60 is selected.
    • Connection Request Timeout in Secs: a time period required to process an HTTP call: from sending a request to receiving a response.
      Note: By default, 10 is selected.
    • Socket Timeout in Secs: a maximum time of inactivity between two data packets when exchanging data with a server.
      Note: By default, 10 is selected.

8. Select the below mentioned Custom Attribute:

Note: The custom attribute that you add here will be assigned to all the resources that are created by the integration. You can add a maximum of five custom attributes (key and value pair).

9. In the RESOURCE TYPE section, select:
   • ALL: All the existing and future resources will be discovered.
   • SELECT: You can select one or multiple resources to be discovered.
10. In the DISCOVERY SCHEDULE section, select Recurrence Pattern to add one of the following patterns:
    • Minutes
    • Hourly
    • Daily
    • Weekly
    • Monthly
11. Click ADD.
    

Now the configuration is saved and displayed on the configurations page after you save it. From the same page, you may Edit and Remove the created configuration.

12. Click NEXT.
13. Below are the optional steps you can perform on the Installation page.

• Under the ADVANCED SETTINGS, Select the Bypass Resource Reconciliation option, if you wish to bypass resource reconciliation when encountering the same resources discovered by multiple applications.

  Note: If two different applications provide identical discovery attributes, two separate resources will be generated with those respective attributes from the individual discoveries.

• Click +ADD to create a new collector by providing a name or use the pre-populated name.

14. Select an existing registered profile.

15. Click FINISH.

The integration is now installed and displayed on the INSTALLED INTEGRATION page. Use the search field to find the installed application.

Modify the Configuration

• See Modify an Installed Integration or Application article.

  Note: Select the Dell Power Max application.

View the Dell Power Max Details

The Dell Power Max integration is displayed in the Infrastructure > Resources > Storage. You can navigate to the Attributes tab to view the discovery details, and Metrics tab to view the metric details for Dell Power Max.

PowerMax Storage Array (Native Resource Type) is displayed under Components:

View Resource Metrics

To confirm Dell PowerMax monitoring, review the following:

• Metric graphs: A graph is plotted for each metric that is enabled in the configuration.
• Alerts: Alerts are generated for metrics that are configured as defined for integration.

Resource Filter Input Keys

Dell Power Store application Resources are filtered and discovered based on few resource attributes.

Supported Alert Custom Macros

Customize the alert subject and description with below macros then it will generate alert based on customisation. Supported macros keys:

Supported Metrics

Risks, Limitations & Assumptions

• Application can handle Critical/Recovery failure alert notifications for below two cases when user enables App Failure Notifications in configuration
  • Connectivity Exception
  • Authentication Exception
• Application will not send any duplicate/repeat failure alert notification until the already existed critical alert is recovered.
• Application cannot control monitoring pause/resume actions based on above alerts. Metrics can be used to monitor PowerMax resources and can generate alerts based on the threshold values.
• OpsRamp has provided 443 as default Port value for processing Power max Rest APIs. Users can modify this value from the application configuration page at any point of time if required.
• Power max Event/Alert polling will be started only if the user enables Event Polling in configuration. Possible values of Alert Severity Filter configuration are “NORMAL”,“INFORMATION”,“MINOR”,“WARNING”,“CRITICAL”,“FATAL”. Based on these values alerts will be filtered and users can customize this at any point of time.
• OpsRamp has provided default mappings to map Power max Severity with OpsRamp Severities as part of Alert Severity Mapping configuration. Users can modify them as per their use-case at any point of time from the application configuration page. Possible OpsRamp Severities are Critical, Warning, Ok, Info. Below is the default severity mapping in configuration:
  • {“NORMAL”:“Warning”,“INFORMATION”:“Info”,“MINOR”:“Warning”,“WARNING”
    :“Warning”,“CRITICAL”:“Critical”,“FATAL”:“Critical”}
• In Alert polling, by default alerts are raised on root resource. Users can populate the alert on its actual resource by unchecking the Alert on root Resource checkbox. Users can also mention possible alert cleared status. We consider “ACKNOWLEDGED” and “CLEARED” status as default.
• No support of displaying activity log and applied time.
• This application supports both Classic Gateway and NextGen Gateway
• We are fetching version information using api {}://{}:{}/univmax/restapi/version.
  • For all the 9 versions (i.e V9.x.x) we are appending 91 as a prefix in endpoints ({}://{}:{}/univmax/restapi/91/system/symmetrix).
  • For version 10.0 (V10.0.x) we are using 100 as prefix ({}://{}:{}/univmax/restapi/100/system/symmetrix).
• PowerMax Storage BE Port and PowerMax Array External Directors are no longer supported in version 4 symmetric Arrays.
• Performance data cannot be captured on remote arrays as APIs cannot fetch its performance data using PowerMax Unisphere IP Address.