<?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: Transparent Cache &amp; Failover Bypass in Application Networking</title>
    <link>https://community.cisco.com/t5/application-networking/transparent-cache-failover-bypass/m-p/332196#M5461</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Joerg,&lt;/P&gt;&lt;P&gt;thanks for the answer.&lt;/P&gt;&lt;P&gt;I think that could work, but i'd need to do client nat only when bypassing the cache.&lt;/P&gt;&lt;P&gt;any ideas?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 09 Sep 2004 07:07:50 GMT</pubDate>
    <dc:creator>estebanmartin</dc:creator>
    <dc:date>2004-09-09T07:07:50Z</dc:date>
    <item>
      <title>Transparent Cache &amp; Failover Bypass</title>
      <link>https://community.cisco.com/t5/application-networking/transparent-cache-failover-bypass/m-p/332194#M5459</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;i'm using transparent caching on a 11501 sending all http traffic to a BlueCoat Cache.&lt;/P&gt;&lt;P&gt;I have set the failover bypass option.&lt;/P&gt;&lt;P&gt;When the cache is down, the CSS bypass the cache, but the problem is that i want the http requests to have the CSS source address so the firewall let them pass.&lt;/P&gt;&lt;P&gt;But the http requests have the client ip.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there a solution to this?&lt;/P&gt;&lt;P&gt;the cache rule is L5&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 08 Sep 2004 07:00:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/transparent-cache-failover-bypass/m-p/332194#M5459</guid>
      <dc:creator>estebanmartin</dc:creator>
      <dc:date>2004-09-08T07:00:54Z</dc:date>
    </item>
    <item>
      <title>Re: Transparent Cache &amp; Failover Bypass</title>
      <link>https://community.cisco.com/t5/application-networking/transparent-cache-failover-bypass/m-p/332195#M5460</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;yes there is a way. This sort of functionaliy is needed in a one armed scenario but you can use the method in a normal one to. &lt;/P&gt;&lt;P&gt;Just followup the steps described in step 5 of the following link (&lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/products/hw/contnetw/ps789/products_configuration_example09186a0080093dff.shtml#topic1" target="_blank"&gt;http://www.cisco.com/en/US/products/hw/contnetw/ps789/products_configuration_example09186a0080093dff.shtml#topic1&lt;/A&gt;)&lt;/P&gt;&lt;P&gt;What is basicaly does is to do client nat and replaces the original Client IP by a configuered IP-adress. I think this will do the job.&lt;/P&gt;&lt;P&gt;Kind Regards,&lt;/P&gt;&lt;P&gt; Joerg&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 08 Sep 2004 12:48:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/transparent-cache-failover-bypass/m-p/332195#M5460</guid>
      <dc:creator>jfoerster</dc:creator>
      <dc:date>2004-09-08T12:48:08Z</dc:date>
    </item>
    <item>
      <title>Re: Transparent Cache &amp; Failover Bypass</title>
      <link>https://community.cisco.com/t5/application-networking/transparent-cache-failover-bypass/m-p/332196#M5461</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Joerg,&lt;/P&gt;&lt;P&gt;thanks for the answer.&lt;/P&gt;&lt;P&gt;I think that could work, but i'd need to do client nat only when bypassing the cache.&lt;/P&gt;&lt;P&gt;any ideas?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 09 Sep 2004 07:07:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/transparent-cache-failover-bypass/m-p/332196#M5461</guid>
      <dc:creator>estebanmartin</dc:creator>
      <dc:date>2004-09-09T07:07:50Z</dc:date>
    </item>
    <item>
      <title>Re: Transparent Cache &amp; Failover Bypass</title>
      <link>https://community.cisco.com/t5/application-networking/transparent-cache-failover-bypass/m-p/332197#M5462</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;HI,&lt;/P&gt;&lt;P&gt;configure the firewall as a service and use it as backupservice for the bluecoat. The source-group will only include the firewall as service so only Client nat is done when the bluecoat fails and get's bypassed.&lt;/P&gt;&lt;P&gt;Maybe this is a posibility depending on the setup of your network.&lt;/P&gt;&lt;P&gt;Kind Regards,&lt;/P&gt;&lt;P&gt; Joerg&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 09 Sep 2004 10:44:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/transparent-cache-failover-bypass/m-p/332197#M5462</guid>
      <dc:creator>jfoerster</dc:creator>
      <dc:date>2004-09-09T10:44:28Z</dc:date>
    </item>
    <item>
      <title>Re: Transparent Cache &amp; Failover Bypass</title>
      <link>https://community.cisco.com/t5/application-networking/transparent-cache-failover-bypass/m-p/332198#M5463</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;i'm going to try that configuration.&lt;/P&gt;&lt;P&gt;but how can i use the firewall service as a backupservice?&lt;/P&gt;&lt;P&gt;thanks in advance.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 10 Sep 2004 14:50:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/transparent-cache-failover-bypass/m-p/332198#M5463</guid>
      <dc:creator>estebanmartin</dc:creator>
      <dc:date>2004-09-10T14:50:05Z</dc:date>
    </item>
    <item>
      <title>Re: Transparent Cache &amp; Failover Bypass</title>
      <link>https://community.cisco.com/t5/application-networking/transparent-cache-failover-bypass/m-p/332199#M5464</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;HI,&lt;/P&gt;&lt;P&gt;just use the primarySorryServer command (see &lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/products/hw/contnetw/ps792/products_command_reference_chapter09186a008028fe78.html#wp1140863" target="_blank"&gt;http://www.cisco.com/en/US/products/hw/contnetw/ps792/products_command_reference_chapter09186a008028fe78.html#wp1140863&lt;/A&gt;). This command takes care or requestes if all other services in a content rule failed. In your case this will take place if your Caches are failing. The sorryserver (your firewall) will than take over the job until the caches return working.&lt;/P&gt;&lt;P&gt;Btw. be aware that this service should only do "routing". So no need for destination NAT.&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt; Joerg&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 12 Sep 2004 17:25:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/transparent-cache-failover-bypass/m-p/332199#M5464</guid>
      <dc:creator>jfoerster</dc:creator>
      <dc:date>2004-09-12T17:25:03Z</dc:date>
    </item>
  </channel>
</rss>

