Introduction

HPE Alletra MP/9000 Series 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.

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, and so on.
• Provided IpAddress/hostname, Credentials should work for both WS APIs and SSH communication.
• The target device must be reachable from the gateway. To verify the connectivity of the end device, use the following commands from the gateway.
  • To ping the IP address specified in the configuration: {ping <IP address>}
  • To test connectivity using telnet: {telnet <IP address> <Port>}
• The minimum user role required to access and use the HPE Alletra integration is browse.
• To check the reachability of the end device from the gateway, use the following commands.
  
  • Try pinging with the IP address provided in the configurations
    ping <IP Address>
    
  • Try telnet using
    telnet <IP Address> <Port>
    
  • Try SSH to the end device from the gateway
    ssh <username>@<IP Address>

Hierarchy of HPE Alletra

Following are the component structure for MP:

HPE Alletra Storage System

    • HPE Alletra Physical Disk
    • HPE Alletra Common Provisioning Group
            • HPE Alletra Storage Volume
                  • HPE Alletra VLUN
    • HPE Alletra Cage
            • HPE Alletra Node
                  • HPE Alletra Adapter
                          • HPE Alletra Port
    • HPE Alletra Host

Following are the component structure for 9000:

HPE Alletra Storage System

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

Supported Metrics

Default Monitoring Configurations

HPE Alletra MP/9000 Series 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 names in global scope:

   {appName nativeType - version - Storage Array Type}

   Ex: hpe-alletra HPE Alletra Storage System - 1 - Alletra MP (i.e, appName = hpe-alletra, nativeType = HPE Alletra Storage System, version = 3, Storage Array Type = Alletra MP)

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 adheres to the following naming convention:

   {appName Storage Array Type nativeType 'Template' - version}

   Ex: hpe-alletra Alletra MPHPE Alletra Storage System Template - 1 (i.e, appName = hpe-alletra, Storage Array Type = Alletra MP, nativeType = HPE Alletra Storage System, version = 3)

3. Default Global Monitors

   You can find the Global Monitors for each Native Type at Setup > Monitoring > Monitors. Search with suggested names in global scope. Each Monitors adheres to the following 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 = 3)

Configure HPE Alletra MP/9000 Series

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 on the HPE Alletra MP/9000 Series tile.
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 Native Types section, select the native types 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 Alletra MP/9000 application.

View the HPE Alletra MP/9000 Details

To discover resources for HPE Alletra MP/9000

1. Navigate to Infrastructure > Search > STORAGE > HPE Alletra MP/9000.
2. The HPE Alletra MP/9000 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 MP/9000.

Resource Filter Input Keys

HPE Alletra application Resources are filtered and discovered based on below keys:

Supported Alert Custom Macros

Customise the alert subject and description with below macros then it will generate alert based on customisation.

Risks, Limitations and Assumptions

• The integration can manage critical/recovery failure alerts for the following two scenarios when the user activates App Failure Notifications in the settings:
  • 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. We will use Physical disk statistical data reports API when the WSAPI version is less than 1.6.15 and we 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, we proceed with below assumptions:
  • For Physical Disk Discovery, we 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, we 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, we considered lun value as Resource Name in OpsRamp.
• HPE Alletra’s Alert polling will be started 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”.
• We have given sample mappings to map HPE Alletra Severity with OpsRamp Severities as part of the 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.
• 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.
• Latest snapshot metric is available from Gateway version 14.0.0.
• For HPE Alletra Adapter and HPE Alletra Host, there will be no global Device Management Policies (DMPs) or templates provided, as monitoring is not supported for these components.
• Used the available v3 APIs to support the alert polling.
• After upgrading the Alletra to version 10.4.2 or later, run a re-discovery and update the monitoring data to reflect the changes.

Version History

References

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

×