DAG Node Join Fail–0x5b4

Just a quick blog and reminder for something I worked a couple of months ago, or even longer and it took a considerable amount of time to figure out. Then last week a colleague just ping me with a question about a case they have been dealing for quite sometime.

Upon trying to join a second DAG member, in a virtualized Hyper-V environment, the following error message is presented:

“WriteError! Exception = Microsoft.Exchange.Cluster.Replay.DagTaskOperationFailedException: A server-side database availability group administrative operation failed. Error The operation failed. CreateCluster errors may result from incorrectly configured static addresses. Error: An error occurred while attempting a cluster operation. Error: Cluster API ‘”AddClusterNode() (MaxPercentage=100) failed with 0x5b4. Error: This operation returned because the timeout period expired”‘ failed.. —> Microsoft.Exchange.Cluster.Replay.AmClusterApiException: An Active Manager operation failed. Error: An error occurred while attempting a cluster operation. Error: Cluster API ‘”AddClusterNode() (MaxPercentage=100) failed with 0x5b4. Error: This operation returned because the timeout period expired”‘ failed. —> System.ComponentModel.Win32Exception: This operation returned because the timeout period expired”

If you look at the cluster logs you would notice the heartbeat failing on port UDP 3343.

Obviously you need to go by the normal troubleshooting steps of network connectivity and firewall rules. If everything seems right, and as my friend pointed out all knobs were turned and he was ready to give up. That’s when I asked…

Have you disabled TCP/UDP Checksum offload on both host and guest network cards ?

After disabling these options on both guest and parent partition cluster could be formed without any issues.

So in this case, after you make sure the obvious have been checked out and you still cannot join your cluster nodes in a virtual environment, take a look at the NIC properties for TCP/UDP Checksum Offload for IPv4 and IPv6.

Thanks,

Alessandro

Advertisements

About smartwindows

Support professional for Microsoft technologies with interest in Performance and Debugging
This entry was posted in ExchangeDAG and tagged , . Bookmark the permalink.

3 Responses to DAG Node Join Fail–0x5b4

  1. Philippe says:

    I had the same issue and your solution realy helps me. Thanks a lot,
    Philippe

  2. Kevin says:

    Alessandro, we had this exact same problem and no one, no where was able to solve it or assist. Your article fixed it for us. We appreciate it greatly. Can you verify that it has to be done on both the host and guest. We tried guests only and it didn’t work. We tried both guest and host and it worked. Do you think it would work with the hosts only? Do you think we should do it to every guest in our VM environment so we don’t run up against some strange issues in the future for something else? Thanks again.

    Kevin

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s