<?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: firewall failove in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/firewall-failove/m-p/1611093#M580596</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks&amp;nbsp; for reply &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sun, 06 Mar 2011 08:18:39 GMT</pubDate>
    <dc:creator>mirehteshamali</dc:creator>
    <dc:date>2011-03-06T08:18:39Z</dc:date>
    <item>
      <title>firewall failove</title>
      <link>https://community.cisco.com/t5/network-security/firewall-failove/m-p/1611087#M580590</link>
      <description>&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; hi all,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;i two 5550 firewall set up for redundance purpose . in failover we define two different ip add one for primary and one for secondary .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;example&lt;/P&gt;&lt;P&gt;interface Ethernet0/0&lt;BR /&gt; nameif outside&lt;BR /&gt; security-level 0&lt;BR /&gt; ip address xxxx.0.0.0.1 255.255.255.0 standby xxxx.0.0.2&lt;BR /&gt;!&lt;BR /&gt;interface Ethernet1/0&lt;BR /&gt; nameif inside&lt;BR /&gt; security-level 100&lt;BR /&gt; ip address 10.0.0.12 255.255.255.0 standby 10.0.0.11&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;question :&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;default gateway for host will be 10.0.0.12 (primary fw address) however in case of failover , the secondary fw will be up with ip address that was assigned for primary .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;in this case the secondary ip add 10.0.0.11 is actually nerver used&amp;nbsp; ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;similarly do i need to have two public ip address for outside (one for primary and one for secondary )&amp;nbsp;&amp;nbsp; ? or in case if primary fails the secondary comes onlie and take the ip of primary fw . hence i only need to purchase just one ip address.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;is my logic correct ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 20:01:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-failove/m-p/1611087#M580590</guid>
      <dc:creator>mirehteshamali</dc:creator>
      <dc:date>2019-03-11T20:01:13Z</dc:date>
    </item>
    <item>
      <title>Re: firewall failove</title>
      <link>https://community.cisco.com/t5/network-security/firewall-failove/m-p/1611088#M580591</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello and Thanks for posting.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In a matter of speaking yes, the secondary IP's are never used. But they are used at the same time. You see, the only way that the firewall can know that an interface is down is doing the hello packets. This packets are sent to the standby IP and from the standby to the primary. In the moment that one of the IP´s stop responding, the failover will occurr, that is mostlikely the use of the secondary IP.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you like, you wouldnt need to have sencondary IP's, you can use just the no monitor interface command and that way you wouldnt need to use them. However, it is not a best practice because you wont be able to determine if there is an interface problem.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I hope this is helpful, Any questions let me know.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Mike Rojas&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 05 Mar 2011 06:48:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-failove/m-p/1611088#M580591</guid>
      <dc:creator>Maykol Rojas</dc:creator>
      <dc:date>2011-03-05T06:48:11Z</dc:date>
    </item>
    <item>
      <title>Re: firewall failove</title>
      <link>https://community.cisco.com/t5/network-security/firewall-failove/m-p/1611089#M580592</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;thanks for prompt reply&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;can i say no monitor outside&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;OR&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;use any dummy ip for secondary (may be this ip is allocated to another costomer by the isp but i dont care as i m using it internally&amp;nbsp; but as for as "global presence / reach is concerned i have one ip for me " ) and still continue with one ip for outside as secondary is never used for connectivity or rechability .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 05 Mar 2011 06:58:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-failove/m-p/1611089#M580592</guid>
      <dc:creator>mirehteshamali</dc:creator>
      <dc:date>2011-03-05T06:58:10Z</dc:date>
    </item>
    <item>
      <title>Re: firewall failove</title>
      <link>https://community.cisco.com/t5/network-security/firewall-failove/m-p/1611090#M580593</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you dont have an available IP, first option would be better, never thought of the second one, but I guess you can do something like that &lt;SPAN __jive_emoticon_name="grin" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.cisco.com/images/emoticons/grin.gif"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Mike&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 05 Mar 2011 07:00:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-failove/m-p/1611090#M580593</guid>
      <dc:creator>Maykol Rojas</dc:creator>
      <dc:date>2011-03-05T07:00:55Z</dc:date>
    </item>
    <item>
      <title>Re: firewall failove</title>
      <link>https://community.cisco.com/t5/network-security/firewall-failove/m-p/1611091#M580594</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Any one can confirm that to me ,&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 05 Mar 2011 09:35:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-failove/m-p/1611091#M580594</guid>
      <dc:creator>mirehteshamali</dc:creator>
      <dc:date>2011-03-05T09:35:47Z</dc:date>
    </item>
    <item>
      <title>Re: firewall failove</title>
      <link>https://community.cisco.com/t5/network-security/firewall-failove/m-p/1611092#M580595</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The problem is that the IP has to be on same broadcast domain, so you may to make your mask on the outside bigger, it will not match with the one with your ISP but other than that you wont have any issues.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Mike&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 05 Mar 2011 17:43:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-failove/m-p/1611092#M580595</guid>
      <dc:creator>Maykol Rojas</dc:creator>
      <dc:date>2011-03-05T17:43:14Z</dc:date>
    </item>
    <item>
      <title>Re: firewall failove</title>
      <link>https://community.cisco.com/t5/network-security/firewall-failove/m-p/1611093#M580596</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks&amp;nbsp; for reply &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 06 Mar 2011 08:18:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-failove/m-p/1611093#M580596</guid>
      <dc:creator>mirehteshamali</dc:creator>
      <dc:date>2011-03-06T08:18:39Z</dc:date>
    </item>
  </channel>
</rss>

