<?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: Failover to other service on same CSS in Application Networking</title>
    <link>https://community.cisco.com/t5/application-networking/failover-to-other-service-on-same-css/m-p/244914#M3516</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Carl,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can use the primary sorry server command. When the service(s) dies, the primary sorry server takes all the connections.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here is the command.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;primarySorryServer server11 &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you want, you can go through this link.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/univercd/cc/td/doc/product/webscale/css/css_720/bsccfggd/contrule.htm#1038009" target="_blank"&gt;http://www.cisco.com/univercd/cc/td/doc/product/webscale/css/css_720/bsccfggd/contrule.htm#1038009&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Sagar&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 14 Jun 2004 16:22:23 GMT</pubDate>
    <dc:creator>sagdas</dc:creator>
    <dc:date>2004-06-14T16:22:23Z</dc:date>
    <item>
      <title>Failover to other service on same CSS</title>
      <link>https://community.cisco.com/t5/application-networking/failover-to-other-service-on-same-css/m-p/244913#M3515</link>
      <description>&lt;P&gt;Is it possible to have one service receive 100% of traffic and use a second service as failover on a single CSS using CSS's already configured in Active-Standby modes.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Typically we have duplicate services on separate CSS's, but now our Systems engineering group want to know if we can do it this way.&lt;/P&gt;</description>
      <pubDate>Mon, 14 Jun 2004 12:50:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/failover-to-other-service-on-same-css/m-p/244913#M3515</guid>
      <dc:creator>Carl King</dc:creator>
      <dc:date>2004-06-14T12:50:06Z</dc:date>
    </item>
    <item>
      <title>Re: Failover to other service on same CSS</title>
      <link>https://community.cisco.com/t5/application-networking/failover-to-other-service-on-same-css/m-p/244914#M3516</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Carl,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can use the primary sorry server command. When the service(s) dies, the primary sorry server takes all the connections.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here is the command.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;primarySorryServer server11 &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you want, you can go through this link.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/univercd/cc/td/doc/product/webscale/css/css_720/bsccfggd/contrule.htm#1038009" target="_blank"&gt;http://www.cisco.com/univercd/cc/td/doc/product/webscale/css/css_720/bsccfggd/contrule.htm#1038009&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Sagar&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 14 Jun 2004 16:22:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/failover-to-other-service-on-same-css/m-p/244914#M3516</guid>
      <dc:creator>sagdas</dc:creator>
      <dc:date>2004-06-14T16:22:23Z</dc:date>
    </item>
    <item>
      <title>Re: Failover to other service on same CSS</title>
      <link>https://community.cisco.com/t5/application-networking/failover-to-other-service-on-same-css/m-p/244915#M3517</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks Sagar,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This answers my question.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Carl&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 14 Jun 2004 17:36:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/failover-to-other-service-on-same-css/m-p/244915#M3517</guid>
      <dc:creator>Carl King</dc:creator>
      <dc:date>2004-06-14T17:36:44Z</dc:date>
    </item>
    <item>
      <title>Re: Failover to other service on same CSS</title>
      <link>https://community.cisco.com/t5/application-networking/failover-to-other-service-on-same-css/m-p/244916#M3518</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The ssumption with a sorry server configuration is that the backup server is less capable than the primary.  If the backup is equally capable (bandwidth, etc..), but you just want to have it as a hot standby you can weight the services with a high differential.  I guess its just a different approach based on the servers' logical roles.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 29 Jun 2004 16:41:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/failover-to-other-service-on-same-css/m-p/244916#M3518</guid>
      <dc:creator>robin.pimentel</dc:creator>
      <dc:date>2004-06-29T16:41:47Z</dc:date>
    </item>
  </channel>
</rss>

