Creating a New Discovery Instance
You must create one discovery instance for each EMC Unisphere for PowerMax that you want to discover. For each Unisphere instance, you can choose to subscribe IO to all PowerMax arrays (and their relationships) or you can subscribe to a subset of the PowerMax arrays that are monitored by the Unisphere instance.
About This Task
The PowerMax array used in a IO configuration must be in a local Unisphere configuration (see Dell EMC documentation for details).
After you configure and subscribe to the integration instance, IO adjusts the appropriate Wisdom Pack license count to reflect additional license consumption.
PowerMax Integration license consumption is based on the number front‐end directors associated with the Unisphere host.
Important
If you have more than one Unisphere management tool monitoring your PowerMax storage arrays, make sure that you only subscribe to a PowerMax array from one of the Unisphere instances. Subscribing to the same PowerMax array from more than one Unisphere results in modeling and metric collection problems.
Prerequisites
An EMC Unisphere for PowerMax REST API user and password must be configured and available. The REST API user must be assigned a role with a minimum of “monitor” or “perfmonitor” privileges. You can assign roles with the proper privileges from the EMC Unisphere for PowerMax interface.
Steps
From the Settings page, click Integrations in the Probes and Integrations section.
Click View for the licensed integration you want to configure.
If this is an initial configuration: You are directed to the New Integration page to configure the first integration.
If there are existing configurations: The Integration page opens, displaying a list of all existing licensed and unlicensed configurations.
Complete the connection details so Virtana Infrastructure Observability can collect metrics from the device.
Enter the device hostname or IP address.
Optional: A description to identify your configured instance.
Optional: Enter the IP port number.
Default is 8443
Enter a username and password for device access.
Optional: Select an SSL certificate.See below for more information about SSL certificate handling.
Select a Metrics Polling Interval.
Options are 5, 10, 15, or 30 minutes, 1 hour 2 hours. The default is 15 minutes.
Important
Data is always collected at 5-minute granularity. Longer poll intervals optimize collection and reduce load on the Unisphere server by collecting more data points in a single call. See metric collection section for more details.
Click Next.
Optional: Enable scheduled discovery and select the discovery Frequency and Start Time.
Click the Arrays tab.
Click the checkbox next to one or more storage arrays and then click Subscribe.
You can only subscribe to local arrays.
The Status column changes from Unsubscribed to Subscribed.
Click Save.
Click the PowerMax Directors tab and verify that the correct number of front‐end directors displays in the list.
There should be at least two directors shown for a high availability PowerMax configuration.
You can start discovery now, or wait to start at a later time.
When discovery starts, status information displays under Collection Status on the Configuration page.
If possible, the first metrics collection cycle backfills up to 2 hours' worth of metric data to provide quicker access to the collected metrics.
SSL Certificate Handling
This integration requires a secure connection to the target device, which can be achieved automatically if the device has a certificate that has been signed by a root certificate authority. If this is the case, you may complete the form and click the Next button to proceed to the next page of the configuration.
If your device does not have a properly signed certificate, you may associate a certificate (for example, a self-signed certificate) with the device using one of the two following methods.
Automatically fetch the certificate from the target system. A valid IP address and port number are required.
Upload the certificate from your local system. Please note: at this time, certificates must be in PEM (plain text) format.
The first page of an integration configuration might look something like this:
Note
SSL Certificate might called something different depending on the integration being configured. The Subject, Issued By, and Expires On fields are initially blank, which means that there is currently no stored certificate. This is also the case when connecting to a system with a certificate issued by a root certificate authority.
Some integrations with per-device configurations, the SSL certificate controls are seen when adding a new device. The functionality of the control is the same regardless.
Using Verify to Automatically Fetch a Certificate
Clicking on the Verify button will trigger an action that will automatically fetch the certificate from the target system. There are two cases:
If the fetched certificate has been signed by a valid root certificate authority you will see a popup window with the details of the certificate as shown below. Press OK to continue configuration. Note: properly signed certificates will not be stored locally and the Subject, Issued By, and Expires On fields will remain empty. Fill in the Name and authentication fields and click the Next button in the upper right hand corner of the screen.
If the fetched certificate is, for example, a self-signed certificate, you will see a popup window with the details of the certificate as shown below. You may either Accept and Trust the retrieved certificate or you may Cancel. If you accept, the Subject, Issued By, and Expires On fields will be updated with a summary of the issuing authority and you may continue configuring the integration. Fill in the Name and authentication fields and click the Next button in the upper right hand corner of the screen.
Uploading a Certificate
Clicking on the Browse... button will prompt you to upload a certificate from your local system. Once uploaded, you'll see a popup window with the details of the certificate as shown below. You may either Accept and Trust the retrieved certificate or you may Cancel. If you accept, the Subject, Issued By, and Expires On fields will be updated with a summary of the issuing authority and you may continue configuring the integration. Fill in the Name and authentication fields and click the Next button in the upper right hand corner of the screen.
It's a good idea to validate the uploaded certificate by clicking on the Verify button.
Viewing the Locally Stored Copy of a Certificate
Click on the View button to display the contents of the locally stored certificate.
Removing a Locally Stored Copy of a Certificate
Click on the Clear button to remove the locally stored copy of your certificate if, for example, you have updated your system certificate with one that is signed by a root certificate authority.