<?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 2100 Sub-Interfaces in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/firepower-2100-sub-interfaces/m-p/3823799#M949003</link>
    <description>&lt;P&gt;Thanks for the info. It turned out that I had a native VLAN on the trunk port. Once I removed that native VLAN, I was able to ping the sub-interfaces.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Much appreciated.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Best, ~zK&lt;/P&gt;</description>
    <pubDate>Thu, 21 Mar 2019 16:02:56 GMT</pubDate>
    <dc:creator>zekebashi</dc:creator>
    <dc:date>2019-03-21T16:02:56Z</dc:date>
    <item>
      <title>FirePower 2100 Sub-Interfaces</title>
      <link>https://community.cisco.com/t5/network-security/firepower-2100-sub-interfaces/m-p/3822438#M949001</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We purchased several FirewPower 2100s but not using the FTD; however, we are only using the hosted ASA. I was trying to create sub-interfaces on the ASA and was able to. The ASA's config show the sub-interfaces. I spent hours&amp;nbsp; just trying to ping the sub-interface with no success. I copied the same configuration to another ASA (not hosted on a FirewPower) and was able to ping the sub-interface.&amp;nbsp; When I issue this command "sh eth-uplink detail expand" on the FXOS, it doesn't show the sub-interfaces.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;My question does the FirePower 2100 have limitations in supporting sub-interfaces/Etherchannling?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks in advance,&lt;/P&gt;
&lt;P&gt;~zK&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 16:57:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-2100-sub-interfaces/m-p/3822438#M949001</guid>
      <dc:creator>zekebashi</dc:creator>
      <dc:date>2020-02-21T16:57:55Z</dc:date>
    </item>
    <item>
      <title>Re: FirePower 2100 Sub-Interfaces</title>
      <link>https://community.cisco.com/t5/network-security/firepower-2100-sub-interfaces/m-p/3822616#M949002</link>
      <description>Subinterfaces will not be shown in FXOS, as it is not supported there for this case. Subinterfaces are configured in ASA. &lt;BR /&gt;You can check the physical/port-channel interface status on FCM, operational status should be up, also check switch side configuration for allowed vlans.</description>
      <pubDate>Wed, 20 Mar 2019 07:57:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-2100-sub-interfaces/m-p/3822616#M949002</guid>
      <dc:creator>Ilkin</dc:creator>
      <dc:date>2019-03-20T07:57:16Z</dc:date>
    </item>
    <item>
      <title>Re: FirePower 2100 Sub-Interfaces</title>
      <link>https://community.cisco.com/t5/network-security/firepower-2100-sub-interfaces/m-p/3823799#M949003</link>
      <description>&lt;P&gt;Thanks for the info. It turned out that I had a native VLAN on the trunk port. Once I removed that native VLAN, I was able to ping the sub-interfaces.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Much appreciated.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Best, ~zK&lt;/P&gt;</description>
      <pubDate>Thu, 21 Mar 2019 16:02:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-2100-sub-interfaces/m-p/3823799#M949003</guid>
      <dc:creator>zekebashi</dc:creator>
      <dc:date>2019-03-21T16:02:56Z</dc:date>
    </item>
  </channel>
</rss>

