Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
SDN 101: An Introduction to Software Defined Networking
Discover the advantages of SDN.
SDN has quickly become one of the hottest trends in IT. But not all SDN solutions offer real software-defined functionality. As more enterprises consider SDN, they want to know, “What is SDN? And what are the real benefits?” If you're ready to explore the advantages of SDN, and want to know how it should be implemented within your enterprise, start by reading our introductory white paper.
Click Here to receive this Complete Guide absolutely free.
stick on src
stick-table type ip size 10240k expire 240m
option httpchk HEAD / HTTP/1.0
server cas1 10.200.1.32 check port 443 check-ssl inter 5000 rise 2 fall 2
server cas2 10.200.1.42 check port 443 check-ssl inter 5000 rise 2 fall 2
stick-table type ip size 10240k expire 60m
stick on src
server cas1 10.200.1.42 weight 1 check port 110 inter 2000 rise 2 fall 3 on-marked-down shutdown-sessions
server ht1 10.200.1.33 check port 25 inter 5000 rise 2 fall 2
server ht2 10.200.1.43 check port 25 inter 5000 rise 2 fall 2
I have 2 backend servers running Exchange OWA. connection speed is excellent if 10.200.1.32 is up. If it is down, traffic will point to 10.200.1.42 and it will start to crawl. OWA will be VERY slow, Outlook(connect using outlook anywhere technology, which is also dependent on 443) will also take forever to connect.
But, I if nat the public ip directly to 10.200.1.42(meaning without going through haproxy), OWA and Outlook can load very fast!.
Question is :
why 10.200.1.32 is fast and why 10.200.1.42 is slow? something wrong with my haproxy config? and why there is not problem if i NAT directly to 10.200.1.42
Thanks in advance.
Last edited by binary_0011; 01-31-2013 at 11:01 PM.