[2 days left] What’s wrong with your cloud strategy? Learn why multicloud solutions matter with Nimble Storage.Register Now

x
?
Solved

Creating DAG and adding membership group fails with cluster error

Posted on 2014-01-04
5
Medium Priority
?
678 Views
Last Modified: 2014-01-11
Hello everyone

I have a migration from 2003 to 2010 and I'm in the process of creating the DAG group and adding 2 Exchange 2010 servers to it.

So I have 2 servers with 2 NICs on each server and 3 TB on each server too with all the roles installed on each of them.

I created 4 databases on each server and created one DAG for replication of the databases between both server but there seems to be a problem.

I have 2 NICs on each server, one is in the LAN for MAPI and the second is on a different Subnet and different physically connected network too for replication.

when I try to setup the DAG it asks for the witness server and folder which I have already setup and added the required Exchange security group permission to the local administrator "Exchange Trusted Subsystem".

The DAG group gets created but with only one Mailbox server or one of the two servers that I have installed.

When I try to add the second server I get this error:

error: a server-side database availability group administrative operation failed, error: The operation failed. createcluster errors may result from incorrectly configured static addresses.

I am also attaching a snapshot of the error. I couldn't get around this problem and hope that someone could know what's the solution?

Just would like to mention 2 things more, I have configured manually the IPs of the replication NICs as following
First SERVER/REPlication NIC
172.16.20.15
255.255.0.0

Second Server/ Replication NIC
172.16.20.16
255.255.0.0

Second thing, the customer doesn't have a DHCP server in the Servers subnet which had me to manually configure a Static IPs for the DAG group.

I'm attaching snapshot of the error.

I would appreciate any help.
Thanks
dag-error.jpg
0
Comment
Question by:Mohammed Hamada
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
5 Comments
 
LVL 19

Expert Comment

by:suriyaehnop
ID: 39756783
Have set statics IP address for DAG name?

http://technet.microsoft.com/en-us/library/dd297934(v=exchg.141).aspx

Also, make sure you do add this records on DNS server as well
0
 
LVL 7

Expert Comment

by:dsnegi_25dec
ID: 39756994
there are many reason for this error like

Server is not able to communicate with DC.
http://social.technet.microsoft.com/Forums/exchange/en-US/4e1032a9-343f-4874-91ff-f6436d37a6c6/add-dag-problem?forum=exchange2010

IPV6 issue
http://msexchangeguru.com/2012/06/05/dag-errors/

Check if Exchange trusted subsystem is added to local admin group?
Check the MAPI and replication network configuration and binding order!
restart system attendant services and check if that works
0
 
LVL 24

Author Comment

by:Mohammed Hamada
ID: 39758931
It seems there's an issue between the witness server and the AD I think, the Witness server is a non-exchange server and i am not sure if this could be a problem.

I am going to try a different server and see how it goes. I'm quite sure of my setup as the NICs binding order is correct. The Exchange Trusted Subsystem is a member of the local admin group but still whenever I create the DAG I get the following error

The Exchange Trusted Subsystem is not a member of the local Administrators group on specified witness server <ServerName>.

I haven't configured the route as I am not sure how would the configuration look like in this case.
0
 
LVL 24

Accepted Solution

by:
Mohammed Hamada earned 0 total points
ID: 39760671
Thanks everyone .

I have solved the problem as it seems it was related to a static persistent route for the second NIC that was configured somehow! I didn't configure it and the only way I could find out is by using command line ( route print )

and there I found the route on both servers
172.16.0.0 255.240.0.0 10.0.10.10 default

Using the command line route /f , have reset all the routing tables on both servers Exch 1 and 2. and after restarting it went very well.

and as for the Witness Server, I have added the Witness Server in AD to the "Exchange Trusted Subsystem" security group. and after recreating the DAG group everything worked well.
0
 
LVL 24

Author Closing Comment

by:Mohammed Hamada
ID: 39773131
self resolved
0

Featured Post

Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

I don't pretend to be an expert at this, but I have found a few things that are useful. I hope that sharing them here will help others, so they will not have to face some rather hard choices. Since I felt this to be a topic of enough importance and…
The main intent of this article is to make you aware of ‘Exchange fail to mount’ error, its effects, causes, and solution.
The viewer will learn how to simulate a series of sales calls dependent on a single skill level and learn how to simulate a series of sales calls dependent on two skill levels. Simulating Independent Sales Calls: Enter .75 into cell C2 – “skill leve…
The viewer will learn how to use the =DISCRINV command to create a discrete random variable, use this command to model a set of probabilities and outcomes in a Monte Carlo simulation, and learn how to find the standard deviation of a set of probabil…
Suggested Courses

656 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question