Radware (VIP and FARM configuration)

In recent projects, there have been many contacts with the Server Load balancer device RADWARE, and many may not know this device very well, so I will share with you the Radware configuration application in the actual project. RADWARE is a world-leading supplier of Smart Application network solutions. It mainly produces application delivery and network security products and is headquartered in Tel Aviv, Israel.

Load Balancing (also known as Load balancing) is called Load Balance, which means to Balance and distribute the Load tasks to multiple operation units for execution, for example, the Web server, FTP Server, Enterprise key application server, and other key task servers can work together to complete tasks. Server Load balancer is not a basic network device, but a performance optimization device. For network applications, Server Load balancer is not required in the first place. When the traffic of network applications increases and a single processing unit cannot meet the load requirements, the network application traffic will suffer a bottleneck, load Balancing will play a very good role. Server Load balancer has two meanings: first, a large amount of concurrent access or data traffic is distributed to multiple node devices for separate processing, reducing the user's waiting for response time. Second, the operation of a single heavy load is distributed to multiple node devices for parallel processing. After each node device finishes processing, the results are summarized and returned to the user, which greatly improves the system processing capability.
Modern Server Load balancer technology usually operates on Layer 4 or Layer 7 of the network. This is a server Load balancer Technology for network applications. It is completely isolated from switches and servers and becomes an independent technical device. Two solutions for Server Load balancer:  A software Load Balancing solution is to install one or more additional software on the operating system of one or more servers to achieve load balancing. Its advantages are that it is easy to configure based on a specific environment, flexible use, low cost, can meet general load balancing needs. Software solutions have many disadvantages, because the installation of additional software on each server consumes a certain amount of resources. The more powerful the module, the more it consumes, therefore, when the connection request is very large, the software itself becomes a key to the success or failure of the server. In addition, software scalability is not very good and is vulnerable to operating system restrictions. Due to Operating System Bugs, security problems are often caused. The hardware Server Load balancer solution directly installs Server Load balancer devices between servers and external networks. This type of device is usually called Server Load balancer. dedicated devices perform specialized tasks and are independent of the operating system, the overall performance has been greatly improved, coupled with a variety of Load Balancing policies, intelligent traffic management, to achieve the best load balancing needs. In general, Hardware load balancing is superior to software in terms of functions and performance, but it is expensive. Radware Server Load balancer: RadwareAppDirector AD) can effectively balance the load of IP applications and optimize network performance. AppDirector plays an important role between the Internet and Server cluster (Server Farms). It can monitor all user requests and intelligently distribute loads among available application resources, this provides excellent fault tolerance, redundancy, optimization, and scalability. First, we first understand two important concepts in RADWARE: VIP and FARM. VIP is the virtual address provided by the Internal Server group for external access. Each virtual address must correspond to a public IP address and then be associated with the defined Farm. Farm is a group of servers that provide the same services. The servers in this group have the same attributes. The server is an element of Farm and belongs to Farm.

650) this. width = 650; "border =" 0 "alt =" "src =" http://www.bkjia.com/uploads/allimg/131227/0253234514-0.jpg "/>

For example:
Currently, there are three FARM groups in the service zone. FARM1 is a WAP application group, FARM2 is a WEB application group, and FARM3 is an OPM application group. Each group has three servers. We only need to set up three VIP virtual addresses to match the public IP addresses with the three virtual addresses for NAT. Then, we can use the Server Load balancer device to load the network applications of key services.

The following describes the corresponding setup methods and procedures:
1. Create a FARM
AppDirector> Farms> Farm Table> Create

650) this. width = 650; "border =" 0 "alt =" "src =" http://www.bkjia.com/uploads/allimg/131227/0253235918-1.jpg "/>

 

650) this. width = 650; "border =" 0 "alt =" "width =" 654 "height =" 417 "src =" http://www.bkjia.com/uploads/allimg/131227/0253234922-2.jpg "/>

Parameter description:
Farm Name:XXXFarm, define the Farm name

Aging Time:60. The aging time of the user session table, in seconds. The longer the session is maintained, the more tables the table is. Connectivity Check Method:PING: The default health check method is PING, but there are multiple options ." Session Mode:Session persistence mode. The default value is EntryPerSession, indicating session persistence for the same source address. If ServerPerSession is selected, session persistence is performed on different ports. Dispatch Method: load balancing algorithm-Cyclic (Round Robin): Round Robin-Weighted Cyclic: weight-based Round Robin (manually and statically define the packet distribution proportion)-Least Traffic: minimum traffic: Fewest Number of Users: Minimum Number of user connections; Response Time Load Balancing: the fastest Response Time. After the Health Check module is enabled and configured, click set to save. 2. Create a SERVER in the FARM group
AppDirector> Server> Application Server> Table> Create

650) this. width = 650; "border =" 0 "alt =" "src =" http://www.bkjia.com/uploads/allimg/131227/0253234425-3.jpg "/>

650) this. width = 650; "border =" 0 "alt =" "width =" 611 "height =" 446 "src =" http://www.bkjia.com/uploads/allimg/131227/0253232647-4.jpg "/>

Farm Name:AppXcel-farm, Farm name Server Address:Real IP address of the server Server Port:The actual Port Number of the server. If the actual port number of the server is the same as the port number of the VIP to provide external services, the default value is None. If the actual port number of the server is 8080, the external service port is 80, the value is 8080. Server Name:After the server name is configured, click "set" to save. 3. Create a VIP and associate it with FARM, protocol, and Port

AppDirector> Layer 4 Farm Selection> Layer 4 Policy Table> Create

650) this. width = 650; "border =" 0 "alt =" "src =" http://www.bkjia.com/uploads/allimg/131227/0253233164-5.jpg "/>

650) this. width = 650; "border =" 0 "alt =" "width =" 620 "height =" 410 "src =" http://www.bkjia.com/uploads/allimg/131227/0253234609-6.jpg "/>

 

Configure the L4 Policy virtual address, protocol type, port number, and name. This combination is the VIP that is provided to external access and then associated with the defined Farm. Now, let's talk about this in this section. We will continue with this section.
 

This article is from the "dripping water and stone" blog and will not be reposted!