<?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: Firepower 2110 - FDM (sub interface not working). in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/firepower-2110-fdm-sub-interface-not-working/m-p/4066246#M1069193</link>
    <description>&lt;P&gt;Hello&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Could you please advice on how you got it sorted as I'm also facing the same challenge, screengrabs could also be handy&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
    <pubDate>Wed, 15 Apr 2020 09:40:48 GMT</pubDate>
    <dc:creator>DivineMuteta90931</dc:creator>
    <dc:date>2020-04-15T09:40:48Z</dc:date>
    <item>
      <title>Firepower 2110 - FDM (sub interface not working).</title>
      <link>https://community.cisco.com/t5/network-security/firepower-2110-fdm-sub-interface-not-working/m-p/4048542#M1067932</link>
      <description>&lt;P&gt;Hi Guys,&lt;BR /&gt;&lt;BR /&gt;Using FDM to try and configure my DIA, PE is set-up with a sub interface. Using my laptop tagged, everything working okay. From FDM though, I can't even get ICMP to the PE.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;interface Ethernet1/1&lt;/P&gt;&lt;P&gt;nameif outside&lt;/P&gt;&lt;P&gt;cts manual&lt;/P&gt;&lt;P&gt;&amp;nbsp; propagate sgt preserve-untag&lt;/P&gt;&lt;P&gt;&amp;nbsp; policy static sgt disabled trusted&lt;/P&gt;&lt;P&gt;security-level 0&lt;/P&gt;&lt;P&gt;no ip address&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;interface Ethernet1/1.3061&lt;/P&gt;&lt;P&gt;vlan 3061&lt;/P&gt;&lt;P&gt;nameif outside_sub&lt;/P&gt;&lt;P&gt;cts manual&lt;/P&gt;&lt;P&gt;&amp;nbsp; propagate sgt preserve-untag&lt;/P&gt;&lt;P&gt;&amp;nbsp; policy static sgt disabled trusted&lt;/P&gt;&lt;P&gt;security-level 0&lt;/P&gt;&lt;P&gt;ip address x.x.x.x 255.255.255.248&lt;BR /&gt;&lt;BR /&gt;Help would be appreciated &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 19 Mar 2020 08:54:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-2110-fdm-sub-interface-not-working/m-p/4048542#M1067932</guid>
      <dc:creator>Xividar</dc:creator>
      <dc:date>2020-03-19T08:54:59Z</dc:date>
    </item>
    <item>
      <title>Re: Firepower 2110 - FDM (sub interface not working).</title>
      <link>https://community.cisco.com/t5/network-security/firepower-2110-fdm-sub-interface-not-working/m-p/4048546#M1067933</link>
      <description>&lt;P&gt;The documentation is also not clear; it suggests you need to avoid naming the physical interface, if you try to do this however, you are rejected.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;"&lt;SPAN&gt;Preventing untagged packets on the physical interface—If you use subinterfaces, you typically do not also want the physical interface to pass traffic, because the physical interface passes untagged packets. Because the physical interface must be enabled for the subinterface to pass traffic, &lt;STRONG&gt;&lt;EM&gt;ensure that the physical interface does not pass traffic by not naming the interface&lt;/EM&gt;&lt;/STRONG&gt;. If you want to let the physical interface pass untagged packets, you can name the interface as usual."&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 19 Mar 2020 09:02:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-2110-fdm-sub-interface-not-working/m-p/4048546#M1067933</guid>
      <dc:creator>Xividar</dc:creator>
      <dc:date>2020-03-19T09:02:12Z</dc:date>
    </item>
    <item>
      <title>Re: Firepower 2110 - FDM (sub interface not working).</title>
      <link>https://community.cisco.com/t5/network-security/firepower-2110-fdm-sub-interface-not-working/m-p/4048905#M1067961</link>
      <description>&lt;P&gt;How is your switch interface setup that is connected to the FTD device?&amp;nbsp; If it is not a trunk already I would suggest configuring to trunk all VLANs to start with.&lt;/P&gt;</description>
      <pubDate>Thu, 19 Mar 2020 20:04:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-2110-fdm-sub-interface-not-working/m-p/4048905#M1067961</guid>
      <dc:creator>Marius Gunnerud</dc:creator>
      <dc:date>2020-03-19T20:04:09Z</dc:date>
    </item>
    <item>
      <title>Re: Firepower 2110 - FDM (sub interface not working).</title>
      <link>https://community.cisco.com/t5/network-security/firepower-2110-fdm-sub-interface-not-working/m-p/4048906#M1067962</link>
      <description>&lt;P&gt;We got it sorted, our core guys sent through wrong port info. All good &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 19 Mar 2020 20:07:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-2110-fdm-sub-interface-not-working/m-p/4048906#M1067962</guid>
      <dc:creator>Xividar</dc:creator>
      <dc:date>2020-03-19T20:07:50Z</dc:date>
    </item>
    <item>
      <title>Re: Firepower 2110 - FDM (sub interface not working).</title>
      <link>https://community.cisco.com/t5/network-security/firepower-2110-fdm-sub-interface-not-working/m-p/4066246#M1069193</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Could you please advice on how you got it sorted as I'm also facing the same challenge, screengrabs could also be handy&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Wed, 15 Apr 2020 09:40:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-2110-fdm-sub-interface-not-working/m-p/4066246#M1069193</guid>
      <dc:creator>DivineMuteta90931</dc:creator>
      <dc:date>2020-04-15T09:40:48Z</dc:date>
    </item>
  </channel>
</rss>

