Tomorrow we are releasing version 3.5.0 in the Quorum Portal . The most important changes include new checks for the MetroCluster Bundle :  ClusterPeerHealth MetroClusterVserver We are also adding options to allow checks that don’t find any instances not to necessarily end with UNKNOWN. As always you can find …
In order to monitor the configuration-health of Metro-Cluster Servers we are introducing a new check: MetroClusterVserver , monitoring all or specific Vservers. The check can be configured to monitor the Vservers of a specific node and/or those fitting a specific naming pattern. Furthermore, the switch --skip_reason …
With release 3.5.0 we are adding a new check to the MetroCluster bundle: ClusterPeerHealth monitors the peering status based on various parameters such as _ping status of the nodes, RDB health _or the availability of inter cluster communication. Out Monitoring-Checks for the NetApp MetroCluster bundle therefore …
ClusterPeerHealth , a new check currently in development, that will allow for continuously monitoring of the different nodes for a Metro Cluster as well as their availability. Health and other status information and various “pings” (data, icmp) will be used for evaluation. Please find information about our …
Included in our next release, check_netapp_mc_config will provide the possibility to monitor the mode information of a MetroCluster. Example 1: An incomplete installation for a simulator $ ./check_netapp_mc_config.pl -H sim83n1 --local --remote NETAPP_MC_CONFIG CRITICAL - Local: sim83 is not_configured, Remote is …