Join Mike Danseglio for an in-depth discussion in this video Overview of the Network Load Balancing (NLB) cluster, part of Windows Server 2012 Active Directory: Network Services.
- One of the things we have in our environment is, if I have two, three, four, or five computers, and these computers are running the same application, and I want to be able to basically load balance those applications. The operation system itself (mateively), can not support running those machines because I can only assign one IP address to each machine. We can't have duplicate IP addresses. So one of the features that Microsoft has had around forever and this is not a new concept, is a concept called Network Load Balancing.
The ability to assign more than one IP address to ... let me rephrase that. To be able to assign the same IP address to multiple different machines so that now those machines can participate in what's called a Network Load Balancing Cluster. So that the service behind the scenes, when a user makes a request of, let's say a web-server or web-services, if I am load balancing the web-services, and I have two machines that are running.
The Network Load Balancing service that will accept the request and determine which note in the service currently is not being tasked, or which one is not being tasked the heaviest. Then I will basically pass that request off to that machine, so that I can then publish the website or reply back to whatever that request might be. So, the application has to be Network Load Balancing aware. So in server 2008 and coming this way, which includes 2008 R2 and sever 2012, a Microsoft Network Load Balancing cluster supports anywhere from two nodes up to 32 nodes in the environment.
So when we're looking at this, all right, some of the new features that came out. and again, Network Load Balancing has been around for a while. The configuration Network Load Balancing in Windows 2000, and 2003, and even in 2008, to configure the Network Load Balancing was really painful. The Wizard wasn't very nice. Configuring the IP addresses weren't very nice. So we would have issues when we were trying to set it all up. In server 2008 R2, Microsoft introduced a brand new Wizard for configuring the server 2008 R2 Network Load Balancing environment, and that Wizard has been brought over into server, it should be server 2012, not server 12.
All right, Server 2012, and once we installed the R Sat tools, for the Network Load Balancing environment, we get 35 new PowerShell commandlets. A lot of books that you'll read when you're talking about Network Load Balancing, you're talking about serve 2012. They'll say new to server 2012 are 35 new PowerShell commandlets. No, it's not true. The 35 PowerShell commandlets for Network Load Balancing were actually introduced in server 2008 R2. So real quick, let me just show you how you would install the Network Load Balancing R Sat tool, and then a little bit later on, we'll talk in another session about what are the requirements installed in Network Load Balancing.
Then walk through the configuration Network Load Balancing. So if I come up my server manager on my 2012 box, come down to add roles and features. Do a next. Next. Next. It's not a role. We're going to be installing a feature, because remember feature is something we're enhance in our own capabilities. So come down, I find the (now I bet a quarter) Network Load Balancing. It's going to automatically install the R Sat tools for me.
So if I do a add feature, next install, right. This is going to install the (binaries) or the components so I could be a Network Load Balancing server. Once this installs and completes the installation, I'll now have under-administrative templates, the Network Load Balancing ability to run the Wizard, I will also have the graphical interface for managing the Network Load Balancing environment. Once it's been configured, and it also adds the manifest for the Network Load Balancing module for PowerShell.
So as soon as this finishes, and it's done. If I come under tools, I now come down here. I've got the Network Load Balancing manager. So if I click on this, right, and then I'll just be real quick, then I'll go ahead and close out of it, because I'm not going to set up a Load Balancing environment today. I can actually come up, and I've got the option to create a Wizard, if my mouse wants to respond. Come on, click. I can create a new Network Load Balancing environment on this machine and it's all Wizard driven.
If I exit out of my server manager, and I just go to my PowerShell commandlet, or my PowerShell interface, if I do the get-module the list available, Now that I've installed the Network Load Balancing environment, notice right here, I now have the Network Load Balancing manifest.
So if I now run a ... clear screen. Now if I run a get-command-module and it's network load balancing clusters, all right, I now see the 35 commandlets that strictly designed for Network Load Balancing.
A couple of the biggies in here I just want to point out, and then we'll talk more about it again later, if I do the new ... let me change colors here. The new NLB cluster exactly what the verbs talk about. No. It's going to create Network Load Balancing cluster. Then if I do get a get help on that, I'll see all this (syn-tacks). If I want to look at what Network Load Balancing clusters I have on the machine, I can do a get NLB cluster. I'll give me back information about what clusters are all ready on the machine.
If I scroll down a little bit, come on scroll down. All right. Here we go. If I scroll down a little bit, I have the ability to remove a cluster. I also have the ability to set a cluster, which means (mumbling) set any component of the clusters properties.
If you come down through here, I can also set any component of the cluster. The node type, I can change it's IP. I can change it's port-rules, all the stuff that we'll talk about in a future session. We can start and stop the cluster, and at the very top there was an enable and disable. The ability to enable cluster and disable cluster. So, all these commandlets, you'll read a whole bunch of books that says these commandlets are all new to server 2012, in reality they've been since server 2008 R2.
So, we'll be using these intensively in the up-coming or extensively in the up-coming sessions. So in this session, we looked at what is a Network Load Balancing cluster? We looked at how to very, very quickly to install the binary so that we can then create a Network Load Balancing cluster. We also looked at the PowerShell commandlets, they're now available to server 2008 R2 and server 2012 environment for creating, managing, stopping, disabling, on Network Load Balancing cluster.