<?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 in CSS11000 in Application Networking</title>
    <link>https://community.cisco.com/t5/application-networking/failover-in-css11000/m-p/69837#M796</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Difei,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The major difference without writing a small book here is that with box/box (also know as active/passive) redundancy, one box is up and active, while the second box is completly down and not active from an ip or interface perspective.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;With VIP and interface redundancy, one CSS is active and considered Primary, while the second box is considered backup but is able to L2 forward requests should they come into the box and get them to the necessary destination.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Pete Knoops&lt;/P&gt;&lt;P&gt;Cisco Systems&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 26 Aug 2002 11:49:08 GMT</pubDate>
    <dc:creator>pknoops</dc:creator>
    <dc:date>2002-08-26T11:49:08Z</dc:date>
    <item>
      <title>failover in CSS11000</title>
      <link>https://community.cisco.com/t5/application-networking/failover-in-css11000/m-p/69836#M795</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;what's the mjor difference between box-to-box and VIP&amp;amp;Interface redundancy?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks /difei&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 26 Aug 2002 02:30:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/failover-in-css11000/m-p/69836#M795</guid>
      <dc:creator>difyang</dc:creator>
      <dc:date>2002-08-26T02:30:27Z</dc:date>
    </item>
    <item>
      <title>Re: failover in CSS11000</title>
      <link>https://community.cisco.com/t5/application-networking/failover-in-css11000/m-p/69837#M796</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Difei,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The major difference without writing a small book here is that with box/box (also know as active/passive) redundancy, one box is up and active, while the second box is completly down and not active from an ip or interface perspective.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;With VIP and interface redundancy, one CSS is active and considered Primary, while the second box is considered backup but is able to L2 forward requests should they come into the box and get them to the necessary destination.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Pete Knoops&lt;/P&gt;&lt;P&gt;Cisco Systems&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 26 Aug 2002 11:49:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/failover-in-css11000/m-p/69837#M796</guid>
      <dc:creator>pknoops</dc:creator>
      <dc:date>2002-08-26T11:49:08Z</dc:date>
    </item>
    <item>
      <title>Re: failover in CSS11000</title>
      <link>https://community.cisco.com/t5/application-networking/failover-in-css11000/m-p/69838#M797</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi Pete,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. what's meaning of dynamic server?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2. how to implement a security design for Reverse proxy caching.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;many thanks for support!&lt;/P&gt;&lt;P&gt;difei&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 27 Aug 2002 00:02:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/failover-in-css11000/m-p/69838#M797</guid>
      <dc:creator>difyang</dc:creator>
      <dc:date>2002-08-27T00:02:39Z</dc:date>
    </item>
  </channel>
</rss>

