<?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 Re: CSM persistent function in Application Networking</title>
    <link>https://community.cisco.com/t5/application-networking/csm-persistent-function/m-p/229347#M3214</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;persistent is only for http1.1 traffic where inside a single TCP connection a client can send multiple GET.&lt;/P&gt;&lt;P&gt;If you need to loadbalance each GET separately, you need the command 'persistent rebalance'.&lt;/P&gt;&lt;P&gt;Otherwise, the first GET will determin the server and all subsequent GET in this same TCP connection will go to the same server.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Stickyness is for multiple TCP connections.&lt;/P&gt;&lt;P&gt;If you want to guarantee that each new tcp connection goes to the same server, you need some sort of stickyness - like sticky source ip.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you configure stickyness it usually means you want all connections/GET to go to the same server, so you would not configure 'persistent rebalance' and sticky  at the same time.&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>Wed, 09 Jun 2004 07:01:32 GMT</pubDate>
    <dc:creator>Gilles Dufour</dc:creator>
    <dc:date>2004-06-09T07:01:32Z</dc:date>
    <item>
      <title>CSM persistent function</title>
      <link>https://community.cisco.com/t5/application-networking/csm-persistent-function/m-p/229346#M3213</link>
      <description>&lt;P&gt;I'm confused with "persistent" and sticky.Can I only use enable persistent feature to stick client's connection to a particular server?&lt;/P&gt;</description>
      <pubDate>Wed, 09 Jun 2004 00:15:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/csm-persistent-function/m-p/229346#M3213</guid>
      <dc:creator>yueric</dc:creator>
      <dc:date>2004-06-09T00:15:40Z</dc:date>
    </item>
    <item>
      <title>Re: CSM persistent function</title>
      <link>https://community.cisco.com/t5/application-networking/csm-persistent-function/m-p/229347#M3214</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;persistent is only for http1.1 traffic where inside a single TCP connection a client can send multiple GET.&lt;/P&gt;&lt;P&gt;If you need to loadbalance each GET separately, you need the command 'persistent rebalance'.&lt;/P&gt;&lt;P&gt;Otherwise, the first GET will determin the server and all subsequent GET in this same TCP connection will go to the same server.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Stickyness is for multiple TCP connections.&lt;/P&gt;&lt;P&gt;If you want to guarantee that each new tcp connection goes to the same server, you need some sort of stickyness - like sticky source ip.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you configure stickyness it usually means you want all connections/GET to go to the same server, so you would not configure 'persistent rebalance' and sticky  at the same time.&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>Wed, 09 Jun 2004 07:01:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/csm-persistent-function/m-p/229347#M3214</guid>
      <dc:creator>Gilles Dufour</dc:creator>
      <dc:date>2004-06-09T07:01:32Z</dc:date>
    </item>
  </channel>
</rss>

