<?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 CSM and proxy stickyness in Application Networking</title>
    <link>https://community.cisco.com/t5/application-networking/csm-and-proxy-stickyness/m-p/165364#M2016</link>
    <description>&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;    let me explain my testbed:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- 16 frontend proxy servers&lt;/P&gt;&lt;P&gt;- 72 backend application servers (AS)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;requests to the proxy servers are first balanced from a couple of css; after that the new request originating from the proxy is balanced between the 72 backend AS from a couple of CSM.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I instructed the proxy to populate the X-Forwarded-For header field so that the CSM can still see the client IP in the header.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;How can I configure some sort of stickyness on the CSM to meet these requirements:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1) the 72 AS are equally loaded;&lt;/P&gt;&lt;P&gt;2) Request from the same client are directed to the same AS;&lt;/P&gt;&lt;P&gt;&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;Fausto Franceschini&lt;/P&gt;</description>
    <pubDate>Fri, 18 Jul 2003 08:25:59 GMT</pubDate>
    <dc:creator>f.franceschini</dc:creator>
    <dc:date>2003-07-18T08:25:59Z</dc:date>
    <item>
      <title>CSM and proxy stickyness</title>
      <link>https://community.cisco.com/t5/application-networking/csm-and-proxy-stickyness/m-p/165364#M2016</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;    let me explain my testbed:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- 16 frontend proxy servers&lt;/P&gt;&lt;P&gt;- 72 backend application servers (AS)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;requests to the proxy servers are first balanced from a couple of css; after that the new request originating from the proxy is balanced between the 72 backend AS from a couple of CSM.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I instructed the proxy to populate the X-Forwarded-For header field so that the CSM can still see the client IP in the header.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;How can I configure some sort of stickyness on the CSM to meet these requirements:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1) the 72 AS are equally loaded;&lt;/P&gt;&lt;P&gt;2) Request from the same client are directed to the same AS;&lt;/P&gt;&lt;P&gt;&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;Fausto Franceschini&lt;/P&gt;</description>
      <pubDate>Fri, 18 Jul 2003 08:25:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/csm-and-proxy-stickyness/m-p/165364#M2016</guid>
      <dc:creator>f.franceschini</dc:creator>
      <dc:date>2003-07-18T08:25:59Z</dc:date>
    </item>
    <item>
      <title>Re: CSM and proxy stickyness</title>
      <link>https://community.cisco.com/t5/application-networking/csm-and-proxy-stickyness/m-p/165365#M2017</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;unfortunately, this is not possible.&lt;/P&gt;&lt;P&gt;First reason is that the header match function, can't match a X-forward header currently.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What I would suggest is do cookie sticky if your servers can generate a cookie or use the 'cookie insert' feature of the csm (the command is 'sticky 1 cookie &lt;NAME&gt; insert'&lt;/NAME&gt;&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>Sun, 20 Jul 2003 09:02:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/csm-and-proxy-stickyness/m-p/165365#M2017</guid>
      <dc:creator>Gilles Dufour</dc:creator>
      <dc:date>2003-07-20T09:02:38Z</dc:date>
    </item>
    <item>
      <title>Re: CSM and proxy stickyness</title>
      <link>https://community.cisco.com/t5/application-networking/csm-and-proxy-stickyness/m-p/165366#M2018</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Sorry.&lt;/P&gt;&lt;P&gt;I need to correct what I said.&lt;/P&gt;&lt;P&gt;You can stick on any header field with the command&lt;/P&gt;&lt;P&gt;'sticy &amp;lt;1-255&amp;gt; header &lt;HEADER_FIELD_NAME&gt;'&lt;/HEADER_FIELD_NAME&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Gilles.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 21 Jul 2003 07:05:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/csm-and-proxy-stickyness/m-p/165366#M2018</guid>
      <dc:creator>Gilles Dufour</dc:creator>
      <dc:date>2003-07-21T07:05:41Z</dc:date>
    </item>
    <item>
      <title>Re: CSM and proxy stickyness</title>
      <link>https://community.cisco.com/t5/application-networking/csm-and-proxy-stickyness/m-p/165367#M2019</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks Gilles,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;   I'll try this configuration as soon as possible.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Fausto&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 21 Jul 2003 10:15:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/csm-and-proxy-stickyness/m-p/165367#M2019</guid>
      <dc:creator>f.franceschini</dc:creator>
      <dc:date>2003-07-21T10:15:25Z</dc:date>
    </item>
    <item>
      <title>Re: CSM and proxy stickyness</title>
      <link>https://community.cisco.com/t5/application-networking/csm-and-proxy-stickyness/m-p/165368#M2020</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Is there something similiar on the CSS as well?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Fausto&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 21 Jul 2003 10:18:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/csm-and-proxy-stickyness/m-p/165368#M2020</guid>
      <dc:creator>f.franceschini</dc:creator>
      <dc:date>2003-07-21T10:18:24Z</dc:date>
    </item>
    <item>
      <title>Re: CSM and proxy stickyness</title>
      <link>https://community.cisco.com/t5/application-networking/csm-and-proxy-stickyness/m-p/165369#M2021</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;this for sure, the answer is NO.&lt;/P&gt;&lt;P&gt;Same workaround as I gave you earlier with cookie.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Gilles.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 21 Jul 2003 13:18:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/csm-and-proxy-stickyness/m-p/165369#M2021</guid>
      <dc:creator>Gilles Dufour</dc:creator>
      <dc:date>2003-07-21T13:18:23Z</dc:date>
    </item>
    <item>
      <title>Re: CSM and proxy stickyness</title>
      <link>https://community.cisco.com/t5/application-networking/csm-and-proxy-stickyness/m-p/165370#M2022</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Fausto,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;sorry for this, but I was in touch with our developper about the command I gave you and unfortunately I have to say that the command is there, but the code not &lt;span class="lia-unicode-emoji" title=":disappointed_face:"&gt;😞&lt;/span&gt;&lt;/P&gt;&lt;P&gt;It means the command is useless.&lt;/P&gt;&lt;P&gt;This command will only work starting with version 3.3&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Gilles.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 22 Jul 2003 14:32:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/csm-and-proxy-stickyness/m-p/165370#M2022</guid>
      <dc:creator>Gilles Dufour</dc:creator>
      <dc:date>2003-07-22T14:32:58Z</dc:date>
    </item>
    <item>
      <title>Re: CSM and proxy stickyness</title>
      <link>https://community.cisco.com/t5/application-networking/csm-and-proxy-stickyness/m-p/165371#M2023</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Gilles,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;    do you know when release 3.3 will be available?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Fausto&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 23 Jul 2003 07:09:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/csm-and-proxy-stickyness/m-p/165371#M2023</guid>
      <dc:creator>f.franceschini</dc:creator>
      <dc:date>2003-07-23T07:09:42Z</dc:date>
    </item>
    <item>
      <title>Re: CSM and proxy stickyness</title>
      <link>https://community.cisco.com/t5/application-networking/csm-and-proxy-stickyness/m-p/165372#M2024</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;6 to 12 months I would say.&lt;/P&gt;&lt;P&gt;3.2 is just coming out now.&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, 23 Jul 2003 08:35:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/csm-and-proxy-stickyness/m-p/165372#M2024</guid>
      <dc:creator>Gilles Dufour</dc:creator>
      <dc:date>2003-07-23T08:35:35Z</dc:date>
    </item>
  </channel>
</rss>

