<?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 Redundant Interface Connectivity in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/redundant-interface-connectivity/m-p/2416279#M306715</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I have two 5585X need to be connected to two Core switch(6509) which is not having the VSS feature in it.HSRP is running. My doubt is regarding the Redundant interface configuration. &lt;/P&gt;&lt;P&gt;Is it required that the two redundant interfaces of an ASA should be on the same Core switch or it can also be done as shown in figure below.&lt;/P&gt;&lt;P&gt;&lt;IMG src="https://community.cisco.com/legacyfs/online/legacy/2/5/3/171352-Firewall%20Installation.jpg" alt="Firewall Installation.jpg" class="jive-image" style="font-size: 10pt;" /&gt;&lt;/P&gt;&lt;P&gt;Thanks &lt;/P&gt;&lt;P&gt;Sibin SS.&lt;/P&gt;</description>
    <pubDate>Tue, 12 Mar 2019 03:21:44 GMT</pubDate>
    <dc:creator>Sibin S S</dc:creator>
    <dc:date>2019-03-12T03:21:44Z</dc:date>
    <item>
      <title>Redundant Interface Connectivity</title>
      <link>https://community.cisco.com/t5/network-security/redundant-interface-connectivity/m-p/2416279#M306715</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I have two 5585X need to be connected to two Core switch(6509) which is not having the VSS feature in it.HSRP is running. My doubt is regarding the Redundant interface configuration. &lt;/P&gt;&lt;P&gt;Is it required that the two redundant interfaces of an ASA should be on the same Core switch or it can also be done as shown in figure below.&lt;/P&gt;&lt;P&gt;&lt;IMG src="https://community.cisco.com/legacyfs/online/legacy/2/5/3/171352-Firewall%20Installation.jpg" alt="Firewall Installation.jpg" class="jive-image" style="font-size: 10pt;" /&gt;&lt;/P&gt;&lt;P&gt;Thanks &lt;/P&gt;&lt;P&gt;Sibin SS.&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 03:21:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/redundant-interface-connectivity/m-p/2416279#M306715</guid>
      <dc:creator>Sibin S S</dc:creator>
      <dc:date>2019-03-12T03:21:44Z</dc:date>
    </item>
    <item>
      <title>Redundant Interface Connectivity</title>
      <link>https://community.cisco.com/t5/network-security/redundant-interface-connectivity/m-p/2416280#M306719</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Sibin,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Are you running any kind of failover on the ASA??&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The thing is that if the primary interface on a redundant link on one of the ASAs goes down then the backup interface will come up. The problem lies on the fact that HSRP will need to be aware on that and switch to the other Catalyst box.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So If you enable tracking on those links I think you should be fine.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I hope I was clear enough (This desing problems are the worst to explain, so many things to say hehe)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Looking for some Networking Assistance?&amp;nbsp; &lt;BR /&gt;&lt;SPAN&gt;Contact me directly at &lt;/SPAN&gt;&lt;A class="jive-link-email-small" href="mailto:jcarvaja@laguiadelnetworking.com"&gt;jcarvaja@laguiadelnetworking.com&lt;/A&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;BR /&gt; &lt;BR /&gt;I will fix your problem ASAP. &lt;BR /&gt; &lt;BR /&gt;Cheers, &lt;BR /&gt; &lt;BR /&gt;Julio Carvajal Segura &lt;BR /&gt;&lt;A class="jive-link-external-small" href="http://laguiadelnetworking.com"&gt;http://laguiadelnetworking.com&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 26 Dec 2013 04:21:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/redundant-interface-connectivity/m-p/2416280#M306719</guid>
      <dc:creator>Julio Carvajal</dc:creator>
      <dc:date>2013-12-26T04:21:14Z</dc:date>
    </item>
    <item>
      <title>Redundant Interface Connectivity</title>
      <link>https://community.cisco.com/t5/network-security/redundant-interface-connectivity/m-p/2416281#M306724</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dear Julio,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for the reply &lt;SPAN __jive_emoticon_name="happy" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.cisco.com/4.5.4/images/emoticons/happy.gif"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ASAs are in active/standby failover.&lt;/P&gt;&lt;P&gt;L3 interfaces are all VLAN interfaeces on Switch and Subinterfaces on ASAs.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Sibin SS.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 27 Dec 2013 08:22:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/redundant-interface-connectivity/m-p/2416281#M306724</guid>
      <dc:creator>Sibin S S</dc:creator>
      <dc:date>2013-12-27T08:22:45Z</dc:date>
    </item>
    <item>
      <title>Redundant Interface Connectivity</title>
      <link>https://community.cisco.com/t5/network-security/redundant-interface-connectivity/m-p/2416282#M306726</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Julio &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;The thing is that if the primary interface on a redundant link on one of the ASAs goes down then the backup interface will come up. The problem lies on the fact that HSRP will need to be aware on that and switch to the other Catalyst box.&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt; &lt;/EM&gt;&lt;/P&gt;&lt;P&gt;Why does it need to do this ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If the primary interface on the active ASA fails and it switches to the backup link HSRP does not have to change because there is a L2 path between the switches so instead of traffic going direct from the HSRP active to the active firewall it goes from the HSRP active to the other switch and then to the active firewall via the new active link. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there something i am mssing in terms of the ASA ? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jon&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 27 Dec 2013 12:24:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/redundant-interface-connectivity/m-p/2416282#M306726</guid>
      <dc:creator>Jon Marshall</dc:creator>
      <dc:date>2013-12-27T12:24:56Z</dc:date>
    </item>
    <item>
      <title>Redundant Interface Connectivity</title>
      <link>https://community.cisco.com/t5/network-security/redundant-interface-connectivity/m-p/2416283#M306733</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Guys,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Nah, as I said before I did not know there was any kind of failover cluster on the network.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If there is failover as the customer just confirmed then no need to worry at all&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Looking for some Networking Assistance?&amp;nbsp; &lt;BR /&gt;&lt;SPAN&gt;Contact me directly at &lt;/SPAN&gt;&lt;A class="jive-link-email-small" href="mailto:jcarvaja@laguiadelnetworking.com"&gt;jcarvaja@laguiadelnetworking.com&lt;/A&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;BR /&gt; &lt;BR /&gt;I will fix your problem ASAP. &lt;BR /&gt; &lt;BR /&gt;Cheers, &lt;BR /&gt; &lt;BR /&gt;Julio Carvajal Segura &lt;BR /&gt;&lt;A class="jive-link-external-small" href="http://laguiadelnetworking.com"&gt;http://laguiadelnetworking.com&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 27 Dec 2013 13:13:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/redundant-interface-connectivity/m-p/2416283#M306733</guid>
      <dc:creator>Julio Carvajal</dc:creator>
      <dc:date>2013-12-27T13:13:46Z</dc:date>
    </item>
    <item>
      <title>Redundant Interface Connectivity</title>
      <link>https://community.cisco.com/t5/network-security/redundant-interface-connectivity/m-p/2416284#M306735</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Sibin&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As far as i am aware there is no requirement for a redundant pair of interfaces to be connected to the same switch so your setup should work as you have described it. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jon&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 27 Dec 2013 13:19:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/redundant-interface-connectivity/m-p/2416284#M306735</guid>
      <dc:creator>Jon Marshall</dc:creator>
      <dc:date>2013-12-27T13:19:43Z</dc:date>
    </item>
    <item>
      <title>Redundant Interface Connectivity</title>
      <link>https://community.cisco.com/t5/network-security/redundant-interface-connectivity/m-p/2416285#M306736</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thankyou Jon and Julio for helping &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Happy new Year!! &lt;SPAN __jive_emoticon_name="happy" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.cisco.com/4.5.4/images/emoticons/happy.gif"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Warm Regards,&lt;/P&gt;&lt;P&gt;Sibin SS&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 28 Dec 2013 08:38:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/redundant-interface-connectivity/m-p/2416285#M306736</guid>
      <dc:creator>Sibin S S</dc:creator>
      <dc:date>2013-12-28T08:38:05Z</dc:date>
    </item>
  </channel>
</rss>

