<?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: ACE Leastconn question in Application Networking</title>
    <link>https://community.cisco.com/t5/application-networking/ace-leastconn-question/m-p/1268604#M26344</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;Nope. I was trying to see what I can do about this, so I removed the leastconn (reverting back to round-robin) then configured leastconn back, but without slow-start parameter. What I immediately noticed is that servers started to be hit in a more equal manner, which is what I expected. I then reapplied the leastconn command, but with slow-start parameter and it would seem that session distribution was as expected. I assume that maybe removing and reapplying leastconn command did the trick, or maybe slow-start parameter was somehow misbehaving when I first applied it....&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now what I noticed is there are some sessions under failure column of "show serverfarm" output and I don't believe I had those before I switched to leastconn. The number is very low, like 5 failed versus 30,000 total, but still I was wondering if there is anything different with leastconn from round-robin that would cause some of the sessions to fail ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;P&gt;David&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 15 Jun 2009 17:28:55 GMT</pubDate>
    <dc:creator>dknov</dc:creator>
    <dc:date>2009-06-15T17:28:55Z</dc:date>
    <item>
      <title>ACE Leastconn question</title>
      <link>https://community.cisco.com/t5/application-networking/ace-leastconn-question/m-p/1268602#M26342</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I had just moved one server farm from round-robin to leastconns with slowstart of 300 second and no new rservers had been added (or failed), they are all the same as before the change.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What I see is that one rserver gets much more hits than other and one of them is practically idle. I know that CSCso93479 states that current connections count in "show serverfarm" is inaccurate, but I cannot understand such a difference....&lt;/P&gt;&lt;P&gt;Is total connections counter bugged as well?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;                                                ----------connections-----------&lt;/P&gt;&lt;P&gt;       real                  weight state        current    total      failures &lt;/P&gt;&lt;P&gt;   ---+---------------------+------+------------+----------+----------+---------&lt;/P&gt;&lt;P&gt;   rserver: prmesapp11&lt;/P&gt;&lt;P&gt;       10.16.127.17:0        8      OPERATIONAL  23         6          0&lt;/P&gt;&lt;P&gt;   rserver: prmesapp12&lt;/P&gt;&lt;P&gt;       10.16.127.18:0        8      OPERATIONAL  44         187        0&lt;/P&gt;&lt;P&gt;   rserver: prmesapp13&lt;/P&gt;&lt;P&gt;       10.16.127.19:0        8      OPERATIONAL  31         43         0&lt;/P&gt;&lt;P&gt;   rserver: prmesapp14&lt;/P&gt;&lt;P&gt;       10.16.127.20:0        8      OPERATIONAL  27         62         0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Or am i missing something about leastconns predictor?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks a lot!&lt;/P&gt;&lt;P&gt;David&lt;/P&gt;</description>
      <pubDate>Sun, 14 Jun 2009 16:40:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/ace-leastconn-question/m-p/1268602#M26342</guid>
      <dc:creator>dknov</dc:creator>
      <dc:date>2009-06-14T16:40:44Z</dc:date>
    </item>
    <item>
      <title>Re: ACE Leastconn question</title>
      <link>https://community.cisco.com/t5/application-networking/ace-leastconn-question/m-p/1268603#M26343</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;do you have stickyness ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;G.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 15 Jun 2009 10:24:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/ace-leastconn-question/m-p/1268603#M26343</guid>
      <dc:creator>Gilles Dufour</dc:creator>
      <dc:date>2009-06-15T10:24:54Z</dc:date>
    </item>
    <item>
      <title>Re: ACE Leastconn question</title>
      <link>https://community.cisco.com/t5/application-networking/ace-leastconn-question/m-p/1268604#M26344</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;Nope. I was trying to see what I can do about this, so I removed the leastconn (reverting back to round-robin) then configured leastconn back, but without slow-start parameter. What I immediately noticed is that servers started to be hit in a more equal manner, which is what I expected. I then reapplied the leastconn command, but with slow-start parameter and it would seem that session distribution was as expected. I assume that maybe removing and reapplying leastconn command did the trick, or maybe slow-start parameter was somehow misbehaving when I first applied it....&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now what I noticed is there are some sessions under failure column of "show serverfarm" output and I don't believe I had those before I switched to leastconn. The number is very low, like 5 failed versus 30,000 total, but still I was wondering if there is anything different with leastconn from round-robin that would cause some of the sessions to fail ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;P&gt;David&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 15 Jun 2009 17:28:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/ace-leastconn-question/m-p/1268604#M26344</guid>
      <dc:creator>dknov</dc:creator>
      <dc:date>2009-06-15T17:28:55Z</dc:date>
    </item>
    <item>
      <title>Re: ACE Leastconn question</title>
      <link>https://community.cisco.com/t5/application-networking/ace-leastconn-question/m-p/1268605#M26345</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;David,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;we have a few slowstart issue where the internal data structure could get corrupted preventing some servers to receive traffic.&lt;/P&gt;&lt;P&gt;You may have hit such a problem.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; CSCsx80991: ACE: Leastcon negative weight after adding new rservers&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Usually, removing/adding the predictor does fix the problem.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Next time you see the issue, you should open a service request to receive guidance on what information to collect.&lt;/P&gt;&lt;P&gt;The procedure is not as easy as show ....&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regarding the failure, it is independent of the predictor.&lt;/P&gt;&lt;P&gt;We count a failure when the connection can't be established.&lt;/P&gt;&lt;P&gt;Reset from server or no response.&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, 16 Jun 2009 13:16:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/ace-leastconn-question/m-p/1268605#M26345</guid>
      <dc:creator>Gilles Dufour</dc:creator>
      <dc:date>2009-06-16T13:16:15Z</dc:date>
    </item>
  </channel>
</rss>

