Monitor one node from cluster only - not all nodes
mschier
Posts: 14 New member
Hi,
with Version 5.2.1.3670 it is not possible anymore, to monitor only one node from a for example a two node cluster.
If I add one node at the field "Add SQL Server" and click on add, it will be automatically switch to the cluster address and add both nodes.
In older Version it was possible to add only one node of a cluster.
Regards
Michael
with Version 5.2.1.3670 it is not possible anymore, to monitor only one node from a for example a two node cluster.
If I add one node at the field "Add SQL Server" and click on add, it will be automatically switch to the cluster address and add both nodes.
In older Version it was possible to add only one node of a cluster.
Regards
Michael
Tagged:
Comments
In version 5 we have made the default behaviour to automatically discover the cluster and all of its nodes by putting in any node of the cluster or the cluster name itself (see the documentation here: https://documentation.red-gate.com/disp ... to+monitor under step 3). The licensing is per Windows host machine so when you try to add the single node of the 2 node cluster it is attempting to add both nodes and unable to do so due to licensing issues.
There is a work around that can be attempted but this is not officially supported. if you would like more information about this please contact support@red-gate.com
Thanks,
Justin
It looks like a colleague was previously assisting you with this through a ticket that's since been closed through lack of response. A new ticket has been created and I'll message you shortly through our ticketing system as it would be beneficial to gain some additional logs that we don't want to post on public forum.
Tom Claringbold | Redgate Software
Have you visited our Help Center?
The error that you are seeing indicates a firewall issue blocking the connectivity from SQL Monitor to the Cluster.
The following link has more information on the this https://documentation.red-gate.com/sm/adding-and-managing-monitored-servers/preparing-for-adding-monitored-servers/adding-servers-on-a-different-network-from-your-base-monitor/summary-of-firewall-requirements
If the cluster is hosted on cloud, then the following link has details on setting up the inbound rules https://documentation.red-gate.com/sm/adding-and-managing-monitored-servers/preparing-for-adding-monitored-servers/adding-servers-on-a-different-network-from-your-base-monitor/machines-hosted-in-the-cloud
If the issue persists, then please perform the following troubleshooting steps from the server hosting the Base Monitor
Using an elevated command prompt to open
wbemtest, then try connecting via WMI to\\<ClusterName>\root\MSCluster(ensure packet privacy is selected)
Then query
SELECT Name FROM MSCluster_Nodeand see if that node shows up?This will help pinpoint the issue.
Tom Claringbold | Redgate Software
Have you visited our Help Center?
Thank you for the reply. One of my node is off and monitor trying to connect to that node and throwing the 'not reachable' exception. It's not reachable because the node is off. Is there any other way we just monitor only available nodes?
Thanks,
Justin
Hi Justin,
Apologies for the delayed response, not sure how this slipped through without response.
If you want to stop monitoring these, suspending the instances on this node would probably be the best way to achieve if I've understood your question correctly.
https://documentation.red-gate.com/sm/adding-and-managing-monitored-servers/managing-monitored-servers/suspending-a-monitored-server
Please let me know if any issues.
Tom Claringbold | Redgate Software
Have you visited our Help Center?