HPE Primera

Introduction

HPE Primera provides a storage experience unmatched in the industry with a series of unique innovations across intelligence, hardware and software. These technologies make possible HPE Primera’s instant access to data, 100% data availability guarantee, and always-fast, ultra-low latency.

HPE Primera is a scale-out block storage system and comprises of three models:

• HPE Primera 630: The architecture has up to four nodes with the internode communication handled by custom ASICs across a backplane.
• HPE Primera 650: The larger models can scale from two to four nodes. The smallest model has two controllers, each with two processors (Intel Skylake) and four ASICs and 24 devices in the basic unit.
• HPE Primera 670:The other model has two or four controllers and 48 devices. Systems scale larger with the addition of device enclosures. Model numbers prefixed with an “A” are all flash systems and with a “C” prefix can have HDDs installed.

Each model is available as an all-flash version (A630, A650 and A670) or converged flash version (C630, C650, C670).

Pre-Requisites

• OpsRamp Classic Gateway 12.0.1 and above.
• Provided IpAddress/hostname, Credentials should work for both WS APIs and SSH communication.

Hierarchy of HPE Primera

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

Default monitoring configurations

HPE Primera has default Global Device Management Policies, Global Templates, Global Monitors and Global metrics in OpsRamp. Users can customize these default monitoring configurations as per their business use cases by cloning respective Global Templates and Global Device Management Policies. OpsRamp recommends doing this activity before installing the app to avoid noise alerts and data.

1. Default Global Device Management Policies

   OpsRamp has a Global Device Management Policy for each Native Type of HPE Primera. 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: hpe-primera HPE Primera Storage System - 1 (i.e, appName = hpe-primera, nativeType = HPE Primera Storage System, version = 1)

2. Default Global Templates

   OpsRamp has a Global template for each Native Type of HPE Primera. 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: hpe-primera HPE Primera Storage System Template - 1 (i.e, appName = hpe-primera, nativeType = HPE Primera Storage System, version = 1)

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: HPE Primera Storage System Monitor hpe-primera HPE Primera Storage System 1(i.e, monitorKey = HPE Primera Storage System Monitor, appName = hpe-primera, nativeType = HPE Primera Storage System, version = 1)

Configure and install the integration

1. From All Clients, select a client.
2. Go to Setup > Integrations and Apps.
3. Click Manage Apps.
   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.

4. Click + ADD on the INSTALLED APP page. The AVAILABLE 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 HPE Primera 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.
• 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 Primera 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.

8. In the Custom Attributes section, select the custom attribute key and value from the dropdown boxes.
   Note:
   • The custom attribute that you add here will be assigned to all the resources that are created by the configuration.
   • You can add a maximum of 5 custom attributes (key and value pair).
   • The custom attribute that you add should be created at the client level.
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. 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 Primera application.

View the HPE Primera details

The HPE Primera 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 HPE Primera.

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 existed critical alert is recovered.
• Application cannot control monitoring pause/resume actions based on above alerts.
• Metrics can be used to monitor HPE Primera resources and can generate alerts based on the threshold values.
• As per Developer guide, support to show disk information was added in WSAPI 1.6.15 release. So, OpsRamp uses Physical disk statistical data reports API when the WSAPI version is less than 1.6.15 and OpsRamp uses querying physical disk information API when the WSAPI version is greater than or equals to 1.6.15.
• As few of the HPE Primera components did not have direct name information in WSAPI responses, OpsRamp proceed 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 equal to 1.6.15) as Resource Name in OpsRamp.
  • For Ports Discovery, OpsRamp considered portWWN (PortWWN will present 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 Primera’s Event/Alert polling will start 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 Primera Severity with OpsRamp severities as part of Event/Alert Severity Mapping configuration field. Users can modify them as per their use case at any point of time from the App Configuration page. Possible OpsRamp Severities are Critical, Warning, Ok, Info.
• In referred HPE Primera 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 for Macro replacement for threshold breach alerts (i.e, customisation for threshold breach alert’s subject, description).
• Component level thresholds can be configured on each resource level.
• No support of showing activity log and applied time.
• No support for the option to get Latest snapshot metric.
• Application is not compatible with Cluster Gateway.