RE: DAG static ip address unreachable
It's certainly related to clustering, and probably not Exchange :) My two cents: you've lost quorum on your DAG, is your FSW (if appropriate) up? -Original Message- From: bounce-988-8066...@lyris.sunbelt-software.com [mailto:bounce-988-8066...@lyris.sunbelt-software.com] On Behalf Of Maglinger, Paul Sent: 17 October 2011 15:17 To: MS-Exchange Admin Issues Subject: FW: DAG static ip address unreachable Looking at my database copies from the EMC, all of them are healthy and nothing is getting queued up. Is this more a question for the Windows list? -Original Message- From: Maglinger, Paul Sent: Sunday, October 16, 2011 3:07 AM To: 'daemon Root' Subject: RE: DAG static ip address unreachable It doesn't appear to be disabled. -Original Message- From: daemon Root [mailto:daemonr...@sysadmin-cr.com] Sent: Saturday, October 15, 2011 5:05 PM To: Maglinger, Paul Subject: RE: DAG static ip address unreachable Is the Cluster Name Object CNO available? Sent from my Windows Mango Phone From: Maglinger, Paul Sent: 10/15/2011 15:42 To: MS-Exchange Admin Issues Subject: DAG static ip address unreachable Running Exchange 2010 SP1 RU5 on Windows 2008 R2 box. Last night we started getting a failure on our backups that the DAG was unreachable. We are unable to ping the DAG from the backup server or even the mailbox servers themselves. The IP is set correctly in the properties. I've checked Windows Firewall and that's not the problem. I've brought up the Failover Cluster Manager and under the Cluster Core Resources the IP Address and the Name are both offline on all three nodes. Attempts to bring the resource online return with 0x80071397 - The operation failed because either the specified cluster node is not the owner of the resource, or the node is not a possible owner of the resource. Going through the system logs I find: Cluster node the_other_server was removed from the active failover cluster membership. The Cluster server on this node may have stopped. The 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. I run the Validate a Configuration wizard and it tells me that my cluster isn't running. I go to the_other_server and find in the system log: The Cluster service is shutting down because quorum was lost. Using Test-ReplicationHealth tells me that my QuorumGroup failed. Googling around found a reference that my cluster could be a little out of sync and suggested clearing and then re-checking the Allow clients to connect through this network box for the Networks in the Failover Cluster Manager. No joy... This appeared to just happen out of blue. There weren't any updates or changes that I put on and no one is fessing up to any changes. Not sure where to go from here. Suggestions? -Paul --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist
RE: DAG static ip address unreachable
The witness server is on one of the servers in my CAA, and is up and online. -Original Message- From: Sobey, Richard A [mailto:r.so...@imperial.ac.uk] Sent: Monday, October 17, 2011 9:20 AM To: MS-Exchange Admin Issues Subject: RE: DAG static ip address unreachable It's certainly related to clustering, and probably not Exchange :) My two cents: you've lost quorum on your DAG, is your FSW (if appropriate) up? -Original Message- From: bounce-988-8066...@lyris.sunbelt-software.com [mailto:bounce-988-8066...@lyris.sunbelt-software.com] On Behalf Of Maglinger, Paul Sent: 17 October 2011 15:17 To: MS-Exchange Admin Issues Subject: FW: DAG static ip address unreachable Looking at my database copies from the EMC, all of them are healthy and nothing is getting queued up. Is this more a question for the Windows list? -Original Message- From: Maglinger, Paul Sent: Sunday, October 16, 2011 3:07 AM To: 'daemon Root' Subject: RE: DAG static ip address unreachable It doesn't appear to be disabled. -Original Message- From: daemon Root [mailto:daemonr...@sysadmin-cr.com] Sent: Saturday, October 15, 2011 5:05 PM To: Maglinger, Paul Subject: RE: DAG static ip address unreachable Is the Cluster Name Object CNO available? Sent from my Windows Mango Phone From: Maglinger, Paul Sent: 10/15/2011 15:42 To: MS-Exchange Admin Issues Subject: DAG static ip address unreachable Running Exchange 2010 SP1 RU5 on Windows 2008 R2 box. Last night we started getting a failure on our backups that the DAG was unreachable. We are unable to ping the DAG from the backup server or even the mailbox servers themselves. The IP is set correctly in the properties. I've checked Windows Firewall and that's not the problem. I've brought up the Failover Cluster Manager and under the Cluster Core Resources the IP Address and the Name are both offline on all three nodes. Attempts to bring the resource online return with 0x80071397 - The operation failed because either the specified cluster node is not the owner of the resource, or the node is not a possible owner of the resource. Going through the system logs I find: Cluster node the_other_server was removed from the active failover cluster membership. The Cluster server on this node may have stopped. The 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. I run the Validate a Configuration wizard and it tells me that my cluster isn't running. I go to the_other_server and find in the system log: The Cluster service is shutting down because quorum was lost. Using Test-ReplicationHealth tells me that my QuorumGroup failed. Googling around found a reference that my cluster could be a little out of sync and suggested clearing and then re-checking the Allow clients to connect through this network box for the Networks in the Failover Cluster Manager. No joy... This appeared to just happen out of blue. There weren't any updates or changes that I put on and no one is fessing up to any changes. Not sure where to go from here. Suggestions? -Paul --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist
RE: DAG static ip address unreachable
FOUND THE PROBLEM! Somehow it appears that the DAG server that resides in another site had lost one of the persistent routes. Now another question... Has anyone heard of a persistent route just disappearing out of the blue? I could understand it going away if it wasn't persistent and we rebooted the system, but that wasn't the case, but the system wasn't rebooted. This was working for 3 weeks before this happened. -Paul -Original Message- From: Maglinger, Paul [mailto:pmaglin...@scvl.com] Sent: Monday, October 17, 2011 9:45 AM To: MS-Exchange Admin Issues Subject: RE: DAG static ip address unreachable The witness server is on one of the servers in my CAA, and is up and online. -Original Message- From: Sobey, Richard A [mailto:r.so...@imperial.ac.uk] Sent: Monday, October 17, 2011 9:20 AM To: MS-Exchange Admin Issues Subject: RE: DAG static ip address unreachable It's certainly related to clustering, and probably not Exchange :) My two cents: you've lost quorum on your DAG, is your FSW (if appropriate) up? -Original Message- From: bounce-988-8066...@lyris.sunbelt-software.com [mailto:bounce-988-8066...@lyris.sunbelt-software.com] On Behalf Of Maglinger, Paul Sent: 17 October 2011 15:17 To: MS-Exchange Admin Issues Subject: FW: DAG static ip address unreachable Looking at my database copies from the EMC, all of them are healthy and nothing is getting queued up. Is this more a question for the Windows list? -Original Message- From: Maglinger, Paul Sent: Sunday, October 16, 2011 3:07 AM To: 'daemon Root' Subject: RE: DAG static ip address unreachable It doesn't appear to be disabled. -Original Message- From: daemon Root [mailto:daemonr...@sysadmin-cr.com] Sent: Saturday, October 15, 2011 5:05 PM To: Maglinger, Paul Subject: RE: DAG static ip address unreachable Is the Cluster Name Object CNO available? Sent from my Windows Mango Phone From: Maglinger, Paul Sent: 10/15/2011 15:42 To: MS-Exchange Admin Issues Subject: DAG static ip address unreachable Running Exchange 2010 SP1 RU5 on Windows 2008 R2 box. Last night we started getting a failure on our backups that the DAG was unreachable. We are unable to ping the DAG from the backup server or even the mailbox servers themselves. The IP is set correctly in the properties. I've checked Windows Firewall and that's not the problem. I've brought up the Failover Cluster Manager and under the Cluster Core Resources the IP Address and the Name are both offline on all three nodes. Attempts to bring the resource online return with 0x80071397 - The operation failed because either the specified cluster node is not the owner of the resource, or the node is not a possible owner of the resource. Going through the system logs I find: Cluster node the_other_server was removed from the active failover cluster membership. The Cluster server on this node may have stopped. The 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. I run the Validate a Configuration wizard and it tells me that my cluster isn't running. I go to the_other_server and find in the system log: The Cluster service is shutting down because quorum was lost. Using Test-ReplicationHealth tells me that my QuorumGroup failed. Googling around found a reference that my cluster could be a little out of sync and suggested clearing and then re-checking the Allow clients to connect through this network box for the Networks in the Failover Cluster Manager. No joy... This appeared to just happen out of blue. There weren't any updates or changes that I put on and no one is fessing up to any changes. Not sure where to go from here. Suggestions? -Paul --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist
RE: DAG static ip address unreachable
Yes. This is a known issue if you use the route.exe command to set routes. The resolution is to use netsh.exe to set routes. And no, there are no plans to fix the problem. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com -Original Message- From: Maglinger, Paul [mailto:pmaglin...@scvl.com] Sent: Monday, October 17, 2011 11:29 AM To: MS-Exchange Admin Issues Subject: RE: DAG static ip address unreachable FOUND THE PROBLEM! Somehow it appears that the DAG server that resides in another site had lost one of the persistent routes. Now another question... Has anyone heard of a persistent route just disappearing out of the blue? I could understand it going away if it wasn't persistent and we rebooted the system, but that wasn't the case, but the system wasn't rebooted. This was working for 3 weeks before this happened. -Paul -Original Message- From: Maglinger, Paul [mailto:pmaglin...@scvl.com] Sent: Monday, October 17, 2011 9:45 AM To: MS-Exchange Admin Issues Subject: RE: DAG static ip address unreachable The witness server is on one of the servers in my CAA, and is up and online. -Original Message- From: Sobey, Richard A [mailto:r.so...@imperial.ac.uk] Sent: Monday, October 17, 2011 9:20 AM To: MS-Exchange Admin Issues Subject: RE: DAG static ip address unreachable It's certainly related to clustering, and probably not Exchange :) My two cents: you've lost quorum on your DAG, is your FSW (if appropriate) up? -Original Message- From: bounce-988-8066...@lyris.sunbelt-software.com [mailto:bounce-988-8066...@lyris.sunbelt-software.com] On Behalf Of Maglinger, Paul Sent: 17 October 2011 15:17 To: MS-Exchange Admin Issues Subject: FW: DAG static ip address unreachable Looking at my database copies from the EMC, all of them are healthy and nothing is getting queued up. Is this more a question for the Windows list? -Original Message- From: Maglinger, Paul Sent: Sunday, October 16, 2011 3:07 AM To: 'daemon Root' Subject: RE: DAG static ip address unreachable It doesn't appear to be disabled. -Original Message- From: daemon Root [mailto:daemonr...@sysadmin-cr.com] Sent: Saturday, October 15, 2011 5:05 PM To: Maglinger, Paul Subject: RE: DAG static ip address unreachable Is the Cluster Name Object CNO available? Sent from my Windows Mango Phone From: Maglinger, Paul Sent: 10/15/2011 15:42 To: MS-Exchange Admin Issues Subject: DAG static ip address unreachable Running Exchange 2010 SP1 RU5 on Windows 2008 R2 box. Last night we started getting a failure on our backups that the DAG was unreachable. We are unable to ping the DAG from the backup server or even the mailbox servers themselves. The IP is set correctly in the properties. I've checked Windows Firewall and that's not the problem. I've brought up the Failover Cluster Manager and under the Cluster Core Resources the IP Address and the Name are both offline on all three nodes. Attempts to bring the resource online return with 0x80071397 - The operation failed because either the specified cluster node is not the owner of the resource, or the node is not a possible owner of the resource. Going through the system logs I find: Cluster node the_other_server was removed from the active failover cluster membership. The Cluster server on this node may have stopped. The 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. I run the Validate a Configuration wizard and it tells me that my cluster isn't running. I go to the_other_server and find in the system log: The Cluster service is shutting down because quorum was lost. Using Test-ReplicationHealth tells me that my QuorumGroup failed. Googling around found a reference that my cluster could be a little out of sync and suggested clearing and then re-checking the Allow clients to connect through this network box for the Networks in the Failover Cluster Manager. No joy... This appeared to just happen out of blue. There weren't any updates or changes that I put on and no one is fessing up to any changes. Not sure where to go from here. Suggestions? -Paul --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana
