Cymbaline65
asked on
DAG Error "No static address matched networks"
Hello All-
I’ve got a 3-node Exchange 2010 SP2 DAG in place. Two primary nodes are at one location and the third (different location,AD Site and subnet) contains copies of the databases. All locations are well-connected.
When I tried to enable DataCenterActivationMode, I received the following error: [PS] C:\Windows\system32>Set-Da
WARNING: No static address matched networks 'Cluster Network 2'. Specified static addresses: '151.x.y.23'
WARNING: Network name ‘dag1' is not online. Please check that the IP address configuration for the database availability group is correct.
Now, I can mount and dismount mailbox databases, activate the copies – all without error. The IP address in the error is the IP address assigned via the EMC GUI when I first stood up the DAG. Also, the Cluster Administrator shows the cluster as being online.
Once everything was stood up last night, no additional error messages were generated by the Cluster Service so everything <appears> to be working properly.
Reviewing the DAGTASK logs, below is the only error that was generated. I was adding a 3rd member to the DAG. Originally, before the 2nd site was stood up, I had a 2-Node DAG with File Share Witness. Here is the error:
[2013-01-28T18:56:44] Updated Progress 'Checking if Mailbox server 'WUDCUSTEX' is in a database availability group.' 14%.
[2013-01-28T18:56:44] Working
[2013-01-28T18:56:44] GetRemoteCluster() for the mailbox server failed with exception = An Active Manager operation failed. Error: An error occurred while attempting a cluster operation. Error: Cluster API '"OpenCluster(WUDCUSTEX.WX
[2013-01-28T18:56:44] Ignoring previous error, as it is acceptable if the cluster does not exist yet.
[2013-01-28T18:56:44] DumpClusterTopology: Opening remote cluster dag1.
[2013-01-28T18:56:44] Dumping the cluster by connecting to: dag1.
According to the log, the DAG is now ignoring the FSW even though it does not like me removing it from the DAG definition.
Final bits of information:
All 3 DAG nodes have a SINGLE network card for both MAPI and replication traffic. I know this is not optimal or best practice but geo-political forces beyond my control forced me to this configuration. A second NIC is not an option.
Exchange Trusted Subsystem is a member of each Exch2010 server's local admin group
I’ve seen some posts of a similar nature to what I’m experiencing but nothing that fits my environment so any and all help is appreciated.
Regards,
Eric
I’ve got a 3-node Exchange 2010 SP2 DAG in place. Two primary nodes are at one location and the third (different location,AD Site and subnet) contains copies of the databases. All locations are well-connected.
When I tried to enable DataCenterActivationMode, I received the following error: [PS] C:\Windows\system32>Set-Da
WARNING: No static address matched networks 'Cluster Network 2'. Specified static addresses: '151.x.y.23'
WARNING: Network name ‘dag1' is not online. Please check that the IP address configuration for the database availability group is correct.
Now, I can mount and dismount mailbox databases, activate the copies – all without error. The IP address in the error is the IP address assigned via the EMC GUI when I first stood up the DAG. Also, the Cluster Administrator shows the cluster as being online.
Once everything was stood up last night, no additional error messages were generated by the Cluster Service so everything <appears> to be working properly.
Reviewing the DAGTASK logs, below is the only error that was generated. I was adding a 3rd member to the DAG. Originally, before the 2nd site was stood up, I had a 2-Node DAG with File Share Witness. Here is the error:
[2013-01-28T18:56:44] Updated Progress 'Checking if Mailbox server 'WUDCUSTEX' is in a database availability group.' 14%.
[2013-01-28T18:56:44] Working
[2013-01-28T18:56:44] GetRemoteCluster() for the mailbox server failed with exception = An Active Manager operation failed. Error: An error occurred while attempting a cluster operation. Error: Cluster API '"OpenCluster(WUDCUSTEX.WX
[2013-01-28T18:56:44] Ignoring previous error, as it is acceptable if the cluster does not exist yet.
[2013-01-28T18:56:44] DumpClusterTopology: Opening remote cluster dag1.
[2013-01-28T18:56:44] Dumping the cluster by connecting to: dag1.
According to the log, the DAG is now ignoring the FSW even though it does not like me removing it from the DAG definition.
Final bits of information:
All 3 DAG nodes have a SINGLE network card for both MAPI and replication traffic. I know this is not optimal or best practice but geo-political forces beyond my control forced me to this configuration. A second NIC is not an option.
Exchange Trusted Subsystem is a member of each Exch2010 server's local admin group
I’ve seen some posts of a similar nature to what I’m experiencing but nothing that fits my environment so any and all help is appreciated.
Regards,
Eric
Amit
What OS level AV you are using. Just stop it and try again. I assume firewall settings are configured properly and there are no time sync issue. Also, want to know, if these are VM or Physical Servers.
ASKER
Hello Amitkulshrestha-
OS: Windows 2008 R2
Firewall: Firewall disabled but service is running
Machines: Machines are virtualized on VMWare host platform
Time: Time is synched
Eric
OS: Windows 2008 R2
Firewall: Firewall disabled but service is running
Machines: Machines are virtualized on VMWare host platform
Time: Time is synched
Eric
What about Remote Registry Service? Is that running on 3 server.
ASKER
Remote Registry Service on on all DAG members
ya, that should be running and set to automatic
ASKER
It is. Researching where it may be related to multiple AD sites and subnets.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Sorry to take so long to update. Indeed it was adding the additional DAG IP from the second site to the DAG configuration.
Not enough time to prep and research prior to actually doing the work.
Thanks!
Not enough time to prep and research prior to actually doing the work.
Thanks!