wlc 5508

First, Brief introduction LVS is a shorthand for Linux Virtual server and is a highly scalable and highly available cluster solution on Linux servers. Developed by Dr. Zhangwensong, it is now integrated into the Linux kernel module and implements a load balancing schedule of four layers (transport layer) at the kernel level. Principle:ii. working mode of LVSThere are three different modes of operation depending on how the backend server returns data:Mode

, LVS will automatically distinguish, so the overall system is very stable.4, no flow, the above has been mentioned. LVS simply distributes the request, and the traffic does not go out of it itself, so it can be used to do some line diversion. Without traffic, the IO performance of the Equalizer will not be affected by large traffic.5, basically can support all applications, because LVS work in the 4 layer, so it can load balance almost all applications, including HTTP, database, chat room and s

(round robin), WRR (with weighted rotation), LC (minimum Connection), WLC (minimum weight connection)6, the configuration is complex, dependence on the network is relatively large, high stability.Features of Ngnix:1, work in the network on the 7 layer, can be targeted for HTTP applications to do some diversion strategy, such as for the domain name, directory structure;2, Nginx dependence on the network is relatively small, in theory can ping through

]--scheduler-s Scheduler one of RR|WRR|LC|WLC|LBLC|LBLCR|DH|SH|SED|NQ,--real-server-r server-address Server-address is host (and port)--masquerading-m masquerading (NAT)--gatewaying-g gatewaying (Direct routing) (default)--delete-server-d Delete Real Server--persistent-p [Timeout] Persistent service--set TCP tcpfin UDP set connection timeout values--weight-w weight capacity of real serverMore detailed parameter reference: Ipvsadm--helpmanually binding

1 >/proc/sys/net/ipv4/conf/all/arp_ignoreEcho 2 >/proc/sys/net/ipv4/conf/all/arp_announceEcho 1 >/proc/sys/net/ipv4/conf/lo/arp_ignoreEcho 2 >/proc/sys/net/ipv4/conf/lo/arp_announcepermanent effect requires modification configuration file: /etc/sysctl.confNet.ipv4.conf.eth0.app_ignore = 1Net.ipv4.conf.eth0.app_announce = 2Net.ipv4.conf.all.arp_ignore = 1Net.ipv4.conf.all.arp_announce = 2sysctl–p make configuration effective# Add RouteRoute Add–host 172.16.58.1 devlo:0# synchronizing time from t

has a request, but 1 hours later, some idle, some or 1001 requests, but static scheduling still distributed according to the rules of the requestRR: PollingWRR: Weighted pollingSH:sessionsharing Implementation session affinity : Session bindingDH: Send the same IP request to the same serverDynamic scheduling: Consider the server state, such as the number of active links, the number of inactive links, they occupy resources is not the sameLC:lestconnection least linkActive*256+inactive who's the

fails, lvs will automatically identify the problem, so the system is very stable as a whole.4. No traffic, as mentioned above. Lvs only distributes requests, but the traffic does not go out of it. Therefore, it can be used to distribute some lines. Without traffic, I/O performance of the balancer is not affected by large traffic.5. Basically, it supports all applications. Because lvs works on Layer 4, it can perform operations on almost all applications.Server Load balancerIncluding http, datab

optimization and supplement, LVS will consider the performance of each server, and add a weight to each server, if the weight of server A is 1, Server B has a weight of 2, then the request dispatched to Server B will be twice times the server A. The higher the weighted value of the server, the more requests are processed.3: The Minimum connection scheduling algorithm (LC) will dispatch the request to the server with the smallest number of successive4: Weighted minimum connection algorithm (

cluster configuration instanceconfiguration instructions for the same first scienceVirtual Server:Configuration structure:Virtual_server IP port or virtual_server fwmark int{...Real_server {...}...}Common parameters:Delay_loop Lb_algo RR|WRR|LC|WLC|LBLC|SH|DH: Define the scheduling method;Lb_kind nat| dr| TUN: type of cluster;Persistence_timeout Protocol TCP: Service protocol, TCP only supported;Sorry_server Real_server {Weight Notify_up Notify_down

the Real-server. ipvs implements eight load scheduling algorithms. Four scheduling algorithms are described here: RR is called scheduling: Equal distribution of R, regardless of load. WRR Weighted Round scheduling: Set high/low weights and assign them to R. Minimum LC connection scheduling: Dynamically assigned to R with few established connections. Wlc weighted least connection scheduling: Dynamically set the weight of R. When allocating new con

192.168.18.18 80 {// define a virtual service Delay_loop 6 Lb_algo wlc // specify the Scheduling Algorithm Lb_kind Dr // specify the Working Model Nat_mask 255.255.255.0 Persistence_timeout 0 // persistent connection Protocol TCP Real_server 192.168.18.203 80 {// define RealServer Weight 1 // set the weight Http_get {// configure HTTP Health Check URL { Path /// check path Status_code 200 // response status information } Connect_timeout 3 // timeout

eth0 virtual_router_id 51 # ID between nodes should be the same as priority 100 # Master advert_int 1 authentication {auth_type pass # authentication method between nodes auth_pass 1111 # consistency between nodes} virtual_ipaddress {192.168.81.229 }# virtual host configuration virtual_server 192.168.81.229 6379 {# Set VIP port delay_loop 6 # Check real_server status lb_algo RR # LVS scheduling algorithm here using Weighted Round Robin: rr | WRR | LC | wlc