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)

Supported Target Versions

Prerequisites

• OpsRamp Classic Gateway(Linux) 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..
• Make sure the WSAPI Server State is ‘Active’ on HPE 3PAR. You may use the following commands to confirm the same:
  • CLI Command to view WSAPI Server Configuration is showwsapi - d
  • CLI Command to start the WSAPI Server is startwsapi
• Provided IpAddress/hostname, credentials should work for both WS APIs and SSH communication.

Hierarchy of HPE 3PAR resources:

8x00 series

• 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 Cage
                • HPE 3PAR Node
                       • HPE 3PAR Adapter
                              • HPE 3PAR Port
                       • HPE 3PAR Battery

9x00, 20x00 series

• 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 Cage
        • HPE 3PAR Node
                 • HPE 3PAR Adapter
                         • HPE 3PAR Port
                 • HPE 3PAR Battery

Supported Metrics

Default Monitoring Configurations

HPE 3PAR has default Global Device Management Policies, Global Templates, Global Monitors and Global Metrics in OpsRamp. You can customize these default monitoring configurations as per your business use cases by cloning respective Global Templates and Global Device Management Policies. We recommend doing this activity before installing the application to avoid noise alerts and data.

1. Default Global Device Management Policies

   You can find the Device Management Policy for each Native Type at Setup > Resources > Device Management Policies. Search with suggested name in global scope. Each Device Management Policy follows below naming convention:

   {appName nativeType - version}

   Ex: hpe-3par HPE-3PAR Storage System - 1 (i.e, appName = hpe-3par, nativeType = HPE-3PAR Storage System, version = 1)

2. Default Global Templates

   You can find the Global Templates for each Native Type at Setup > Monitoring > Templates. Search with suggested names in global scope. Each template follows below naming convention:

   {appName nativeType 'Template' - version}

   Ex: hpe-3par HPE-3PAR Storage System Template - 1 (i.e, appName = hpe-3par, nativeType = HPE-3PAR Storage System, version = 1)

3. Default Global Monitors

   You can find the Global Monitors for each Native Type at Setup > Monitoring > Monitors. Search with suggested name in global scope. Each Monitors follows below naming convention:

   {monitorKey appName nativeType - version}

   Ex: HPE-3PAR Storage System Monitor hpe-3par HPE-3PAR Storage System 1(i.e, monitorKey = HPE-3PAR Storage System Monitor, appName = hpe-3par, nativeType = HPE-3PAR Storage System, version = 1)

Configure and Install the HPE 3PAR Integration

1. From All Clients, select a client.
2. Navigate to Setup > Account.
3. Select the Integrations tab.
4. The Installed Integrations page, where all the installed integrations are displayed. Click + ADD on the Installed Integrations page.
5. If you do not have any installed applications, you will be navigated to the Available Integrations page. The Available Integrations page displays all the available applications along with the newly created application with the version.
   Note: Search for the application using the search option available. Alternatively, use the All Categories option to search.
6. Click ADD on the HPE 3PAR tile.
7. In the Configurations page, click + ADD. The Add Configuration page appears.
8. 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/Alert Polling: enables integrating third party alerts into OpsRamp using further configurations.
  • 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.
• 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.

9. 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).

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

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

    • Minutes
    • Hourly
    • Daily
    • Weekly
    • Monthly

12. Click ADD.

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.

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

14. Click NEXT.

15. (Optional) Click +ADD to create a new collector by providing a name or use the pre-populated name.

16. Select an existing registered profile.

17. Click FINISH.

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

Modify the Configuration

• See Modify an Installed Integration or Application article.

  Note: Select HPE 3PAR.

View the HPE 3PAR Details

To discover resources for HPE 3PAR

1. Navigate to Infrastructure > Search > Storage > HPE 3PAR.
2. The HPE 3PAR page is displayed, select the application name.
3. The RESOURCE page appears from the right.
4. Click the ellipsis (…) on the top right and select View Details.
5. Navigate to the Attributes tab to view the discovery details.

• Click the Metrics tab to view the metric details for HPE 3PAR.

Resource Filter Input Keys

HPE 3PAR application resources are filtered and discovered based on below keys:

Supported Alert Custom Macros

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

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.
• Latest snapshot metric is available from Gateway version 14.0.0.
• Application will send any duplicate/repeat failure alert notification for every 6 hours.
• 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 referred 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.
• Support for Macro replacement for threshold breach alerts (i.e, customisation for threshold breach alert’s subject, description).
• No support of showing activity log and applied time.
• Application is not compatible with Cluster Gateway.
• This application supports both Classic Gateway and NextGen Gateway
• For HPE 3PAR Adapter and HPE 3PAR Host, there will be no global Device Management Policies (DMPs) or templates provided, as monitoring is not supported for these components.

Version History

Troubleshooting

Before troubleshooting, ensure all prerequisites prerequisites are met.

If HPE 3PAR integrations fail to discover or monitor, troubleshoot using the following steps:

• Check if there are any alerts generated on the HPE 3PAR Storage System or gateway, or if there are any error logs in vprobe.
• To rule out API/SSH specific failures like end device connectivity or authentication, try to check the reachability of end device from gateway using the below commands:
  • Try to ping the IP address provided in the configuration from the gateway ping <IP Address>
  • Try telnet using telnet <IP Address><port>
  • Try SSH to the end device from the gateway ssh <username>@<IP Address>
  • If you still need assistance, reach out to the support team to check the API accessibility using the API commands used internally on the app side.
• If there are no connectivity or authentication issues, reach out to the support team for further assistance.

References

https://support.hpe.com/hpesc/public/docDisplay?docId=c03606339

×