免费注册 查看新帖 |

Chinaunix

  平台 论坛 博客 文库
12345下一页
最近访问板块 发新帖
查看: 42891 | 回复: 43

LVS-HOWTO中文翻译计划,感兴趣加入群72050696 [复制链接]

论坛徽章:
0
发表于 2008-10-13 10:55 |显示全部楼层
现在网友友对LVS的只是都是很热衷,现在打算建立一个lvs howto的翻译项目,主要目的是翻译austintek的LVS HOWTO文章,最后做成一个比较实用的能增加网友对LVS项目的深入理解,并将翻译文章成果以GPL的形式进行发布,以帮助国内的网友尽快的掌握LVS的精华并能在实践中进行具体的应用。
为了保证项目能够良好的进行,需要合作者对基于LVS的群集理论及实践应用有一定的理解和经验,对开源协作等有一定的经验,而且最好能有一位有丰富开源项目经验的朋友加入,因为开源需要很多的交流和讨论。
我不是一个有经验群集管理,但在群集系统实现上大家多给予一些帮助,初步预测这个项目要具有分布式(将51个章节的内容分配到不同的项目成员手中,各个项目成员要相配合),具体翻译内容需要深入的进行讨论并结合实践进行说明再详细讨论,年底之前出完全版吧,不知道有没有感兴趣,我想我们不仅仅是重在参与,而且还得重视结果,也希望对LVS等项目有研究的朋友给予一定的帮助哦,我们不求做的那么大,但求实用。

感兴趣的加入群72050696。
希望CU群集与虚拟机的网友积极参加进来。

第二楼和第三楼分别是翻译内容的第一章到第五十一章的目录。
热心的网友已经开始加入这个计划了
西安|百湖|3 翻译第三章,计划10月的第四个星期完成;
广州|小叶|2 翻译第二章,计划十一月第一个星期完成;
红豆翻译第51节;
小学没毕业|7翻译第7章;

[ 本帖最后由 kns1024wh 于 2008-10-14 12:14 编辑 ]

论坛徽章:
0
发表于 2008-10-13 13:21 |显示全部楼层

需要翻译的内容目录第一至第三十章

Table of Contents
1. LVS: Introduction
1.1. Thanks
1.2. About the HOWTO
1.3. Nomenclature/Abbreviations
1.4. Minimal knowledge required
1.5. Free Technical Help
1.6. After you've Got Technical Help
1.7. Paid technical help
1.8. Mailing list: subscribing, unsubscribing, searching
1.9. Mailing list: posting to
1.10. Bug Fixes
1.11. Other load balancing solutions, GPL, opensource and commercial
1.12. Books on LVS
1.13. LVS in the news
1.14. Software/Information/HOWTOs useful/related to LVS
2. LVS: What is an LVS? Can I use an LVS?
2.1. What is a VIP?
2.2. Where do you use an LVS?
2.3. Client/Server relationship is preserved in an LVS
2.4. LVS director is an L4 switch
2.5. LVS forwards packets to realservers
2.6. LVS runs on Linux and FreeBSD directors
2.7. Code for LVS is different for each kernel series
2.8. kernels from 2.4.x series are SMP for kernel code
2.9. OS for realservers
2.10. LVS works on ethernet
2.11. LVS works on IPv6
2.12. LVS is continually being developed
2.13. LVS is 64 bit
2.14. Other documentation
2.15. LVS is not simple to install, get going or keep running
2.16. LVS Control (Failure, Thundering Herd, Sorry Servers)
2.17. clients on realservers
3. LVS: Install, Configure, Setup
3.1. Installing from Source Code
3.2. Ultra Monkey
3.3. Keepalived
3.4. ipvsman(d)
3.5. Alternate hardware: Soekris (and embedded hardware)
3.6. LVS on a CD: Malcolm Turnbull's ISO files
4. LVS: Ipvsadm and Schedulers
4.1. Using ipvsadm
4.2. Memory Requirements
4.3. sysctl documentation
4.4. Compile a version of ipvsadm that matches your ipvs
4.5. put realservers in /etc/hosts
4.6. RR and LC schedulers
4.7. Netmask for VIP
4.8. LBLC, DH schedulers
4.9. LVS with mark tracking: fwmark patches for multiple firewalls/gateways
4.10. SH scheduler
4.11. What is an ActiveConn/InActConn (Active/Inactive) connnection?
4.12. FAQ: ipvsadm shows entries in InActConn, but none in ActiveConn, connection hangs. What's wrong?
4.13. FAQ: initial connection is delayed, but once connected everything is fine. What's wrong?
4.14. unbalanced realservers: does rr and lc weighting equally distribute the load? - clients reusing ports
4.15. Changing weights with ipvsadm
4.16. Dynamically changing realserver weights
4.17. feedbackd
4.18. lvs-kiss
4.19. connection threshold
4.20. Flushing connection table
4.21. Thundering herd problem, Slow start code for realserver(s) coming on line
4.22. Handling kernel version dependant files e.g. System.map and ipvsadm
4.23. Limiting number of clients connecting to LVS
4.24. Who is connecting to my LVS?
4.25. experimental scheduling code
4.26. Ratz's primer on writing your own scheduler
4.27. changing ip_vs behaviour with sysctl flags in /proc
4.28. Counters in ipvsadm
4.29. Exact Counters
4.30. Scheduling TCP/UDP/SCTP/TCP splicing/
4.31. patch: machine readable error codes from ipvsadm
4.32. patch: stateless ipsvadm - add/edit patch
4.33. patch: fwmark name-number translation table
4.34. ip_vs_conn.pl
4.35. Luca's php monitoring script
4.36. ipvsadm set option
4.37. ipvsadm error messages
4.38. ipvsadm fast update bug with smp
5. LVS: LVS-NAT
5.1. Introduction
5.2. LVS-NAT bugs
5.3. Example 1-NIC, 2 Network LVS-NAT (VIP and RIPs on different network)
5.4. All packets sent from the LVS-NAT realserver to the client must go through the LVS-NAT director
5.5. Run the configure script
5.6. Setting up demasquerading on the director; 2.4.x and 2.2.x
5.7. rewriting, re-mapping, translating ports with LVS-NAT
5.8. masquerade timeouts
5.9. Julian's step-by-step check of a L4 LVS-NAT setup
5.10. How LVS-NAT works
5.11. In LVS-NAT, how do packets get back to the client, or how does the director choose the VIP as the source_address for the outgoing packets?
5.12. One Network LVS-NAT
5.13. re-mapping ports, rewriting is slow for 2.0, 2.2 kernels
5.14. Two instances of demon running on realserver
5.15. Performance of LVS-NAT
5.16. Various debugging techniques for routes
5.17. Connecting directly from the client to a service:port on an LVS-NAT realserver
5.18. A NAT router has no connections
5.19. Thoughts on extending NAT
5.20. Postings from the mailing list
5.21. LVS-NAT source routing patch (Brownfield, Sawari and Black)
5.22. LVS-NAT FTP Recipe
5.23. LVS-NAT vhosts with apache
5.24. LVS-NAT timeout problem
6. LVS: The ARP Problem
6.1. The problem
6.2. Put the VIP on the realservers lo device
6.3. The Cure(s)
6.4. The Cure: 2.0 kernels - nothing needed
6.5. The Cure: 2.2.x kernels - many options
6.6. The Cure: 2.4.x kernels - arp_ignore/arp_announce
6.7. The Cure: 2.6.x kernels - arp_ignore/arp_announce
6.8. arptables
6.9. The arp problem is on the realserver's VIP not the RIP
6.10. Testing an interface for replies to arp requests
6.11. Normal machines, Solaris
6.12. problems with switches
6.13. The ARP problem, the first inklings
6.14. A posting to the mailinglist by Peter Kese explaining the "arp problem"
6.15. arp bouncing
6.16. Lar's Method
6.17. Static Routing to Director
6.18. iproute2 arp on|off flag
6.19. Is the arp behaviour of 2.2.x kernel a bug?
6.20. The device doesn't reply to arp requests, the kernel does.
6.21. Properties of devices for the VIP
6.22. Topologies for LVS-DR and LVS-Tun LVS's
6.23. Why do all devices broadcast the arp replies
6.24. A discussion about the arp problem
6.25. ATM/ethernet and router problems
6.26. Same IP on multiple NICs
7. LVS: LVS-DR
7.1. LVS-DR example
7.2. How LVS-DR works
7.3. Handling the arp problem for LVS-DR
7.4. LVS-DR scales well
7.5. LVS-DR director as default gw for realservers, transparent proxy and Julian's martian and forward_shared patches
7.6. Accepting packets on LVS-DR director by fwmarks
7.7. security concerns: default gw(s) and routing with LVS-DR/LVS-Tun
7.8. routing to realserver from director
7.9. LVS-DR, LVS-Tun need rp_filter=0
7.10. Director as client in LVS-DR
7.11. from the mailing list
7.12. rewriting, re-mapping, translating ports with LVS-DR
8. LVS: LVS-Tun
8.1. LVS-Tun Intro
8.2. LVS-Tun example setup
8.3. You need a tunl0 device
8.4. the ARP problem with LVS-Tun
8.5. Reply packets appear to be spoofed
8.6. How LVS-Tun works
8.7. The RIP (not the tunl device) receives the ipip packet
8.8. Configure LVS-Tun
8.9. set rp_filter correctly
8.10. FreeBSD and Solaris realservers with LVS-Tun
8.11. Windows realservers with LVS-Tun
8.12. Realservers without ipip encapsulation
8.13. LVS-Tun has smaller MTUu: PMTU is disabled - handling fragmentation
8.14. MTU: early signs of problems
8.15. tunl mtu solved: Setting the MTU by MSS with iptables on the realserver
8.16. Setting the MTU by route
8.17. rewriting, re-mapping, translating ports with LVS-Tun
9. LVS: LocalNode
9.1. Two LocalNode Servers
9.2. Two Box LVS
9.3. Testing LocalNode
9.4. Localnode on the backup director
9.5. rewriting, re-mapping, translating ports with Localnode
10. LVS: You can't map (or earewrite) ports with LVS-DR, LVS-Tun or localnode (but you can with iptables)
10.1. You can't rewrite ports with localnode (but you can with iptables)
10.2. rewriting, re-mapping, translating ports with iptables in LVS-DR
10.3. can't port map with LVS
11. LVS: Non-LVS clients on Realservers
11.1. always NAT out clients through VIP
11.2. Masquerading clients on realservers to the outside world (SNAT)
11.3. Masquerading clients on LVS-NAT realservers
11.4. Masquerading clients on LVS-DR realservers
11.5. Masquerading clients on LVS-Tun realservers
11.6. Masquerading clients through the VIP on the director
11.7. 3-Tier LVS
11.8. Routes needed for 3-Tier LVS
11.9. Setting up routes using iptables and iproute2
11.10. from the mailing list
12. LVS: LVS clients on Realservers
12.1. Do you really need LVS clients on the realserver in a 3-Tier setup?
12.2. Realserver as LVS client in LVS-NAT
12.3. Realserver as LVS client in LVS-DR
13. LVS: Non Linux Realservers
13.1. Loopback interface on Windows/Microsoft/NT/W2K
13.2. Mac OS X (and Solaris)
14. LVS: identd/authd
14.1. What is authd/identd?
14.2. authd/identd and other 3-Tier clients
14.3. symptoms of the identd problem
14.4. comp.os.linux.security FAQ on identd
14.5. Russ Nelson on identd
14.6. Why identd is a problem for LVS
14.7. tcpdumps of connections delayed by identd
14.8. There are solutions to identd problem in some cases
14.9. Turn off tcpwrappers
14.10. Identd and smtp/pop/qmail
15. LVS: Variants on LVS: Local Nodes (One Box LVS)
16. LVS: Variants on LVS: Peter Warasin's ip_vs() in PREROUTING
17. LVS-J: Ludo's reinJect Forwarder: using the director as a gateway to load balance connections to the internet
17.1. Introduction
17.2. reinJect setup with ipvsadm
17.3. The target LVS: sending packets with dst_addr=0/0 to ip_vs
17.4. setting up LVS-J forwarding
17.5. SNAT'ing the output
17.6. LVS-J discussion by Ludo
18. LVS: Services: general, setup, debugging new services
18.1. Single port services are simple
18.2. setting up a (new) service
18.3. services must be setup for forwarding type
18.4. Realservers present the same content: Synchronising (filesharing) content and config files, backing up realservers
18.5. cfengine for synchronising files
18.6. File Systems for (really big) Clusters: Lustre, Panasas
18.7. File Systems for Clusters: Samba waits for a commit and is slow, NFS fills buffers and is fast
18.8. Discussion on distributed filesystems
18.9. load balancing and scheduling based on the content of the packet: Cookies, URL, file requested, session headers
18.10. timeouts for TCP/UDP connections to services
18.11. name resolution on realservers: running name resolution friendly demons on realservers
18.12. Debugging new services
18.13. "broken" services:servlets and j2ee
18.14. http logs, error logs
19. LVS: Services: single-port
19.1. ftp, tcp 21
19.2. ssh, sftp, scp, tcp 22
19.3. telnet, tcp 23
19.4. smtp, tcp 25; pop3, tcp 110; imap tcp/udp 143 (imap2), 220(imap3). Also sendmail, qmail, postfix, and mailfarms.
19.5. Mail Farms
19.6. dns, tcp/udp 53 (and dhcpd server 67, dhcp client 6
19.7. http name and IP-based (with LVS-DR or LVS-Tun), tcp 80
19.8. http with LVS-NAT
19.9. httpd is stateless and normally closes connections
19.10. netscape/database/tcpip persistence (keepalives)
19.11. dynamically generated images on web pages
19.12. http: sanity checks, shutting down, indexing programs, htpasswd, apache proxy and reverse proxy to look at URL, mod_backhand, logging
19.13. HTTP 1.0 and 1.1 requests
19.14. Large HTTP /POST with LVS-Tun
19.15. Microsoft http clients and servers violate the RFC for TCP/IP
19.16. http keepalive - effect on InActConn
19.17. Fallback/Sorry pages with Apache
19.18. Testing http with apachebench (ab)
19.19. Apache setup for DoS
19.20. squids, tcp 80, 3128
19.21. authd/identd, tcp 113 and tcpwrappers (tcpd)
19.22. ntp, udp 123
19.23. https, tcp 443
19.24. name based virtual hosts for https
19.25. Obtaining certificates for https
19.26. Self made certificates
19.27. SSL Accelerators and Load Balancers
19.28. r commands; rsh, rcpi (and their ssh replacements), tcp 514
19.29. lpd, tcp 515
19.30. Databases
19.31. Databases: mysql
19.32. Using Zope with databases
19.33. Databases: Microsoft SQL server, tcp 1433
19.34. Databases: Oracle
19.35. Databases: ldap, tcp/udp 389, tcp/udp 636
19.36. nfs, udp 2049
20. LVS: Services: multi-port
20.1. Introduction
20.2. ftp general, active tcp 20,21; passive 21,high_port
20.3. ftp helper modules: ip_vs_ftp/ip_masq_ftp
20.4. ftp (active) - the classic command line ftp
20.5. ftp (passive)
20.6. ftp helper bug(s)
20.7. ftp is difficult to secure
20.8. ftps (ssl based ftp), tcp 21, 22?
20.9. dns, tcp/udp 53 (and dhcpd server 67, dhcp client 6
20.10. samba, udp 137, udp 138, tcp 139, tcp 445
20.11. xdmcp, X-window, udp 177 (xdmcp), tcp 6000 (and ssh X-forwarding)
20.12. r commands; rsh, rcp, and their ssh replacements, tcp 513 (,514) and another connection
20.13. Streaming Media: RealNetworks, Quicktime, Windows Media Server, tcp/udp 554 (and other ports)
20.14. Radius, udp 1645,1646
21. LVS: Services that we haven't got to work with LVS yet
21.1. Kerberos
21.2. RMI
22. LVS: UDP Services - unique problems
22.1. SIP (Session Initiation Protocol)
22.2. UDP timeouts (SIP)
22.3. UDP timeouts (DNS)
22.4. Julian's One Packet Scheduler (OPS) for UDP, timeouts for DNS
22.5. icmp responses aren't generated by UDP timeouts on VIP-less directors
23. LVS: Routing and packet delivery to a director without a VIP (for fwmark and transparent proxy)
23.1. Introduction
23.2. Routing to and accepting packets by a VIP-less director
23.3. Routing to the MAC address of the director
23.4. Julian's iproute2 solutions
23.5. Ludos LVS target in iptables
23.6. Transparent proxy Q and A
23.7. Other tricks
24. LVS: Fwmarks (firewall marks)
24.1. Introduction
24.2. ipvsadm syntax for fwmark
24.3. setting up routing and packet delivery to the director
24.4. single-port service: telnet with fwmarks
24.5. Grouping services: single group, active ftp(20,21)
24.6. Grouping services: two groups, active ftp(20,21) and e-commerce(80,443)
24.7. passive ftp
24.8. fwmark with LVS-NAT
24.9. collisions between fwmark and VIP rules
24.10. persistence granularity with fwmark
24.11. fwmark allows LVS-DR director to be default gw for realservers
24.12. fwmark simplifies configuration for large numbers of addresses
24.13. Example: firewall farm
24.14. Example: LVS'ing a CIDR block
24.15. Example: forwarding based on client source IP
24.16. Example: load balancing multiple class C networks
24.17. Example: proxy server
24.18. Example: transparent web cache
24.19. Example: Multiply-connected router
24.20. httpd clients (browsers)
24.21. Example: dynamically generated images in webpages
24.22. Example: Balancing many IPs/services as one block
24.23. Example: Source controlled LVS - services and realserver customised by Client IP
24.24. Appendix 1: Specificiations for grouping of services with fwmarks
24.25. Appendix 2: Demonstration of grouping services with fwmarks
24.26. Appendix 3: Announcement of grouping services with fwmarks
24.27. fwmark examples from the mailing list
25. LVS: Transparent proxy (TP or Horms' method)
25.1. setting up routing and packet delivery to the director
25.2. General
25.3. How you use TP
25.4. The original 2.2 TP setup method
25.5. Transparent proxy for 2.4.x (and presumably 2.6.x)
25.6. Experiments showing that 2.4TP is different to 2.2TP
25.7. What IP TP packets arriving on?
25.8. Take home lesson for setting up TP on realservers
25.9. Handling identd requests from 2.4.x LVS-DR realservers using TP
25.10. Performance of Transparent Proxy
25.11. The difference between REDIRECT and TPROXY
26. LVS: Transparent Bridging
27. LVS: Persistent Connection (Persistence, Affinity in cisco-speak)
27.1. LVS persistence
27.2. Scheduling looks different under persistence
27.3. Persistent and regular (non-persistent) services together on the same realserver.
27.4. Tracing connections: where will the client connect next?
27.5. Bringing down persistent services.
27.6. Forcing a break in a persistent connection: expire_quiescent_template - Horms sysctl for quiescing persistent connections
27.7. what if a realserver holding a persistent (sticky) connection crashes
27.8. Load Balancing time constant is longer with persistence
27.9. The tcp NONE flag
27.10. Resetting the persistence timeout counter (persistence behaviour for short timeout values)
27.11. Why you don't want persistence for your e-commerce site: why you should rewrite your application
27.12. more about e-commerce sites: we used to think memory was the problem - it isn't
27.13. persistence with windows realservers
27.14. messing with the ipvsadm table while your LVS is running
27.15. Persistence for multiport services
27.16. Proxy services, e.g. AOL
27.17. key exchanges (SSL)
27.18. About longer timeouts
27.19. passive ftp and persistence
27.20. The Persistence Template (about port 0)
27.21. persistent clients behind a proxy or nat box
27.22. Rogue clients hidden by persistence
27.23. Long (1 day) persistence to windows terminal servers
28. LVS: Running a firewall on the director: Interaction between LVS and netfilter (iptables).
28.1. Start with no filter rules
28.2. Introduction
28.3. Path of an ip_vs controlled packet
28.4. how to filter with netfilter
28.5. ipvs_nfct, netfilter connection tracking for ipvs
28.6. LVS-NAT netfilter conntrack example with ftp
28.7. tcpdump is LVS compatible
28.8. Writing Filter Rules
28.9. The Antefacto Netfilter Connection Tracking patches
28.10. The design of LVS as a netfilter module, pt1
28.11. The design of LVS for Netfilter and Linux 2.4, pt2
28.12. Example ip_tables filter scripts
28.13. performance hit on director with iptables/netfilter
28.14. Long sessions through LVS DR director terminated by icmp-host-prohibited (ICMP type 3 code 10)
29. LVS: Cluster friendly versions of applications that need to maintain state
29.1. rewriting your application/service
29.2. Session Data, maintaining state in a cluster, from Andreas Koening
29.3. Single Session
29.4. IIS session management: how it works
29.5. Maintaining state with persistence
29.6. How others maintain state
30. LVS: Squid Realservers (poor man's L7 switch)
30.1. Terminology
30.2. Preview
30.3. Let's start assembling
30.4. One squid
30.5. Another squid
30.6. Combining pieces with LVS
30.7. Problems

论坛徽章:
0
发表于 2008-10-13 13:22 |显示全部楼层

翻译计划内容第三十一章至第五十一章目录

31. LVS: Performance and Kernel Tuning
31.1. Performance Articles
31.2. Estimating throughput: Rule of Thumb
31.3. Estimating throughput: 100Mbps FE is really 8000packets/sec ethernet
31.4. Jumbo frames
31.5. Network Latency
31.6. Mixture of 100Mbps and GigE ethernet
31.7. NICs and Switches, 100Mbps (FE) and 1Gbps (GigE)
31.8. NIC bonding
31.9. NIC problems - eepro100
31.10. NIC problems - tulip
31.11. dual/quad ethernet cards, IRQ sharing problems
31.12. Flakey Switch
31.13. performance testing tools
31.14. Max number of realservers
31.15. FAQ: What is the minimum hardware requirements for a director
31.16. FAQ: How fast/big should my director be?
31.17. SMP doesn't help
31.18. Performance Hints from the Squid people
31.19. realservers filling conntrack tables (LVS-DR)
31.20. Conntrack, effect on throughput
31.21. Don't use the preemptible/preemptable/preemptive kernels
31.22. 9.6Gbps served using LVS-DR with gridftp
32. LVS: Monitoring
32.1. CPU usage/load level on the director?
32.2. LVS throughput at the director with ipvsadm
32.3. Monitoring: LVS director throughput statistics from the /proc system (originally /proc/net/ip_vs_stats)
32.4. MRTG family: Intro
32.5. MRTG family: LVSGSP
32.6. MRTG
32.7. MRTG family: RRDtool
32.8. MRTG family: cacti
32.9. MRTG family: Ganglia (incl. INSTALL)
32.10. MRTG family: rrd images
32.11. Nagios
32.12. MIB/SNMP
32.13. home brew MIB/SNMP
32.14. Disks
32.15. Other output GUIs
33. LVS: Details of LVS operation, Security, DoS
33.1. Top 20 security vunerabilities
33.2. Top 75 security tools from the people at nmap
33.3. Network Testing with Abberant Packets
33.4. Do I need security, really?
33.5. What to do after a break-in, prevention strategies
33.6. More about syncookies
33.7. Can filter rules stop the intruder hopping to other machines?
33.8. Where filter rules act
33.9. /proc filesystem flags for ipv4, e.g.rp_filter
33.10. tcp timeout values, don't change them (at least yet)
33.11. /proc file system settings for LVS: security and private copies of tcp timeouts for LVS connections (you can change these)
33.12. timeouts the same for all services
33.13. Director Connection Hash Table
33.14. Hash table connection timeouts
33.15. Hash Table DoS
33.16. Hash table size, director will crash when it runs out of memory.
33.17. The LVS code does not swap
33.18. Other factors determining the number of connections
33.19. Port range: limitations, expanding port range on directors
33.20. Director does not have any ports (connections) open for an LVS connection
33.21. apps starved for ports
33.22. realserver running out of ports
33.23. Maximum number of NICs
33.24. DoS
33.25. DoS, from the mailing list
33.26. Testing DoS Strategies with testlvs: Creating large numbers of InActConn
33.27. Debugging LVS
33.28. realserver content: filesystem or database? (the many reader, single writer problem)
33.29. Developement: Supporting IPSec on LVS
34. LVS: ICMP
34.1. MTU discovery and ICMP handling
34.2. LVS code only needs to handle icmp redirects for LVS-NAT and not for LVS-DR and LVS-Tun
34.3. ICMP checksum errors
34.4. ICMP Timeouts
34.5. PMTUD (path MTU discovery)
34.6. Long sessions through LVS DR director terminated by icmp-host-prohibited (ICMP type 3 code 10)
35. LVS: High Availability, Failover protection
35.1. Introduction
35.2. Single Point of Failure (SPOF) - you can't protect against everything
35.3. Stateful Failover
35.4. Director failure
35.5. UltraMonkey and Linux-HA
35.6. Keepalived and Vrrpd
35.7. Using keepalived to failover routers
35.8. monitoring/failover messages should stay internal to LVS
35.9. Parsing problems with vrrpd config file
35.10. Two instances of vrrpd
35.11. HA MySQL
35.12. Failover of large numbers (say 1024) of VIPs
35.13. Some vrrpd setup instructions
35.14. Filter rules for vrrpd broadcasts
35.15. Vinnie's comparison between ldirectord/heartbeat and keepalived/vrrpd
35.16. Saru: All directors active at the same time
35.17. Server Load Balancing Registration Protocol
35.18. using iproute2 to keep demons running during failover, while link is down
36. LVS: Dynamic Routing, multiple gateways, realservers in multiple LVSs, dead gateway detection
36.1. Setting up multiple gateways: Realservers shared between two LVSs: ip route append
36.2. Connecting from clients through multiple parallel links: the dead gateway problem
36.3. Dynamic Routing to handle loss of routing in directors
36.4. Dynamic routing with gated: An LVS that connects to the outside world through two networks
36.5. flapping stemming from convergence time for spanning tree
37. LVS: Server State Sync Demon, syncd (saving the director's connection state on failover)
37.1. Intro
37.2. Release Notice
37.3. Expiration of Connection in Backup Director
37.4. LVS and syncd do not use conntrack
37.5. Connection Synchronisation (TCP Fail-Over)
37.6. The synchd produces broadcast traffic
37.7. from the mailing list
37.8. Bug (fixed) in syncd: mixed endianness on directors
38. LVS: Realserver failure handled by Mon
38.1. Introduction
38.2. ethernet NIC failure, and channel bonding
38.3. Service/realserver failout: mon, ldirectord
38.4. Mon for server/service failout
38.5. Monitoring the service running on the VIP on the realserver from the director
38.6. About Mon
38.7. Mon Install
38.8. Mon Configure
38.9. Testing mon without LVS
38.10. Can virtualserver.alert send commands to LVS?
38.11. Running mon with LVS
38.12. Why is the LVS monitored for failures/load by an external agent rather than by the kernel?
38.13. Running multiple directors (each with their own IP)
38.14. Mon scripts from Christopher DeMarco
39. LVS: Setting up Linux-HA for directors (mostly by using rpms)
39.1. linux-ha howto
39.2. Fix the (possible) ethernet alias issue.
39.3. Configure /etc/ha.d/. files.
39.4. Stop ldirectord from starting, ensure heartbeat starts on reboot
39.5. starting heartbeat and verifying functionality
39.6. Test your fail-over features, understand HA.
39.7. Configuration of mon - recommended
40. LVS: Director failover using heartbeat
40.1. Introduction
40.2. On using serial and ethernet connections for heartbeat
40.3. Ard van Breeman's replacement for IPaddr using ip and arping
41. LVS: Running LVS under UML (User Mode Linux), by Brett Elliot
41.1. Introduction
41.2. Ethernet bridging
41.3. Putting it all together: UML + LVS examples (not finished)
42. LVS: Newer networking tools: Policy Routing
42.1. Introduction
42.2. Policy Routing and ifconfig
42.3. Various debugging techniques for routes
42.4. checking source routed packets
42.5. handling arp problem with iproute2
42.6. ip commands you mightn't know about
42.7. Ratz's corrections on common iproute2/aliases misconceptions
42.8. Ratz's wrappers (for iproute2)
43. LVS: Weird hardware (and software)
43.1. Arp caching defeats Heartbeat switchover
43.2. Weird Hardware I: cisco catalyst routers gratuitously cache arp data (failover is slow)
43.3. Weird Hardware II: autonegotiation failure on cisco CSS 11050
43.4. Weird Hardware III: Watchguard firewall at client site
43.5. Weird Hardware IV: wrong device gets MAC address
43.6. Weird Hardware V: SonicWAll firewall rewriting sequence numbers
43.7. Weird Hardware VI: cisco 2924XL switch
43.8. Weird Hardware VII: unknown switches don't defragment
43.9. Weird Hardware VIII: bad routers/routing tables at ISP
43.10. Possible Wierd Hardware (or driver) IX: Broadcom GigE card
44. LVS: Misc/FAQ/Wisdom from the mailing list
44.1. Having one director handling multiple LVS sites, Multiple VIPs
44.2. Setting up a fake service on the realserver with inetd
44.3. How to bring down a realserver for maintenance (eg swap disks)
44.4. temporarily removing a realserver from view of keepalived
44.5. Howto turn your single node ftp/http server into an LVS without taking it off-line
44.6. shutdown of LVS
44.7. Other projects like LVS - Beowulf
44.8. Projects like LVS - Eddie
44.9. Recommendations for a redundant file system, RAID
44.10. on the need for extended testing
44.11. Bringing down aliased devices
44.12. Multiple IPs on the Director
44.13. Testimonials
44.14. Transport Layer Security(TLS)
44.15. Setting up a hot spare server
44.16. An LVS of LVSs
44.17. LVS on a Linux/IBM mainframe
44.18. mqseries
44.19. LVS log files
44.20. LVS and linux vlan
44.21. multi-home, multi-router LVS
44.22. Horror story, mostly from slow file system with disk intensive application
44.23. RTNETLINK answers:
44.24. LVS chokes on 600+ connections
45. LVS: L7 Switching
45.1. Introduction
45.2. KTCPVS
45.3. DRWS
45.4. Alexandre's (unamed) L7 code
45.5. UltraMonkey-L7
45.6. from the mailing list about L7 switching
45.7. What is TCPSP?
46. LVS: Geographically distributed load balancing
46.1. Determining Location from the IP
46.2. Supersparrow
46.3. sharing/separate routers
46.4. Other uses of BGP4 with LVS
46.5. Geographically remote nodes connected by Bridging
46.6. Load Balancing by DNS (round robin DNS)
46.7. BIND, BGP with load balancing (more ideas from Horms)
46.8. Commercial Geographically Distributed Servers
46.9. from the mailing list
47. LVS: Loadbalancing with unmodified realservers
47.1. F5 style SNAT
47.2. NetScaler
47.3. Using MASQ with REDIRECT to accept packet on realserver to replace a NetScaler
47.4. Using HAProxy with LVS to substitute for the remote server failover of a NetScaler
48. LVS: Virtualised Hosts in a Linux Virtual Server
48.1. Introduction
48.2. Virtualised Realsevers: VMWare/Xen
48.3. Running a test LVS (director, backup director and realservers) on one box (UML, VMWare)
48.4. VMWare problems with ntp
48.5. Xen tcpip checksum bug
49. LVS: Linux Distributions prepatched with LVS, Unsupported LVS addons
49.1. Distributions prepatched with LVS
49.2. PB's Nutshell HOWTO for Piranha/LVS-NAT
49.3. Horms advice for installing on RedHat systems
49.4. Recipe and LVS binaries for RedHat from Alex Kramarov
49.5. recipes for installing with RedHat from the mailing list
49.6. Hidden RPMs
50. LVS: Useful things that have no other place
50.1. Ramdisk
50.2. cscope
50.3. Neutral currents in multiphase power lines with non-linear loads (like computers with switching power supplies)
50.4. netcat/phatcat
51. LVS: FAQ
51.1. When will LVS be ported to Solaris, xxxBSD...?
51.2. Is there a HOWTO in Japanese, French, Italian, Mandarin...?

论坛徽章:
49
15-16赛季CBA联赛之福建
日期:2016-06-22 16:22:002015年亚洲杯之中国
日期:2015-01-23 16:25:12丑牛
日期:2015-01-20 09:39:23未羊
日期:2015-01-14 23:55:57巳蛇
日期:2015-01-06 18:21:36双鱼座
日期:2015-01-02 22:04:33午马
日期:2014-11-25 09:58:35辰龙
日期:2014-11-18 10:40:07寅虎
日期:2014-11-13 22:47:15申猴
日期:2014-10-22 15:29:50摩羯座
日期:2014-08-27 10:49:43辰龙
日期:2014-08-21 10:47:58
发表于 2008-10-13 13:44 |显示全部楼层

支持一下哦
CU社区要多做一些这类的活动啊,为整个国内的社区做出榜样啊!

论坛徽章:
0
发表于 2008-10-13 13:59 |显示全部楼层
雷人。都学会了头发也白了。

论坛徽章:
0
发表于 2008-10-13 14:37 |显示全部楼层
支持楼主!使用lvs的

论坛徽章:
0
发表于 2008-10-14 10:32 |显示全部楼层

回复 #1 kns1024wh 的帖子

支持啊,我也很关注这个项目,可是自己的英语太差了

论坛徽章:
0
发表于 2008-10-14 11:10 |显示全部楼层

第三章节部分翻译内容3. LVS: Install, Configure, Setup

3.LVS:安装、配置、设置
3.1.从源码安装LVS
LVS-mini-HOWTO文档描述从源代码中安装的方法。在这个描述中有两种方法安装说明
从命令行开始安装。这种方式很好理解发生了什么事情,如果你只希望有一个单一类型的设置。对于LVSs定义配置文件,将是乏味和有错误倾向。如果它不工作,你会花一些时间找出原因。
通过配置脚本建立一个具有单一调度器的LVS。这个脚本定义初始化的基本设置:它的错误证明(会给你足够的信息未能找出可能是错误的) ,我用它为我所有的测试LVS项目中。因为它不容易扩展处理调度器故障和现在其它配置工具能够解决这个问题, configure脚本没有被开发了。对于生产系统,这里需要对调度器设置failover(容错),应该使用其他安装工具或储存设置作为一个脚本(例如ipvsadm-sav) 。
3.2. Ultra Monkey(超猴)
Ultra Monkey是一个二进制的LVS安装包,包括Linux-HA实现调度器节点容错和ldirectord实现realserver故障检测。Ultra Monkey的作者是Horms ,一个LVS开发者。Ultra Monkey被VA Linux预装到服务器上出售,这种方式为该公司赚取了很多利润。Ultra Monkey从2000年开始发布以来,是成熟和稳定。关于Ultra Monkey的疑问在LVS邮件列表中有找到答案。Ultra Monkey在LVS-HOWTO文档中多次被提及到。

这里有安装指导,关于如何在Centos/RHEL4环境安装两个节点Ultra Monkey LVS实现HA/LB的过程。(http://www.jedi.com/obiwan/technology/ultramonkey-rhel4.html).

我最近使用Ultramonkey的RPM包安装LVS。以下是(根据我的理解)完成如何实现CentOS 5 上设置LVS:在两台PC上标准安装64位CentOS 5 系统,使用Ultramonkey 和 Streamlined/HA 的拓扑结构实现对Apache服务的以下假定访问:
Real Server names are ws01.testlab.local and ws02.testlab.local (replace these with the result from uname -n from each RS)
真实服务器主机名分别为ws01.testlab.local 和 ws02.testlab.local(可以通过uname -n在每个真实服务器上获取主机名称)
Real Server IPs are 10.0.0.10/24 and 10.0.0.20/24,
真实服务器IP地址分别是10.0.0.10/24 和 10.0.0.20/24
Gateway: 10.0.0.1
网关是10.0.0.1
Virtual IP: 10.0.0.100
虚拟服务IP地址是 10.0.0.100
Username: tester
注:1-44个步骤分别描述了Ultramonkey在Centos上的安装与配置过程。
1、开机并在BIOS自检过程插入Centos 5 安装CD;
2、选择从CD启动计算机;
3、键入“Enter”回车键进入图形化安装;
4、将提示您测试安装介质。您可以选择测试介质或跳过测试(通常你可以跳过这一步) ;
5、点击“Next”下一步开始安装;
6、选择“English”作为安装的语言并点击“Next”继续下一步;
7、选择“U.S.English”作为键盘映射配置并点击“Next”继续下一步;
8、选择'Remove all partitions on selected drivers and create default layout' 并点击“Next”继续下一步;
9、为每个适配器配置网络设置;
a、点击“Edit”编辑;
i、取消使用“DHCP”的选项;
ii、输入IP地址和子网掩码;
iii、点击“OK”;
b、输入网关和DNS地址并点击“Next”继续下一步;
10、选择“Asia/ Shanghai”并点击“Next”继续下一步;
11、输入两次root密码的设置口令并点击“Next”继续下一步;
12、选择安装的系统软件包
a、点选 'Desktop-Gnome', 'Server', 'Server-GUI', 'Clustering', 'Storage Clustering' ;
b、选择“Customize Now”现在定制;
c、点击“Next”继续下一步;
13、详细设置安装的系统软件包
a、展开并点击'Details'详细选择,在Desktop Environments->GNOME Desktop Environment菜单;
i、取消 'desktop-printing', 'dvd+rw tools', 'esc', 'gimp-print-utils', 'gnome-audio', 'gnome-backgrounds', 'gnome-mag', 'gnome-pilot', 'gnome-themes', 'gok', and 'nautilus-cd' 软件包选择;
b、展开Servers服务器菜单;
i、取消'DNS', 'Legacy Network Server', 'Mail Server', 'Network Servers', 'News', and 'Printing Support' 软件包选择;
c、展开Base System基本系统菜单;
i、取消 'Dialup Networking Support' 软件包选择;
d、展开Base System->Base菜单并点击“Details”详细按钮;
i、取消'bluez-utils' and 'ccid' 软件包选择;
e、点击“Next”继续下一步;
14、点击“Next”继续下一步,开始复制文件;
15、移除 DVD 安装介质并点击“Reboot” 安装后重新启动机器;
16、设置"Disabled"取消防火墙并点击“Forward”继续;
在弹出的对话框中点击“Yes”继续;
17、设置“Disabled”取消SELinux并点击“Forward”继续;
18、选择'Network Time Protocol'标签, 选中 'Enable Network Time Protocol'启用网络时间协议, 并点击 'Forward'继续;
19、在username字段中输入tester用户名, 在Full name字段中输入'Test User', 在password字段中输入两次密码, 点击'Forward'继续;
20、点击“Forward”掉过声卡测试;
21、点击'Finish'以完成Centos 5系统的安装过程;
22、以root用户名和设置的密码登陆本地系统;
23、编辑“/etc/group”文件
vi /etc/group
  a、找到'tester'用户并在其后附加'wheel'用户 (按i键进入插入状态, 按[ESC]键退出编辑状态);
  b、键入':wq'键保存文件并退出;
24、退出服务器,到一台pc上通过SSH客户端(如PuTTY)登陆到服务器;
25、以tester用户登陆服务器;
26、通过SU切换到root帐户
su -
27、通过 yum命令安装后续软件使用dries软件仓库,在/etc/yum.repo.d/ 目录中建立建立 dries.repo配置文件通过下面的参数内容
[/etc/yum.repo.d/dries.repo]
[dries]
name=Extra Fedora rpms dries - $releasever - $basearch baseurl=http://ftp.belnet.be/packages/dries.ulyssis.org/redhat/el5/en/x86_64/dries/RPMS
28、安装dries的GPG key
rpm --import http://dries.ulyssis.org/rpm/RPM-GPG-KEY.dries.txt
29、更新您的本地软件包并安装一些额外的软件包
yum update -y && yum -y install lynx libawt xorg-x11-deprecated-libs nx freenx arptables_jf httpd-devel
30、修正版本信息
mv /etc/redhat-release /etc/redhat-release.orig && \
echo "Red Hat Enterprise Linux Server release 5 (Tikanga)" > /etc/redhat-release
31、从http://www.ultramonkey.org站点下载Ultramonkey RPMs软件包(also grab perl-MAIL-POP3Client, available from http://rpm.pbone.net/index.php3/stat/4/idpl/4508518/com/perl-Mail-POP3Client-2.17-1.el5.centos.noarch.rpm.html as of the time of this writing)
32、安装arptables-noarp-addr 和 perl-Mail-POP3Client 软件包 (改变路径到Ultramonkey下载目录中)
cd /usr/local/src/Ultramonkey && rpm -Uvh arptables-noarp-addr-0.99.2-1.rh.el.um.1.noarch.rpm && \
rpm -Uvh perl-Mail-POP3Client-2.17-1.el5.centos.noarch.rpm
33、安装Ultramonkey
yum install -y heartbeat*
34、从http://www.ultramonkey.org下载和编辑Ultramonkey配置文件以符合您想要的拓扑结构到,在/etc/ha.d/目录编辑它们能够满足您想要的配置。例子如下:
[/etc/ha.d/authkeys]
auth 2
2 sha1 Ultramonkey!
[/etc/ha.d/ha.cf]
logfacility     local0
mcast eth0 225.0.0.1 694 1 0
auto_failback off
node    ws01.testlab.local
node    ws02.testlab.local
ping 10.0.0.1
respawn hacluster /usr/lib64/heartbeat/ipfail
apiauth ipfail gid=haclient uid=hacluster
[/etc/ha.d/haresources]
ws01.testlab.local      \
        ldirectord::ldirectord.cf \
        LVSSyncDaemonSwap::master \
        IPaddr2::10.0.0.100/24/eth0/10.0.0.255
[/etc/ha.d./ldirector.cf]
checktimeout=10
checkinterval=2
autoreload=yes
logfile="/var/log/ldirectord.log"
quiescent=no
# Virtual Service for HTTP
virtual=10.0.0.100:80
        fallback=127.0.0.1:80
        real=10.0.0.10:80 gate
        real=10.0.0.20:80 gate
        service=http
        request="alive.html"
        receive="I'm alive!"
        scheduler=wrr
        persistent=1800
        protocol=tcp
          checktype=negotiate
# Virtual Service for HTTPS
virtual=10.0.0.100:443
        fallback=127.0.0.1:443
        real=10.0.0.10:443 gate
        real=10.0.0.20:443 gate
        service=https
        request="alive.html"
        receive="I'm alive!"
        scheduler=wrr
        persistent=1800
        protocol=tcp
          checktype=negotiate
35、设置authkeys文件的权限
chmod 600 /etc/ha.d/authkeys
36、启动httpd服务
httpd -k start
37、在/var/www/html目录中以如下的内容创建alive.html文件(这是设置监控脚本的步骤)
I'm alive!
在/etc/hosts文件中为每个LVS的机器编辑FQDN名称(这个步骤不是必须的,不过能够帮助解决遇到的问题)
# Do not remove the following line, or various programs # that require network functionality will fail.
127.0.0.1               localhost.localdomain localhost
10.0.0.10               ws01.testlab.local      ws01
10.0.0.20               ws02.testlab.local      ws02
::1             localhost6.localdomain6 localhost6
38、在/etc/sysconfig/network-scripts/ifcfg-lo 文件中设置虚拟IP(Virtual IP)
DEVICE=lo
IPADDR=127.0.0.1
NETMASK=255.0.0.0
NETWORK=127.0.0.0
BROADCAST=127.255.255.255
ONBOOT=yes
NAME=loopback
DEVICE=lo:0
IPADDR=10.0.0.100
NETMASK=255.255.255.255
NETWORK=10.0.0.0
BROADCAST=10.0.0.255
ONBOOT=yes
NAME=loopback
39、编辑/etc/sysconfig/network-scripts/ifcfg-eth0 文件(每个调度器/真实服务器的IP地址,设置具体的etho接口信息
[/etc/sysconfig/network-scripts/ifcfg-eth0 on ws01] \
DEVICE=eth0 ONBOOT=yes BOOTPROTO=static IPADDR=10.0.0.10 NETMASK=255.255.252.0 GATEWAY=10.0.0.1
[/etc/sysconfig/network-scripts/ifcfg-eth0 on ws02] \
DEVICE=eth0 ONBOOT=yes BOOTPROTO=static IPADDR=10.0.0.20 NETMASK=255.255.252.0 GATEWAY=10.0.0.1
40、真实服务器重启network服务使网络设置生效
service network restart
41、在/etc/sysctl.conf 文件中设置ARP数据包的忽略和数据包转发
net.ipv4.ip_forward = 1
net.ipv4.conf.eth0.arp_ignore = 1
net.ipv4.conf.eth0.arp_announce = 2
net.ipv4.conf.all.arp_ignore = 1
net.ipv4.conf.all.arp_announce = 2
42、是 sysctl.conf 配置文件生效
/sbin/sysctl -p
43、确认所有的服务在系统启动时加载
chkconfig httpd on && chkconfig --level 2345 heartbeat on && chkconfig --del ldirectord
44、启动heartbeat服务
/etc/init.d/ldirectord stop && /etc/init.d/heartbeat start

论坛徽章:
0
发表于 2008-10-14 11:14 |显示全部楼层
翻译占位:)初次翻译,有不足的地方望大家斧正

2. LVS: 什么是LVS?我能够使用LVS吗?

Linux Virtual Server ( Linux 虚拟服务 简称LVS) 是指使一个群集的服务器在对外服务时表现为单个服务器的技术。这个表现出来的“单个服务器”被我们称为“虚拟服务器”。那些单独的组成集群的服务器(也就是真实提供服务的服务器,我们称为realservers)是由内核打了ipvs补丁包的Linux控制器(或是负载平衡器)控制着。运行的ipvs补丁包的控制器就具体了基本的LVS特征。其它运用层的程序是用来管理LVS(如:为服务处理,容错处理设置规则)。控制器是基于可修改规则的4层路由结构(换而言之,连接并不来自于或是终止于控制器,控制器并不发送信息,它仅仅是一个路由)。

在LVS结构中一个新的连接是如何由客户端请求到服务器的呢(以httpd为例),控制器将为客户端选择一个真实服务器(realserver)。客户端与真实服务器(realserver)之间将以tcp(或是udp)通信。当下一个tcp请求来临时,控制器将为它选择一个新的真实服务器(realserver)(这个也许是,或不是之前的那个真实服务器)。所以,浏览器请求由LVS系统所提供的一个复杂页面(包括众多图片,文档)时,有可能为每个连接都指向不同的真实服务器。

由于控制器随机把客户请求发送给某台真实服务器,这个请求有可能是只读操作(如,web服务),也有可能是读写操作(如,在线商店的购物车),因此某些外部机制必须提供给LVS用来将这种请求在适当的时候发送给其它的真实服务器(所有节点的真实服务器,这次购买物品的数量应该在下次购买该物品前减一)。最好LVS系统只提供只读服务。

假设你希望某个服务节点能够在任意时间更新,同时其它没有成为首要节点的节点(或是多个节点)被激活成主节点提供服务,那么你需要的可能并不是LVS系统:而是高可用性设置,例:如LINUX-HA(LINUX心跳系统),vrrp 或是 carp。

如果你想要一些分布在不同地区的服务器,那么需要的是类似 Supersparrow的异地分布式服务器。

以下是一些展示负载平衡的RRD图片(链接http://www.austintek.com/LVS/LVS ... lvs.html#rrd_images)

用户工具ipvsadm及schedulers是用于管理LVS,用来添加真实服务器以及移除出错服务器。LVS自身不用于检测错误状态;外部代理通过ipvsadm检测错误状态,然后更新LVS状态。

[10.15更新]

2.1. 什么是VIP?

控制器显示在用户端的IP我们称为VIP(虚拟IP)。(当我们使用防火墙网关时(fwmark),虚拟IP被分解为一群的真实IP,但是仍然以同一个IP的原则应用)。当客户端连接到虚拟IP时,控制器转发客户端的数据包到一个连接到LVS系统的真实服务器(realserver)。连接由管理器选择和管理。realservers提供的服务(如FTP,HTTP,DNS,telnet远程登录,NNTP ,smtp)在/etc/services或是inetd.conf中定义。LVS系统通过控制层仅显示一个IP(虚拟IP,VIP)给客户端。

VIP是“服务群”的IP地址,而不作为系统提供的特定服务(如控制器和真实服务器realservers)的IP地址。

当故障发生时,VIP将从故障控制器移动到其它的备份控制器(通常来说这借助于mon和心跳系统,或是其它类似机制)。控制器可以拥有多个VIP。每个VIP分配给一个或多关相关服务器使用,例如你可以让一个HTTP/HTTPS负载平衡系统使用一个VIP,让FTP(或是其它)负载平衡系统使用另一个VIP,因此对这些VIP的请求将可能被不同的服务器应答。

任意一组的VIP或是端口都可以由防火墙网关设置。

真实服务器的VIP配置由控制器决定(这包括处理ARP问题)。

假如你使用了COOKIES或是HPPTS,或是希望服务器能够保持连接状态信息,这可能会产生持处连接的问题。这个问题的处理方案在LVS persistence page。(http://www.linuxvirtualserver.org/docs/persistence.html

2.2. 你会在什么地方用到LVS?

      A 需要更高的吞吐量。在LVS系统中,通过增加真实服务器来增加吞吐量的费用是线性,而通过购买更大更好的机器来增加吞吐量比线性增长更耗费。

      B 以备不时之需。个别的机器可以移出LVS系统,升级及替换都不会影响到整个系统在线对外服务。机器可以逐步的移到一个新的地址,而不影响系统的对外服务。

      C 为具备高适应能力。如果吞吐量逐步改变(当新的业务建立),或是突然改变(一个突发事件),服务器的数量可以增加 (或减少) ,这种变化对客户而言,是不明显的。

2.3. 客户/服务器关系只是存在于一个LVS系统

      A 客户端只能看到一个IP地址,并且认为它只是连接到一台单独的机器。所有真实服务器的IP映射到同一个IP(VIP)。虽然客户端感觉只是连接到一台机器,但其实随后的连接将被分配到一个新的,可能不同的机器。

      B 拥有不同IP地址的服务器则认为他们是直接连接客户端。

[ 本帖最后由 ysllyfe 于 2008-10-15 09:22 编辑 ]

论坛徽章:
0
发表于 2008-10-14 17:19 |显示全部楼层
支持。
您需要登录后才可以回帖 登录 | 注册

本版积分规则 发表回复

  

北京盛拓优讯信息技术有限公司. 版权所有 京ICP备16024965号-6 北京市公安局海淀分局网监中心备案编号:11010802020122 niuxiaotong@pcpop.com 17352615567
未成年举报专区
中国互联网协会会员  联系我们:huangweiwei@itpub.net
感谢所有关心和支持过ChinaUnix的朋友们 转载本站内容请注明原作者名及出处

清除 Cookies - ChinaUnix - Archiver - WAP - TOP