<?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 Since the distribution in Switching</title>
    <link>https://community.cisco.com/t5/switching/asa-high-availability/m-p/3031908#M376687</link>
    <description>&lt;P&gt;Since the distribution switches are running layer-3, you just need a transit vlan (layer-3) between the distribution switches and the firewalls. Usually a /29 subnet would be sufficient.&lt;/P&gt;
&lt;P&gt;HTH&lt;/P&gt;</description>
    <pubDate>Wed, 03 May 2017 15:56:14 GMT</pubDate>
    <dc:creator>Reza Sharifi</dc:creator>
    <dc:date>2017-05-03T15:56:14Z</dc:date>
    <item>
      <title>ASA High Availability</title>
      <link>https://community.cisco.com/t5/switching/asa-high-availability/m-p/3031907#M376686</link>
      <description>&lt;P&gt;If two ASA5508-X are operating in Active-Standby HA mode and the internal interfaces are connected to two separate layer 3 distribution switches, what mechanism should run on the distrubtion switches to route traffic. Note, the two distribution layer switches are running HSRP for the stacked access layer 2 switches.&lt;/P&gt;
&lt;P&gt;Thanks&lt;/P&gt;
&lt;P&gt;Mike&lt;/P&gt;</description>
      <pubDate>Fri, 08 Mar 2019 18:25:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/asa-high-availability/m-p/3031907#M376686</guid>
      <dc:creator>Docklands</dc:creator>
      <dc:date>2019-03-08T18:25:19Z</dc:date>
    </item>
    <item>
      <title>Since the distribution</title>
      <link>https://community.cisco.com/t5/switching/asa-high-availability/m-p/3031908#M376687</link>
      <description>&lt;P&gt;Since the distribution switches are running layer-3, you just need a transit vlan (layer-3) between the distribution switches and the firewalls. Usually a /29 subnet would be sufficient.&lt;/P&gt;
&lt;P&gt;HTH&lt;/P&gt;</description>
      <pubDate>Wed, 03 May 2017 15:56:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/asa-high-availability/m-p/3031908#M376687</guid>
      <dc:creator>Reza Sharifi</dc:creator>
      <dc:date>2017-05-03T15:56:14Z</dc:date>
    </item>
    <item>
      <title>Hi </title>
      <link>https://community.cisco.com/t5/switching/asa-high-availability/m-p/3031909#M376688</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I usually use HSRP between the firewalls and distribution switches, if the firewalls are not the gateway for the VLANs you can use static route between the firewall and distribution switches. As Reza mentioned you need a /29 subnet between them.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Let me share an example of the config that you need. It is a basic configuration.&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="text-decoration: underline;"&gt;&lt;STRONG&gt;DISTRIBUTION 1&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;conf t&lt;BR /&gt;vlan 777&lt;BR /&gt;int vlan 777&lt;BR /&gt;ip add 192.168.77.2 255.255.255.248&lt;BR /&gt;standby 77 ip 192.168.77.1&lt;BR /&gt;standby 77 preempt&lt;BR /&gt;standby 77 priority 105&lt;/P&gt;
&lt;P&gt;ip route 0.0.0.0 0.0.0.0 192.168.77.4&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;*Trunk between the distribution switches to pass the vlan 777&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="text-decoration: underline;"&gt;&lt;STRONG&gt;DISTRIBUTION 2&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;conf t&lt;BR /&gt;vlan 777&lt;BR /&gt;int vlan 777&lt;BR /&gt;ip add 192.168.77.3 255.255.255.248&lt;BR /&gt;standby 77 ip 192.168.77.1&lt;BR /&gt;standby 77 preempt&lt;BR /&gt;standby 77 priority 100&lt;/P&gt;
&lt;P&gt;ip route 0.0.0.0 0.0.0.0 192.168.77.4&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;*Trunk between the distribution switches to pass the vlan 777&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="text-decoration: underline;"&gt;&lt;STRONG&gt;PRIMARY FIREWALL&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;interface GigabitEthernet0/0&lt;BR /&gt; description OUTSIDE&lt;BR /&gt; nameif OUTSIDE&lt;BR /&gt; security-level 0&lt;BR /&gt; no shut&lt;BR /&gt; ip address 192.168.77.4 255.255.255.248 standby 192.168.77.5&lt;/P&gt;
&lt;P&gt;route OUTSIDE 0.0.0.0 0.0.0.0 192.168.77.1 1&lt;/P&gt;</description>
      <pubDate>Wed, 03 May 2017 17:15:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/asa-high-availability/m-p/3031909#M376688</guid>
      <dc:creator>Julio E. Moisa</dc:creator>
      <dc:date>2017-05-03T17:15:29Z</dc:date>
    </item>
    <item>
      <title>Hi Julio,</title>
      <link>https://community.cisco.com/t5/switching/asa-high-availability/m-p/3031910#M376689</link>
      <description>&lt;P&gt;Hi Julio,&lt;/P&gt;
&lt;P&gt;Thank you for the reply.&lt;/P&gt;
&lt;P&gt;I'm not quite sure why the 192.168.77.4 and .5 addresses are attached to the OUTSIDE interfaces. I am connecting the distribution switches to the firewall INTERNAL interfaces?&lt;/P&gt;
&lt;P&gt;Thanks&lt;/P&gt;
&lt;P&gt;Mike&lt;/P&gt;
&lt;P&gt;Ps. Sorry for the delay in replying but I just got home&lt;/P&gt;</description>
      <pubDate>Wed, 03 May 2017 19:59:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/asa-high-availability/m-p/3031910#M376689</guid>
      <dc:creator>Docklands</dc:creator>
      <dc:date>2017-05-03T19:59:28Z</dc:date>
    </item>
    <item>
      <title>You are correct.  It should</title>
      <link>https://community.cisco.com/t5/switching/asa-high-availability/m-p/3031911#M376690</link>
      <description>&lt;P&gt;You are correct. &amp;nbsp;It should be the internal interface.&lt;/P&gt;
&lt;P&gt;HTH&lt;/P&gt;</description>
      <pubDate>Wed, 03 May 2017 20:07:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/asa-high-availability/m-p/3031911#M376690</guid>
      <dc:creator>Reza Sharifi</dc:creator>
      <dc:date>2017-05-03T20:07:06Z</dc:date>
    </item>
    <item>
      <title>Thanks Reza</title>
      <link>https://community.cisco.com/t5/switching/asa-high-availability/m-p/3031912#M376691</link>
      <description>&lt;P&gt;Thanks Reza&lt;/P&gt;</description>
      <pubDate>Wed, 03 May 2017 20:18:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/asa-high-availability/m-p/3031912#M376691</guid>
      <dc:creator>Docklands</dc:creator>
      <dc:date>2017-05-03T20:18:37Z</dc:date>
    </item>
    <item>
      <title>Lol  you are right, it is</title>
      <link>https://community.cisco.com/t5/switching/asa-high-availability/m-p/3031913#M376692</link>
      <description>&lt;P&gt;Lol &amp;nbsp;you are right, it is just an example hehe but it can be inside or a name related.&lt;/P&gt;
&lt;P&gt;Also you can use access mode port over the vlan 777 to connect to the firewalls&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 03 May 2017 20:41:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/asa-high-availability/m-p/3031913#M376692</guid>
      <dc:creator>Julio E. Moisa</dc:creator>
      <dc:date>2017-05-03T20:41:06Z</dc:date>
    </item>
  </channel>
</rss>

