SQL Monitor unpingable cluster IP

Bert_DWM

Hi,

I would like to add SQL monitor (latest) to our setup in the Google Cloud Platform to monitor the SQL cluster (or in a pinch the SQL nodes individually). However after adding the node to it, it discovers the cluster and tries to add this to the setup. This fails with the error:  PingFailedException Ping failed

I figured this is because the actual Cluster IP is not pingable due to a limitation with virtual IPs on a load balancer within the Google Cloud setup. The Cluster IP can only really be used for SQL connections, and not much else. 

This document outlines the inability to ping a loadbalancer IP for the interested parties: https://cloud.google.com/load-balancing/docs/internal/setting-up-internal

Is there a way to circumvent this and make it so that I can monitor either the individual nodes (can be pinged as well) or add the cluster without the need for this check?

Russell D

It isn't possible to add single nodes I'm afraid, no.

Regarding GCP we don't support it; I remember that we did some work and testing on it a while ago to see if would work. I can't remember what the outcome was but I'll ask internally, it might have hit problems with their loadbalancers.

Bert_DWM

Thank you Russel, I had completely ignored that Azure manual as I, mistakenly, thought it was meant only to add servers via that special Azure Servers button. 

By checking this manual I was able to get it to work, simply by adding TCP 135 to the frontend config as is described in said manual. 



Issue is hereby solved, again thanks!

Russell D

The only thing that might help is forcing the cluster name in advanced under connection properties, but I'm not to ofay with how google do load balancing.

Bert_DWM

Not sure I understand, the cluster name resolves to an IP that is not pingable. And even if I could solve it like this, where is this advanced menu you speak of?

Is it possible for Redgate to include the single nodes and not bother with the cluster at all otherwise? I have no possibility to change the way Google Loadbalancers work unfortunately. 

Russell D

Hm we seem to think that GCP machines should be supported, so it could be something specific about google load balancers that stops the resolution working. If you look at this page: https://documentation.red-gate.com/sm/configuring-sql-monitor/adding-servers-to-monitor/monitoring-sql-server-failover-cluster-instances-and-alwayson-availability-groups-hosted-in-azure-iaas, the steps for the Azure load balancers are actually relatively simple and straight forward, so perhaps this will help? Unfortunately we've not done any testing with GCP load balancers, just standalone VMs.