<?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: PIX configured with 2 ISP links in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/pix-configured-with-2-isp-links/m-p/912305#M973788</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This document says "this setup may not be suitable for inbound access to resources behind the security appliance." And my requirement is mainly for inbound continues access. So, Will this work for inbound access by configuring with the simple static and access-list commands for the corresponding ISP interfaces along with the above Backup interface configurations? Please advise.... Is anyone tried this before?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 11 Oct 2007 05:30:57 GMT</pubDate>
    <dc:creator>timit</dc:creator>
    <dc:date>2007-10-11T05:30:57Z</dc:date>
    <item>
      <title>PIX configured with 2 ISP links</title>
      <link>https://community.cisco.com/t5/network-security/pix-configured-with-2-isp-links/m-p/912303#M973786</link>
      <description>&lt;P&gt;Hi, I would like to know is it possible/advisable to have 2 ISP links on PIX515E interfaces so that if one goes down the other will be up for outside users to access the server services inside the PIX local LAN with out any service disturbance. Please advice and kind enough to send me the sample configurations. Thanks.&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 11:23:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-configured-with-2-isp-links/m-p/912303#M973786</guid>
      <dc:creator>timit</dc:creator>
      <dc:date>2019-03-11T11:23:24Z</dc:date>
    </item>
    <item>
      <title>Re: PIX configured with 2 ISP links</title>
      <link>https://community.cisco.com/t5/network-security/pix-configured-with-2-isp-links/m-p/912304#M973787</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes it is possible.&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/vpndevc/ps2030/products_configuration_example09186a00806e880b.shtml#req" target="_blank"&gt;http://www.cisco.com/en/US/products/hw/vpndevc/ps2030/products_configuration_example09186a00806e880b.shtml#req&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;you may need to run 7.2.x code for the backup command as this was introduced in code 7.2.1&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 10 Oct 2007 13:06:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-configured-with-2-isp-links/m-p/912304#M973787</guid>
      <dc:creator>JORGE RODRIGUEZ</dc:creator>
      <dc:date>2007-10-10T13:06:42Z</dc:date>
    </item>
    <item>
      <title>Re: PIX configured with 2 ISP links</title>
      <link>https://community.cisco.com/t5/network-security/pix-configured-with-2-isp-links/m-p/912305#M973788</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This document says "this setup may not be suitable for inbound access to resources behind the security appliance." And my requirement is mainly for inbound continues access. So, Will this work for inbound access by configuring with the simple static and access-list commands for the corresponding ISP interfaces along with the above Backup interface configurations? Please advise.... Is anyone tried this before?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 11 Oct 2007 05:30:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-configured-with-2-isp-links/m-p/912305#M973788</guid>
      <dc:creator>timit</dc:creator>
      <dc:date>2007-10-11T05:30:57Z</dc:date>
    </item>
    <item>
      <title>Re: PIX configured with 2 ISP links</title>
      <link>https://community.cisco.com/t5/network-security/pix-configured-with-2-isp-links/m-p/912306#M973789</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;it will not work with inbound access with above example ,  personaly I have not  faced this scenario but would definately like to lab this out, frankly I don't know if there is a simpler way to do this, if you want to have inbound access through ISP2 should ISP1 fail  or vise versa this becomes a bit  complicated  as may question arises with DNS ,  and NATing two different public IP blocks into single inbound host but possible, you would have place a router in front of firewall and BGP multihomed with two ISP. &lt;/P&gt;&lt;P&gt;You may also post your initial question in WAN routing forum, where there are much more audience that may have done  your requirements. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;these links may also help &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.oreillynet.com/pub/a/network/2001/05/11/multihoming.html" target="_blank"&gt;http://www.oreillynet.com/pub/a/network/2001/05/11/multihoming.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.spirit.com/Network/net0503.html" target="_blank"&gt;http://www.spirit.com/Network/net0503.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/tech/tk365/technologies_configuration_example09186a008009456d.shtml" target="_blank"&gt;http://www.cisco.com/en/US/tech/tk365/technologies_configuration_example09186a008009456d.shtml&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&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>Thu, 11 Oct 2007 19:17:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-configured-with-2-isp-links/m-p/912306#M973789</guid>
      <dc:creator>JORGE RODRIGUEZ</dc:creator>
      <dc:date>2007-10-11T19:17:36Z</dc:date>
    </item>
  </channel>
</rss>

