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

Supported Target Version

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..
• Provided IPaddress/hostname. Credentials should work for both WS APIs and SSH communication.

Hierarchy of HPE Primera

HPE Primera Storage System
      • HPE Primera Physical Disk
      • HPE Primera Common Provisioning Group
              • HPE Primera Storage Volume
                      · HPE Primera VLUN
      • HPE Primera Cage
              • HPE Primera Node
                      · HPE Primera Adapter
                              · HPE Primera Port
                      · HPE Primera Battery
      • HPE Primera Host

Supported Metrics

Default Monitoring Configurations

HPE Primera 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 requirement by cloning respective Global Templates and Global Device Management Policies. It is recommended to clone them 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-primera HPE Primera Storage System - 1 (i.e, appName = hpe-primera, nativeType = HPE Primera 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-primera HPE Primera Storage System Template - 1 (i.e, appName = hpe-primera, nativeType = HPE Primera 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 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 the HPE Primera

1. To select your client, navigate to All Clients, and click the Client/Partner dropdown menu.
   Note: You may either type your client’s name in the search bar or select your client from the list.
2. Navigate to Setup > Account. The Account Details screen is displayed.
3. Click Integrations. The Installed Integrations screen is displayed with all the installed applications.
   Note: If you do not have any installed applications, you will be navigated to the Available Integrations and Apps page with all the available applications along with the newly created application with the version.
4. Click + ADD on the Installed Integrations page.
   Note: Search for the integration either by entering the name of the integration in the search bar or by selecting the category of the integration from the All Categories dropdown list.
5. Click ADD in the HPE Primera application.
6. In the Configuration screen, click + ADD. The Add Configuration screen appears.

7. Enter the following BASIC INFORMATION:

8. CUSTOM ATTRIBUTES: Custom attributes are the user-defined data fields or properties that can be added to the preexisting attributes to configure the integration.

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

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.
Note: From the same page, you may Edit and Remove the created configuration.
12. 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.
13. Click NEXT.
14. (Optional) Click +ADD to create a new collector. You can either use the pre-populated name or give the name to your collector.
15. Select an existing registered profile. 16. Click FINISH.
The integration 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 the HPE Primera application.

View the HPE Primera details

To discover resources for HPE Primera

1. Navigate to Infrastructure > Search > Storage > HPE Primera.
2. The HPE Primera 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. Click the Metrics tab to view the metric details for HPE Primera.

Resource Filter Input Keys

HPE Alletra 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.
• 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 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 Alert polling will start only if the user enables Alert Polling in configuration.
• Possible values of Alert Severity Filter configuration property are SEVERITY_FATAL,SEVERITY_CRITICAL,SEVERITY_MAJOR,SEVERITY_MINOR,SEVERITY_INFO.
• OpsRamp has given sample mappings to map HPE Primera Severity with OpsRamp severities as part of 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.
• Support for Macro replacement for threshold breach alerts (i.e, customisation for threshold breach alert’s subject, description).
• No support of showing activity logs.
• The Template Applied Time will only be displayed if the collector profile (Classic and NextGen Gateway) is version 18.1.0 or higher.
• Latest snapshot metric is available from Gateway version 14.0.0.
• This application supports both Classic Gateway and NextGen Gateway
• For HPE Primera Adapter and HPE Primera Host, there will be no global Device Management Policies (DMPs) or templates provided, as monitoring is not supported for these components.

References

https://support.hpe.com/hpesc/public/docDisplay?docId=a00118636en_us&page=GUID-82F860B3-7C2F-48F0-BE55-D7833484E1A0.html

Troubleshooting

Before troubleshooting, ensure all prerequisites prerequisites are met.

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

• If there is an error or alert related to the end device connectivity or authentication, try checking the reachability of the end device from the gateway with the following commands:
  • to ping the IP address provided in the configuration: {ping <IP Address>}
  • to try telnet: {telnet <IP Adress> <Port>}
  • To run a SSH command:

    • Prepare the request payload by using below sample request:

      { “apiVersion”: “debug/v1”, “module”: “Debug”, “app”: “hpe-primera”, “action”: “Reachability”, “payload”: { “ipAddressOrHostName”: “”, “protocol”: “https”, “port”: 443, “requestPath”: “”,

      “version”:“v1”,

      “requestMethod”:"<get/post>", “userName”: “”, “password”: “” } }

    • Encode the request payload to base64

    • Log in to the gateway concole and connect to the GCLI terminal using the below command: {## gcli}

    • Run the command using the previously generated base64 encoded string {## sdkappdebug <base64 encoded string>}

Version History

×