1 title: General status of the CRM for heartbeat nodes using crm=yes
7 This check uses the output of the {crm_mon} command as sent by the Check_MK
8 linux agent. The check uses general information from that output like:
9 The last update time of the output, the DC, the number of nodes and the number
10 of resources in the cluster.
12 The check reports CRITICAL in the following situations: When the "last update"
13 time is larger than the threshold (normally {60} seconds), when the number
14 of nodes or resources change or - optionally - when the expected DC of the cluster changes.
16 Till version 1.2.5i6 the check nailed down the DC to the node which was DC during
17 inventory. This has been changed to not nailing down the node. You can change this back
18 to the old default by changing your configuration.
21 One service will be created on each node of the cluster. If {naildown_dc} is
22 set to {True} in {inventory_heartbeat_crm_rules}, then the node which is currently
23 DC will be required to stay DC in future.