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.

  Note

  • 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, and 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, and Info.
• Component level thresholds can be configured on each resource level.
• 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.
• User can filter PCIeSlot devices for server hardware using the custom attribute isPCIeSlot and the following query.

nativeType = 'HPE OneView ServerHw Device' AND topology.sourceId = '' AND tag['isPCIeSlot'] = "true"

• In the previous query, topology.sourceId refers to the Server Hardware ID.

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>}
• If there are no connectivity or authentication issues, reach out to the support team for further assistance.