Dell EMC PowerMax

Simplify monitoring of your PowerMax infrastructure. Focus on essential insights into your PowerMax arrays.

This extension is intended for users, who:

• Run their workloads on Dell PowerMax, for v3 and v4 hardware versions.
• Want to extend Dynatrace insights into the storage infrastructure on which workloads depend.

This extension enables you to:

• Monitor your PowerMax arrays using a PowerMax-specific entity model and comprehensive unified analysis views.
• Receive alerts on performance and health issues detected in your PowerMax infrastructure.
• Take proactive actions based on anomalies detected in PowerMax infrastructure before they affect your applications.

• Operational monitoring of your PowerMax array using Unisphere API in Dynatrace, integrated with related insights into the infrastructure and apps that utilize your PowerMax array.
• Monitor resource utilization and receive alerts for detected anomalies.

The PowerMax extension runs on a Dynatrace ActiveGate and connects to the Dell Unisphere APIs.

Activate the extension in your environment via the in-product Hub, then provide the PowerMax connection and a user account to connect to Unisphere APIs.

SSL Configuration

In order to enable SSL communication between the Activegate and the Unisphere server, the CA certificate from the Unisphere server must be extracted and placed on the Activegate.

The following command can be used to get the CA certificate of the Unisphere server:

$ openssl s_client -showcerts -connect {server_hostname}:8443 \
</dev/null 2>/dev/null|openssl x509 -outform PEM > {cert_name}.pem

This PEM key file will need to be placed on any ActiveGate that is running the extension, in a location that is accessible to the extension. The recommended default location for the PEM file is:

• Linux:

  <CONFIG>/remotepluginmodule/agent/conf/certificates/
  (default: /var/lib/dynatrace/remotepluginmodule/agent/conf/certificates/)
  

• Windows:

  %PROGRAMDATA%\dynatrace\remotepluginmodule\agent\conf\certificates
  

Read more about Extensions 2.0 operations in Dynatrace Documentation.

The extension package contains:

• Python scripts that implement the metric ingestion from the Dell Unisphere API, using a pull model
• Topology and relationship definitions for physical and logical entities that comprise the PowerMax platform
• A sample dashboard offering the PowerMax monitoring overview and status
• Unified analysis views for each entity, leveraging the topology model for interactive analysis

Summary of the PowerMax entities monitored:

The PowerMax extension collects metrics for PowerMax entities and builds topological relationships between them so that Dynatrace performance analytics can leverage causal dependencies and surface the root causes of issues. The following entities are monitored:

• Array
• Storage Resource Pool (SRP)
• Disk Group
• Storage Group
• Host
• Board
• BE Director
• FE Director
• RDF Director
• EDS Director
• IM Director
• EM Director
• RDFA
• System
• Volumes

• A Dell PowerMax array connected to the Unisphere API, reachable from an ActiveGate set up in your Dynatrace environment.
• Unisphere API connection details: Unisphere IP, username, password, array id, and key file for authentication with the Unisphere API.
• The Unisphere versions required are from 10.1.0.0, up to 10.1.0.2.
• Two dashboards are available on the Dynatrace portal, one for each supported hardware version. Please select the one compatible with the monitored array.

Q: What is the DDU Consumption of this extension?

A: The formula for DDU consumption of the extension is:

  ( ( 40 * number of Arrays)
+ ( ( 10 * number of Hosts)
+ ( ( 4 * number of Boards)
+ ( ( 9 * number of BE Directors)
+ ( ( 1 * number of EDS Directors)
+ ( ( 10 * number of FE Directors)
+ ( ( 3 * number of IM Directors)
+ ( ( 9 * number of RDF Directors)
+ ( ( 5 * number of SRPs)
+ ( ( 15 * number of Disk Groups)
+ ( ( 26 * number of Storage Groups)
+ ( ( 4 * number of Volumes)
+ ( 9 ) * 525.6 DDUs/year

DDU cost above does not include any possible Log events or Custom events triggered by the extension. For more information on this, please visit the DDU log event cost and DDU custom event cost pages.