Status Detail:
UNKN - Item not found in agent output
That particular Exchange is part of a Cluster of Exchanges (the others we dont monitor). Databases for example are sometimes moving from Server A to Server B, so checks “fail” because they changed. Everytime we then do a “cmk -II” and reload to fix the “Problem”.
Is there a better way to monitor more or less constantly changing services besides ingnoring them or to re-discover constantly?
thank you, but if i understand that documentation correctly this wont work for us since we do not monitor the whole cluster. Just one Server out of 3 is part of our environment and monitored. The other Servers are not under our control and we dont have them in our monitoring.
OK, that’s… an interesting agreement you have… And your customers can’t install the CMK
agent on their “part” of the cluster and give you access through a site to site VPN or similar to be done with it?
Anyway, is there any other way you can get the current cluster status information? E.g. by a (or multiple) running (or not running) service(s), eventlog entries or an own script?
Because then you could choose to ignore and disable the “floating” resources and monitor your cluster based on the “other” criteria.
Otherwise I fear, you’ll only get through this with a lot of… patience and repetition…
That cannot be. All the Exchange servers of one cluster must belong to one AD domain.
I only know that you can setup an SQL availability group over two domains.
What can be is that the Exchange DAG spanns more than one logical site.
For an Exchange cluster you have no real option. You need to monitor all servers and there are no floating resources like in the classic cluster setup. Only the database status is changing on the nodes from passiv to active and vice versa.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed. Contact @fayepal if you think this should be re-opened.