<?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: vFMC deployment pn validation in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/vfmc-deployment-pn-validation/m-p/4080003#M1069882</link>
    <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/326046"&gt;@Marvin Rhoads&lt;/a&gt;&amp;nbsp;thanks for lending your expertise. I missed the actual feature licenses. I am looking to buy the&amp;nbsp;L-ASA5516-TAMC= PN for our 5516's. We don't have the 5516's setup for firepower services currently. Would the PN&amp;nbsp;ASA5516-TAMC= work for both modes if we were to convert?&lt;/P&gt;</description>
    <pubDate>Tue, 05 May 2020 19:49:22 GMT</pubDate>
    <dc:creator>NE Team</dc:creator>
    <dc:date>2020-05-05T19:49:22Z</dc:date>
    <item>
      <title>vFMC deployment pn validation</title>
      <link>https://community.cisco.com/t5/network-security/vfmc-deployment-pn-validation/m-p/4079752#M1069864</link>
      <description>&lt;P&gt;I am looking for help with a sanity check with a virtual deployment. Current we have the&amp;nbsp;ASA5516-FPWR-K9 and&amp;nbsp;ASA5516-CTRL-LIC licenses so I think we are good on the ASA side. I was looking to purchase the pn&amp;nbsp;&lt;SPAN class="SkuNameCart"&gt;SF-FMC-VMW-10-K9 for 4 of our physical ASA's. Should that cover our needs?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="SkuNameCart"&gt;Thanks in advance,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="SkuNameCart"&gt;Danny&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 05 May 2020 14:27:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/vfmc-deployment-pn-validation/m-p/4079752#M1069864</guid>
      <dc:creator>NE Team</dc:creator>
      <dc:date>2020-05-05T14:27:25Z</dc:date>
    </item>
    <item>
      <title>Re: vFMC deployment pn validation</title>
      <link>https://community.cisco.com/t5/network-security/vfmc-deployment-pn-validation/m-p/4079904#M1069872</link>
      <description>&lt;P&gt;That part number is Firepower Management Center for VMware with capability to manage 10 devices.&lt;/P&gt;
&lt;P&gt;It won't manage the ASAs per se but rather the Firepower service modules on them.&lt;/P&gt;
&lt;P&gt;You need to have your own ESXi server. The latest FMC release (6.6) requires 28 GB of RAM so it's a relatively heavy application.&lt;/P&gt;</description>
      <pubDate>Tue, 05 May 2020 17:10:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/vfmc-deployment-pn-validation/m-p/4079904#M1069872</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2020-05-05T17:10:08Z</dc:date>
    </item>
    <item>
      <title>Re: vFMC deployment pn validation</title>
      <link>https://community.cisco.com/t5/network-security/vfmc-deployment-pn-validation/m-p/4079952#M1069877</link>
      <description>&lt;P&gt;Hi Marvin, thanks I'm planning on hosting it in Azure. It's going to be really expensive for the size environment that we have.&lt;/P&gt;</description>
      <pubDate>Tue, 05 May 2020 18:09:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/vfmc-deployment-pn-validation/m-p/4079952#M1069877</guid>
      <dc:creator>NE Team</dc:creator>
      <dc:date>2020-05-05T18:09:31Z</dc:date>
    </item>
    <item>
      <title>Re: vFMC deployment pn validation</title>
      <link>https://community.cisco.com/t5/network-security/vfmc-deployment-pn-validation/m-p/4080003#M1069882</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/326046"&gt;@Marvin Rhoads&lt;/a&gt;&amp;nbsp;thanks for lending your expertise. I missed the actual feature licenses. I am looking to buy the&amp;nbsp;L-ASA5516-TAMC= PN for our 5516's. We don't have the 5516's setup for firepower services currently. Would the PN&amp;nbsp;ASA5516-TAMC= work for both modes if we were to convert?&lt;/P&gt;</description>
      <pubDate>Tue, 05 May 2020 19:49:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/vfmc-deployment-pn-validation/m-p/4080003#M1069882</guid>
      <dc:creator>NE Team</dc:creator>
      <dc:date>2020-05-05T19:49:22Z</dc:date>
    </item>
    <item>
      <title>Re: vFMC deployment pn validation</title>
      <link>https://community.cisco.com/t5/network-security/vfmc-deployment-pn-validation/m-p/4080196#M1069898</link>
      <description>&lt;P&gt;That part number is OK as the top level SKU for IPS, URL Filtering and AMP for the 5516-X. There is a term license that goes along with it as well. Something like "&lt;SPAN style="color: #1e76c7; font-family: Arial, Helvetica, sans-serif; font-size: 12px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: bold; letter-spacing: normal; orphans: 2; text-align: left; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; background-color: #ffffcc; text-decoration-style: initial; text-decoration-color: initial; display: inline !important; float: none;"&gt;L-ASA5516-TAMC-3Y&lt;/SPAN&gt;" (or -1Y or -5Y depending on 1, 3 or 5-year term).&lt;/P&gt;
&lt;P&gt;If you change over to run FTD then a different part number applies.&lt;/P&gt;
&lt;P&gt;I'd recommend seriously considering FTD with CDO cloud-based management.&lt;/P&gt;</description>
      <pubDate>Wed, 06 May 2020 04:29:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/vfmc-deployment-pn-validation/m-p/4080196#M1069898</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2020-05-06T04:29:14Z</dc:date>
    </item>
  </channel>
</rss>

