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>}

  • If there are no connectivity or authentication issues, reach out to the support team for further assistance.