Hi all,
We have team NIC which includes two network adapters. when one NIC fails, the cluster was down foe less than 20 seconds. This is SQL cluster. is it supoosed to be since primary NIC needs to failover to passive NIC?
Thank you!
Hi all,
We have team NIC which includes two network adapters. when one NIC fails, the cluster was down foe less than 20 seconds. This is SQL cluster. is it supoosed to be since primary NIC needs to failover to passive NIC?
Thank you!
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>
Lee
Hello
I have 2 Hosts , HP Proliant DL580 G7 with Server windows server 2012 Installed and updated with the last windows updates and drivers and hardware firmware. And the Hyper-v Role installed.
With FC SAN storage connected.
Each server have 6 NICs and only 2 NICs in each server are connected and the NIC Team is enabled for with 2 NICs.
I installed the Windows Failover Cluster Feature and the validation process passed with no failed results.
I have one 2012 domain controller running 2008 R2 AD Functional Level.
but when i start creating the cluster it stops with the following errors:
Creating a new computer account (object) for 'HVC' in the domain. Unable to successfully cleanup. An error occurred while creating the cluster and the nodes will be cleaned up. Please wait... An error occurred while creating the cluster and the nodes will be cleaned up. Please wait... There was an error cleaning up the cluster nodes. Use Clear-ClusterNode to manually clean up the nodes. There was an error cleaning up the cluster nodes. Use Clear-ClusterNode to manually clean up the nodes. An error occurred while creating the cluster.An error occurred creating cluster '1'.An operations error occurred To troubleshoot cluster creation problems, run the Validate a Configuration wizard on the servers you want to cluster.
i enabled the diagnostic log on the failover cluster Client in the event log and i got the following errors:
OpenClusterImpl (1119): Could not connect to cluster. sc = 1753
ConnectCluster (979): Connect to Local Cluster: ApiGetClusterName failed, sc = 1753.
ConnectCluster (999): Failed to open remote cluster 'HOST1.domain.com', status == 1753.
ConnectRemoteCluster (856): Couldn't resolve RPC binding to cluster 'HOST1.domain.com', Status = 1753
CreateCluster (1883): Create cluster failed with exception. Error = 8224, msg: Failed to create cluster name HVC on DC \\DC.domain.com. Error 8224.
CreateClusterNameCOIfNotExists (6879): Failed to create computer object HVC on DC \\DC.domain.com with OU CN=Computers,DC=domain,DC=com. Error 8224.
I didn't find any solution or anyone talking about these errors,
Some Guys say that i have to install hotfix 976424 from here http://support.microsoft.com/kb/2784261
but i cant install it on windows server 2012 its not running.
Your help is appreciated :D
Thanks
Daoud Ghannam
I'm working on installing a new system for my company's internet radio station. Currently, we are running a Windows program to play back the audio (on the host machine) and then a second application to stream out the audio signal over the WAN.
I am wanting to setup basic hardware and software redundancy for the station. Would two or three computers configured in a cluster provide both hardware and software redundancy, or would I need anything else?
I'm trying to learn the best way to do this, so sorry if this is in the wrong place.
Thanks!
Hi ,
we are using NetServerEnum API to retrive the list of cluster from domain. But it failed with error 2127 on windows 2008 server and the cluster /list command also failed with same error.
But if we pass domain name to cluster .exe then it works.
So is there any win32 API other than NetserverEnum which will give the list of clusters in a domain.
have some questions regarding creating a backup for an all in one server. The server has active directory, DNS, the file server and everything on it. I'm trying to create a redundancy setup in case of failure. So I was reading about failover clusters and this seem to be what I need to do. I'm just a little bit confused. What is the difference between using hyper V and using clusters?
When I create a cluster and add servers to it, what exactly happens? For instance simplest case I have the main server with all the data. Now I bring in another machine with nothing on it. I install windows server 2012 on it and add it and the other computer to a cluster. Does the data from the main server automatically get copied onto all the servers that are part of this cluster? At this point if one server fails will the other one take over?
Any help is greatly appreciated.
Hi,
I am having issues as described in mention below KB link.
http://support.microsoft.com/kb/2838043
after applying this hotfix I have restart Nodes now I need to perform post installation task as described in article that's is simulate failure on Cluster Network Name and repair it .
I am confuse and need responses on below queries
Usama Arif
I found this in the documentation for DHCP , but I am planning to use this machine for a DMZ implementation thus I cannot get away with DHCP?
Get-ClusterResource "IP Address 172.24.11.0" | Stop-ClusterResource | Update-ClusterIPResource –Release
I have run into a networking problem on my cluster, and I cannot figure out what changed.
I had a cluster configured and working. Its access network is 192.168.10.0/24. I have other networks, including a node management network on 10.29.130.0/24. The access network is private to my lab; it's here I have my AD defined. The management network is a 'lab' network that has a gateway available so we can access the lab from our corporate network with no issues. In other words, the access network is only routed within my private lab, but the management network can be routed to corporate access.
But, as you know, Windows simply doesn't like creating two different networks with default gateways. So before building the cluster, I removed the gateway from the management network, ensuring there was only a single gateway configured on each host. Ran the validation and it came through fine (typical network warnings about non-routed networks not able to reach other networks, but that is expected and presents no problems). Built the cluster.
I wanted to try to create an environment that would allow me to access the physical hosts through the management network, so I tried issuing a route add command specific to the management network.
route add 10.29.130.0 mask 255.255.255.0 10.29.130.1 if 3
It didn't work as expected (I am by no means a networking expert, but I figured I would try it.) Since it didn't work, I deleted it.
route delete 10.29.130.0 mask 255.255.255.0 10.29.130.1 if 3
Came back and ran another validation wizard on the cluster and now the validation fails with the following error (to each of the other nodes in the cluster):
Network interfaces FT4-Infra01.VSPEX.COM - Mgmt and FT4-Infra03.VSPEX.COM - Mgmt are on the same cluster network, yet address 10.29.130.37 is not reachable from 10.29.130.35 using UDP on port 3343.
I check my firewall, and those ports are open on all node for all firewall profiles. From FT4-Infra01 (the machine I was messing with), I can ping the other nodes of the cluster. From the other nodes in the cluster, I cannot ping FT4-Infra01. Yes, I know ping is a different rule, but I always go back to basics. And the fact that it is not responding to pings after playing with the route is strange.
Does anybody have any ideas about what playing with the route command could have changed? I am assuming that is the cause because everything worked fine before issuing the command and now these errors are there. No other changes were made to the cluster or the nodes.
.:|:.:|:. tim
Any ideas on why a Fileserver keeps going offline on only 1 node. Even tried swapping the server and its still failing. This is a windows 2008r2 cluster
Cluster file server resource 'FileServer-(NAME)(Database Disk)' failed a health check. This was because some of its shared folders were inaccessible. Verify that the folders are accessible from clients. Additionally, confirm the state of the Server service on this cluster node using Server Manager and look for other events related to the Server
Hello,
I have a couple Server 2008 R2 Hyper-V Host clusters with many VM's running on them. Is there a way I can introduce a Server 2012 R2 Hyper-V host server into each cluster, migrate the VM's to the Server 2012 R2 system and then be able to live migrate the VM's to another Server 2012 R2 Hyper-V host in another cluster? Thanks
Pat
Pat
I am trying to create a High Availability Cluster on Serve 2012r2 that will run Remote Desktop Services i.e. RemoteApps. The idea being that if one server goes down the second one will take over. I have created a cluster with 2 nodes, the two nodes in the cluster are virtual servers on two separate physical servers running Server 2012r2 with Hyper-V. From what I can tell the cluster is setup properly (server manager>local server recognizes them as being apart of the cluster), but I'm unclear whether these two nodes are the High Availability cluster I require, or if I should have made the physical servers that host Hyper-v the nodes in the cluster. I would think that once these 2 nodes are in a cluster if I make a change to one node i.e. install a feature that the other node would be automatically updated to match, and should one node shutdown the other node takes over. Doesn't seem to be the case for me, which makes me think I shouldn't have used the two virtual servers as nodes.
Should I have created the cluster between the two physical servers instead? Then created a virtual machine from that cluster?
My only other experience with clustering is with Synology, so I'm basing a lot of my assumption on how Synology clusters their devices.
Any help is greatly appreciated.
Brendon
I am currently seeing this under my Storage in the Failover Cluster Manager on Server 2012 r2....
"Cluster Disk 2" is stuck in an "Online Pending" state. The thing is I don't have any disk that would be claiming this role.
When I try and look at the properties of this disk I get a message: "operation has failed..... unable to cast object of type 'MS.Internal.ServerClusters.Cluster' to type 'MS.Internal.ServerClusters.ClusterResource'. " or sometime the MMC crashes with an unhandled exception. If I try and remove it in the Failover Cluster MMC, it fails with "The file cannot be opened because it is in the process of being deleted. Error Code: 0x8007012f"
If I try and remove it with cmdlets in PowerShell, ' Remove-ClusterResource "Cluster Disk 2", no result because the resource doesn't exist. 'Get-ClusterResource' shows no resource related to the ghost disk.
Any thoughts on what may be causing this ghost disk to be showing up as available storage, or any resolutions to removing it.
2 Hyper-V hosts (2012 R2 DC) in Cluster config
Cluster got created BEFORE Hyper-V hosts AD Computer Objects got moved to a proper desired OU
Is there a way to move Hyper-V host AD objects now?
Will Cluster need to be re-created?
Thanks
Seb
Hi,
We are looking to implement a 2-node 2012 R2 Scale-out File Server cluster (using SAS JBOD enclosure) for the primary purpose of storing the VHD files that will be accessed by a 4-node 2012 R2 Hyper-V cluster using 10 gigabit Ethernet (no RDMA). Our environment can be characterised as having a large number of mostly idle VMs that experience sporadic, low intensity use (this is *not* a VDI environment). We have 2 questions.
1) To what extent is RAM a consideration for the SoFS servers? We can't find any documentation to suggest that there are benefits to be gained by having more RAM in the SoFS servers but we don't know if we should go with 8/16/32/64+ GB RAM in each of the nodes.
2) With the need to keep costs down, we don't think RDMA / SMB-Direct NICs are going to be within our reach. Should we however look to have 2 * dual-port 10 Gbps NICs in both the SoFS & Hyper-V boxes?
We have a Microsoft cluster running on 2 Server Enterprise 2008R2 Servers with the FileServices Roles (including DFS roles). We have 3 Standalone DFS namespaces (roots) which have been up and running for a couple of months. Users were complaining about performance so we added the DfsDnsConfig registry entry to force the FQDN format in the namespace (KB244380).
Although it doesn't say to do so in the KB Article, I found several threads that said you also need to delete and recreate the namespaces afterwards. This is where I got into the problem.
I deleted one of my namespaces from the Failover Cluster Manager utility. I then recreated the namespace. While it works, the share was empty. This is because by default it placed the namespace in DFSRoots and we have our namespaces in DFSroot (no trailing "s").
So I am trying to delete the new namespace in DFSRoots and create it in the DFSRoot folder, but I get the error listed in the title. This is what I've tried so far to resolve this:
1. dfsutil to remove the namespace and it fails saying the command is not supported in a cluster environment. Fair enough.
2. I tried to delete the share (using "Share and "), but it fails saying the shared folder is a DFS namespace root.
3. I tried to find an option to add the namespace to the resource group (using "Failover Cluster Manager") but I can't find the appropriate option. Maybe it cant be done from the "Failover Cluster Manager" unless you are created a new one, I think.
4. Of course I tried to delete the namespace (using the "DFS Management" utility) and that's where I get the error in the Title of this post.
5. I deleted the registry entry for the namespace under hklm\software\Microsoft\dfs\roots\standalone. I did this on both Fileserver nodes in the cluster. However then all the utilities complained that they couldn't find the namespace and I couldn't do anything with the specific namespace. So I put the registry key back in.
At this point I don't know what else to try to delete this namespace properly. Any assistance is appreciated.