Windows Server 2003 Clustering & Load Balancing phần 8 pps

8. Now you’re ready to configure DHCP as a resource in the cluster. To do this, open the Cluster Administrator tool, as shown in Figure 6-2. Once opened, you can go to the File menu and choose to configure a new application. Once selected, open the Cluster Application Wizard. Chapter 6: Designing a Highly Available Solution with Windows Services 269 OsbNetw / Windows Server 2003 Clustering & Load Balancing / Shimonski/ 222622-6 / Chapter 6 Figure 6-1. Viewing the DHCP Server console P:\010Comp\OsbNetw\622-6\ch06.vp Tuesday, March 25, 2003 10:16:19 AM Color profile: Generic CMYK printer profile Composite Default screen 9. When you open the wizard, as seen in the following illustration, you begin the process of creating a DHCP cluster. The wizard helps to configure an application to run in a cluster. This wizard takes you through all the steps you need to follow to create or select a Virtual Server and prepare an application to be clustered. Next, as seen in Figure 6-3, you can create a Virtual Server. Again, to reiterate what was learned in past chapters, a Virtual Server is what the client will access 270 Windows Server 2003 Clustering & Load Balancing OsbNetw / Windows Server 2003 Clustering & Load Balancing / Shimonski/ 222622-6 / Chapter 6 Figure 6-2. Cluster Administrator P:\010Comp\OsbNetw\622-6\ch06.vp Tuesday, March 25, 2003 10:52:42 AM Color profile: Generic CMYK printer profile Composite Default screen OsbNetw / Windows Server 2003 Clustering & Load Balancing / Shimonski/ 222622-6 / Chapter 6 to get to the applications on the cluster. Two nodes exist and what they share between them is a name and an IP address, which the client will access to get to the resources hosted on both nodes. 10. In Figure 6-3, you have the option to create a new server or you can use one that’s already created. Select which one you want, and then click Next. 11. In the next illustration, you can create a new resource group for your Virtual Server. Because I already made one prior to launching the wizard, I’m selecting it here. You can also create a new one if you want to. Chapter 6: Designing a Highly Available Solution with Windows Services 271 Figure 6-3. Creating a new Virtual Server P:\010Comp\OsbNetw\622-6\ch06.vp Tuesday, March 25, 2003 10:16:20 AM Color profile: Generic CMYK printer profile Composite Default screen 272 Windows Server 2003 Clustering & Load Balancing OsbNetw / Windows Server 2003 Clustering & Load Balancing / Shimonski/ 222622-6 / Chapter 6 12. After selecting your resource group, give it a name for the Virtual Server, as seen in the following illustration. Do this so you can have a meaningful name that represents a role within the cluster. I kept it simple, but you can make the name as elaborate as you need to keep it distinguished from the rest of the resources. Then, click Next. 13. Now that you have your new Virtual Server and resource group set up, you need to configure an IP address to associate the resource with the cluster and the clients. In the following illustration, you can configure the IP address and the network name. You need to supply a unique IP address that the clients will access to get to the resource, which is the DHCP service. In this example, I supplied an IP address and a network name the clients will need to use to access this resource. P:\010Comp\OsbNetw\622-6\ch06.vp Tuesday, March 25, 2003 10:16:20 AM Color profile: Generic CMYK printer profile Composite Default screen Chapter 6: Designing a Highly Available Solution with Windows Services 273 OsbNetw / Windows Server 2003 Clustering & Load Balancing / Shimonski/ 222622-6 / Chapter 6 14. After clicking Next, you have to select some advanced Virtual Server properties, as seen in the following illustration. You can configure quite a few things here. First, understand that up to now, you’ve provided what’s needed for the resource to function, but you can configure a few more things now instead of later. Select Resource Group Properties and click the Advanced Properties button. 15. In the next illustration, check over the failover and failback options. You learned about both services in the first few chapters of the book. If you want to configure these options, do so now. Also, remember, all these are optional and you can configure them later. They’re only here for ease of use. P:\010Comp\OsbNetw\622-6\ch06.vp Tuesday, March 25, 2003 10:16:20 AM Color profile: Generic CMYK printer profile Composite Default screen 274 Windows Server 2003 Clustering & Load Balancing OsbNetw / Windows Server 2003 Clustering & Load Balancing / Shimonski/ 222622-6 / Chapter 6 16. In the next section of Advanced Properties configuration you’ll configure IP address parameters further than what you already designated earlier in the wizard. This is shown in the next illustration. The Parameters tab is important for the success of your DHCP resource. In this tab, you’ll find the IP address you already assigned the Virtual Server but, more important, you can see what network it wants to use. 17. Understand that when you use the Cluster Service, you always have two individual network cards connected to two completely different networks. If you configure the resource on the wrong network, then clients won’t be able to reach it. In this tab, you can configure on which network the resource is located. In this example, I configured the LAN network instead of the Heartbeat network. By default, when I looked at it the first time, it was set for the wrong network, so that would have impeded communications. You must configure this properly for the cluster to work! Visibly verify that your connections are properly marked and connected for communications to take place. You can click Apply when you’ve set it the way you want it. 18. The last resource you can configure is the Advanced Network Name Resource Properties, as seen in the next illustration. In this dialog box, you can configure the network name if needed. This has already been done, though, so you have no need to change it. P:\010Comp\OsbNetw\622-6\ch06.vp Tuesday, March 25, 2003 10:16:20 AM Color profile: Generic CMYK printer profile Composite Default screen Chapter 6: Designing a Highly Available Solution with Windows Services 275 OsbNetw / Windows Server 2003 Clustering & Load Balancing / Shimonski/ 222622-6 / Chapter 6 19. Next, configure the manager of the resource. In this part of the wizard, you can create a cluster resource to manage the actual application you’re clustering. Here, you’ll answer Yes and create a resource for the application, as shown in the illustration. P:\010Comp\OsbNetw\622-6\ch06.vp Tuesday, March 25, 2003 10:16:21 AM Color profile: Generic CMYK printer profile Composite Default screen 276 Windows Server 2003 Clustering & Load Balancing OsbNetw / Windows Server 2003 Clustering & Load Balancing / Shimonski/ 222622-6 / Chapter 6 20. After clicking Next, the following illustration shows you how to set up the resource type. DHCP Service comes preconfigured, so you needn’t worry about it. Simply drop down the menu and select the DHCP Service option. 21. Click Next again. You’ll need to specify a name for this specific resource. I selected the DHCPGROUP but, again, you can select whatever seems logical in your own environment. After you configure what you need in the following illustration, click Next to create the resource. 22. You can also click the Advanced Properties button to configure the Restart policy and other dependencies if you need to do so. Click Advanced Properties. P:\010Comp\OsbNetw\622-6\ch06.vp Tuesday, March 25, 2003 10:16:21 AM Color profile: Generic CMYK printer profile Composite Default screen OsbNetw / Windows Server 2003 Clustering & Load Balancing / Shimonski/ 222622-6 / Chapter 6 In the next illustration, you can see the options available, such as the Restart or Do not restart options, within the Resource Group. The restart policy allows the group to restart itself after a certain threshold passes. 23. If you need to configure Dependencies, then you can also work through that configuration here. Click the Dependencies tab and choose Modify. Then, double-click a physical disk resource, an IP address resource, and a network name resource, so you can add them. Click OK to have them all added. In Figure 6-4, I removed one resource, so you can see what happens if you don’t meet the requirements, such as having a name, an IP address, or a shared storage device. 24. In the next illustration, you generate an error if any of the resources are missing that need to be applied, such as an IP address or shared storage devices. Make sure you have your cluster configured properly or you won’t be able to finish the configuration. I always add or create problems in the test environment to help solve problems that could arise during the configuration of the production environment. Chapter 6: Designing a Highly Available Solution with Windows Services 277 P:\010Comp\OsbNetw\622-6\ch06.vp Tuesday, March 25, 2003 10:16:21 AM Color profile: Generic CMYK printer profile Composite Default screen 25. This is the time to cluster your DHCP service. Once you click Next, the wizard prompts you for the location of the DHCP database files. Select the dependent disk that was left out of Figure 6-4. Close the wizard and you’ll have to bring the group online. You can right-click it, and then select Bring Online. 26. That’s it! Now you only need to configure your scopes and you’re finished. Open the DHCP console and right-click the server on which you want to set up the scope. Congratulations! You’ve built your first resource into the clustered server solution. Now, you should feel comfortable knowing your DHCP service is highly available. You can always test the solution, if needed, by powering down one server and seeing if the other server takes over. If so, then you’re all set. If not, you need to do some troubleshooting to see why this didn’t work. Some of the most common causes of failure are misconfiguration, so go back through Chapters 1 through 3 if you’re having an issue with your cluster. Now, let’s look at our next resource: the Windows Internet Naming Service. Highly Available WINS Just like DHCP, Windows Internet Naming Service (WINS) is a service used on the server to make life easier for you and your network. WINS is a core part of the Windows 2000 and Server 2003 operating systems. Although you can do away with this service in a pure Windows 2000 and above network, it still comes standard with all servers’ OSs you purchase. WINS is responsible for managing the NetBIOS name to IP address association on your network in a database, so you can cut down on the amount of NetBIOS broadcasts that occur on your network. The NetBIOS protocol, when configured on any workstation, generally broadcasts its name by default, causing massive amounts of broadcast traffic, depending on the size of your network. All other services like the Master Browser service, for example, which helps maintain the browse list in My Network Places, is also made better by the use of the WINS service. When it’s used correctly, WINS is a 278 Windows Server 2003 Clustering & Load Balancing OsbNetw / Windows Server 2003 Clustering & Load Balancing / Shimonski/ 222622-6 / Chapter 6 Figure 6-4. Modify Dependencies dialog box P:\010Comp\OsbNetw\622-6\ch06.vp Tuesday, March 25, 2003 10:54:30 AM Color profile: Generic CMYK printer profile Composite Default screen [...]... chapter might save you some headaches in the future 287 CHAPTER 7 Building Advanced Highly Available Load- Balanced Configurations Copyright 2003 by The McGraw-Hill Companies, Inc Click Here for Terms of Use 289 290 Windows Server 2003 Clustering & Load Balancing n this chapter, you learn how to take your knowledge of load balancing and apply it to building load- balanced solutions facing the Internet In this... configure only Server 2003 NLB clusters You can manage clusters that contain Server 2003 Enterprise and Windows 2000 Advanced, or NT 4.0 (Enterprise Edition) servers, but NLBMGR can only manage them, not configure them With this collection of tips, you should have a nice head start in testing and running an advanced load- balanced solution 301 302 Windows Server 2003 Clustering & Load Balancing NLB Security... suggest only mixing newer solutions, such as Windows 2000, with the older one If you want to plan 299 300 Windows Server 2003 Clustering & Load Balancing an entire new solution with Windows Servers 2003, then you might not want to mix older solutions like Windows 2000 because, even though this will work, you might have configured some newer features that Windows 2000 won’t support This is simply a design... can have the database backed up on shutdown 285 286 Windows Server 2003 Clustering & Load Balancing Figure 6-7 Using Ntbackup 6 Open WINS MMC and right-click the WINS server | Properties | General tab Click to select the Back up database during server shutdown check box, as seen in the next illustration Chapter 6: Designing a Highly Available Solution with Windows Services This backs up the WINS database... you can either create a new Virtual Server or configure an existing Virtual Server I recommend you create a new one for this exercise 23 After you follow the prompts to create the Virtual Server, you can then create an application resource on the Create Application Cluster Resource page, as seen in the next illustration 281 282 Windows Server 2003 Clustering & Load Balancing 24 Click the resource type... might think that to use NLB, you need to have only Windows 2000 Advanced Servers or only Windows Server 2003 The question here would be: “If I could mix nodes of any OS into the same cluster, then what are my options?” In the following lists, the OSs to consider include • Windows NT 4.0 (Enterprise Edition) • Windows 2000 Advanced Server • Windows Server 2003 (Enterprise Edition) From the previous list,... at the least, the most minimal form of protection you can get In this case, you can see an uplink between the servers from switch to switch could be 293 294 Windows Server 2003 Clustering & Load Balancing Figure 7-2 TCP/IP view of the NLB solution Chapter 7: Building Advanced Highly Available Load- Balanced Configurations exploited With the back-end firewall, you protect yourself completely Make sure... Service, as seen in the following illustration where I checked WINS for installation, and then press the OK button 279 280 Windows Server 2003 Clustering & Load Balancing 7 Once you finish, you’ll begin the install of the service As you did with DHCP, follow the prompts and install the service 8 You can now install the WINS service on the other node in the cluster 9 Now that you’ve finished installing WINS... You can mix Windows NT 4.0, Windows 2000, and Windows Server 2003 as long as they support WLBS or NLB • A commonality of NLB and WLBS is the heartbeat packets they can share between them, no matter what the platform The heartbeat packets from NLB in Windows are backward-compatible with WLBS • At press time, you can’t use a mixed environment and benefit from the features of Windows Server 2003 like Virtual... storage device in the path specified for the WINS resource, as seen in Figure 6-6 and also here: %SystemRoot%\System32\WINS Figure 6-6 Viewing the WINS database files on a local drive 283 284 Windows Server 2003 Clustering & Load Balancing • When you back up the WINS directory, you need to know some of the items it creates When the backup is done, a subfolder under the WINS folder called Wins_bak is created, . service. When it’s used correctly, WINS is a 2 78 Windows Server 2003 Clustering & Load Balancing OsbNetw / Windows Server 2003 Clustering & Load Balancing / Shimonski/ 222622-6 / Chapter 6 Figure. printer profile Composite Default screen 282 Windows Server 2003 Clustering & Load Balancing OsbNetw / Windows Server 2003 Clustering & Load Balancing / Shimonski/ 222622-6 / Chapter. 25, 2003 10:16:22 AM Color profile: Generic CMYK printer profile Composite Default screen 284 Windows Server 2003 Clustering & Load Balancing OsbNetw / Windows Server 2003 Clustering & Load