LrdKanien
asked on
Exchange 2010 DAG cluster name wouldn't stay online
I'm entering this as a related question because I had help with another issue that could have been related, but I'm not sure it was as it doesn't seem likely. Here was my other problem:
https://www.experts-exchange.com/questions/27304293/Exchange-2010-DAG-800-mails-in-queue-help.html
My cluster kept going off line and this is the event I was seeing:
Log Name: System
Source: Microsoft-Windows-Failover
Date: 9/12/2011 2:28:31 PM
Event ID: 1135
Task Category: None
Level: Critical
Keywords:
User: SYSTEM
Computer: abc-EXCHANGE.domain.local
Description:
Cluster node 'EXCHANGE' was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapters on this node. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Fa
<EventID>1135</EventID>
<Version>0</Version>
<Level>1</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000
<TimeCreated SystemTime="2011-09-12T21:
<EventRecordID>231709</Eve
<Correlation />
<Execution ProcessID="8976" ThreadID="6232" />
<Channel>System</Channel>
<Computer>abc-EXCHANGE.dom
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="NodeName">EXCHANGE</
</EventData>
</Event>
https://www.experts-exchange.com/questions/27304293/Exchange-2010-DAG-800-mails-in-queue-help.html
My cluster kept going off line and this is the event I was seeing:
Log Name: System
Source: Microsoft-Windows-Failover
Date: 9/12/2011 2:28:31 PM
Event ID: 1135
Task Category: None
Level: Critical
Keywords:
User: SYSTEM
Computer: abc-EXCHANGE.domain.local
Description:
Cluster node 'EXCHANGE' was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapters on this node. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Fa
<EventID>1135</EventID>
<Version>0</Version>
<Level>1</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000
<TimeCreated SystemTime="2011-09-12T21:
<EventRecordID>231709</Eve
<Correlation />
<Execution ProcessID="8976" ThreadID="6232" />
<Channel>System</Channel>
<Computer>abc-EXCHANGE.dom
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="NodeName">EXCHANGE</
</EventData>
</Event>
Malli Boppe
How many members in the DAG and are the database mounted on any of the server.
ASKER
2 members in separate active directory sites
Dagname is ABCDAG resovles to 192.168.1.122.
Primary exchange is Exchange and resolves to 192.168.1.227.
Secondary exchagne is ABC-Exchange and resolves to 192.168.10.227.
Witness is in same site as the .10 network where all of the clients are.
Databases mounted on Exchange.
Dagname is ABCDAG resovles to 192.168.1.122.
Primary exchange is Exchange and resolves to 192.168.1.227.
Secondary exchagne is ABC-Exchange and resolves to 192.168.10.227.
Witness is in same site as the .10 network where all of the clients are.
Databases mounted on Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I had to take the DAG down until this weekend. I had two networks listed as DAG networks, but only one IP for the DAG. I think I should have had one IP from each site for the DAG.
yes, you need one IP for each site
otherwise when you attempt to bring the cluster online in other site it will be on the wrong subnet
you may want to also include Windows for this question, as this is not an Exchange issue, but a Windows clustering one
otherwise when you attempt to bring the cluster online in other site it will be on the wrong subnet
you may want to also include Windows for this question, as this is not an Exchange issue, but a Windows clustering one
Did you check the link that I pasted. It clearly explains about having 2 DAG IP's when using a 2 member DAG at multiple sites.
ASKER
Yes, I did. Thank you!