Link to home
Start Free TrialLog in
Avatar of mshaikh22

asked on

Exchange 2010 Dag enviroment issues

Dear Experts,

I am currently having some serious problems with my exchange 2010 dag environment running on 5 exchange mailbox servers and 14 databases. 3 mailbox servers holding database copies and 2 mailbox server are being used for only heartbeat for now.

2 exchange mailbox server (ex01 and ex03) are on the subnet.  (,
1 Exchange mailbox server (ex02) is on the subnet    ( (All 3 mailbox servers are on one site)
hw01 - mailbox server (seperate site)
nw01 - mailbox server (seperate site)

The cluster is on a node majority mode

dag ips

Earlier this morning, ex02 ip went offline with the following event log 1135 and dag ip came online and was offline. As a result all of the databases on went in a failed state and ip went unavailable  and was giving errors like the network manager could not be intialized.

after sometime and a reboot ex02 came back online, but ex03 ip became unavailable and its database went into failed state. I am not sure about ex03,  why did it go out and how can i bring the ip to an available state

Would need your help in the matter?

thank you

Avatar of ArneLovius
Flag of United Kingdom of Great Britain and Northern Ireland image

I would guess that the cluster IP has moved to the other subnet, you should be able to see this in cluster manager

to move it back, you would need to update the cluster from an elevated command prompt

cluster.exe <DAG F.Q.D.N.> group "cluster group" /moveto:<server name>
cluster.exe <DAG F.Q.D.N.> group "available storage" /moveto:<server name>

Open in new window

if the domain name was domain.internal, the  DAG name was DAG-01 and the server was server-1, they would look like

cluster.exe DAG-01.domain.internal group "cluster group" /moveto:server-1
cluster.exe DAG-01.domain.internal group "available storage" /moveto:server-1

Open in new window

However, this does not cover the databases being in a failed state. I would guess that "something else" has happened as well, such as losing the witness share at the same time.
Avatar of mshaikh22


thank you ArneLovius

I put in the following command

cluster.exe DAG-01.domain.internal group "cluster group"

I am getting the following  

System error 1331 has occurred (0x00000533).
Logon failure: account currently disabled.

how can i find out the account related to this.
I locked out my account. its fine.
Sorry about that. The issue regarding the cluster group has not been resolved. the symptons are the same.

ex03 node is still unable in the cluster. It has not moved to another subnet

In failover cluster manager

cluster network 1 says - online  - unavailable

in daggroupavailabilitynetwork section its showing ex03 ip as unavailable also.

I dont see much in event logs, the cluster service keep stopping.

How can we resolve this issue?
can you post screengrabs from the cluster manager
Please find Failover Cluster Manager screenshot

cluster network 1 says - online  - unavailable
I even followed steps laid in the technet post, but it didnt bring the cluster resource back online, even by unchecking the client option and re checking it.
are you using different MAPI and replication networks ?

I'm not sure what you meant by "2 mailbox server are being used for only heartbeat for now" I they are not active mailbox servers, then remove them from the DAG.

Where is your file share witness ?
we are using a team nic that does mapi and replication together.

there is no file witness - its configured as node majority model (which works on a n+1 model)

bg ad site - ex01 ex03 same subnet
bg ad site - different subnet - l ex01
h ad site h ex01
n ad site n ex01
I tried changing the ip of ex03 to a different subnet. I noticed that nothing changed on the cluster and the new cluster network is not showing.

Would really appreciate your help with this.


when you have 5 live servers, the witness is not used, but as soon as a server goes down and you had an even number of live servers, the witness was required, and this lack of witness is the probable cause of your failure

I would suggest that you configured the witness.
I keep getting this error

Node 'EX03' failed to establish a communication session while joining the cluster. This was due to an authentication failure. Please verify that the nodes are running compatible versions of the cluster service software.
I would check time sync between the servers.

Have you added the witness?

The witness can be on any member server, but not a domain controller or a DFS share.
file share witness is on configured to be on cas01
and cas02

but the failover cluster manager is based on node majority model
time is synced between all servers
Done the witness yet ?
cluster does not use its use node majority model.
witness was configured prior to changing the model

How can I solve 1570 event error
hi experts

we removed ex03 from the dag and left it for a day, but cant re add to the dag, we are getting the following error message. would appreciate your help on this, #

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

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..
I am going to guess that the cluster IP address does not match the active cluster host.
the dag ip is the same as the server ip, as it was failed over.

dag ips  online offline
Avatar of mshaikh22

Link to home
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Couldn't get a solution for the issue