Build a high-availability environment using Windows NLB and IIS arr-from Network

Classification: experience-based technology exploring Analysis and Design of Network TechnologyRead by 1272Comment (1)FavoritesReport

Windowsiis server microsoftserver Network

In many existing network applications, sometimes a server cannot meet the requirements of the client. Is there any solution to the high scalability, high availability, high reliability, and high performance of the server, increase server SLA? Using the network load balancing (NLB) and IIS 7 ARP modules in Windows Server 2008/R2 is the solution to this problem.

A cluster refers to a group of servers that provide the same service or application through collaboration with each other.ProgramTo improve availability, reliability, and scalability of services or applications ). When the servers in the cluster are down, service requests are forwarded to nodes in other clusters for uninterrupted services within 24 hours.

Network Load Balancing (NLB) is a load balancing technology provided by Microsoft on all Windows 2000 Server, Windows Server 2003, Windows Server 2008, and Windows Server 2008 R2 operating systems. Network Load Balancing (NLB) distributes network connection customers and server applications on multiple servers in the same NLB cluster. NLB allows additional servers to be added, so it is scalable. In addition, NBL allows users to replace unhealthy servers to ensure reliability. NBL is crucial for enterprises that need to distribute Multiple customer requests on a group of servers. In particular, it can ensure that web-based applications running on Internet Information Service (IIS) can be expanded by adding additional servers to increase workload.

Network Load Balancing (NLB) includes the following features:

2. scalability

Scalability is the standard used to measure how computers, services, or applications can be better improved to meet sustained growth in performance requirements. For NLB clusters, scalability refers to the function of gradually adding one or more systems to an existing cluster when all the load of the cluster exceeds its capacity. The following table describes the NLB scalability in detail:

-- Balance the load requests of various TCP/IP Services on the NLB Cluster

-- Supports up to 32 computers in a group

-- Balance multiple server load requests between multiple hosts in the cluster (from the same client or from several clients)

-- Supports adding hosts to the NLB cluster without shutting down the cluster when the load increases

-- Allows you to delete hosts from a cluster when the load is reduced.

-- Improve performance and reduce overhead with all pipelines. The pipeline allows sending requests to the NLB cluster without waiting to respond to the previous sending request

2. High Availability

By minimizing downtime, high-availability systems can reliably provide acceptable services. NLB includes some built-in functions to provide high availability by automatically performing the following operations:

-- Detects and recovers faulty or offline cluster hosts.

-- Balance network load when adding or deleting hosts.

-- Restore and resend the load within 10 seconds.

2. manageability

NLB provides the following manageability functions:

-- Using the NLB manager, you can manage and configure multiple NLB clusters and cluster hosts from a single computer.

-- Using port management rules, you can specify Load Balancing behavior for a single IP port or a group of ports.

-- Different port rules can be defined for each website. If you use the same set of Server Load balancer servers for multiple applications or websites, port rules are based on the target virtual IP address (using a virtual cluster ).

-- Use optional single-host rules to direct all client requests to a single host. NLB routes client requests to a specific host running a specific application.

-- Prevents unnecessary network access to some IP Ports.

-- You can enable the Internet Group Management Protocol (IGMP) support on the cluster host to control vswitch broadcast (when operating in multicast mode ).

-- Using shell commands or scripts, You can remotely start, stop, and control NLB operations on any networked computer running Windows.

-- You can view Windows event logs to check NLB events. NLB records all operations and cluster changes in the event log.

2. ease of use

NLB provides many easy-to-use features:

-- NLB can be installed as a standard Windows Network Driver component.

-- NLB can be enabled and run without changing any hardware.

-- Use the NLB manager to create an NLB cluster.

-- Using the NLB manager, you can configure and manage multiple clusters and all hosts in the cluster from one remote computer or local computer.

-- NLB allows the client to access the cluster using a single logical Internet Name and virtual IP address (called the cluster IP address, which retains the names of each computer. NLB allows multiple host servers to have multiple virtual IP addresses.

Note: For a virtual cluster, you do not need to use a multi-host server to have multiple virtual IP addresses.

-- You can bind NLB to multiple network adapters so that you can configure multiple independent clusters on each host. Different network adapters are supported from virtual clusters Because Virtual clusters allow you to configure multiple clusters on a single network adapter.

2. NLB Configuration

NLB runs as a Windows Network Driver. Its operations are transparent to TCP/IP network stacks.

Shows the relationship between NLB and other software components in a typical NLB host configuration.

-- The server application can be run in the NLB group without modification.

-- If the cluster host fails and becomes online again, you can configure NLB to automatically add the host to the cluster. Then, the added host can start to process new server requests from the client.

-- The computer can be taken offline for preventive maintenance without interrupting cluster operations on other hosts.

The network load balancing function in Windows Server 2008 R2 is used by more users at the same time. The network load balancing functions in Windows Server 2008 R2 are improved:

1. Better support for persistent connections between applications and services

The network load balancing IP stickiness feature allows you to configure persistent connections between clients and cluster nodes. By default, network load balancing distributes each request to nodes in the cluster. Some applications such as shopping cart applications require a service that will maintain persistent connection with a specific cluster node.

2. Improved health monitoring for applications and services

The Windows Server 2008 R2 network load balancing management package allows you to monitor the running status of applications and services running in a network load balancing group.

3. Support for next-generation TCP/IP

Windows Server 2008 R2 supports Internet Protocol Version 4 (IPv4) and Internet Protocol version 6 (IPv6 ). NLB supports both IPv4 and all IPv6 communications.

4. Support for multiple IP addresses

Now, each node in the NLB cluster has multiple dedicated IP addresses.

5. Microsoft ISA Server Integration

Microsoft ISA Server allows clients in a network environment with a hybrid IPv4 and IPv6 infrastructure to access each NLB node through Microsoft ISA Server. ISA Server can also provide intrusion detection services to protect your NLB cluster.

Disadvantages of network load balancing

2. The NLB cluster itself consumes some CPU resources. Therefore, in actual application, the more cluster nodes, the better the performance. Ms officially provides such a test report, simulating that the Web Client downloads a 10 KB static web page from the cluster. When the cluster size exceeds 8 to 10 members, the extension factor significantly deviates from linear expansion. As shown in

2. NLB can only detect the server status and the application status. If the IIS of a node server is unavailable, the client will still be allocated to the node server, as a result, the request fails. To solve the problem at the application layer, you need to use the application Request Routing (ARR) of IIS 7 to Monitor the application status and reverse control the node server. At the same time, NLB can provide high availability for the ARR module of IIS 7.

In short, arr is an iis7 Server Load balancer module that manages multiple Server clusters in IIS 6/7 at a time. The rules are based on URLs, host names, or HTTP headers. Microsoft's application Request Routing (ARR) 2.0 enables Web administrators, virtual host providers, and content delivery network (CDN) to match machine names through rule-based routing, HTTP request load balancing and distributed disk cache to improve the scalability and reliability of Web applications. With the ARR technology, administrators can optimize resource and application server management costs.

2. Server Load balancer can effectively improve resource utilization.

With arr, administrators can create powerful rule-based URLs and HTTP headers variables and determine the most appropriate Web application server. Arr selects routes at the application layer, and adds hardware Load balancer such as big ip 5 or Windows Server Load balancer technology to it to perform layer-3 architecture routing. Typical Methods: With arr, the administrator can route *. aspx to an independent application server.

2. Using standard IIS manager makes it easier to manage multiple web farms

Arr provides administrators with the ability to create, manage, and apply load balancing rules. administrators can easily add a server to the Web farms as needed, ARR also monitors the real-time traffic and URL tests of each server. The administrator can view the statistics of each server in Web farms in IIS 7 manager.

2. Optimize bandwidth usage and expand server capabilities through Cache

Arr can cache any HTTP Communication through the server on the disk. By running the arr iis Web server together with the disk cache and hierarchical IIS website, the CDN and hierarchical server capabilities can greatly reduce the network traffic to the source server.

The specific Configuration documentation is not detailed here. Only the documentation links on IIS. NET are provided. Main configuration steps:

Step 1:Follow this document to install application Request Routing to install arr V2, restart the server, and then complete the subsequent steps.

Step 2:Follow this document to configure your arr server farm according to achieving high availability and scalability-Arr and NLB. Here is a configuration document named achieving high availability and scalability-Arr and hardware Load balancer.

Applications are scalable and require application architecture support. For ASP. net Applications, mainly to solve two problems ASP. net session state and ASP. net cache, which has a good solution in Windows Server appfabric. SeeArticleWindows Server appfabric beta 2 for vistual studio 2010 has been released. wizardwu has a blog post on how to use IIS 7, arr, and velocity to build high-performance large websites for your reference.

Pdf version: http://cid-33478a966734670f.skydrive.live.com/self.aspx/.Public/%e9% AB %98%e5%8f%af%e7%94%a8%e6%80%a7/Windows%20NLB%e6%90%ad%e9%85%8dIIS%e7%9a%84ARR%e6%90%ad%e5%bb%ba%e9% AB %98%e5%8f%af%e7%94%a8%e7%8e%af%e5%a2%83.pdf

Download:

Arr V2 x86: http://download.microsoft.com/download/4/D/F/4DFDA851-515F-474E-BA7A-5802B3C95101/ARRv2_setup_x86.EXE

Arr V2 x64: http://download.microsoft.com/download/3/4/1/3415F3F9-5698-44FE-A072-D4AF09728390/ARRv2_setup_x64.EXE

Share:

• Previous:Introduction to Server Load balancer
• Next article:IT industry talent salary exposure, Income Survey, salary exposure