<?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: Cisco FTD inline set support for VLAN pairs in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/cisco-ftd-inline-set-support-for-vlan-pairs/m-p/5163235#M1115224</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;Thanks a lot for your reply. We have 3 segments, and I am planning to put the FTD inline pair in all the three segments. Please find the attached diagram.&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="SHABEEBKUNHIPOCKER_0-1724163034221.png" style="width: 760px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/226716i27D67386B2CA0572/image-dimensions/760x736?v=v2" width="760" height="736" role="button" title="SHABEEBKUNHIPOCKER_0-1724163034221.png" alt="SHABEEBKUNHIPOCKER_0-1724163034221.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;I have the below concerns&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;If you take the traffic flow from server to internet, the traffic will be inspected first by the IPS layer placed in the inside segment of the ASA and then it will be inspected by the IPS layer placed in the outside interface of the ASA. Is there any way to avoid this double inspection?&amp;nbsp;&lt;/LI&gt;
&lt;LI&gt;Initially I was planning to build HA between the IPS FTDs but seems like with the above design it is not possible. If the ASA-01 is made standby from the CLI then the IPS-02 should become active which it will not as there will not be any interface failure. So in that scenario, IPS-01 and ASA-02 will be active and the traffic will be blocked. So either I need to add switches in every segment, or I will keep the IPS appliances as stand alone. Kindly advise what is the best practice.&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;Thanks&lt;/P&gt;
&lt;P&gt;Shabeeb&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 20 Aug 2024 14:19:47 GMT</pubDate>
    <dc:creator>SHABEEB KUNHIPOCKER</dc:creator>
    <dc:date>2024-08-20T14:19:47Z</dc:date>
    <item>
      <title>Cisco FTD inline set support for VLAN pairs</title>
      <link>https://community.cisco.com/t5/network-security/cisco-ftd-inline-set-support-for-vlan-pairs/m-p/5162605#M1115181</link>
      <description>&lt;P&gt;Hello Everyone,&lt;/P&gt;
&lt;P&gt;I am migrating from a ASA with SFR module to aFTD running ASA image and another FTD running inline sets. The plan is to replace ASA with FTD running ASA image and SFR with an FTD running inline sets. In the current ASA we have around 31 sub interfaces and our target is to connect the FTD (running ASA image) and FTD (IPS) to a switch , then direct the traffic to IPS using VLAN pairs. Since there are sub interfaces in the ASA we would need the same in FTD inline sets to properly direct the traffic to the IPS so that the device connectivity can be done through a switch. Does the FTD support sub interfaces to configured as inline pairs or does it have something like VLAN pairs like old Cisco IPS?. What would be the approach I should follow in such a scenario?.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Kindly advise&lt;/P&gt;
&lt;P&gt;Shabeeb&lt;/P&gt;</description>
      <pubDate>Mon, 19 Aug 2024 12:29:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cisco-ftd-inline-set-support-for-vlan-pairs/m-p/5162605#M1115181</guid>
      <dc:creator>SHABEEB KUNHIPOCKER</dc:creator>
      <dc:date>2024-08-19T12:29:30Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco FTD inline set support for VLAN pairs</title>
      <link>https://community.cisco.com/t5/network-security/cisco-ftd-inline-set-support-for-vlan-pairs/m-p/5162830#M1115201</link>
      <description>&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/td/docs/security/secure-firewall/management-center/device-config/720/management-center-device-config-72/interfaces-settings-ifcs-ips.html" target="_blank"&gt;https://www.cisco.com/c/en/us/td/docs/security/secure-firewall/management-center/device-config/720/management-center-device-config-72/interfaces-settings-ifcs-ips.html&lt;/A&gt;&lt;/P&gt;
&lt;UL class="ul" style="margin: 12px 0px; padding: 0px; border: 0px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-variant-numeric: inherit; font-variant-east-asian: inherit; font-variant-alternates: inherit; font-variant-position: inherit; font-weight: 400; font-stretch: inherit; font-size: 14px; line-height: inherit; font-family: CiscoSans, Arial, sans-serif; font-optical-sizing: inherit; font-size-adjust: inherit; font-kerning: inherit; font-feature-settings: inherit; font-variation-settings: inherit; vertical-align: baseline; list-style: outside none disc; color: #58585b; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; white-space: normal; background-color: #ffffff; text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial;"&gt;
&lt;LI id="reference_62C2A6976E334458AC1982083304A226__li_F8D9B1C4E22741C58F96245EF4D4088E_d2620e70a1310" class="li" style="margin: 0px 0px 6px; padding: 0px; border: 0px; font-style: inherit; font-variant: inherit; font-weight: 400; font-stretch: inherit; font-size: 1.4rem; line-height: 1.4em; font-family: inherit; font-optical-sizing: inherit; font-size-adjust: inherit; font-kerning: inherit; font-feature-settings: inherit; font-variation-settings: inherit; vertical-align: baseline; color: #58585b;"&gt;
&lt;P class="p" style="margin: 12px 0px; padding: 0px; border: 0px; font-style: inherit; font-variant: inherit; font-weight: 400; font-stretch: inherit; font-size: 1.4rem; line-height: 1.4em; font-family: inherit; font-optical-sizing: inherit; font-size-adjust: inherit; font-kerning: inherit; font-feature-settings: inherit; font-variation-settings: inherit; vertical-align: baseline; color: #58585b; overflow-wrap: break-word;"&gt;Inline sets and passive interfaces support physical interfaces and EtherChannels only, and cannot use VLANs or other virtual interfaces, including multi-instance chassis-defined subinterfaces.&lt;/P&gt;
&lt;/LI&gt;
&lt;LI class="li" style="margin: 0px 0px 6px; padding: 0px; border: 0px; font-style: inherit; font-variant: inherit; font-weight: 400; font-stretch: inherit; font-size: 1.4rem; line-height: 1.4em; font-family: inherit; font-optical-sizing: inherit; font-size-adjust: inherit; font-kerning: inherit; font-feature-settings: inherit; font-variation-settings: inherit; vertical-align: baseline; color: #58585b;"&gt;But you should be able to define a trunk on switch connecting to the FTD and FTD can pass the VLANs seamlessly. this works just fine. since it is a inline pair it will just propagate the vlan just fine.&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;**Please rate as helpful if this was useful**&lt;/P&gt;</description>
      <pubDate>Mon, 19 Aug 2024 20:58:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cisco-ftd-inline-set-support-for-vlan-pairs/m-p/5162830#M1115201</guid>
      <dc:creator>ccieexpert</dc:creator>
      <dc:date>2024-08-19T20:58:26Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco FTD inline set support for VLAN pairs</title>
      <link>https://community.cisco.com/t5/network-security/cisco-ftd-inline-set-support-for-vlan-pairs/m-p/5162864#M1115204</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;Thanks a lot for your response. So we need to put the IPS physically between the switch and the ASA right?.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 19 Aug 2024 21:31:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cisco-ftd-inline-set-support-for-vlan-pairs/m-p/5162864#M1115204</guid>
      <dc:creator>SHABEEB KUNHIPOCKER</dc:creator>
      <dc:date>2024-08-19T21:31:54Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco FTD inline set support for VLAN pairs</title>
      <link>https://community.cisco.com/t5/network-security/cisco-ftd-inline-set-support-for-vlan-pairs/m-p/5162877#M1115206</link>
      <description>&lt;P&gt;I am not so sure you need to try&amp;nbsp;&lt;BR /&gt;SW(trunk)-link-FTD1 IPS-only-link-FTD2 with subinterface&amp;nbsp;&lt;BR /&gt;FTD IPS-only not remove the header which include the VLAN&amp;nbsp;&lt;/P&gt;
&lt;P&gt;if it remove header then config&amp;nbsp;&lt;BR /&gt;SW(access port)-link-FTD1 IPS-only-link-FTD2&amp;nbsp;&lt;BR /&gt;here the IPS even if it remove the l2 header the traffic not drop&amp;nbsp;&lt;/P&gt;
&lt;P&gt;MHM&lt;/P&gt;</description>
      <pubDate>Mon, 19 Aug 2024 22:12:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cisco-ftd-inline-set-support-for-vlan-pairs/m-p/5162877#M1115206</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2024-08-19T22:12:37Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco FTD inline set support for VLAN pairs</title>
      <link>https://community.cisco.com/t5/network-security/cisco-ftd-inline-set-support-for-vlan-pairs/m-p/5162891#M1115209</link>
      <description>&lt;P&gt;Correct.. put the FTD in the middle and it should work just fine.&lt;/P&gt;
&lt;P&gt;**Please rate as helpful if this was useful**&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 19 Aug 2024 22:08:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cisco-ftd-inline-set-support-for-vlan-pairs/m-p/5162891#M1115209</guid>
      <dc:creator>ccieexpert</dc:creator>
      <dc:date>2024-08-19T22:08:21Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco FTD inline set support for VLAN pairs</title>
      <link>https://community.cisco.com/t5/network-security/cisco-ftd-inline-set-support-for-vlan-pairs/m-p/5163235#M1115224</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;Thanks a lot for your reply. We have 3 segments, and I am planning to put the FTD inline pair in all the three segments. Please find the attached diagram.&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="SHABEEBKUNHIPOCKER_0-1724163034221.png" style="width: 760px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/226716i27D67386B2CA0572/image-dimensions/760x736?v=v2" width="760" height="736" role="button" title="SHABEEBKUNHIPOCKER_0-1724163034221.png" alt="SHABEEBKUNHIPOCKER_0-1724163034221.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;I have the below concerns&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;If you take the traffic flow from server to internet, the traffic will be inspected first by the IPS layer placed in the inside segment of the ASA and then it will be inspected by the IPS layer placed in the outside interface of the ASA. Is there any way to avoid this double inspection?&amp;nbsp;&lt;/LI&gt;
&lt;LI&gt;Initially I was planning to build HA between the IPS FTDs but seems like with the above design it is not possible. If the ASA-01 is made standby from the CLI then the IPS-02 should become active which it will not as there will not be any interface failure. So in that scenario, IPS-01 and ASA-02 will be active and the traffic will be blocked. So either I need to add switches in every segment, or I will keep the IPS appliances as stand alone. Kindly advise what is the best practice.&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;Thanks&lt;/P&gt;
&lt;P&gt;Shabeeb&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 20 Aug 2024 14:19:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cisco-ftd-inline-set-support-for-vlan-pairs/m-p/5163235#M1115224</guid>
      <dc:creator>SHABEEB KUNHIPOCKER</dc:creator>
      <dc:date>2024-08-20T14:19:47Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco FTD inline set support for VLAN pairs</title>
      <link>https://community.cisco.com/t5/network-security/cisco-ftd-inline-set-support-for-vlan-pairs/m-p/5166325#M1115404</link>
      <description>&lt;P&gt;Hi friend&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Can we review your issue here,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Why you use ftd ips-only and ftd in series why you not use ftd and run IPS with it?&lt;/P&gt;
&lt;P&gt;Did yoh have a load traffic?&lt;/P&gt;
&lt;P&gt;MHM&lt;/P&gt;</description>
      <pubDate>Tue, 27 Aug 2024 08:10:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cisco-ftd-inline-set-support-for-vlan-pairs/m-p/5166325#M1115404</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2024-08-27T08:10:35Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco FTD inline set support for VLAN pairs</title>
      <link>https://community.cisco.com/t5/network-security/cisco-ftd-inline-set-support-for-vlan-pairs/m-p/5166328#M1115405</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;Thanks a lot for your reply. The customer currently has ASA with SFR modules. They have around 30 VPN tunnels in the firewall, and they are a bank. They would like to make sure the migration is very smooth. When we checked with local cisco team for design suggestion, they informed that FTD with ASA image + Separate FTD with IPS is the recommended design for banking customers.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 27 Aug 2024 08:16:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cisco-ftd-inline-set-support-for-vlan-pairs/m-p/5166328#M1115405</guid>
      <dc:creator>SHABEEB KUNHIPOCKER</dc:creator>
      <dc:date>2024-08-27T08:16:19Z</dc:date>
    </item>
  </channel>
</rss>

