- The integration can handle critical and recovery failure alert notifications for the following two cases when the user enables App Failure Notifications in the configuration:
- Connectivity Exception
- Authentication Exception
- The integration uses the provided IP address/hostname, credentials for API communications.
- The integration sends any duplicate/repeat failure alert notification for every 6 hours.
- The integration can’t control monitoring pause/resume actions based on above alerts.
- Metrics can be used to monitor HPE Cray ClusterStor resources and can generate alerts based on the threshold values.
- Component level thresholds can be configured on each resource level.
- Latest snapshot metric support from Gateway 14.0.0.
- This integration is not compatible with Cluster Gateway.
Troubleshooting
Before troubleshooting, ensure all prerequisites prerequisites are met.
When HPE Cray ClusterStor integration fails to discover / monitor, follow these troubleshooting steps:
- Check if any alerts generated on the HPE Cray ClusterStor, on the gateway, or any error logs in vprobe.
- To rule out API accessibility or specific failures like end device connectivity or authentication, check the reachability of the end device from the gateway using the following commands:
- Try pinging with the IP address provided in the configuration:
ping <IP Address> - Try telnet using
telnet <IP Address> <port> - try ssh to the end device from gateway ssh
@
- Try pinging with the IP address provided in the configuration:
- If you still need assistance, reach out to the support team to check API accessibility using the SDK App Debug Command Center (available depending on the gateway version 18.1.0 and app support) or DiscoveryandMonitoring-TargetAPIResponses.
- If there are no connectivity or authentication issues, refer to the SDK App Debugging process and contact the support team for further assistance.