<?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: CSS - VRRP with Fate sharing in Application Networking</title>
    <link>https://community.cisco.com/t5/application-networking/css-vrrp-with-fate-sharing/m-p/680281#M12921</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;this is done with the 'ip critical-service' command inside the circuit definition.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/products/hw/contnetw/ps792/products_configuration_guide_chapter09186a0080157898.html" target="_blank"&gt;http://www.cisco.com/en/US/products/hw/contnetw/ps792/products_configuration_guide_chapter09186a0080157898.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can create a service with a scripted keepalive that monitor the vip, or you can monitor the services that are defined under the content rule and when they are all down, it means the vip will also be down, and then failover.&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, 10 Oct 2006 09:05:06 GMT</pubDate>
    <dc:creator>Gilles Dufour</dc:creator>
    <dc:date>2006-10-10T09:05:06Z</dc:date>
    <item>
      <title>CSS - VRRP with Fate sharing</title>
      <link>https://community.cisco.com/t5/application-networking/css-vrrp-with-fate-sharing/m-p/680280#M12920</link>
      <description>&lt;P&gt;Hi giles,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am having a setup with 2*CSS 11506 and planing to deploy VRRP in fate sharing model.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is it possible to flip the backup role to master when one of the active content VIP is down on the Master CSS while the same content is active on backup.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance !!!&lt;/P&gt;</description>
      <pubDate>Tue, 10 Oct 2006 06:19:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/css-vrrp-with-fate-sharing/m-p/680280#M12920</guid>
      <dc:creator>Keong.leow</dc:creator>
      <dc:date>2006-10-10T06:19:18Z</dc:date>
    </item>
    <item>
      <title>Re: CSS - VRRP with Fate sharing</title>
      <link>https://community.cisco.com/t5/application-networking/css-vrrp-with-fate-sharing/m-p/680281#M12921</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;this is done with the 'ip critical-service' command inside the circuit definition.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/products/hw/contnetw/ps792/products_configuration_guide_chapter09186a0080157898.html" target="_blank"&gt;http://www.cisco.com/en/US/products/hw/contnetw/ps792/products_configuration_guide_chapter09186a0080157898.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can create a service with a scripted keepalive that monitor the vip, or you can monitor the services that are defined under the content rule and when they are all down, it means the vip will also be down, and then failover.&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, 10 Oct 2006 09:05:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/css-vrrp-with-fate-sharing/m-p/680281#M12921</guid>
      <dc:creator>Gilles Dufour</dc:creator>
      <dc:date>2006-10-10T09:05:06Z</dc:date>
    </item>
  </channel>
</rss>

