Cannot monitor member of the cluster?

timothytimothy Posts: 5 New member
in Redgate Monitor
Hi, 

I'm trying to add a server to our monitored server list that is the primary in a AOAG cluster.  When I specify the server name serverA for example, redgate ends up detecting the cluster name server-cluster1 and then not being able to connect.

The error in the log shows: 

The RPC server is unavailable. (Exception from HRESULT: 0x800706BA)

However the RPC server is running.
Tagged:
· Share on Twitter

Answers

  • Russell DRussell D Posts: 1,324 Diamond 5
    Do you have enough free licences to add all machines in the cluster?
    Have you visited our Help Centre?
    · Share on Twitter
  • timothytimothy Posts: 5 New member
    Russell D said:
    Do you have enough free licences to add all machines in the cluster?
    Yes we have 2 of 10 licenses available.  All servers except the primary in the cluster are assigned licenses.
    · Share on Twitter
  • way0utwestway0utwest Posts: 312 Rose Gold 1
    Are you adding the virtual server or the node itself? Can you disclose some of the names/setup?
    Editor, SQLServerCentral
    · Share on Twitter
  • timothytimothy Posts: 5 New member
    edited September 11, 2018 5:00PM
    It's a physical node that I'm trying to add.  The server names are close enough to databaseserverA and databaseserverB with the cluster name being databaseserver-c (can't disclose the actual names though).  

    ive started searching through the tables to find out if there is some field I can edit to square this away but too many ids so I'm thinking that won't happen :cry:
    · Share on Twitter
  • cfendrickcfendrick Posts: 15 Bronze 2
    Are you able to see what your actual Failover Cluster name is and use that for the server you want to monitor?  I know when I had to configuration one environment with what I like to call magical/nightmare things (dns alias or cname) and if I used anything other than the Cluster Name it would not work....  So while you are talking about AG groups I believe you would potentially want to look up what is in Failover Cluster Manager and potentially use the fully qualified domain name of what is listed there and that will hopeful pull in all the servers for you.  Test that thing multiple times as when it pulls in the information it should all be GREEN and list all your servers.  Also make sure the local windows firewall on each node has any needed ports open.

    As and example if you look at RedGates demo example site  https://monitor.red-gate.com/

    The Monitored server are really pulled in from the Cluster.





    Open up Failover Cluster Manager on one of the nodes and see what that FQDN name is and try that.




    · Share on Twitter
  • timothytimothy Posts: 5 New member
    so when we put in databaseserverA redgate monitor seems to resolve it to the FQDN of of the cluster databaseserver-c.domain.whatev

    im wondering if the ip address associated with the cluster name is incorrect
    · Share on Twitter
  • cfendrickcfendrick Posts: 15 Bronze 2
    Start having someone look at DNS and all the NICs to see if something is IP'd wrong.  Break out CMD and start doing some PING and NSLOOKUP to see how things resolve out.


    Good Luck and stay safe out there!

    · Share on Twitter
  • way0utwestway0utwest Posts: 312 Rose Gold 1
    I would definitely investigate with whoever handles the networking and verify that things are setup correctly between the system, DNS, and AD.
    Editor, SQLServerCentral
    · Share on Twitter
Sign In or Register to comment.