<?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: ASA 5525 vlan interface traffic not working in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-5525-vlan-interface-traffic-not-working/m-p/3734023#M9221</link>
    <description>&lt;P&gt;In the switch config, ports 23 and 24 go to gig0/3 on each firewall? Based on the redundant config, gig0/2 on the firewall will be the active interface.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Is Q-in-Q configured on gig0/23 for a specific reason?&lt;/P&gt;
&lt;P&gt;What does spanning tree for one of the vlans look like on each switch?&lt;/P&gt;</description>
    <pubDate>Fri, 26 Oct 2018 22:08:21 GMT</pubDate>
    <dc:creator>rmfalconer</dc:creator>
    <dc:date>2018-10-26T22:08:21Z</dc:date>
    <item>
      <title>ASA 5525 vlan interface traffic not working</title>
      <link>https://community.cisco.com/t5/network-security/asa-5525-vlan-interface-traffic-not-working/m-p/3733820#M9215</link>
      <description>&lt;P&gt;I am working on configuring a pair of cisco ASA 5525 and I am running into some trouble. I have done the basic configuration and have a management interface and HA setup without issue. Now I am trying to configure some vlan sub-interfaces but cannot get them to pass traffic. I am familiar with cisco switches and Palo Alto firewalls and watchguard firewalls.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Basic setup is two cisco switches for redundancy connected to the ASA on interface 2 and 3 set as a redundant interface. The switch connections to the ASA are set a trunk interfaces with the proper vlans allowed. Similar to how I have set up other networks.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The ASA has the sub-interfaces configured with the correct vlans and show a status of UP in the home section of the ASDM. I however cannot ping the interface IP address nor can I pass traffic to another VLAN interface. I also cannot pass any external traffic. I am sure it is something simple that I am missing.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Any help or advice would be great! I can post a copy of the ASA config if needed. Thanks&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 16:24:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-5525-vlan-interface-traffic-not-working/m-p/3733820#M9215</guid>
      <dc:creator>Maddhattr</dc:creator>
      <dc:date>2020-02-21T16:24:13Z</dc:date>
    </item>
    <item>
      <title>Re: ASA 5525 vlan interface traffic not working</title>
      <link>https://community.cisco.com/t5/network-security/asa-5525-vlan-interface-traffic-not-working/m-p/3734006#M9217</link>
      <description>&lt;P&gt;Yes, the relevant ASA and switch configuration snips would be helpful.&lt;/P&gt;</description>
      <pubDate>Fri, 26 Oct 2018 21:21:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-5525-vlan-interface-traffic-not-working/m-p/3734006#M9217</guid>
      <dc:creator>rmfalconer</dc:creator>
      <dc:date>2018-10-26T21:21:46Z</dc:date>
    </item>
    <item>
      <title>Re: ASA 5525 vlan interface traffic not working</title>
      <link>https://community.cisco.com/t5/network-security/asa-5525-vlan-interface-traffic-not-working/m-p/3734019#M9219</link>
      <description>&lt;P&gt;&lt;U&gt;&lt;STRONG&gt;Here are the interface ports on the switch that is connected to the FW:&lt;/STRONG&gt;&lt;/U&gt;&lt;/P&gt;
&lt;P&gt;interface GigabitEthernet1/0/3&lt;BR /&gt; description FEP1 N1&lt;BR /&gt; switchport trunk native vlan 888&lt;BR /&gt; switchport trunk allowed vlan 413-415,417&lt;BR /&gt; switchport mode trunk&lt;BR /&gt; spanning-tree portfast disable&lt;BR /&gt;!&lt;BR /&gt;interface GigabitEthernet1/0/4&lt;BR /&gt; description FEP1 N2&lt;BR /&gt; switchport trunk native vlan 888&lt;BR /&gt; switchport trunk allowed vlan 413-415,417&lt;BR /&gt; switchport mode trunk&lt;BR /&gt; spanning-tree portfast disable&lt;BR /&gt;!&lt;BR /&gt;interface GigabitEthernet1/0/5&lt;BR /&gt; description FEP2 N1&lt;BR /&gt; switchport trunk native vlan 888&lt;BR /&gt; switchport trunk allowed vlan 413-415,417&lt;BR /&gt; switchport mode trunk&lt;BR /&gt; spanning-tree portfast disable&lt;BR /&gt;!&lt;BR /&gt;interface GigabitEthernet1/0/6&lt;BR /&gt; description FEP2 N2&lt;BR /&gt; switchport trunk native vlan 888&lt;BR /&gt; switchport trunk allowed vlan 413-415,417&lt;BR /&gt; switchport mode trunk&lt;BR /&gt; spanning-tree portfast disable&lt;BR /&gt;!&lt;BR /&gt;interface GigabitEthernet1/0/23&lt;BR /&gt; description "FW1 P3"&lt;BR /&gt; switchport trunk allowed vlan 413-417,904&lt;BR /&gt; switchport mode dot1q-tunnel&lt;BR /&gt; no cdp enable&lt;BR /&gt; spanning-tree portfast disable&lt;BR /&gt;!&lt;BR /&gt;interface GigabitEthernet1/0/24&lt;BR /&gt; description "FW2 P3"&lt;BR /&gt; switchport trunk allowed vlan 413-417,904&lt;BR /&gt; switchport mode trunk&lt;BR /&gt; spanning-tree portfast disable&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;U&gt;&lt;STRONG&gt;Here is the ASA settings:&lt;/STRONG&gt;&lt;/U&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;ASA Version 9.8(2)&lt;BR /&gt;!&lt;BR /&gt;hostname FW01&lt;/P&gt;
&lt;P&gt;!&lt;BR /&gt;interface GigabitEthernet0/0&lt;BR /&gt; description Interface for external ISP 1&lt;BR /&gt; nameif ISP01&lt;BR /&gt; security-level 0&lt;BR /&gt; zone-member Z0-Public&lt;BR /&gt; ip address 192.168.40.33 255.255.254.0&lt;BR /&gt;!&lt;BR /&gt;interface GigabitEthernet0/0.904&lt;BR /&gt; description MGMT&lt;BR /&gt; vlan 904&lt;BR /&gt; nameif MGMT&lt;BR /&gt; security-level 100&lt;BR /&gt; no ip address&lt;BR /&gt;!&lt;BR /&gt;interface GigabitEthernet0/1&lt;BR /&gt; description Interface for external ISP 2&lt;BR /&gt; shutdown&lt;BR /&gt; nameif ISP02&lt;BR /&gt; security-level 0&lt;BR /&gt; zone-member Z0-Public&lt;BR /&gt; no ip address&lt;BR /&gt;!&lt;BR /&gt;interface Redundant4&lt;BR /&gt; member-interface GigabitEthernet0/2&lt;BR /&gt; member-interface GigabitEthernet0/3&lt;BR /&gt; nameif REDUNDANT&lt;BR /&gt; security-level 0&lt;BR /&gt; no ip address&lt;BR /&gt;!&lt;BR /&gt;interface Redundant4.413&lt;BR /&gt; vlan 413&lt;BR /&gt; nameif HM-PHYS&lt;BR /&gt; security-level 60&lt;BR /&gt; ip address 192.168.13.1 255.255.255.0&lt;BR /&gt;!&lt;BR /&gt;interface Redundant4.414&lt;BR /&gt; vlan 414&lt;BR /&gt; nameif HM-AD&lt;BR /&gt; security-level 70&lt;BR /&gt; ip address 192.168.14.1 255.255.255.0&lt;BR /&gt;!&lt;BR /&gt;interface Redundant4.415&lt;BR /&gt; vlan 415&lt;BR /&gt; nameif HM-DMZ&lt;BR /&gt; security-level 50&lt;BR /&gt; ip address 192.168.15.1 255.255.255.0&lt;BR /&gt;!&lt;BR /&gt;interface Redundant4.416&lt;BR /&gt; vlan 416&lt;BR /&gt; nameif HM-PLNT&lt;BR /&gt; security-level 20&lt;BR /&gt; ip address 192.168.16.1 255.255.255.0&lt;BR /&gt;!&lt;BR /&gt;interface Redundant4.417&lt;BR /&gt; vlan 417&lt;BR /&gt; nameif HM-FEP&lt;BR /&gt; security-level 80&lt;BR /&gt; ip address 192.168.17.1 255.255.255.0&lt;BR /&gt;!&lt;BR /&gt;object network FEPA&lt;BR /&gt; host 192.168.17.21&lt;BR /&gt; description FEPA&lt;BR /&gt;object network FEPA-NAT&lt;BR /&gt; host 10.116.251.93&lt;BR /&gt; description NAT for PLNT acccess by the FEP&lt;BR /&gt;object network FEPB-NAT&lt;BR /&gt; host 10.116.251.94&lt;BR /&gt; description NAT for PLNT access from FEPB&lt;BR /&gt;object network FEPB&lt;BR /&gt; host 192.168.17.22&lt;BR /&gt; description FEPB&lt;BR /&gt;object network HERMDC1&lt;BR /&gt; host 192.168.14.15&lt;BR /&gt; description DC1&lt;BR /&gt;object network HERMDC2&lt;BR /&gt; host 192.168.14.16&lt;BR /&gt; description DC2&lt;BR /&gt;object network HMPHFEPA&lt;BR /&gt; host 192.168.13.21&lt;BR /&gt; description Physical FEP server A&lt;BR /&gt;object network HMPHFEPB&lt;BR /&gt; host 192.168.13.22&lt;BR /&gt; description Physical FEP server B&lt;BR /&gt;object network HM-EMS-SW01&lt;BR /&gt; host 192.168.104.201&lt;BR /&gt;object network HM-EMS-SW02&lt;BR /&gt; host 192.168.104.202&lt;BR /&gt;object network HERM-FW02&lt;BR /&gt; host 192.168.104.102&lt;BR /&gt;object network HERM-FW01&lt;BR /&gt; host 192.168.104.101&lt;BR /&gt;object network HM-ISP-SW01&lt;BR /&gt; host 192.168.104.205&lt;BR /&gt;object network HM-ISP-SW02&lt;BR /&gt; host 192.168.104.206&lt;BR /&gt;object network PHYS-GW&lt;BR /&gt; host 192.168.13.1&lt;BR /&gt;object network AD-GW&lt;BR /&gt; host 192.168.14.1&lt;BR /&gt;object-group network DM_INLINE_NETWORK_1&lt;BR /&gt; network-object object HMPHFEPA&lt;BR /&gt; network-object object HMPHFEPB&lt;BR /&gt;object-group network DM_INLINE_NETWORK_2&lt;BR /&gt; network-object object HERMDC1&lt;BR /&gt; network-object object HERMDC2&lt;BR /&gt;object-group network DM_INLINE_NETWORK_3&lt;BR /&gt; network-object object FEPA&lt;BR /&gt; network-object object FEPB&lt;BR /&gt;object-group network DM_INLINE_NETWORK_4&lt;BR /&gt; network-object object HERMDC1&lt;BR /&gt; network-object object HERMDC2&lt;BR /&gt;object-group network DM_INLINE_NETWORK_5&lt;BR /&gt; network-object object HMPHFEPA&lt;BR /&gt; network-object object HMPHFEPB&lt;BR /&gt;object-group network DM_INLINE_NETWORK_6&lt;BR /&gt; network-object object HERMDC1&lt;BR /&gt; network-object object HERMDC2&lt;BR /&gt;object-group network DM_INLINE_NETWORK_7&lt;BR /&gt; network-object object HMPHFEPA&lt;BR /&gt; network-object object HMPHFEPB&lt;BR /&gt;object-group network DM_INLINE_NETWORK_8&lt;BR /&gt; network-object object HERMDC1&lt;BR /&gt; network-object object HERMDC2&lt;BR /&gt;object-group network DM_INLINE_NETWORK_9&lt;BR /&gt; network-object object HMPHFEPA&lt;BR /&gt; network-object object HMPHFEPB&lt;BR /&gt;access-list PLNT_access_in_1 remark Allows communication from FEPA to the PLNT network&lt;BR /&gt;access-list PLNT_access_in_1 extended permit ip object FEPA 192.168.251.64 255.255.255.224&lt;BR /&gt;access-list PLNT_access_in_1 remark Allows communication from FEPB to the PLNT network&lt;BR /&gt;access-list PLNT_access_in_1 extended permit ip object FEPB 192.168.251.64 255.255.255.224&lt;BR /&gt;access-list PHYS_access_out extended permit ip object-group DM_INLINE_NETWORK_5 192.168.14.0 255.255.255.0&lt;BR /&gt;access-list PHYS_access_out extended permit ip any any&lt;BR /&gt;access-list HERM-AD-SVR_access_in extended permit ip object-group DM_INLINE_NETWORK_1 object-group DM_INLINE_NETWORK_2&lt;BR /&gt;access-list HERM-AD-SVR_access_in extended permit ip object-group DM_INLINE_NETWORK_3 object-group DM_INLINE_NETWORK_4&lt;BR /&gt;access-list HERM-AD-SVR_access_out extended permit ip object-group DM_INLINE_NETWORK_6 object-group DM_INLINE_NETWORK_7&lt;BR /&gt;access-list PHYS_access_in extended permit ip object-group DM_INLINE_NETWORK_8 object-group DM_INLINE_NETWORK_9&lt;BR /&gt;access-list PHYS_access_in extended permit ip any any&lt;BR /&gt;access-list AD_access_out extended permit ip 192.168.14.0 255.255.255.0 192.168.13.0 255.255.255.0&lt;BR /&gt;access-list AD_access_out extended permit ip any any&lt;BR /&gt;access-list AD_access_in extended permit ip any any&lt;BR /&gt;access-list HERM-PHYS_access_out extended permit ip any any&lt;BR /&gt;access-list HERM-PHYS_access_in extended permit ip any any&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 26 Oct 2018 21:53:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-5525-vlan-interface-traffic-not-working/m-p/3734019#M9219</guid>
      <dc:creator>Maddhattr</dc:creator>
      <dc:date>2018-10-26T21:53:49Z</dc:date>
    </item>
    <item>
      <title>Re: ASA 5525 vlan interface traffic not working</title>
      <link>https://community.cisco.com/t5/network-security/asa-5525-vlan-interface-traffic-not-working/m-p/3734023#M9221</link>
      <description>&lt;P&gt;In the switch config, ports 23 and 24 go to gig0/3 on each firewall? Based on the redundant config, gig0/2 on the firewall will be the active interface.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Is Q-in-Q configured on gig0/23 for a specific reason?&lt;/P&gt;
&lt;P&gt;What does spanning tree for one of the vlans look like on each switch?&lt;/P&gt;</description>
      <pubDate>Fri, 26 Oct 2018 22:08:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-5525-vlan-interface-traffic-not-working/m-p/3734023#M9221</guid>
      <dc:creator>rmfalconer</dc:creator>
      <dc:date>2018-10-26T22:08:21Z</dc:date>
    </item>
    <item>
      <title>Re: ASA 5525 vlan interface traffic not working</title>
      <link>https://community.cisco.com/t5/network-security/asa-5525-vlan-interface-traffic-not-working/m-p/3734036#M9223</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I have updated the configs for the switch ports. They no longer have spanning tree portfast disable on them. This seems to have solved the issue of ping and interface traffic. I discovered this when going through the questions you asked and checking my connections. I removed the cable to FW1 P3 and had ping all of a sudden.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;interface GigabitEthernet1/0/23&lt;BR /&gt; description "FW1 P3"&lt;BR /&gt; switchport trunk native vlan 888&lt;BR /&gt; switchport trunk allowed vlan 413-417,904&lt;BR /&gt; switchport mode trunk&lt;BR /&gt;!&lt;BR /&gt;interface GigabitEthernet1/0/24&lt;BR /&gt; description "FW2 P3"&lt;BR /&gt; switchport trunk native vlan 888&lt;BR /&gt; switchport trunk allowed vlan 413-417,904&lt;BR /&gt; switchport mode trunk&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Originally I had planned to set the interfaces as an Etherchannel but could not get that to work and figured redundant ports would be easier to configure. I left some settings on SW01 from when I had been configuring that. Now I just have to figure out how to set up a tunnel and VPN! And make some static routes. Can you point me a any good resources for that.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;For example does my route for external look correct? Ignoring the fact that the address of 40.1 is a private ip. This system is currently sitting behind another firewall.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;route ISP01 0.0.0.0 0.0.0.0 192.168.40.1 1&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Then I guess I have to work on NAT's.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 26 Oct 2018 22:51:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-5525-vlan-interface-traffic-not-working/m-p/3734036#M9223</guid>
      <dc:creator>Maddhattr</dc:creator>
      <dc:date>2018-10-26T22:51:43Z</dc:date>
    </item>
    <item>
      <title>Re: ASA 5525 vlan interface traffic not working</title>
      <link>https://community.cisco.com/t5/network-security/asa-5525-vlan-interface-traffic-not-working/m-p/3734039#M9227</link>
      <description>&lt;P&gt;Yes, that route does look correct. If you are just doing static routing, then it's pretty basic.&lt;/P&gt;
&lt;P&gt;When you do get to setting up VPN, you'll want to have routes for the VPN traffic to access internal resources. This needs the keyword 'tunneled' included. It basically differentiates between traffic going through the firewall and traffic going through VPN.&lt;/P&gt;
&lt;P&gt;Ex: route&amp;nbsp;inside&amp;nbsp;0.0.0.0 0.0.0.0 x.x.x.x&amp;nbsp;tunneled&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The Cisco site has plenty of documentation about setting up VPN. You'll want to make sure you have the proper licensing in place for the number of clients you'll need. 'Sh Ver' will tell you how many you have.&lt;/P&gt;</description>
      <pubDate>Fri, 26 Oct 2018 23:04:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-5525-vlan-interface-traffic-not-working/m-p/3734039#M9227</guid>
      <dc:creator>rmfalconer</dc:creator>
      <dc:date>2018-10-26T23:04:04Z</dc:date>
    </item>
  </channel>
</rss>

