Learn how to view Cluster Events. Cluster Events can happen at any time, and just like using the Event Viewer in Windows, viewing Cluster Events can be a quick way to see if there is any trouble with the cluster
- [Instructor] Windows Server 2016 gives us some great troubleshooting tools, such as the way we can troubleshoot any type of failover cluster event. So let's open up failover cluster manager and see how we do that. So from our server manager we go to tools, and failover cluster manager, and let's expand our cluster, cluster1, and we click on cluster events. And we see a lot of cluster events here. We see a lot of event 1196. So we need to figure out how to resolve that.
Let's take a look and see what this says. It says the cluster network name or resource cluster name failed registration of one or more DNS names. DNS server failure. Well, that could be a problem. So, what we want to do is resolve this, figure out what's going on. Let's go to TechNet in our favorite web browser, and we'll look up what could cause this. We're at technet.com, let's type in cluster event 1196, and there's several different websites that we can go to, or blogs, or repairs, various different things that will tell us how to possibly fix this issue.
Let's take a look at this first one and see what information we can get. Says here in a cluster, network name resource can be important, because it's got to be resolvable. Check the DNS configuration. Well, that's good information. Let's go ahead and see if we can resolve the name of our cluster to our IP address. So we know our cluster name is cluster1, we see that at the top left. Let's double-check our IP address. We see that it's 15.229. All right, let's go to a command prompt and see if we can ping that IP address.
And we can, very good. Now let's see if we can ping cluster1. Oh, there's our problem. All right, we need to switch over to our active directory domain controller, go into DNS, and add this host record, because it did not add itself automatically. I've now switched over to our domain names service domain controller, click on tools, and DNS and server manager, and we're going to expand our server. Open up the forward lookup zone and add the A record, and we'll type in cluster1, and we'll put in the IP address and click add host.
And it was successfully created. Now, we also want to make sure it's in our second server, that it's replicated okay, so let's go over to widget, and we'll wait a few seconds here for it to replicate. Sometimes all you have to do is refresh a couple of times. And there it is, cluster1. All right, so it's showing up in both of our domain controllers, so now we should be able to go back to our original server where the failover cluster manager resides, and we should be able to resolve this name. We're back in our failover cluster manager server, and let's go ahead and flush the DNS.
That clears out any old information, and we will ping cluster1 once again. Hey, look at that. Now it's starting to work. So that should resolve our event that we see in the cluster events. Now, if you no longer want to look at your events, then you can easily just clear them all out, but first you may want to save those events in case you need to look at them again in the future. So we can click save events as, and it'll save it as an evtx file, we'll just put it on the desktop, and we'll just call it Clusterevents.
And now we can click reset recent events, and now all the events are gone, but we still have those events in case we need them back on our desktop. And there it is, Clusterevents. You can double-click on that, and we can see our events in our event viewer, which is separate from our failover cluster manager viewer. And it might take a few seconds to load up. And there it is. There are our events that we had cleared out earlier. Reviewing cluster events can save you from imminent problems, but also help you fix a problem that may have already occurred.
After you've created your cluster, take a look at your cluster events and see if you missed anything or if there's any software bugs that might keep you from moving forward with your failover cluster.
- Configuring network load balancing
- Configuring failover clustering
- Managing clusters
- Interacting with Hyper-V
- Managing failover cluster roles
- Configuring role-specific settings
- Configuring virtual machine monitoring
- Managing cluster movement