See a demonstration of creating a network load balanced set of hosts. This allows administrators to be able to fail over to one or more hosts in case of hardware or software problems, or times of maintenance. It is a great feature included in Microsoft Windows Server 2016.
- [Instructor] Let's set up network load balancing on Windows Server 2016. We're going to start by going to the server manager and clicking on add roles and features. And, from here, we're going to skip forward until we get to the features section, and then we're going to scroll down to where it says network load balancing; go ahead and check that. Choose to add the features, and click next, and install. It usually just takes a couple of minutes to install, and network load balancing will give us the ability to have more than one server respond to the same name and IP address.
That way, if one of the servers goes down, the other servers can pick up the slack and continue servicing the clients. Now, we're going to need to install this on every server that's going to be in our network load balancing cluster, but this is our first server, so we'll go ahead and let this finish up. Our installation is complete; go ahead and click close. And now, back in server manager, we're going to go to the tools menu, and choose network load balancing manager. And we can see that there is no cluster as of yet, so let's go ahead and create a new cluster by right-clicking and choosing the new cluster option.
And, we're going to put in the name of our host. If you don't remember the name, we can always just put in local host, and it'll just resolve for you. And this particular server has two network cards, so we have to choose which one's going to be our NLB network card, and let's go ahead and choose the number three one, 'cause that is our secondary network card, and click next. And we're going to leave the unique host identifier to one, this is our first cluster, our first server in the cluster, so we'll go ahead and leave that. If for some reason you get a message about DHCP, then you should cancel this, and set your network card to a static IP address, and then go back in and continue on with the wizard.
Alright, we're going to want to leave the default state as started, but you can change that to stopped or suspended if you have a reason to do that, and let's go ahead and click next. Now we need a cluster IP address; this is the IP address that all the different servers are going to respond to, and we're going to go ahead and choose an IP address that we know is not currently used by anything else. And, it's got to be in the same subnet as our other servers, otherwise this won't work. Go ahead and choose okay, and click next. Now we're going to need to give it an internet name, so this is going to be a name, where we can resolve this, and we can set this up to resolve both internally and externally, and just for fun, we'll go ahead and call it clusterNLB, just because that is very descriptive as to what we're doing.
And now, we have the option for unicast, multicast, or IGMP multicast; now we've got an upcoming video that goes into all this in detail, but we're just going to go ahead and choose unicast for now. And then we have port rules, and we will be discussing this in another upcoming video, but if we just take a look at edit, you can see, you can change the port range, and you can change the protocols that you use. We can also change the affinity, as well, which is something we will also go over in upcoming work.
Let's go ahead and click finish, and now our cluster is created, and we can see, there's a little clock here, telling us we've got to wait for all the information to be added in. So pretty soon, we'll see all that finished. And, now it is. So, it shows that our cluster IP address is in there, the status is enabled, the ports, et cetera. And if we want to, we can look at the bottom and take a look at other information, such as the service starting, et cetera.
If we want to, we can delete the host; we can go into the host properties, and make changes, we can look at the host status. It says it's converged, which means that the IP address of the server is now converged with the cluster IP address, which is exactly what we want. We can also go to control host, by starting, stopping, drain stop, which makes that particular role go away for that one server, suspend, or resume. We can also go in and change the ports as well.
I've gone into another server and installed the same network load balancing feature, so let's go ahead and add that host into our cluster. So, right-click and choose add host to cluster. We'll put in the name of the server, click connect, and within a few seconds, we will see the IP addresses of the different interfaces of that server, and there they are. So I've specified ethernet three for this particular task, ethernet two is going to be the main IP address, ethernet three is going to be used for the cluster.
Let's go ahead and click next, and we still have our same dedicated IP address, which is .231. And next, and finish. Now it's just verifying the information, and once it's done, both of our hosts will be in our cluster. So the next step will be to go into DNS and add clusterNLB, which is the name we've given for our cluster, and the IP address, into DNS, and so that way, both servers will start responding to that name. Right now, they would respond to the IP address, but most people don't remember those, which is why we created the name.
Alright, so that's all done, let's go ahead and switch over to our domain controller and make that DNS change. We are in our domain controller; let's go to tools, and then go to DNS, for our DNS manager. And we're going to create a host record, which is a forward lookup record. That's going to be clusterNLB, to our IP address. So let's right-click and choose to create a new host address. And we'll give it the same name, and we'll give it that 231 IP address.
And we don't need a PTR record, 'cause we're not doing a reverse DNS. Click create, it's been created. Great, now let's right-click and choose a command prompt, and we're going to try to ping our new clusterNLB. Let's take a look and see if it works. Now it can't find it, because it needs to flush the DNS. You can either wait 15 minutes, or you can right-click on the start button and choose to go to a command prompt for admin. So we'll type ipconfig /flushdns and now we should be able to ping the clusterNLB.
Let's take it back to where we switch over to the domain controller, and start again from there. We're now in our domain controller, and we're going to go into DNS manager, by going to server manager, and tools, followed by DNS. And we need to add a host record that will point to our new clusterNLB host. So what we want to do is expand our widget.internal forward lookup zone, and create a new host. So just right-click anywhere on the screen, click new host, and from here, we'll just give it the same name that we gave it when we created the cluster, and then we need to put in our IP address, and click add host.
Let's click done, and we'll minimize, and we'll test it out. Let's go down to our start button, right-click, and choose command prompt. And from here, we'll just type ping clusterNLB. And there we go, our cluster is now responding. If we install duplicate programs, or file-sharing, on these two servers, then they can both service the clients, as the clients request them. Even if one of the servers goes down, then the NLB will still pick up the slack, and the other server will continue running.
Now that you've seen a demonstration of installing an NLB cluster on multiple hosts, you can now add the redundancy you need to your cluster-enabled network.
- 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