<?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: FMC path to the internet in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/fmc-path-to-the-internet/m-p/5546867#M1125013</link>
    <description>&lt;P&gt;How about SCC/cdFMC instead?&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 20 Apr 2026 18:56:06 GMT</pubDate>
    <dc:creator>ahollifield</dc:creator>
    <dc:date>2026-04-20T18:56:06Z</dc:date>
    <item>
      <title>FMC path to the internet</title>
      <link>https://community.cisco.com/t5/network-security/fmc-path-to-the-internet/m-p/5546789#M1125010</link>
      <description>&lt;P&gt;I'm designing a standard FMC + FTD HA topology and trying to determine the best way to give the FMC internet access for Smart Licensing, AMP cloud, and VDB updates.&lt;/P&gt;&lt;P&gt;If I route the FMC's outbound traffic through the FTD data plane, it creates a "chicken-and-egg" scenario: the FMC cannot reach the internet to license itself or get updates until the FTD is fully deployed and passing traffic.&lt;/P&gt;&lt;P&gt;Is the standard real-world practice to just push a basic "bootstrap" config to the FTDs first so the FMC can get online? Or do most enterprise environments put the FMC on a completely separate firewall/ISP connection so it doesn't rely on the very FTDs it is managing?&lt;/P&gt;&lt;P&gt;Thanks for the input!&lt;/P&gt;</description>
      <pubDate>Mon, 20 Apr 2026 13:27:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/fmc-path-to-the-internet/m-p/5546789#M1125010</guid>
      <dc:creator>5010</dc:creator>
      <dc:date>2026-04-20T13:27:01Z</dc:date>
    </item>
    <item>
      <title>Re: FMC path to the internet</title>
      <link>https://community.cisco.com/t5/network-security/fmc-path-to-the-internet/m-p/5546867#M1125013</link>
      <description>&lt;P&gt;How about SCC/cdFMC instead?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 20 Apr 2026 18:56:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/fmc-path-to-the-internet/m-p/5546867#M1125013</guid>
      <dc:creator>ahollifield</dc:creator>
      <dc:date>2026-04-20T18:56:06Z</dc:date>
    </item>
    <item>
      <title>Re: FMC path to the internet</title>
      <link>https://community.cisco.com/t5/network-security/fmc-path-to-the-internet/m-p/5546890#M1125016</link>
      <description>&lt;P&gt;The FMC has an evaluation period of 90 days before it stops being able to deploy changes.&lt;/P&gt;&lt;P&gt;That should leave you enough time to get everything configured. I have never seen a deployment using another device for internet access than the device the FMC is managing.&lt;/P&gt;&lt;P&gt;Just make sure that the FMC can reach the FTD management IP without going through the firewall.&lt;/P&gt;</description>
      <pubDate>Mon, 20 Apr 2026 20:11:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/fmc-path-to-the-internet/m-p/5546890#M1125016</guid>
      <dc:creator>beepmeep</dc:creator>
      <dc:date>2026-04-20T20:11:01Z</dc:date>
    </item>
  </channel>
</rss>

