HPE OneView

Application Version and Upgrade Details

Introduction

HPE OneView is a software-defined infrastructure management platform developed by Hewlett Packard Enterprise (HPE). It is designed to simplify and streamline the management of data center resources, including servers, storage, and networking devices, through a unified interface.

HPE OneView provides a comprehensive set of tools and features to enable efficient and automated management of the entire infrastructure lifecycle, from initial deployment to ongoing operations. Some key features and capabilities of HPE OneView include:

• Infrastructure Automation
• Template-Based Provisioning
• Monitoring and Alerting
• Resource Pooling and Federation
• Integration and Extensibility

Overall, HPE OneView offers a unified and streamlined approach to managing and optimizing data center resources, bringing simplicity, agility, and automation to IT infrastructure management.

Key Use cases

Discovery Use cases

• It discovers the HPE OneView components.
• Publishes relationships between resources to have a topological view and ease of maintenance.

Monitoring Use cases

• Provides metrics related to job scheduling time and status etc..
• Concern alerts will be generated for each metric to notify the administrator regarding the issue with the resource.

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 HPE OneView REST API’s

Hierarchy of HPE OneView Resources

    · HPE OneView Resource
            · HPE OneView Appliance
            · HPE OneView Enclosure
                    · HPE OneView Enclosure Interconnect
                    · HPE OneView Enclosure PowerSupply
                    · HPE OneView Enclosure Fan
                    · HPE OneView Enclosure ManagerBay
            · HPE OneView Server Hardware
            · HPE OneView Storage System
                    · HPE OneView Storage System Port
                    · HPE OneView Storage Pool
            · HPE OneView Server Profile
            · HPE OneView Drive Enclosure
                · HPE OneView Drive Bay
                      · HPE OneView Drive
                · HPE OneView Drive Enclosure IOAdapter
            · HPE OneView Logical JBOD Attachment
            · HPE OneView Logical JBOD
            · HPE OneView SAN
            · HPE OneView SAN Manager

Supported Metrics

Default Monitoring Configurations

HPE OneView 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-oneview HPE OneView Resource - 1 (i.e, appName = hpe-oneview, nativeType = HPE OneView Resource, 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-oneview HPE OneView Resource Template - 1 (i.e, appName = hpe-oneview, nativeType = HPE OneView Resource, 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 OneView Resource Monitor hpe-oneview HPE OneView Resource 1 (i.e, monitorKey = HPE OneView Resource Monitor, appName = hpe-oneview, nativeType = HPE OneView Resource, version = 1)

Configure and Install the HPE OneView 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 in the HPE OneView application.
7. In the Configurations page, click + ADD. The Add Configuration page appears.
8. Enter the following 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.
  • Alert Configuration: enables integrating third party alerts into OpsRamp using further configurations.
  • Alert On Root Resource: Checking this will generate event polling alerts on root resource.
    • Below are the default values set for:
      • Alert Severity: Possible values of Alert Severity filter configuration property are [“Critical”,“Disabled”,“OK”,“Unknown”,“Warning”]
      • Alert Severity Mapping: Provides alert severity mapping configuration.
        • Default values for Alert Severity Mapping configuration are {“Critical”:“Critical”,“Disabled”:“Critical”,“OK”:“Ok”,“Unknown”:“Warning”,“Warning”:“Warning”}.
  • 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.

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 the HPE OneView application.

View the HPE OneView Details

To discover resources for HPE OneView:

1. Navigate to Infrastructure > Search > SERVERS AND VMS > HPE OneView.
2. The HPE OneView 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.
6. Click the Metrics tab to view the metric details for HPE OneView.

View resource metrics

To confirm HPE OneView monitoring, review the following:

• Metric graphs: A graph is plotted for each metric that is enabled in the configuration.
• Alerts: Alerts are generated for metrics that are configured as defined for integration.

Resource Filter Input keys

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

Note: You filter the resources with the discoverable keys only.

Supported Alert Custom Macros

Customize the alert subject and description with below macros will generate alerts 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 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 the resources and can generate alerts based on the threshold values.

• HPE OneView Event/Alert polling will start only if the user enables Event/Alert Polling in configuration.

  Notes:

  • Here Event/Alert polling support is given for HPE OneView Alarms only.
  • When a status value which presents in the Event/Alert Cleared Status field occurs, we will create an Ok alert accordingly. Otherwise, we will create an alert based on Event/Alert Severity Filter & Event/Alert Severity Mappings of Event/Alert Polling configurations.
  • Possible HPE OneView Event/Alert Severity Filter configurations are Critical, Disabled, OK, Unknown, Warning.
  • We have provided default mappings to map HPE OneView Severity with OpsRamp Severities as part of Event/Alert Severity Mapping configuration.
  • You can modify them as per their use-case at any point of time from the application configuration page. Possible Severities are Critical, Warning, Ok, Info.

• Component level thresholds can be configured on each resource level.

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

• This application supports both Classic Gateway and NextGen Gateway.

• Latest snapshot metric support from Gateway 14.0.0.

References

https://support.hpe.com/docs/display/public/dp00003294en_us/index.html

Troubleshooting

Before troubleshooting, ensure all prerequisites prerequisites are met.

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

• Check if any alerts have been generation on HPE OneView Resource, the gateway, or in vprobe.
• 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 an API:

    • Prepare the request payload by using below sample request:

      { “apiVersion”: “debug/v1”, “module”: “Debug”, “app”: “hpe-oneview”, “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>}