• Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
  • Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!
Collapse

You are not logged in or you do not have permission to access this page. This could be due to one of several reasons:

  • You are not logged in. If you are already registered, fill in the form below to log in, or follow the "Sign Up" link to register a new account.
  • You may not have sufficient privileges to access this page. Are you trying to edit someone else's post, access administrative features or some other privileged system?
  • If you are trying to post, the administrator may have disabled your account, or it may be awaiting activation.

Previously on "CISCO load balancer setup"

Collapse

  • monkeyboy
    replied
    With the CSS you can within the content rule not supply a port so it will be valid for all ports and use source ip sticky. If behind a firewall not a real problem. This does present the problem of health checks as you can only supply the 2 real servers once.

    Unfortunately there is no way to link these rules together.

    Setting the servers to dish out cookies is the prefered method. This allows the content rule to take advantage of the advanced-balance methods of cookies and cookies-URL. (Cookies-URL will first look in the Hyper-Text Transfer Protocol (HTTP) GET of the packet for the cookie. If it does not find it there, it will look for it in the URL after a question mark.) Some customers are unaware of how to do this or do not have access to the servers to configure this.

    SSL is used explicitly for encrypted traffic. It uses a different port than HTTP, and should be considered a different protocol. It is only mentioned in this document because it is a form of sticky.


    This means that you can't link the http session to the https session except when doing the above.

    Leave a comment:


  • PropertyCrashUK
    replied
    IMPO Cisco manuals are pretty poor - here speaks a man who was with them for several years.

    I personally find the Syngress book range on Cisco products to be good - perhaps you should consider them?

    Leave a comment:


  • threaded
    replied
    Would arrowpoint-cookies help me in this quest?

    Leave a comment:


  • threaded
    replied
    Still stuck, I can make it sticky for 80 and 443, but I want any particular client to got back to the same webserver for both 80 and 443.

    this is what I have:

    content web-servers
    vip address xxx.xxx.xxx.xxx
    add service www-server1
    add service www-server2
    protocol tcp
    port 80
    advanced-balance sticky-srcip
    sticky-inact-timeout 60
    active

    content web-servers-https
    vip address xxx.xxx.xxx.xxx
    add service www-server1
    add service www-server2
    protocol tcp
    port 443
    advanced-balance sticky-srcip
    sticky-inact-timeout 60
    active

    Leave a comment:


  • threaded
    replied
    Thanks for that.

    Leave a comment:


  • Viktor
    replied
    http://www.cisco.com/univercd/home/home.htm

    hope this helps...

    Leave a comment:


  • threaded
    started a topic CISCO load balancer setup

    CISCO load balancer setup

    I have this Cisco CSS11501 and I want it to do 'round-robin sticky on client ip' to a set of web-servers serving pages with a mix of both HTTP and HTTPS.

    What do I do? Alternatively point me at a manual.
Working...
X