<?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 Two GSS with Hash in Application Networking</title>
    <link>https://community.cisco.com/t5/application-networking/two-gss-with-hash/m-p/1838793#M36136</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Joao,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The hash algorithm is the same on all GSS, so, assuming all the answers are operational, the results returned by both GSS should be the same. However, be aware because once answers start going up and down, this may no longer be the case. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you really want to ensure that both GSS retrun the same answer, then, you should configure DNS stickiness instead. In the end, that's what this feature was designed for &lt;SPAN __jive_emoticon_name="wink" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.cisco.com/4.5.4/images/tiny_mce3/plugins/jiveemoticons/images/spacer.gif"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For more details, please check the link below:&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://www.cisco.com/en/US/docs/app_ntwk_services/data_center_app_services/gss4400series/v4.1.1/configuration/gui/gslb/guide/Sticky.html"&gt;http://www.cisco.com/en/US/docs/app_ntwk_services/data_center_app_services/gss4400series/v4.1.1/configuration/gui/gslb/guide/Sticky.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I hope this helps&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Danie&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 17 Feb 2012 15:31:36 GMT</pubDate>
    <dc:creator>Daniel Arrondo Ostiz</dc:creator>
    <dc:date>2012-02-17T15:31:36Z</dc:date>
    <item>
      <title>Two GSS with Hash</title>
      <link>https://community.cisco.com/t5/application-networking/two-gss-with-hash/m-p/1838792#M36135</link>
      <description>&lt;P&gt;Hello.&lt;/P&gt;&lt;P&gt;I want to set up a cluster of two GSS in different Data Center.&lt;/P&gt;&lt;P&gt;If I use the hash method as loadbalance method does both GSS take the same decision? If I have only one GSS I can use hash to perform stickyness; my concern is if one GSS goes down does the other reply with the same answers.&lt;/P&gt;&lt;P&gt;Best ragards,&lt;/P&gt;&lt;P&gt;Joao.&lt;/P&gt;</description>
      <pubDate>Fri, 17 Feb 2012 12:16:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/two-gss-with-hash/m-p/1838792#M36135</guid>
      <dc:creator>jcarvalh</dc:creator>
      <dc:date>2012-02-17T12:16:43Z</dc:date>
    </item>
    <item>
      <title>Two GSS with Hash</title>
      <link>https://community.cisco.com/t5/application-networking/two-gss-with-hash/m-p/1838793#M36136</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Joao,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The hash algorithm is the same on all GSS, so, assuming all the answers are operational, the results returned by both GSS should be the same. However, be aware because once answers start going up and down, this may no longer be the case. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you really want to ensure that both GSS retrun the same answer, then, you should configure DNS stickiness instead. In the end, that's what this feature was designed for &lt;SPAN __jive_emoticon_name="wink" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.cisco.com/4.5.4/images/tiny_mce3/plugins/jiveemoticons/images/spacer.gif"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For more details, please check the link below:&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://www.cisco.com/en/US/docs/app_ntwk_services/data_center_app_services/gss4400series/v4.1.1/configuration/gui/gslb/guide/Sticky.html"&gt;http://www.cisco.com/en/US/docs/app_ntwk_services/data_center_app_services/gss4400series/v4.1.1/configuration/gui/gslb/guide/Sticky.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I hope this helps&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Danie&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 17 Feb 2012 15:31:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/two-gss-with-hash/m-p/1838793#M36136</guid>
      <dc:creator>Daniel Arrondo Ostiz</dc:creator>
      <dc:date>2012-02-17T15:31:36Z</dc:date>
    </item>
    <item>
      <title>Two GSS with Hash</title>
      <link>https://community.cisco.com/t5/application-networking/two-gss-with-hash/m-p/1838794#M36137</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Daniel.&lt;/P&gt;&lt;P&gt;Thanks for your reply.&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Joao.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 22 Feb 2012 16:23:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/two-gss-with-hash/m-p/1838794#M36137</guid>
      <dc:creator>jcarvalh</dc:creator>
      <dc:date>2012-02-22T16:23:58Z</dc:date>
    </item>
  </channel>
</rss>

