<?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: Unable to add newly deployed FTDv on AWS to Onprem FMC in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/unable-to-add-newly-deployed-ftdv-on-aws-to-onprem-fmc/m-p/5231751#M1117943</link>
    <description>&lt;P&gt;What command are you using to add the FMC as a manager on the FTDv?&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Are you receiving any errors? If yes, please also provide the error output.&lt;/P&gt;</description>
    <pubDate>Tue, 03 Dec 2024 08:10:52 GMT</pubDate>
    <dc:creator>Marius Gunnerud</dc:creator>
    <dc:date>2024-12-03T08:10:52Z</dc:date>
    <item>
      <title>Unable to add newly deployed FTDv on AWS to Onprem FMC</title>
      <link>https://community.cisco.com/t5/network-security/unable-to-add-newly-deployed-ftdv-on-aws-to-onprem-fmc/m-p/5231546#M1117937</link>
      <description>&lt;P&gt;Hello Everyone,&lt;/P&gt;&lt;P&gt;We have recently deployed FTDv on AWS and trying to add it to on-prem FMC. Both are on same latest version. I am trying to add command on FTDv to add FMC, from AWS console but its not taking somehow.&lt;/P&gt;&lt;P&gt;Can someone plese guide urgently to fix this. Or do we need to add FMC ip, key during deployment itself but i didnt see that option anywhere.&lt;/P&gt;&lt;P&gt;Thanks in advanced.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 02 Dec 2024 17:16:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/unable-to-add-newly-deployed-ftdv-on-aws-to-onprem-fmc/m-p/5231546#M1117937</guid>
      <dc:creator>User_80617</dc:creator>
      <dc:date>2024-12-02T17:16:37Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to add newly deployed FTDv on AWS to Onprem FMC</title>
      <link>https://community.cisco.com/t5/network-security/unable-to-add-newly-deployed-ftdv-on-aws-to-onprem-fmc/m-p/5231751#M1117943</link>
      <description>&lt;P&gt;What command are you using to add the FMC as a manager on the FTDv?&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Are you receiving any errors? If yes, please also provide the error output.&lt;/P&gt;</description>
      <pubDate>Tue, 03 Dec 2024 08:10:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/unable-to-add-newly-deployed-ftdv-on-aws-to-onprem-fmc/m-p/5231751#M1117943</guid>
      <dc:creator>Marius Gunnerud</dc:creator>
      <dc:date>2024-12-03T08:10:52Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to add newly deployed FTDv on AWS to Onprem FMC</title>
      <link>https://community.cisco.com/t5/network-security/unable-to-add-newly-deployed-ftdv-on-aws-to-onprem-fmc/m-p/5231896#M1117954</link>
      <description>&lt;P&gt;In general, try to use the "configure manager add IP passkey nat" values for such environments.&lt;/P&gt;
&lt;P&gt;Make sure that both vFTD/vFMC are able to communicate to each other either by ssh into them or ping.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Sometimes small networking configuration issues in AWS where the vFTD / vFMC being in the different subnet or event network by accident can be the root of this problem.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 03 Dec 2024 13:22:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/unable-to-add-newly-deployed-ftdv-on-aws-to-onprem-fmc/m-p/5231896#M1117954</guid>
      <dc:creator>ckleopa</dc:creator>
      <dc:date>2024-12-03T13:22:39Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to add newly deployed FTDv on AWS to Onprem FMC</title>
      <link>https://community.cisco.com/t5/network-security/unable-to-add-newly-deployed-ftdv-on-aws-to-onprem-fmc/m-p/5232728#M1117984</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Got this fixed by redeploying instance with following in user data field. You also need to ensure proper device index for network interfaces else the interfaces will be tagged wrongly. Interfaces must be tagged in order, index 0: mgmt, 1: diag, 2 outside,3 inside. last 2 can be in any order.&lt;/P&gt;&lt;P&gt;#Sensor&lt;BR /&gt;{&lt;BR /&gt;"AdminPassword": "&amp;lt;your_password&amp;gt;",&lt;BR /&gt;"Hostname": "&amp;lt;your_hostname&amp;gt;",&lt;BR /&gt;"IPv6Mode": "dhcp",&lt;BR /&gt;"ManageLocally": "No",&lt;BR /&gt;"FmcIp": "&amp;lt;IP address of FMC&amp;gt;",&lt;BR /&gt;"FmcRegKey":"&amp;lt;registration_passkey&amp;gt;",&lt;BR /&gt;"FmcNatId":"&amp;lt;NAT_ID_if_required&amp;gt;"&lt;BR /&gt;}&lt;/P&gt;</description>
      <pubDate>Thu, 05 Dec 2024 06:18:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/unable-to-add-newly-deployed-ftdv-on-aws-to-onprem-fmc/m-p/5232728#M1117984</guid>
      <dc:creator>User_80617</dc:creator>
      <dc:date>2024-12-05T06:18:28Z</dc:date>
    </item>
  </channel>
</rss>

