Is there a way to set back the threshold on the API timeout for this one cluster and not all of them? Where would that be?
Running OCUM 7.3p1 with half a dozen 9.2 and 9.3 clusters. One of them, ClusterH, is on a network that has close to 180ms latency there and back while the rest of the clusters are between 10 and 100ms. After no issues for a year with monitoring this same system, recently I've been getting alerts for Cluster Monitoring Failed off and on. They always alert, then clear (go obsolete). There's no issues locally with the netapp connections and nothing can be done about the latency from the OCUM server to the cluster. Trying not to have to install another OCUM instance closer to that 1 cluster.
Alert example:
Risk - Cluster Monitoring Failed
Impact Area - Availability
Severity - Warning
State - Obsolete
Source - ClusterH
Trigger Condition - Monitoring failed for cluster ClusterH. Reason: Cluster cannot be reached. Ensure that there is network connectivity to the cluster and the API has not timed out. The following settings must also be configured correctly for the cluster: hostname or cluster-management IP address, protocol, and port. If the issue persists, contact technical support.