<?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 CSS and dual homed servers in Application Networking</title>
    <link>https://community.cisco.com/t5/application-networking/css-and-dual-homed-servers/m-p/34415#M373</link>
    <description>&lt;P&gt;I am working on a simple CSS design using Active/Backup with VIP and interface redundancy.  My servers are dual homed to the Active and Backup CSS's using teaming.  I am sure this has been done before, but I have not found any documentation on how this would work, and how to best configure the teaming (Active/Active, Active/Passive, etc).  Has anyone seen any documentation on this, or implemented a similar scenario?  My concern is that when the Active CSS takes itself out of service for a component failure, how will this affect the teaming.  In an Active/Passive teaming config, will the Active Nic continue to forward traffic to the now downed CSS since the link is still up?  In an Active/Active teaming config, I have the same concern.  Will half of the traffic still go to the downed CSS?  Any info would be much appreciated.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks....&lt;/P&gt;</description>
    <pubDate>Thu, 24 Oct 2002 15:42:52 GMT</pubDate>
    <dc:creator>tlomonaco</dc:creator>
    <dc:date>2002-10-24T15:42:52Z</dc:date>
    <item>
      <title>CSS and dual homed servers</title>
      <link>https://community.cisco.com/t5/application-networking/css-and-dual-homed-servers/m-p/34415#M373</link>
      <description>&lt;P&gt;I am working on a simple CSS design using Active/Backup with VIP and interface redundancy.  My servers are dual homed to the Active and Backup CSS's using teaming.  I am sure this has been done before, but I have not found any documentation on how this would work, and how to best configure the teaming (Active/Active, Active/Passive, etc).  Has anyone seen any documentation on this, or implemented a similar scenario?  My concern is that when the Active CSS takes itself out of service for a component failure, how will this affect the teaming.  In an Active/Passive teaming config, will the Active Nic continue to forward traffic to the now downed CSS since the link is still up?  In an Active/Active teaming config, I have the same concern.  Will half of the traffic still go to the downed CSS?  Any info would be much appreciated.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks....&lt;/P&gt;</description>
      <pubDate>Thu, 24 Oct 2002 15:42:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/css-and-dual-homed-servers/m-p/34415#M373</guid>
      <dc:creator>tlomonaco</dc:creator>
      <dc:date>2002-10-24T15:42:52Z</dc:date>
    </item>
    <item>
      <title>Re: CSS and dual homed servers</title>
      <link>https://community.cisco.com/t5/application-networking/css-and-dual-homed-servers/m-p/34416#M374</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This might help you out: &lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/partner/products/hw/contnetw/ps789/products_tech_note09186a008009432f.shtml" target="_blank"&gt;http://www.cisco.com/en/US/partner/products/hw/contnetw/ps789/products_tech_note09186a008009432f.shtml&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 31 Oct 2002 22:00:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/css-and-dual-homed-servers/m-p/34416#M374</guid>
      <dc:creator>fmeetz</dc:creator>
      <dc:date>2002-10-31T22:00:20Z</dc:date>
    </item>
  </channel>
</rss>

