<?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: Source IP stickyness question in Application Networking</title>
    <link>https://community.cisco.com/t5/application-networking/source-ip-stickyness-question/m-p/1197318#M24792</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I think this can be best explained using an example.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;3 hosts connect to your VIP address:&lt;/P&gt;&lt;P&gt;host1 - 192.168.0.5&lt;/P&gt;&lt;P&gt;host2 - 192.168.0.200&lt;/P&gt;&lt;P&gt;host3 - 172.16.0.20&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;imagine you use source sticky with a netmask of 255.255.255.0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;host1 connects to the VIP and a check for is done if he already exists in the sticky table. this is not the case so the predictor is used to balance. he goes to server 1, and a sticky entry is added to the sticky database (I don't know the way this is done internally, but the result will be that any host with source address 192.168.0.0/24 (&amp;lt;-- netmask) is sticked to server1.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Host 2 arrives and the same process is done; a lookup in the sticky database results in a match, because host1 its source matches 192.168.0.0/24, and he is also send to server1.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Host3 does the same thing, again a lookup in the sticky database, no entry found, balance using predictor, send to server2 and added to sticky database.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Imagine if we used a netmask of 255.255.255.128, in this case host1 and host2 would not match each other and would be balanced individually.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Concerning the predictor, this is only used when no sticky entry exists for a certain connection. I think it is the same question you can pose yourself when you need to choose a predictor with or without stickyness.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH,&lt;/P&gt;&lt;P&gt;Dario&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 28 Apr 2009 11:58:52 GMT</pubDate>
    <dc:creator>dario.didio</dc:creator>
    <dc:date>2009-04-28T11:58:52Z</dc:date>
    <item>
      <title>Source IP stickyness question</title>
      <link>https://community.cisco.com/t5/application-networking/source-ip-stickyness-question/m-p/1197317#M24791</link>
      <description>&lt;P&gt;In the parameters to be set for stickyness based on IP, there is a mask to be configured.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can someone explain the behaviour of changing the length of this mask, say 255.255.255.0 versus 255.255.255.128 or any other permutation.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also, I would like to understand the link with the predictor.  How does the 2 really react and is there some permutation that work best with source IP stickyness.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks &lt;/P&gt;</description>
      <pubDate>Tue, 28 Apr 2009 11:30:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/source-ip-stickyness-question/m-p/1197317#M24791</guid>
      <dc:creator>quesne02</dc:creator>
      <dc:date>2009-04-28T11:30:35Z</dc:date>
    </item>
    <item>
      <title>Re: Source IP stickyness question</title>
      <link>https://community.cisco.com/t5/application-networking/source-ip-stickyness-question/m-p/1197318#M24792</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I think this can be best explained using an example.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;3 hosts connect to your VIP address:&lt;/P&gt;&lt;P&gt;host1 - 192.168.0.5&lt;/P&gt;&lt;P&gt;host2 - 192.168.0.200&lt;/P&gt;&lt;P&gt;host3 - 172.16.0.20&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;imagine you use source sticky with a netmask of 255.255.255.0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;host1 connects to the VIP and a check for is done if he already exists in the sticky table. this is not the case so the predictor is used to balance. he goes to server 1, and a sticky entry is added to the sticky database (I don't know the way this is done internally, but the result will be that any host with source address 192.168.0.0/24 (&amp;lt;-- netmask) is sticked to server1.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Host 2 arrives and the same process is done; a lookup in the sticky database results in a match, because host1 its source matches 192.168.0.0/24, and he is also send to server1.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Host3 does the same thing, again a lookup in the sticky database, no entry found, balance using predictor, send to server2 and added to sticky database.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Imagine if we used a netmask of 255.255.255.128, in this case host1 and host2 would not match each other and would be balanced individually.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Concerning the predictor, this is only used when no sticky entry exists for a certain connection. I think it is the same question you can pose yourself when you need to choose a predictor with or without stickyness.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH,&lt;/P&gt;&lt;P&gt;Dario&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 28 Apr 2009 11:58:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/source-ip-stickyness-question/m-p/1197318#M24792</guid>
      <dc:creator>dario.didio</dc:creator>
      <dc:date>2009-04-28T11:58:52Z</dc:date>
    </item>
    <item>
      <title>Re: Source IP stickyness question</title>
      <link>https://community.cisco.com/t5/application-networking/source-ip-stickyness-question/m-p/1197319#M24793</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;So the mask really applies close to a subnet mask to the incoming client coming in.   &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;All clients within this mask will go to the same server based on internal calculation.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I now also understand the relationship with the predictor.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 28 Apr 2009 12:05:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/source-ip-stickyness-question/m-p/1197319#M24793</guid>
      <dc:creator>quesne02</dc:creator>
      <dc:date>2009-04-28T12:05:15Z</dc:date>
    </item>
  </channel>
</rss>

