<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Automatic Server failover, not exactly load balancing using CSS? in Application Networking</title>
    <link>https://community.cisco.com/t5/application-networking/automatic-server-failover-not-exactly-load-balancing-using-css/m-p/341988#M5675</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have been investigating the use of the single CSS11501 box to satisfy a customers specific requirement for the following.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A sticky connection from a Winframe Cluster(client side) to a backend web servers via a VIP. The reason for the sticky connection to the backend server is that there are some additional servers providing services to two standalone backend web servers servicing the VIP. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Most of the traffic on the client side will be sourced from a limited set of ip addresses (or maybe even just one) representing many unique winframe sessions i.e.unique browser sessions. I believe this can be achieved by using Cookies. Is this correct and are there any other methods of achieving this?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;At the backend that VIP must use only the primary web server while it is active/available, but have the ability to failover automatically to a second server if the first one fails.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I believe this can be achieved by be using a script or keepalive type of HTTP in the service. My question is what load balancing method can be used to achieve this sort of Active/Standby (HSRP) like functionality on the CCS for attached Services(Servers)?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regan&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
    <pubDate>Thu, 27 Jan 2005 13:15:50 GMT</pubDate>
    <dc:creator>reganv</dc:creator>
    <dc:date>2005-01-27T13:15:50Z</dc:date>
    <item>
      <title>Automatic Server failover, not exactly load balancing using CSS?</title>
      <link>https://community.cisco.com/t5/application-networking/automatic-server-failover-not-exactly-load-balancing-using-css/m-p/341988#M5675</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have been investigating the use of the single CSS11501 box to satisfy a customers specific requirement for the following.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A sticky connection from a Winframe Cluster(client side) to a backend web servers via a VIP. The reason for the sticky connection to the backend server is that there are some additional servers providing services to two standalone backend web servers servicing the VIP. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Most of the traffic on the client side will be sourced from a limited set of ip addresses (or maybe even just one) representing many unique winframe sessions i.e.unique browser sessions. I believe this can be achieved by using Cookies. Is this correct and are there any other methods of achieving this?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;At the backend that VIP must use only the primary web server while it is active/available, but have the ability to failover automatically to a second server if the first one fails.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I believe this can be achieved by be using a script or keepalive type of HTTP in the service. My question is what load balancing method can be used to achieve this sort of Active/Standby (HSRP) like functionality on the CCS for attached Services(Servers)?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regan&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 27 Jan 2005 13:15:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/automatic-server-failover-not-exactly-load-balancing-using-css/m-p/341988#M5675</guid>
      <dc:creator>reganv</dc:creator>
      <dc:date>2005-01-27T13:15:50Z</dc:date>
    </item>
    <item>
      <title>Re: Automatic Server failover, not exactly load balancing using</title>
      <link>https://community.cisco.com/t5/application-networking/automatic-server-failover-not-exactly-load-balancing-using-css/m-p/341989#M5676</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Regan,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. cookie should be used for stickyness if ip addresses can't.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2. check the primary sorry server functionality.&lt;/P&gt;&lt;P&gt;This lets you configure normal servers [or just one] that will receive all the traffic and if they are all down, the sorry server will be used.&lt;/P&gt;&lt;P&gt;So in your case, the backup server will be defined as a sorry server.&lt;/P&gt;&lt;P&gt;The command you need is primary sorryserver under the content rule definition.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Gilles.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 27 Jan 2005 13:31:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/automatic-server-failover-not-exactly-load-balancing-using-css/m-p/341989#M5676</guid>
      <dc:creator>Gilles Dufour</dc:creator>
      <dc:date>2005-01-27T13:31:47Z</dc:date>
    </item>
    <item>
      <title>Re: Automatic Server failover, not exactly load balancing using</title>
      <link>https://community.cisco.com/t5/application-networking/automatic-server-failover-not-exactly-load-balancing-using-css/m-p/341990#M5677</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Gilles,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Many thanks...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Regan&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 27 Jan 2005 14:47:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/automatic-server-failover-not-exactly-load-balancing-using-css/m-p/341990#M5677</guid>
      <dc:creator>reganv</dc:creator>
      <dc:date>2005-01-27T14:47:52Z</dc:date>
    </item>
  </channel>
</rss>

