DAG/cluster network troubleshooting

We have a 2 DAG cluster EX01 and EX02. EX02 holds all active copies and EX01 holds all passive copies.
When trying to move active copies from 02 to 01 it fails everytime. Also trying to move Primary active manager from 02 to 01 fails. There is an error in Cluster manager: Cluster resource 'IPv4 Static Address 1 (Cluster Group)' in clustered service
or application 'Cluster Group' failed. Event ID 1069. All Replication test and health test come back good. I think the error is related to network design and need some advice.
EX01 (HUB,CAS, MB)                 EX02 (MB)
Mapi 10.11.1.4/24                   Mapi 10.11.1.20/24
Replication 10.0.5.2/30           Replication 10.0.5.1/30
We have a single DAG IP 10.11.1.21 does it need to be on the same network as replication ?? Do we need to have 2 IPs for DAG??
We want EX01 be the primary and hold active copies and EX02 be secondary
Please advice

Yes that have never been an issue - the DAG is online all passive copies are healthy. The issue is that EX01 can hold only passive copies - when I run move-activedatabasecopy cmdlet it fails to mount it every time. Currently EX01 holds all
passive copies and EX02 holds all active copies and it should be the other way around. It looks like the versions of updates/rollups are slightly different between 2 servers so I'm exploring options how to sync updates
alex serdyukov
Hi,
Can you create a test database and then try to move it ? Paste the error if you get any.
Amit Rawat | MCITP - Exchange 2007/2010| CCNA |MCSE- 2003| Lync 2010|http://blog.amitrawat.net

Similar Messages

DAG 2010 Cluster IP address resource 'Cluster IP Address' cannot be brought online because the cluster network replication

Hello,
DAG Exchange 2010 SP3 RU6 with MAPI network and Replication network. All works correctly.
But, when the DAG member restarts , the cluster goes offline and i can't bring it online.
The message error:
Cluster IP address resource 'Cluster IP Address' cannot be brought online because the cluster network 'Cluster Network 1' is not configured to allow client access.
Cluster Network 1 is the replication network and it is normal that allow client access is unchecked
I already tried to check, apply then uncheck apply. it does anything.
Could you please help me to figure out the issue ?
Best regards

Hi,
Check below link.
http://forums.msexchange.org/Cluster_network_name_is_not_online/m_1800552315/tm.htm
I was able to resolve the issue without taking down any resources.
First, I noticed that the Failover Cluster Manager "Cluster Name" had the IP address of the replication network only..
After going back through the guide @
http://technet.microsoft.com/en-us/library/dd638104.aspx I changed the properties on the NICs for file sharing, etc..I then adjusted windows firewall rules to block traffic from my MAPI network destined for the replication network.
I then removed the IP from the replication network on the DAG leaving only the 1 MAPI network IP.
After an hour or so, I ran Get-DatabaseAvailabilityGroupNetwork and seen that the MAPIAccess property was finally set to true on my MAPI network. I went back to Failover Cluster Manager and my Cluster Core Resource Cluster Name dropped the IP address that was
associated (IP from the replication network) I added a new IP from my Mapi network range, updated the DAG IP in Exchange and the DNS record for the DAG and my cluster resource came online.

DAG Cluster Failed to Resume Primary Active Manager

Hi there,
I ran the StartDagServerMaintenance.ps1 script on our SiteA Exchange server then updated it and rebooted. SiteB Exchange server now has active Mailbox Database and is doing Client Access etc. After reboot of SiteA Exchange we had network issues and in the
process of troubleshooting I deleted the network adapters from Device Manager, and ran netsh int ip reset, then reconfigured them with their static IP's, and static routes for the Replication network.
Site A MAPI Network - 192.168.1.0/24
Site B MAPI Network - 192.168.2.0/24
Site A Replication Network - 10.10.1.0/24
Site B Replication Network - 10.10.2.0/24
Each site has one Exchange Server running all Roles and is in DAC Mode, on Exchange 2010 SP2.
Right now I cannot run the StopDagServerMaintenance.ps1 script because it says
Failed to resume the ability of the server SiteA-EX1 to host the Primary Active Manager, 'cluster.exe /cluster:SiteA-EX1 node SiteA-EX1 /resume' returned 5050.
In the EMC, Organization-Mailbox-DAG Networks, DagNetwork03 and DagNetwork04 say subnet 192.168.1.0/24 and 10.10.1.0/24 are Down and Unavailable.
In Failover Cluster Manager, Cluster Network 3 and Cluster Network 4 are in Status: Down.
I can ping all the subnets and Exchange IP addresses from both Exchange server.
SiteA Database copy is Healthy and no copy count. SiteB is Mounted.
EDIT: Networks are all up, question now is how do I move the PAM to the SiteA?
I tried this command:
Cluster.exe DAG1 group "Cluster Group" /moveto:SiteA-EX1
I get System error 5012 has occurred
The cluster group cannot be found.
The AlternateWitnessShareInUse is the alternate in SiteB.
When I run the command "cluster group" I get this:
Group Node
Status
Cluster Group SiteB-EX1
Online
Available Storage SiteB-EX1
Offline
I dont see the Node for SiteB.

I tried this command:
Cluster.exe DAG1 group "Cluster Group" /moveto:SiteA-EX1
I get System error 5012 has occurred
The cluster group cannot be found.
The AlternateWitnessShareInUse is the alternate in SiteB.
When I run the command "cluster group" I get this:
Group Node
Status
Cluster Group SiteB-EX1
Online
Available Storage SiteB-EX1
Offline
I dont see the Node for SiteB.
Hi,
Have you tried to run Cluster Group "Cluster Group" /move
Martina Miskovic

The cluster network name is not online

Our cluster is a four node, Windows Server 2012 failover cluster running Hyper-V role only. Today it starts throwing the error 'The cluster network name is not online'. The IP is online (and all the VMs are running) but migrations fail and any
scripts that rely on the name fail. Attempting a More Actions | Repair results in 'The action 'Repair' did not complete. Error code 0x80005000'
The AD object for the cluster still exists. We do not have a disjoint namespace.
I am at a loss and hoping for some insight from the forum.
Thanks

Hi BlakeDuffey,
It seems like the computer object registry keys missing, please first try to runn gpupdate /force command on all nodes and repair again, if it not work please refer the following
article to repair the object registry key..
The related article:
Cluster network name resource 'Cluster Name' cannot be brought online, Unable to get Computer Object using GUID.
http://blogs.technet.com/b/csstwplatform/archive/2010/10/15/cluster-network-name-resource-cluster-name-cannot-be-brought-online-unable-to-get-computer-object-using-guid.aspx
Windows Server 2008 R2: Failover Clustering Troubleshooting Scenarios
https://technet.microsoft.com/en-us/magazine/hh289314.aspx
How to Troubleshoot Create Cluster failures in Windows Server 2012
http://blogs.msdn.com/b/clustering/archive/2012/05/07/10301709.aspx
http://blogs.technet.com/b/askcore/archive/2012/09/25/cno-blog-series-increasing-awareness-around-the-cluster-name-object-cno.aspx
I’m glad to be of help to you!
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Cluster network name resource 'Cluster Name' failed registration of one or more associated DNS name(s) for the following reason: The handle is invalid.

I'm stuck here trying to figure this error out.
2003 domain, 2012 hyper v core 3 nodes. (I have two of these hyper V groups, hvclust2012 is the problem group, hvclust2008 is okay)
In Failover Cluster Manager I see these errors, "Cluster network name resource 'Cluster Name' failed registration of one or more associated DNS name(s) for the following reason: The handle is invalid."
I restarted the host node that was listed in having the error then another node starts showing the errors.
I tried to follow this site: http://blog.subvertallmedia.com/2012/12/06/repairing-a-failover-cluster-in-windows-server-2012-live-migration-fails-dns-cluster-name-errors/
Then this error shows up when doing the repair: there was an error repairing the active directory object for 'Cluster Name'
I looked at our domain controller and noticed I don't have access to local users and groups. I can access our other hvclust2008 (both clusters are same version 2012).
<image here>
I came upon this thread: http://social.technet.microsoft.com/Forums/en-US/85fc2ad5-b0c0-41f0-900e-df1db8625445/windows-2012-cluster-resource-name-fails-dns-registration-evt-1196?forum=winserverClustering
Now, I'm stuck on adding a managed service account (mas). I'm not sure if I'm way off track to fix this. Any advice? Thanks in advance!
<image here>

Thanks Elton,
I restarted 3 hosts after applying the hotfix. Then I did the steps below and got stuck on step 5. That is when I get the error (image above). There
was an error repairing the active directory object for 'Cluster Name'. For more data, see 'Information Details'.
To reset the password on the affected name resource, perform the following steps:
From Failover Cluster Manager, locate the name resource.
Right-click on the resource, and click Properties.
On the Policies tab, select If resource fails, do not restart, and then click OK.
Right-click on the resource, click More Actions, and then click Simulate Failure.
When the name resource shows "Failed," right-click on the resource, click More Actions, and then click Repair.
After the name resource is online, right-click on the resource, and then click Properties.
On the Policies tab, select If resource fails, attempt restart on current node, and then click OK.
Thanks

Can I change which nic is used for a cluster network when more than one nic on the node is on same subnet?

This cluster has been up and working for maybe a year and a half the way it is. There are two nodes, running Server 2012. In addition to a couple network interfaces devoted to VM traffic each node has:
Management Interface: 192.168.1.0/24
iSCSI Interface: 192.168.1.0/24
Internal Cluster Interface: 192.168.99.0/24
The iSCSI interfaces have to be on same subnet as management interfaces due to limitations in the shared storage. Basically if I segregate it I wouldn't be able access the shared storage itself for any kind of management or maintenance tasks.
I have restricted the iSCSI traffic to only use the one interface on each cluster node but I noticed that one of the cluster networks is connecting the management interface on one cluster node member with the iSCSI interface on the other cluster node member.
I would like for the cluster network to be using the management interface on both cluster node members so as not to interfere with iSCSI traffic. Can I change this?
Binding order of interfaces is the same on both boxes but maybe I did that after I created the cluster, not sure.

Hi MnM Show,
Tim is correct, if you are using ISCSI Storage and using the network to get to it, it is recommended that the iSCSI Storage fabric have a dedicated and isolated network. This
network should be disabled for Cluster communications so that the network is dedicated to only storage related traffic.
This prevents intra-cluster communication as well as CSV traffic from flowing over same network. During the creation of the Cluster, ISCSI traffic will be detected and the network
will be disabled from Cluster use. This network should set to lowest in the binding order.
The related article:
Configuring Windows Failover Cluster Networks
http://blogs.technet.com/b/askcore/archive/2014/02/20/configuring-windows-failover-cluster-networks.aspx
I’m glad to be of help to you!
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Failover Cluster Network Name Failed and Can't be Repaired

I have an issue that seem to be a different problem than any others have encountered.
I've scoured everything I can find and nothing has fixed my problem.
The problem starts with the common problem of the cluster network name failing on my 2 node server 2012 file server cluster. The computer object was still in AD and appeared to be fine so it was not the common problem of the object
getting deleted somehow. At the time, there was no other object with that name in the recycling bin, so I don't think it was mistakenly deleted and quickly recreated to cover any tracks, so to speak.
Following one guide, I tried to find the registry key that corresponded with the GUID of the object, but neither node in the cluster had it in its registry (which may be part of the problem).
Since it was in the failed state, I tried to do the repair on the object to no avail.
We run a "locked down" DC environment so all computer objects have to be pre-provisioned. They were all pre-provisioned successfully and successfully assigned during cluster creation. The cluster was running with no issues for a month
or so before this problem came up.
When I do a repair on the object while taking diagnostic logs the following 4609 error appears:
The action 'Repair' did not complete. - System.ApplicationException: An error occurred resetting the password for 'Cluster Name'. ---> System.ComponentModel.Win32Exception: Unknown error (0x80005000)
There appears to be a corresponding 4771 error with a failure code 0x18 that comes from the security log of the DC that states there was a Kerberos pre-authentication failure for the cluster network name object (Domain\Clustername$)
I believe this is what is causing the repair failure. All the information I found related to security error 4771 was either a bad credentials given for a user account or the fix was to reconnect the computer to the domain. I can't seem to find
a way to do this with the cluster network name. If there's a way please let me know.
I've tried a number of things, like resetting the object, disabling it, deleting and creating a new object with the same name, deleting that new object and recovering the original, etc...
Can anyone shed some light on what is going on and hopefully how to fix it other than rebuilding the cluster? I'm quite close to just tearing it down and building it back up but am hesitant because this cluster in currently in production...
Any help would be appreciated

Hi,
I don’t find out the similar issue with yours, base on my experience, the 4096 error
often caused by the CSV disk issue, and the 0x80005000 error some time caused by the repetitive computer object in OU. Please check the above related part or run the validate test then post the error information.
Although I do have a CSV, there doesn't seem to be any problems with it and it was running just fine for a month or so before the problem started. I double checked and there is no duplicate computer objects, maybe I don't understand what you mean by
repetitive, could you explain further?
The cluster validates successfully with a few warnings:
Validating cluster resource Name: DT-FileCluster.
This resource is marked with a state of 'Failed' instead of
'Online'. This failed state indicates that the resource had a problem either
coming online or had a failure while it was online. The event logs and cluster
logs may have information that is helpful in identifying the cause of the
failure.
- This is because the cluster name is in the failed state
Validating the service principal names for Name:
DT-FileCluster.
The network name Name: DT-FileCluster does not have a valid
value for the read-only property 'ObjectGUID'. To validate the service principal
name the read-only private property 'ObjectGuid' must have a valid value. To
correct this issue make sure that the network name has been brought online at
least once. If this does not correct this issue you will need to delete the
network name and re-create it.
- This is definitely related to the problem and the GUID probably got removed when we attempted a fix by resetting the object and trying the repair from the failover cluster manager.
The user running validate, does not have permissions to create
computer objects in the 'ad.unlv.edu' domain.
- This is correct, we run a restricted domain. I have a delegated OU that I can pre-provision accounts in. The account was pro-provisioned successfully and was at one point setup and working just fine.
There are no other errors nor warnings.

Cluster Network name resource could not be updated in domain

Hi,
I have the following error and need clarification on the below solution in bold:
Event Id 1206 -
The computer object associated with the cluster network name resource 'Cluster Name' could not be updated in domain 'xxxxx.xxxx'. The error code was 'Password change'. The cluster identity 'ClusterGroup1$' may lack permissions required to update the object.
1 - Move CNO back to the Computers Container
2- Give the Cluster Node Computer Accounts Change Password permission on the CNO
3 - Take the Cluster Name Resource offline
4 - Repair Cluster Name Resource
5 - Bring Cluster Name Resource back online
Firstly, is there any implication?
Secondly if ClusterGroup1$ is my CNO (Cluster Name Object) then is my
cluster node computer account the server nodes in the cluster? E.g. ClusterGroup1$ is the cluster, the nodes are hyperv01 and hyperv02, do I add hyperv01 and hyperv02 to clustergroup1 -- properties -- security?
Thank you.

Hi SPD IT,
If you have pre-stage your cluster object to a specific OU, you needn’t move them to default computer OU, with your current error information it most possible caused by the
lack permission of cluster nodes or some unless GPO applied to cluster nodes, please exclude the cluster from any GPO, then test this issue.
If it does not work please follow this repair action then monitor this issue:
1. Open Failover Cluster manager
2. Select Clustername
3. Under Cluster Core Resources right click on Cluster Name and select Take offline
4. Right click on Cluster Name and select repair.
I’m glad to be of help to you!
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Server 2008 R2 Failover cluster network configuration

Hi
We have a customer with a Server 2008 R2 Hyper-V failover cluster. They have 2 cluster networks, "Cluster Network 1" and "Cluster Network 2".
"Cluster Network 1": NIC team on 172.16.1.0/24 for private cluster network communication
"Cluster Network 2": NIC team on 192.168.1.0/24 for production network communication
I can see that "Cluster Network 1" is configured to "Allow cluster network communication on this network" and "Allow clients to connect through this network".
If "Cluster Network 1" is ONLY for communication between the to cluster nodes then I assume the selection in "Allow clients to connect through this network" should be removed?
/Lasse

It will cause a lost network connection for any client that is accessing through that network. Those clients would need to reconnect.
Did you configure both IPs on the cluster resource name that clients are accessing? If you only configured the one you want, there should be no issue. If you configured both, then it is possible some clients might be connected via the private
network.
Another thing you should, and if you have already done this you will most likely not have issues at all, is that you should disable DNS registration on any network you do not want client access coming through. If the clients can only find the resource
through the DNS name registered, that is the way they will be coming in. In my clusters, which often have 7 or more NICs, there is only one with a published DNS record.
. : | : . : | : . tim

Cluster Network Randomly Failing on Hyper-V Cluster

Please let me know if there is a more appropriate forum. I am having a really strange issue that is seemingly random. I have a 3 host cluster that are all identical hardware and running Hyper-V Server 2012 R2. The networking is as follows and each network
is a different VLAN/Subnet:
3 Cluster networks for virtual machines
1 Cluster network for cluster traffic/management
1 Heartbeat network
2 iSCSI networks for storage
All of the networks are perfectly fine except for one which seems to fail on a random node at a random time during the day (so far, a maximum of once per day).
If I start to live migrate virtual machines that are on the failed network, the cluster network comes back up. The cluster networks are teamed using SCVMM and they are switch independent and running the Dynamic teaming algorithm. We have tried changing the
network switches to see if it was faulty network hardware and things ran fine for one day and then just happened again today so we've ruled that out. The only error message I get is 1127 which is the error stating that the cluster network has gone into a failed
state which doesn't help much. I've run the cluster validation tool for networking several times and it always passes 100%. What I am worried about is hardware incompatibilities as I am using Dell servers (PowerEdge R720) that have Broadcom NIC's in them.
We have 12 Ethernet ports in each server and they are all identical hardware. Four of them are integrated Broadcom, another four that are from a Broadcom quad add-on NIC, and another 4 that are from an Intel quad add-on NIC. All are server grade NIC's. The
only problem I've had in the past is with VMQ which we've had to disable as a workaround but that has always stabilized our virtual networks. In any case all of the cluster networks for virtual machines are set up identically and only this particular one randomly
fails on any one of the three hosts (it has happened at least once on each node now).
I am wondering if anyone has had this experience before. I have read that there are some nasty compatibility issues between Broadcom and Hyper-V but I am wondering if someone could give me some ideas to find out how to narrow this down since the event
logs don't seem to be speaking in obvious terms to me.
Please let me know if you have any suggestions on how to narrow down what's causing this or if there is more information that I could provide. In the meantime, I'm going to try and take note of which virtual machines are running on the host that has the
network fail just in case there's some correlation there but that could take a while to accrue any useful data and our users aren't too happy with the instability...
Thank you in advance for your time and sorry for the lengthy post!

Since I made the change last Friday evening, 4/10, I haven't experienced the issue. I won't be completely convinced that this resolved it until I monitor for at least one more week since it didn't actually present itself for the first time until I was already
one week into live deployment. Also, this link below is much more eloquent than how I put it and describes my issue exactly. Coupled with the KB article that someone posted within this comments section (the same that I posted earlier here) of the article,
this is what led me to check the VMQ status through PowerShell which is much better than going through the registry to do it (I'm running Hyper-V Server 2012 R2 which is like core so I don't have the GUI options shown in the article).
http://alexappleton.net/post/77116755157/hyper-v-virtual-machines-losing-network
I could try updating the driver but there is mention in the comments of this post that driver updates have yet to resolve this issue so we may still be waiting on Broadcom for a fix. Please confirm otherwise if anyone has any information.

Cluster network name resource error 1196

I have a two-node Hyper-V 2012 Core Server cluster. Initially, the cluster was working fine and I was able to do live migrations with no problem. I first realized that something had gone wrong when I was attempting to move a VM's storage to the Cluster Disk.
When I right click on the VM and select Move > Virtual Machine Storage, the bottom left area of the "move storage" screen says "Loading..." forever and never displays the cluster storage. This happened once before and I was able to correct
the issue by taking the Server Name resource offline and doing More Actions > Repair. However, if I try a repair now I receive the following error messages:
"There was an error repairing the active directory object for 'Cluster Name'. Error Code: 0x800713b8. The cluster request is not valid for this object".
I have verified that the cluster name Active Directory object (CCSDCluster) still exists and each node as well as itself has full permissions to the object. What I am not certain of is whether the object is still in the same Organizational Unit as it was
originally. After the failed repair attempt, I am able to bring the Server Name resource back online successfully.
In addition, I am continually receiving cluster event errors indicating the following:
"Cluster network name resource 'Cluster Name' failed registration of one or more associated DNS name(s) for the following reason: The handle is invalid. Ensure that the network adapters associated with dependent IP address resources are configured
with at least one accessible DNS server."
Each of the two nodes has multiple NICs configured. One for management, one for guest OSs (Hyper-V virtual switch is configured to use this NIC and not allow management OS access), and two for iSCSI (for redundancy and multi-path). Live migration is set
to only use the management NICs. The management NIC on both nodes is configured with valid DNS servers. The CCSDCluster DNS entry has full permissions for both nodes and itself.
Any suggestions on what to try would be greatly appreciated. Thank you!

Could my issues be related to a problematic network configuration? Please see the ipconfig below from one of my Hyper-V host servers.
Ethernet adapter Ethernet 8 = iSCSI
Ethernet adapter Ethernet 6 = iSCSI
Ethernet adapter Ethernet 2 = Management interface
10.1.3.19 = Management IP address, 10.1.3.3 = IP address of Cluster Name Object
Tunnel adapter Local Area Connection *11 = ?? Not sure what this one is
Windows IP Configuration
Host Name . . . . . . . . . . . . : CCSDVM01
Primary Dns Suffix . . . . . . . : clairton.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : clairton.local
Ethernet adapter Ethernet 9:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : HP NC552SFP Dual Port 10GbE Server Adapter #4
Physical Address. . . . . . . . . : 28-92-4A-AF-46-34
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Ethernet adapter Ethernet 8:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : HP NC552SFP Dual Port 10GbE Server Adapter #3
Physical Address. . . . . . . . . : 28-92-4A-AF-61-68
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 172.16.1.12(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 172.16.1.1
NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter Ethernet 7:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : HP NC552SFP Dual Port 10GbE Server Adapter #2
Physical Address. . . . . . . . . : 28-92-4A-AF-61-6C
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Ethernet adapter Ethernet 6:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : HP NC552SFP Dual Port 10GbE Server Adapter
Physical Address. . . . . . . . . : 28-92-4A-AF-46-30
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 172.16.1.11(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 172.16.1.1
NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter Ethernet 3:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom BCM5709C NetXtreme II GigE (NDIS VBD Client) #55
Physical Address. . . . . . . . . : E4-11-5B-B9-3A-9C
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Ethernet adapter Ethernet 2:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom BCM5709C NetXtreme II GigE (NDIS VBD Client) #58
Physical Address. . . . . . . . . : E4-11-5B-B9-3A-A2
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 10.1.3.19(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IPv4 Address. . . . . . . . . . . : 10.1.3.3(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.1.3.100
DNS Servers . . . . . . . . . . . : 10.1.3.10
10.1.3.39
NetBIOS over Tcpip. . . . . . . . : Enabled
Tunnel adapter Local Area Connection* 11:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Failover Cluster Virtual Adapter
Physical Address. . . . . . . . . : 02-AD-4B-6D-A9-FB
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 169.254.2.92(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Enabled

Routing and Remote access can cause cluster network issues?

After enabling routing and remote access on the servers, we found lots of cluster issues on our server like<o:p></o:p>
Cluster Service stopped
Communication was lost and reestablished between cluster nodes
Unable to access witness resource
Cluster resource failed
can RRAS enabling causes cluster network issues?
Rahul

Hi TwoR,
Please offer more information about your current cluster and RRAS configuration, such as are you installed the RRAS role on any cluster node? Are your cluster in Hyper-V environment?
Or if you want to create the RRAS cluster you can refer the following KB:
Deploy Remote Access in a Cluster
http://technet.microsoft.com/en-us/library/jj134175.aspx
How to configure Network Load Balancing (NLB) based cluster of VPN Servers
http://blogs.technet.com/b/rrasblog/archive/2009/07/02/configuring-network-load-balancing-nlb-cluster-of-vpn-servers.aspx
I’m glad to be of help to you!
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

DAG Replication Network Isolation from MAPI

Hi,
Recently We have implemented Exchange 2010 SP2 DR setup.
We have two sites Prod and DR. We are facing some issue in DAG replication Network (Replication Adapter).
We are using 10.10.10.x for Mapi Networks and 192.168.1.x for Replication Network for Prod and 10.11.10.x for MAPI and 192.168.2.x for Replications.
As per Microsoft recommended, We configured replication adapters and added static routes for Replication Network.
We understand, Replicarion adapter is used for DAG Replication (Log Shipping and Seeding) and configured forewall to allow tonly DAG port 64327 for replication Vlans between sites.
Now, When we check the replication network hit in firewall. Its still using MAPI Network (MAPI Nic) to communication with DR sites. Replication Nics is not working properly.
Please let me know, How to isolate the MAPI and Replication Networks. Do we need configure Replication Port in DAG properties.
How to check whether Replication Network is working between the sites.
Regards
M

My Problem is, While seeding is happening between Primary Site to DR Site. Connections are going only via MAPI Networks. It is not using Replication Netowork. I have added the static route in all the prod and DR Mailbox Servers. But I have not
configured Replication Port in DAG properties. And also, I allowed only Port 64327 for Replication Vlan in both Primary and DR. Please let me know if you have any solutions. Regards M
That's expected if you are just using the EMC, or using standard options via EMS
What happens if you use
http://technet.microsoft.com/en-us/library/dd335201(v=exchg.141).aspx
Update-MailboxDatabaseCopy -Network
and
http://technet.microsoft.com/en-us/library/dd335158.aspx
Managing Mailbox Database Copies
To specify the networks you want to use for seeding, use the Network parameter when running the
Update-MailboxDatabaseCopy cmdlet and specify the DAG networks that you want to use. If you don't use the
Network parameter, the system uses the following default behavior for selecting a network to use for the seeding operation:
If the source server and target server are on the same subnet and a replication network has been configured that includes the subnet, the replication network will be used.
If the source server and target server are on different subnets, even if a replication network that contains those subnets has been configured, the client (MAPI) network will be used for seeding.
If the source server and target server are in different datacenters, the client (MAPI) network will be used for seeding.
Cheers,
Rhoderick
Microsoft Premier Field Engineer, Exchange
Blog:
http://blogs.technet.com/rmilne Twitter:
LinkedIn:
Facebook:
Note: My posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Network troubleshooting service windows server 2008

Which network troubleshooting service/application not available on windows server 2008 by default ?

Hi,
Here is the information you may need,
Troubleshoot Windows Server 2008
http://technet.microsoft.com/en-us/library/cc753935(v=WS.10).aspx
Changes in Functionality from Windows Server 2003 with SP1 to Windows Server 2008
http://technet.microsoft.com/en-us/library/cc753208(v=ws.10).aspx
If there is any misunderstanding, please let us know what you would like to achieve.
Hope this helps.
Steven Lee
TechNet Community Support

Network Troubleshooting Error 0x8E5E0247

Hi I have a Sony VAIO S Series VPCS117GA Laptop with Windows 7 installed on it.
Recently, I encountered a problem while connecting to an already existing WIFI network.
It was working fine until a few days back. But now I can't connect to it.
When I try to troubleshoot the error, it says "A problem is preventing the troubleshooter from starting"
Package ID : Unknown
Path : C:\Windows\diagnostics\system\networking
Error code : 0x8E5E0247
Source : Engine
User :
Context : Restricted
What should I do to solve this problem?
I have tried every thing I could. Still there seems to be no solution to this.
Please help.
Thanks in advance

Hi,
Have you checked the below articles?
Use Network troubleshooter event logs to solve network problems
Wired and wireless network problems
Please take a try with the suggestions mentioned and if possible upload us the event log for the network errors.
Best regards
Michael Shao
TechNet Community Support

DAG/cluster network troubleshooting

Similar Messages

Maybe you are looking for