<?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 Hash cookie predictor with ACE Cookie insert in Application Networking</title>
    <link>https://community.cisco.com/t5/application-networking/hash-cookie-predictor-with-ace-cookie-insert/m-p/1755662#M34985</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Even I used the same way ( pedictor as hash cookie and stickiness based on http cookie insertion)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;for me too load balancing works perfectly fine.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;now i am also amazed to see the reply....&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So in this way , predictor is never invoked ?... in that case how is it equally load balancing ...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks,&lt;/P&gt;&lt;P&gt;Parvees&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 18 Aug 2011 03:09:36 GMT</pubDate>
    <dc:creator>parveesm123</dc:creator>
    <dc:date>2011-08-18T03:09:36Z</dc:date>
    <item>
      <title>Hash cookie predictor with ACE Cookie insert</title>
      <link>https://community.cisco.com/t5/application-networking/hash-cookie-predictor-with-ace-cookie-insert/m-p/1755657#M34980</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have implemented the config with ACE Cookie Persistance and in serverfarm we used hash cookie &amp;lt;ACE Cookie&amp;gt;. We see equal load balanincg when we do load genrator test.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But will it create any other issue and is this advisable?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Config:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;serverfarm host SF-S1WBCT-WLS-S11916&lt;/P&gt;&lt;P&gt;predictor hash cookie ACE-COOKIE-EVEREST-STG &lt;/P&gt;&lt;P&gt;&amp;nbsp; rserver RS-S1WBCT-WLS-10.102.161.251-S 11916&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; probe PR-S1WBCT-WLS-S11916&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; inservice&lt;/P&gt;&lt;P&gt;&amp;nbsp; rserver RS-S1WBCT-WLS-10.102.162.11-S 11916&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; probe PR-S1WBCT-WLS-S11916&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; inservice&lt;/P&gt;&lt;P&gt;&amp;nbsp; rserver RS-S1WBCT-WLS-10.102.162.12-S 11916&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; probe PR-S1WBCT-WLS-S11916&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; inservice&lt;/P&gt;&lt;P&gt;&amp;nbsp; rserver RS-S1WBCT-WLS-10.102.162.13-S 11916&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; probe PR-S1WBCT-WLS-S11916&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; inservice&lt;/P&gt;&lt;P&gt;&amp;nbsp; rserver RS-S1WBCT-WLS-10.102.162.14-S 11916&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; probe PR-S1WBCT-WLS-S11916&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; inservice&lt;/P&gt;&lt;P&gt;&amp;nbsp; rserver RS-S1WBCT-WLS-10.102.162.15-S 11916&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; probe PR-S1WBCT-WLS-S11916&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; inservice&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;sticky http-cookie ACE-COOKIE-EVEREST-STG SG-S1WBCT-WLS-S11916&lt;/P&gt;&lt;P&gt;&amp;nbsp; cookie insert browser-expire&lt;/P&gt;&lt;P&gt;&amp;nbsp; timeout 15&lt;/P&gt;&lt;P&gt;&amp;nbsp; replicate sticky&lt;/P&gt;&lt;P&gt;&amp;nbsp; serverfarm SF-S1WBCT-WLS-S11916&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;policy-map type loadbalance first-match LB-S1WBCT-WLS-S11916&lt;/P&gt;&lt;P&gt;&amp;nbsp; class class-default&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; sticky-serverfarm SG-S1WBCT-WLS-S11916&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;policy-map multi-match GP-SUBPROD-01-VIP&lt;/P&gt;&lt;P&gt;class VC-S1WBCT-WLS-S11916&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; loadbalance vip inservice&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; loadbalance policy LB-S1WBCT-WLS-S11916&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; loadbalance vip icmp-reply active&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; nat dynamic 150 vlan 202&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; connection advanced-options TCP_PARAM_MAP&lt;/P&gt;&lt;P&gt;appl-parameter http advanced-options http_parameter_map&lt;/P&gt;</description>
      <pubDate>Wed, 17 Aug 2011 02:19:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/hash-cookie-predictor-with-ace-cookie-insert/m-p/1755657#M34980</guid>
      <dc:creator>Yahshanulla S</dc:creator>
      <dc:date>2011-08-17T02:19:19Z</dc:date>
    </item>
    <item>
      <title>Hash cookie predictor with ACE Cookie insert</title>
      <link>https://community.cisco.com/t5/application-networking/hash-cookie-predictor-with-ace-cookie-insert/m-p/1755658#M34981</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Why do you need hash predictor with cookie insertion?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The predictor algorithm will only be used in case an http request doesn't have the ACE-COOKIE-EVEREST-STG cookie. So the predictor won't find any data to hash…&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;--Olivier&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 17 Aug 2011 08:50:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/hash-cookie-predictor-with-ace-cookie-insert/m-p/1755658#M34981</guid>
      <dc:creator>ohynderi</dc:creator>
      <dc:date>2011-08-17T08:50:59Z</dc:date>
    </item>
    <item>
      <title>Hash cookie predictor with ACE Cookie insert</title>
      <link>https://community.cisco.com/t5/application-networking/hash-cookie-predictor-with-ace-cookie-insert/m-p/1755659#M34982</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for reply.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You are correct. First HTTP request will not have any ACE Cookie , so i assume it will go to new available server. isnt it? The reason we used is, With this predictor only we are seeing Equal load balancing with 6 servers. Other Predictors Least Conns, Round Robin giving Unqual Load balancing and some of the users never been used.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So Please advise How Hash Cookie Predictor works here and how its giving good equal load balancing?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 17 Aug 2011 11:32:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/hash-cookie-predictor-with-ace-cookie-insert/m-p/1755659#M34982</guid>
      <dc:creator>Yahshanulla S</dc:creator>
      <dc:date>2011-08-17T11:32:40Z</dc:date>
    </item>
    <item>
      <title>Re: Hash cookie predictor with ACE Cookie insert</title>
      <link>https://community.cisco.com/t5/application-networking/hash-cookie-predictor-with-ace-cookie-insert/m-p/1755660#M34983</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If an http request doesn't contain the expected cookie, ACE should do round robin. In that case, the server weight won't be taken into account.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You should try the following:&lt;/P&gt;&lt;P&gt;1/ configured round robin with cookie insertion&lt;/P&gt;&lt;P&gt;2/ clear the stats (clear serverfarm &lt;SF&gt;)&lt;/SF&gt;&lt;/P&gt;&lt;P&gt;3/ genereat x requests&lt;/P&gt;&lt;P&gt;4/ check the serverfarm stats&lt;/P&gt;&lt;P&gt;5/ same steps with leastconn and hash predictor&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Small q, does your traffic generator actually learn cookies?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Olivier&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 17 Aug 2011 14:13:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/hash-cookie-predictor-with-ace-cookie-insert/m-p/1755660#M34983</guid>
      <dc:creator>ohynderi</dc:creator>
      <dc:date>2011-08-17T14:13:48Z</dc:date>
    </item>
    <item>
      <title>Hash cookie predictor with ACE Cookie insert</title>
      <link>https://community.cisco.com/t5/application-networking/hash-cookie-predictor-with-ace-cookie-insert/m-p/1755661#M34984</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;SO even if we have HASH COOKIE predictor in this case ACE will do round robin when it see no cookie in header right? Nothing will get dropp of from ACE i hope.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We tried with round robin and cookie insertion, Least connection&amp;nbsp; and hash predictor. Only Hash predictor gives good load balancing results.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I will ask Load ganarators about cookie clear option.&amp;nbsp; Do you see any difficulties of having HASH COOKIE predictor&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 17 Aug 2011 16:21:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/hash-cookie-predictor-with-ace-cookie-insert/m-p/1755661#M34984</guid>
      <dc:creator>Yahshanulla S</dc:creator>
      <dc:date>2011-08-17T16:21:13Z</dc:date>
    </item>
    <item>
      <title>Hash cookie predictor with ACE Cookie insert</title>
      <link>https://community.cisco.com/t5/application-networking/hash-cookie-predictor-with-ace-cookie-insert/m-p/1755662#M34985</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Even I used the same way ( pedictor as hash cookie and stickiness based on http cookie insertion)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;for me too load balancing works perfectly fine.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;now i am also amazed to see the reply....&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So in this way , predictor is never invoked ?... in that case how is it equally load balancing ...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks,&lt;/P&gt;&lt;P&gt;Parvees&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 18 Aug 2011 03:09:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/hash-cookie-predictor-with-ace-cookie-insert/m-p/1755662#M34985</guid>
      <dc:creator>parveesm123</dc:creator>
      <dc:date>2011-08-18T03:09:36Z</dc:date>
    </item>
    <item>
      <title>Re: Hash cookie predictor with ACE Cookie insert</title>
      <link>https://community.cisco.com/t5/application-networking/hash-cookie-predictor-with-ace-cookie-insert/m-p/1755663#M34986</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Your understanding is correct, in case a request doesn't contain the cookie name configured in the predictor, request won't be dropped. The round robin algorithm will be used instead.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The fact the hash cookie give better result that round robin is quite strange to me. I would recommend you to confirm this and open a TAC SR if this turns out to be indeed the case.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Parvees, with cookie insertion, the predictor is used to load balance requests that don't have the cookie. If a request contain the cookie, it is simply forwarded according to the sticky db.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;--Olivier&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 18 Aug 2011 12:17:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/hash-cookie-predictor-with-ace-cookie-insert/m-p/1755663#M34986</guid>
      <dc:creator>ohynderi</dc:creator>
      <dc:date>2011-08-18T12:17:11Z</dc:date>
    </item>
  </channel>
</rss>

