Unable to add second DAG Member in Echange 2013

I am have been having issues creating a DAG in Exchange 2013.

I have a scenario where I've got 2-DCs, 1-FileShare (non-exchange), Four Exchange Servers (1-CAS, 3-MBX).

I successfully create a DAG and try to add two servers to it. On each attempt, the CAS server adds without issues, but the MBX server fails to add with the following error:
"error

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 failed: "AddClusterNode() (MaxPercentage=100) failed with 0x5b4. Error: This operation returned because the timeout period expired". [Server: cas01.rshq.local]"

How do I get the second server to add so I can complete the DAG creation please? Looking forward to your help on this as I've been on this for over 2 weeks and can't seem to find a solution anywhere that works.
Lance07Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

 
suriyaehnopCommented:
Based on:

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 failed: "AddClusterNode() (MaxPercentage=100) failed with 0x5b4. Error: This operation returned because the timeout period expired". [Server: cas01.rshq.local]"

Do you assign an static IP address for your DAG name? Make sure the host name appear in DNS server as well

https://technet.microsoft.com/en-us/library/dd297985%28v=exchg.150%29.aspx

Set-DatabaseAvailabilityGroup -Identity DAG1 -DatabaseAvailabilityGroupIPAddresses 10.0.0.8
0
 
Lance07Author Commented:
Yes i do have an static IP address for the DAG name and it is configured in DNS (forward and reverse lookup). as the first server has been added and the DAG CNO has become enabled, I can ping the DAG CNO (the name gets resoled to the IP accordingly).

I've got both a MAPI and a replication network on the Exchange server (prospective DAG member servers). All IPv4 addresses are manually configured, while IPv6 is set to DHCP (as am not using these yet).

I also noticed that the "witness directory" directory disappears immediately after the DAG gets created, is this normal?

Any further thoughts?
0
 
Simon Butler (Sembee)ConsultantCommented:
You don't add CAS role servers to the DAG - only mailbox role servers.
Therefore if you have added the CAS to the DAG, then you have done something wrong.

I would trash the DAG completely, recreate it with a new name and new IP address.
The CAS can act as the FSW because it doesn't have the mailbox role on it and that saves changing permissions on another server.

Simon.
0

Experts Exchange Solution brought to you by ConnectWise

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
Lance07Author Commented:
Hello Simon,

The CAS Server also host a Mailbox server role, however, all the others only host Mailbox roles. I think this would normally work - having a server with multiple roles installed joining the DAG, I have seen that before.

Any more ideas please?

Thank you.
0
 
Simon Butler (Sembee)ConsultantCommented:
Personally I would have all roles on all servers. That is the recommended configuration by Microsoft and I see no point in having the roles separated at all. What does that separate CAS do for you? Nothing at all.
The rest of my response still stands - trash the DAG and try again.

Simon.
0
 
MAS (MVE)EE Solution GuideCommented:
Agree with Simon. For example if you have 2 CAS and 2 MBX. You change it 2 or 3 servers with all the roles installed.
This way you save hardware cost and sofware cost(Exchange license).
FYI CAS is a stateless server in Exchange2013 it is just an interface to clients.
0
 
Lance07Author Commented:
Ok, I forgot to mention that the CAS also has MBX role installed.

I'll think of the multi-role servers option tonight and let you know what I decide and how I proceed.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.