Jeffrey
asked on
Server 2012 R2 Failover Cluster - Can't change network state to Do Not Allow...
Hello,
I have three Exchange 2013 CU11 DAG's that are using Failover Cluster Services on Windows Server 2012 R2 machines.
By default the ISCI connections on all of them are supposed to be set to: Do not allow cluster network communications on this network.
However all of them are set to: Allow cluster communications on this network.
When I click the checkbox for "Do not..." and click apply it changes the state for about 20 seconds and then reverts back to "Allow..."
Please advise if you are familiar with this scenario.
Thanks,
j
I have three Exchange 2013 CU11 DAG's that are using Failover Cluster Services on Windows Server 2012 R2 machines.
By default the ISCI connections on all of them are supposed to be set to: Do not allow cluster network communications on this network.
However all of them are set to: Allow cluster communications on this network.
When I click the checkbox for "Do not..." and click apply it changes the state for about 20 seconds and then reverts back to "Allow..."
Please advise if you are familiar with this scenario.
Thanks,
j
ASKER
LVL 17, thank you for the response and information.
The cluster subnet is different than both ISCI subnets. Each node has a different subnet for MAPI, Replication and 2 ISCSI connections back to the storage array. All are enabled and up.
NIC's
(2) ISCSI = Cluster Only (weird, the cluster service is supposed to set this to "no comm..." automatically when building the cluster
(1) Repl = Cluster Only
(1) MAPI = Cluster & Client Communication
The cluster subnet is different than both ISCI subnets. Each node has a different subnet for MAPI, Replication and 2 ISCSI connections back to the storage array. All are enabled and up.
NIC's
(2) ISCSI = Cluster Only (weird, the cluster service is supposed to set this to "no comm..." automatically when building the cluster
(1) Repl = Cluster Only
(1) MAPI = Cluster & Client Communication
I've run out of ideas :) Sorry. I don't even have an iSCSI solution anymore with which to test - everything I have is FC.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks for the help! I need to remember that the GUI does not always give the expected results. I used the commends that you listed and they removed the ISCI connections from all communication as they are supposed to. Thanks again!
Check out the networks for your cluster. Can you confirm that you have multiple cluster networks and that all of them have the status of "Up"? Failover Clustering won't allow you to remove Cluster Communication from a network if Cluster Communication is not enabled on any other network, or any of the other networks is in a status of "Down".