<?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 A sample configuration is in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/firewall-inside-interface-with-core/m-p/2723420#M176361</link>
    <description>&lt;DIV&gt;A sample configuration is attached. &amp;nbsp;I have this working in GNS3&lt;/DIV&gt;</description>
    <pubDate>Wed, 07 Oct 2015 09:57:39 GMT</pubDate>
    <dc:creator>chris noon</dc:creator>
    <dc:date>2015-10-07T09:57:39Z</dc:date>
    <item>
      <title>Firewall inside interface with Core</title>
      <link>https://community.cisco.com/t5/network-security/firewall-inside-interface-with-core/m-p/2723403#M176344</link>
      <description>&lt;P&gt;Hi,&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have nexus core with multiple vlans configured on it. Cisco asa firewall is connected with core using port-channel and trunk.&amp;nbsp;&lt;/P&gt;&lt;P&gt;How can &amp;nbsp;I make all vlans traffic routable on firewall? I will use IP address at port-channel interface? how firewall will handle vlan tags?&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 06:42:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-inside-interface-with-core/m-p/2723403#M176344</guid>
      <dc:creator>Rizwan</dc:creator>
      <dc:date>2019-03-12T06:42:09Z</dc:date>
    </item>
    <item>
      <title>You will require a sub</title>
      <link>https://community.cisco.com/t5/network-security/firewall-inside-interface-with-core/m-p/2723404#M176345</link>
      <description>&lt;P&gt;You will require a sub interface for each VLAN on the firewall, e.g.:&lt;/P&gt;&lt;P&gt;config term&lt;/P&gt;&lt;P&gt;interface portchannel 1.100 &amp;gt;&amp;gt; for vlan 100&lt;/P&gt;&lt;P&gt;encapsulation dot1q 100 &amp;gt;&amp;gt; for vlan 100&lt;/P&gt;&lt;P&gt;ip address [ip address] [mask]&lt;/P&gt;&lt;P&gt;exit&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The following document has a more in depth explanation:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;http://www.cisco.com/c/en/us/support/docs/lan-switching/inter-vlan-routing/14976-50.html&lt;/P&gt;</description>
      <pubDate>Tue, 06 Oct 2015 12:03:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-inside-interface-with-core/m-p/2723404#M176345</guid>
      <dc:creator>chris noon</dc:creator>
      <dc:date>2015-10-06T12:03:57Z</dc:date>
    </item>
    <item>
      <title>My core switch is layer-3</title>
      <link>https://community.cisco.com/t5/network-security/firewall-inside-interface-with-core/m-p/2723405#M176346</link>
      <description>&lt;P&gt;My core switch is layer-3 then and all inter-vlan routing is done by core. Is there any way to make&amp;nbsp;&lt;/P&gt;&lt;P&gt;to just route traffic to firewall instead of making sub-interface for each vlan at firewall?&lt;/P&gt;</description>
      <pubDate>Tue, 06 Oct 2015 12:09:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-inside-interface-with-core/m-p/2723405#M176346</guid>
      <dc:creator>Rizwan</dc:creator>
      <dc:date>2015-10-06T12:09:46Z</dc:date>
    </item>
    <item>
      <title>Yes, if your core switch is a</title>
      <link>https://community.cisco.com/t5/network-security/firewall-inside-interface-with-core/m-p/2723406#M176347</link>
      <description>&lt;P&gt;Yes, if your core switch is a layer 3 device you could create SVIs on the switch like so:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;config term&lt;/P&gt;&lt;P&gt;interface vlan 100 &amp;gt;&amp;gt; for vlan 100&lt;/P&gt;&lt;P&gt;ip address [IP address] [mask]&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;then apply a default route up to the firewall from the core switch:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;ip route 0.0.0.0 0.0.0.0 [interface towards firewall] [firewalls inside IP address]&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;SVI documentation:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;http://www.cisco.com/c/en/us/products/collateral/routers/1800-series-integrated-services-routers-isr/prod_white_paper0900aecd8064c9f4.html&lt;/P&gt;</description>
      <pubDate>Tue, 06 Oct 2015 12:13:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-inside-interface-with-core/m-p/2723406#M176347</guid>
      <dc:creator>chris noon</dc:creator>
      <dc:date>2015-10-06T12:13:26Z</dc:date>
    </item>
    <item>
      <title>One more question please, if</title>
      <link>https://community.cisco.com/t5/network-security/firewall-inside-interface-with-core/m-p/2723407#M176348</link>
      <description>&lt;P&gt;One more question please, if at core I have port-channel configure with firewall then in default route i will mention port-channel number or physical port interface number&amp;nbsp;&lt;SPAN style="font-size: 14.4px; line-height: normal;"&gt;[interface towards firewall] ?&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 06 Oct 2015 13:00:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-inside-interface-with-core/m-p/2723407#M176348</guid>
      <dc:creator>Rizwan</dc:creator>
      <dc:date>2015-10-06T13:00:17Z</dc:date>
    </item>
    <item>
      <title>I'm confident in saying the</title>
      <link>https://community.cisco.com/t5/network-security/firewall-inside-interface-with-core/m-p/2723408#M176349</link>
      <description>&lt;P&gt;I'm confident in saying the port channel interface.&lt;/P&gt;</description>
      <pubDate>Tue, 06 Oct 2015 13:04:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-inside-interface-with-core/m-p/2723408#M176349</guid>
      <dc:creator>chris noon</dc:creator>
      <dc:date>2015-10-06T13:04:29Z</dc:date>
    </item>
    <item>
      <title>I am facing following error</title>
      <link>https://community.cisco.com/t5/network-security/firewall-inside-interface-with-core/m-p/2723409#M176350</link>
      <description>&lt;P style="margin-left: 40px;"&gt;I am facing following error while configuring default route towards firewall with port-channel interface and physical interface both&amp;nbsp;&lt;/P&gt;&lt;P style="margin-left: 40px;"&gt;% Pin-Interface cannot be a switchport&lt;/P&gt;</description>
      <pubDate>Tue, 06 Oct 2015 13:08:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-inside-interface-with-core/m-p/2723409#M176350</guid>
      <dc:creator>Rizwan</dc:creator>
      <dc:date>2015-10-06T13:08:26Z</dc:date>
    </item>
    <item>
      <title>I will configure it on some</title>
      <link>https://community.cisco.com/t5/network-security/firewall-inside-interface-with-core/m-p/2723410#M176351</link>
      <description>&lt;P&gt;I will configure it on some lab equipment and let you know... give me some time please.&lt;/P&gt;</description>
      <pubDate>Tue, 06 Oct 2015 13:09:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-inside-interface-with-core/m-p/2723410#M176351</guid>
      <dc:creator>chris noon</dc:creator>
      <dc:date>2015-10-06T13:09:30Z</dc:date>
    </item>
    <item>
      <title>Hi Chris  Waiting for your</title>
      <link>https://community.cisco.com/t5/network-security/firewall-inside-interface-with-core/m-p/2723411#M176352</link>
      <description>&lt;P&gt;Hi Chris&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Waiting for your response&lt;/P&gt;</description>
      <pubDate>Tue, 06 Oct 2015 14:22:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-inside-interface-with-core/m-p/2723411#M176352</guid>
      <dc:creator>Rizwan</dc:creator>
      <dc:date>2015-10-06T14:22:58Z</dc:date>
    </item>
    <item>
      <title>If you are routing the vlans</title>
      <link>https://community.cisco.com/t5/network-security/firewall-inside-interface-with-core/m-p/2723412#M176353</link>
      <description>&lt;P&gt;If you are routing the vlans on the Nexus switch then you don't need subinterfaces or vlan tags on the firewall.&lt;/P&gt;&lt;P&gt;In which case your default route should use the IP address of the interface on the firewall as the next hop IP.&lt;/P&gt;&lt;P&gt;Jon&lt;/P&gt;</description>
      <pubDate>Tue, 06 Oct 2015 14:28:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-inside-interface-with-core/m-p/2723412#M176353</guid>
      <dc:creator>Jon Marshall</dc:creator>
      <dc:date>2015-10-06T14:28:30Z</dc:date>
    </item>
    <item>
      <title>Hi Jon, I have port-channel</title>
      <link>https://community.cisco.com/t5/network-security/firewall-inside-interface-with-core/m-p/2723413#M176354</link>
      <description>&lt;P&gt;Hi Jon,&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have port-channel (vPC) between&amp;nbsp;nexus and asa, similarly port-channel on firewall side.&amp;nbsp;&lt;BR /&gt;I make port-channel interface as inside interface of firewall and assigned IP on it.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Now I make default route on nexus pointing to inside interface of firewall.&amp;nbsp;&lt;/P&gt;&lt;P&gt;ip route 0.0.0.0 0.0.0.0 192.168.200.1&amp;nbsp;&lt;/P&gt;&lt;P&gt;But I am unable to ping 192.168.200.1 from nexus&lt;/P&gt;</description>
      <pubDate>Tue, 06 Oct 2015 14:37:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-inside-interface-with-core/m-p/2723413#M176354</guid>
      <dc:creator>Rizwan</dc:creator>
      <dc:date>2015-10-06T14:37:09Z</dc:date>
    </item>
    <item>
      <title>Are you running HSRP on the</title>
      <link>https://community.cisco.com/t5/network-security/firewall-inside-interface-with-core/m-p/2723414#M176355</link>
      <description>&lt;P&gt;Are you running HSRP on the Nexus side ?&lt;/P&gt;&lt;P&gt;If so can you ping the VIP or either of the physical IPs from the ASA ?&lt;/P&gt;&lt;P&gt;Jon&lt;/P&gt;</description>
      <pubDate>Tue, 06 Oct 2015 14:43:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-inside-interface-with-core/m-p/2723414#M176355</guid>
      <dc:creator>Jon Marshall</dc:creator>
      <dc:date>2015-10-06T14:43:03Z</dc:date>
    </item>
    <item>
      <title>yep, you are right Jon. I am</title>
      <link>https://community.cisco.com/t5/network-security/firewall-inside-interface-with-core/m-p/2723415#M176356</link>
      <description>&lt;P&gt;yep, you are right Jon. I am running HSRP on nexus side and unable to ping any IP address VIP or physical IP on nexus from ASA.&amp;nbsp;&lt;/P&gt;&lt;P&gt;How to configure this?&lt;/P&gt;</description>
      <pubDate>Tue, 06 Oct 2015 15:11:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-inside-interface-with-core/m-p/2723415#M176356</guid>
      <dc:creator>Rizwan</dc:creator>
      <dc:date>2015-10-06T15:11:15Z</dc:date>
    </item>
    <item>
      <title>Hi Jon, I'm waiting for your</title>
      <link>https://community.cisco.com/t5/network-security/firewall-inside-interface-with-core/m-p/2723416#M176357</link>
      <description>&lt;P&gt;Hi Jon,&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm waiting for your response. Thanks&lt;/P&gt;</description>
      <pubDate>Tue, 06 Oct 2015 15:52:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-inside-interface-with-core/m-p/2723416#M176357</guid>
      <dc:creator>Rizwan</dc:creator>
      <dc:date>2015-10-06T15:52:36Z</dc:date>
    </item>
    <item>
      <title>Sorry, thought you had sorted</title>
      <link>https://community.cisco.com/t5/network-security/firewall-inside-interface-with-core/m-p/2723417#M176358</link>
      <description>&lt;P&gt;Sorry, thought you had sorted it.&lt;/P&gt;&lt;P&gt;What troubleshooting have you done ie. are the HSRP interfaces up, are the physical interfaces up on all devices, what do the mac address tables show when you try to ping etc.&lt;/P&gt;&lt;P&gt;Jon&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 06 Oct 2015 16:00:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-inside-interface-with-core/m-p/2723417#M176358</guid>
      <dc:creator>Jon Marshall</dc:creator>
      <dc:date>2015-10-06T16:00:38Z</dc:date>
    </item>
    <item>
      <title>Everything is working on core</title>
      <link>https://community.cisco.com/t5/network-security/firewall-inside-interface-with-core/m-p/2723418#M176359</link>
      <description>&lt;P&gt;Everything is working on core just problem is connectivity between Firewall and Core.&lt;/P&gt;&lt;P&gt;I have two nexus core switches and two asa firewalls configured on failover.&amp;nbsp;&lt;/P&gt;&lt;P&gt;vPC link is up between firewall and core switches I have assigned inside IP address on port-channel interface at firewall.&amp;nbsp;&lt;/P&gt;&lt;P&gt;!&lt;BR /&gt;interface Port-channel2&lt;BR /&gt;&amp;nbsp;nameif inside&lt;BR /&gt;&amp;nbsp;security-level 100&lt;BR /&gt;&amp;nbsp;ip address 192.168.200.1 255.255.255.0 standby 192.168.200.2&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;At nexus&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;(config)# ip route 0.0.0.0 0.0.0.0 192.168.200.1&lt;/P&gt;&lt;P&gt;&amp;nbsp;ping 192.168.200.1&lt;BR /&gt;PING 192.168.200.1 (192.168.200.1): 56 data bytes&lt;BR /&gt;ping: sendto 192.168.200.1 64 chars, No route to host&lt;BR /&gt;Request 0 timed out&lt;BR /&gt;ping: sendto 192.168.200.1 64 chars, No route to host&lt;/P&gt;</description>
      <pubDate>Tue, 06 Oct 2015 16:23:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-inside-interface-with-core/m-p/2723418#M176359</guid>
      <dc:creator>Rizwan</dc:creator>
      <dc:date>2015-10-06T16:23:07Z</dc:date>
    </item>
    <item>
      <title>Hi Jon,  Any update on this?</title>
      <link>https://community.cisco.com/t5/network-security/firewall-inside-interface-with-core/m-p/2723419#M176360</link>
      <description>&lt;P&gt;Hi Jon,&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any update on this? Can you help me out?&lt;/P&gt;</description>
      <pubDate>Wed, 07 Oct 2015 05:47:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-inside-interface-with-core/m-p/2723419#M176360</guid>
      <dc:creator>Rizwan</dc:creator>
      <dc:date>2015-10-07T05:47:33Z</dc:date>
    </item>
    <item>
      <title>A sample configuration is</title>
      <link>https://community.cisco.com/t5/network-security/firewall-inside-interface-with-core/m-p/2723420#M176361</link>
      <description>&lt;DIV&gt;A sample configuration is attached. &amp;nbsp;I have this working in GNS3&lt;/DIV&gt;</description>
      <pubDate>Wed, 07 Oct 2015 09:57:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-inside-interface-with-core/m-p/2723420#M176361</guid>
      <dc:creator>chris noon</dc:creator>
      <dc:date>2015-10-07T09:57:39Z</dc:date>
    </item>
    <item>
      <title>Can you do a "show int desc"</title>
      <link>https://community.cisco.com/t5/network-security/firewall-inside-interface-with-core/m-p/2723421#M176362</link>
      <description>&lt;P&gt;Can you do a "show int desc" on the nexsus and firewall please?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Remove all public IP addresses before you post &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 07 Oct 2015 10:00:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-inside-interface-with-core/m-p/2723421#M176362</guid>
      <dc:creator>chris noon</dc:creator>
      <dc:date>2015-10-07T10:00:15Z</dc:date>
    </item>
  </channel>
</rss>

