HPE Alletra

Application Version Details

Introduction

HPE Alletra 9000 is ideally suited for mission-critical workloads with extreme sensitivity to latency and high availability requirements. It is particularly well-suited for environments that demand a compact data center footprint.

It resolves the agility versus reliability trade-off inherent in the choice between the public cloud and traditional enterprise storage by delivering a modern, as-a-service experience through HPE GreenLake. This experience is further enhanced by intelligence and automation that ensure applications are always available and operational.

This platform features a unique, massively parallel, multi-node, and all-active architecture, with all volumes active across all media, controllers, and host ports. It allows for limitless scalability when consolidating both traditional and next-generation mission-critical applications, offering predictable performance and ultra-low latency, all supported by a 100% availability guarantee. Additionally, it simplifies and reduces the costs associated with business continuity and disaster recovery through fully Active Bidirectional Replication.

Prerequisites

• OpsRamp Classic Gateway 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 Alletra

    ‐ HPE Alletra Storage System
          ‐ HPE Alletra Common Provisioning Group
              ‐ HPE Alletra Storage Volume
                  ‐ HPE Alletra VLUN
            ‐ HPE Alletra Physical Disk
            ‐ HPE Alletra Host
                ‐ HPE Alletra Port
                      ‐ HPE Alletra Port Device
                      ‐ HPE Alletra FC Switch

Default Monitoring Configurations

HPE Alletra have 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 Alletra. 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-alletra HPE Alletra Storage System - 1 (i.e, appName = hpe-alletra, nativeType = HPE Alletra Storage System, version = 1)

2. Default Global Templates

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

Configure and Install the HPE Alletra Integration

1. From All Clients, select a client.
2. Go to Setup > Account.
3. Select the Integrations and Apps tab.
4. The Installed Integrations page, where all the installed applications are displayed.
   Note: If there are no installed applications, it will navigate to the ADD APP page.
5. Click + ADD on the Installed Integrations page. The Available Integrations and 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.

6. Click ADD on the HPE Alletra tile.
7. From 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.
• Below are the default values set for:
  • Event/Alert Severity Filter: Possible values of Alert Severity Filter configuration property are “FATAL”,“CRITICAL”,“MAJOR”,“MINOR”.
  • Event Category: “1”,“2”
  • Alert Severity Mapping: Possible values of Alert Severity Mapping Filter configuration property are “FATAL”:“Critical”,“CRITICAL”:“Critical”,“MAJOR”:“Warning”,“MINOR”:“Warning”,
    “DEGRADED”:“Warning”,“INFORMATIONAL”:“Info”,“DEBUG”:“Info”,“UNKNOWN”:“Info”.

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. Click NEXT
14. Below are the optional steps you can perform on the Installation page.

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

• Click +ADD to create a new collector by providing a name or use the pre-populated name.

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 Alletra application.

View the HPE Alletra Details

To discover resources for HPE Alletra, you have two options:

Option 1:
Navigate to Infrastructure > Resources > Storage, with Native Resource Type as HPE Alletra Storage System. You can go to the Attributes tab to view the discovery details.

Option 2:

1. Navigate to Infrastructure > Search > STORAGE MANAGEMENT > HPE Alletra.
2. The HPE ALLETRA page is displayed, select the application name.
3. The RESOURCE DETAILS 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 Alletra.

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 WS APIs 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 Alletra 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 will use Physical disk statistical data reports API when the WSAPI version is less than 1.6.15 and OpsRamp will use Querying physical disk information API when the WSAPI version is greater than or equals to 1.6.15.
• As few of the HPE Alletra 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 (Port WWN 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 Alletra’s Event/Alert polling will be started 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 two is used to identify an alert.
• OpsRamp has given sample mappings to map HPE Alletra 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 app configuration page. Possible OpsRamp Severities are Critical, Warning, Ok, Info.
• In referred hpe-alletra 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.
• Application is not compatible with Cluster Gateway.