Not able to add node in the cluster

smk 161 Reputation points
2020-08-10T18:53:41.027+00:00

Hi ,

we are planning to create Failover cluster between DC and DR , but when trying to add DR server in the DC failover cluster we are getting the below error.

16855-cluster.jpg

network team confirmed 3343 (TCP and UDP) and Dynamic Ports are open. any other ports are required ?
what else can be verified ?
when we add DR from other DR server it's working , only not happening between DC and DR.

Regards,
Mani

Windows Server 2016
Windows Server 2016
A Microsoft server operating system that supports enterprise-level management updated to data storage.
2,387 questions
Windows Server Clustering
Windows Server Clustering
Windows Server: A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.Clustering: The grouping of multiple servers in a way that allows them to appear to be a single unit to client computers on a network. Clustering is a means of increasing network capacity, providing live backup in case one of the servers fails, and improving data security.
961 questions
0 comments

5 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Jon Alfred Smith 541 Reputation points
    2020-08-10T19:01:21.067+00:00

    If you with DC mean domain controller: You cannot add a domain controller as a node in a Windows Server failover cluster environment.

    0 comments
  2. smk 161 Reputation points
    2020-08-11T05:06:26.88+00:00

    i meant Primary Datacenter (DC) and DR - Disaster Recovery

    0 comments
  3. Xiaowei He 9,871 Reputation points
    2020-08-11T06:06:49.677+00:00

    Hi,

    1. I'd like to check if there's any NAT device between the Datacenter nodes and the DR site node? As far as I know, clustered servers are not supported with NAT devices in between nodes.
    2. Please capture network traffic between the datacenter node and the DR site node, we can install the network monitor tool on one of the Cluster nodes in the datacenter, and install the network monitor tool on the DR site node. Start capture, then try to add the DR site node into the cluster, after the issue reproduces, stop the capture and check if the nodes can receive and send UDP 3343 heartbeat packets successfully.

    Below is the example I tested to add a new node into the Cluster:

    16874-capture.png

    Besides, it's recommended to check the Cluster Addnodes log and the Cluster logs for the detailed information:

    16875-image.png

    -----------------------------

    If the reply could be of help, please help to accept it as an answer, thanks for your cooperation!
    Thanks for your time!
    Best Regards,
    Anne

  4. Xiaowei He 9,871 Reputation points
    2020-08-14T03:04:45.657+00:00

    Hi,

    I would like to check if the above reply could be of help? If yes, please help accept it as an answer, so that others meet a similar issue can find useful information quickly. If you have any other concerns or questions, please feel free to feedback.

    If the reply could be of help, please help to accept it as an answer, thanks for your cooperation!
    Thanks for your time!
    Best Regards,
    Anne

    0 comments
  5. Nico 1 Reputation point
    2021-03-24T07:29:45.817+00:00

    Hi,

    We have had the exact same issue, rebooting al cluster nodes solved the issue.

    0 comments