Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 642
  • Last Modified:

Exchange 2010 Event ID 1223 - Cannot bring cluster IP/Network Name Online

We are running Exchange 2010 SP3 Rollup 7. We have 2 CAS/HT servers and 2 MB servers running on physical servers running Windows 2008 R2 SP1 all updated. First let me say that our environment is working just fine but when I go into Failover Cluster Manager, I can see that Cluster Network name is not online and when I try to bring it online, I receive the following error:

Cluster IP address resource 'IPv4 Static Address 1 (Cluster Group)' cannot be brought online because the cluster network 'Cluster Network 2' is not configured to allow client access. Please use the Failover Cluster Manager snap-in to check the configured properties of the cluster network.

I went to Cluster Network 2 and sure enough, it was set to "Do not allow cluster network communications and this network". So, I selected "Allow cluster network communications on this network" and hit OK. I tried to bring the cluster name online and got the same error. I went back to the Cluster Network 2 and "Do not allow cluster network communications and this network" was selected again. For some reason, it's not letting me change this setting.

I hit on an article (http://blogs.technet.com/b/timmcmic/archive/2010/05/12/cluster-core-resources-fail-to-come-online-on-some-exchange-2010-database-availability-group-dag-nodes.aspx) that talked about the issue and how to fix it but it did not work. I'm not sure what to try next.
0
Kevin Litman
Asked:
Kevin Litman
  • 3
  • 2
1 Solution
 
tshearonCommented:
Have you made any changes, like IP or subnet changes to any of the resources? Specifically the Cluster name? Check the IP and subnet. Also make sure your cluster IP is on the same subnet your as your cluster resources in that site. Can you ping the cluster name and it resolve? I would be looking at something like that since the allow option is not staying. Can you also explain exactly which option you used in the article you posted so I can be sure of your steps. Thanks.
0
 
Kevin LitmanNetwork AdministratorAuthor Commented:
To answer your questions:

1) No changes of any kind have been made.
2) Cluster IP is on the same subnet.
3) I can ping and resolve the cluster IP/name.
4) I tried all 2 options but on option 2 I got the error "There are no more endpoints available from the endpoint mapper." and option 3 the error "Get-ClusterNetwork : The cluster service is not running.  Make sure that the service is running on all nodes in the cluster". I verified the cluster service is running.
0
 
tshearonCommented:
On your Mailbox server that holds the  Primary Active Manager for the cluster, is your replication service running? Can you stop and restart it? Does it stay running? In powershell can you do the following on the Active manager node and post the results?

test-replicationHealth
and
test-serviceHealth

Thanks.
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
Kevin LitmanNetwork AdministratorAuthor Commented:
I got it. For some reason, I had Replication disabled on the DAG network. Once I enabled replication, I was able to change the setting and bring the resource online.
0
 
dsnegi_25decCommented:
Did you went through the event viewer not sure what exact is issue for you ....But below is the good article for failover cluster issue

http://windowsitpro.com/windows-server-2012/troubleshooting-windows-server-2012-failover-clusters
0
 
Kevin LitmanNetwork AdministratorAuthor Commented:
My comment was the solution.
0

Featured Post

Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now