HPE 3PAR

Introduction

HPE 3PAR StoreServ Storage is a family of flash-optimized storage systems that offer automated provisioning. This offers an advanced storage solution that uses a multi-tenant ability that distributes the load dynamically depending on the requirements set by each tenant. In addition, this single tier-1 storage system architecture is designed for in-built data security and availability.

HPE 3PAR StoreServ Storage regulates and manages itself. The rate at which the storage resources are consumed is constantly monitored. Compaction technologies such as thin provisioning, thin deduplication, and thin reclamation are incorporated and fully automated in HPE 3PAR StoreServ Storage systems. Thin provisioning allows a volume to be created and made available as a Logical Unit Number (LUN) to a host without the need to dedicate physical storage until it is actually needed.

HPE 3PAR StoreServ Storage systems include hardware components that physically store your data and software applications that manage your data.

The HPE 3PAR StoreServ Storage system is composed of the following logical data layers:

• Physical Disk (PD)
• Chunklet
• Logical Disk (LD)
• Common Provisioning Group (CPG)
• Virtual Volume (VV)

Hierarchy of HPE 3PAR resources:

HPE 3PAR Storage System
   - HPE 3PAR Common Provisioning Group
     - HPE 3PAR Storage Volume
       - HPE 3PAR VLUN
      - HPE 3PAR Physical Disk
      - HPE 3PAR Host
            - HPE 3PAR Port
                 - HPE 3PAR Port Device
                 - HPE 3PAR FC Switch

Prerequisites

• The OpsRamp Gateway must be installed.
• Provided IpAddress/hostname, credentials should work for both WS APIs and SSH communication.

Configure and install the integration

1. Go to Setup > Integrations and Apps.
2. Click + ADD on the INSTALLED APP page. The ADD APP page displays all the available applications along with the newly created application with the version.
   Notes:
   • If there are already installed applications, it will redirect to the INSTALLED APPS page, where all the installed applications are displayed.
   • If there are no installed applications, it will navigate to the ADD APP page.
   • You can even search for the application using the search option available. Also you can use the All Categories option to search.

3. Click ADD in the HPE 3PAR application.
4. In the Configurations page, click + ADD. The Add Configuration page appears.
5. Enter the below mentioned BASIC INFORMATION:

Notes:

• By default the Is Secure checkbox is selected.
• 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/Alert Polling: enables integrating third party alerts into OpsRamp using further configurations.
• Below are the default values set for:
  • Event/Alert Severity Filter: provides severity alerts and gets integrated out of all possible alerts.
    • Default Values: FATAL,CRITICAL, MAJOR, MINOR.
    • Possible Values: FATAL, CRITICAL, MAJOR, MINOR, DEGRADED, INFORMATIONAL, DEBUG, UNKNOWN.
  • Event Category: only provides category alerts that are generated out of possible values.
    • Category 1 is used to identify a lifecycle.
    • Category 2 is used to identify an alert.
    • Possible values of Event Category configuration property are 1,2.
  • Event/Alert Severity Mapping: enables you to map the severities between HPE 3PAR and OpsRamp as severities are predefined values in each system.
    • Default mappings: “FATAL”:“Critical”,“CRITICAL”:“Critical”,“MAJOR”:“Warning”,“MINOR”:“Warning”,
      “DEGRADED”:“Warning”,“INFORMATIONAL”:“Info”,“DEBUG”:“Info”,“UNKNOWN”:“Info”.
      Note: You can change it as per your business use cases at any point in time from the Configuration page.

6. 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.

7. In the DISCOVERY SCHEDULE section, select Recurrence Pattern to add one of the following patterns:

   • Minutes
   • Hourly
   • Daily
   • Weekly
   • Monthly

8. Click ADD.
   

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

10. Click NEXT

11. In the Installation page, select an existing registered gateway profile, and click FINISH.

The application 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 HPE 3PAR application.

View the HPE 3PAR details

The HPE 3PAR integration is displayed in the Infrastructure > Resources > Storage.

Supported metrics

Risks, Limitations & Assumptions

• Application can handle Critical/Recovery failure notifications for below two cases when user enables App Failure Notifications in configuration:
  • Connectivity Exception
  • Authentication Exception
• Application uses the provided IpAddress/hostname, credentials for both WSAPIs and SSH communications.
• Application will not send any duplicate/repeat failure alert notification until the already existing critical alert is recovered.
• Application cannot control monitoring pause/resume actions based on above alerts.
• Metrics can be used to monitor HPE 3PAR resources and generate alerts based on the threshold values.
• OpsRamp refers to HPE Support developer guide to implement discovery, monitoring and alerts polling of HPE 3PAR. Given that support to show disk information was added in WSAPI 1.6.15 release, OpsRamp uses Physical disk statistical data reports API when the WSAPI version is less than 1.6.15. For version greater than or equals to 1.6.15, OpsRamp uses Querying physical disk information API to get data.
  Note: Currently, there is no reference of Fan Speed, Temperature, Power related metrics within the developer guide.
• As few of the HPE 3PAR components didn’t have direct name information in WSAPI responses, OpsRamp proceeded with below assumptions :
  • For Physical Disk Discovery, OpsRamp considered Physical disk ID (if WSAPI version is less than 1.6.15) OR WWN (if WSAPI version is greater than or equals to 1.6.15) as Resource Name in OpsRamp.
  • For Ports Discovery, OpsRamp considered portWWN (Port WWN presents for FCoE and FC ports only) OR port portPos (when portWWN was not present in response) as Resource Name in OpsRamp.
  • For VLUN Discovery, OpsRamp considered lun value as Resource Name in OpsRamp.
• HPE 3PAR’s Event/Alert Polling starts only if the user enables Event/Alert Polling in configuration.
• Possible values of Event/Alert Severity Filter configuration property are FATAL, CRITICAL, MAJOR, MINOR, DEGRADED, INFORMATIONAL, DEBUG, UNKNOWN.
• Possible values of Event Category configuration property are 1,2. Category 1 is used to identify a lifecycle event and 2 is used to identify an alert.
• OpsRamp has given sample mappings to map HPE 3PAR Severity with OpsRamp Severities as part of the Event/Alert Severity Mapping configuration file. 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.
• In referred HPE 3PAR developer guides, There is no information about how Logged system events are getting resolved, hence OpsRamp has not included polled events/alerts recovery mechanism.
• No support of showing activity log and applied time.
• No support for the option to get Latest snapshot metric.