<?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 firepower Managment in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/firepower-managment/m-p/2899668#M1031261</link>
    <description>&lt;P&gt;Dears,&lt;/P&gt;
&lt;P&gt;I am replacing the legacy firewall to new 55XX-X I have migrated the configuration but not brought it live, I have some question below.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;management 0/0 is in different ip address than a inside interface, inside and management are connecting to the core switch where routing is happening in between them ----is it ok by design perspective.???&lt;/P&gt;
&lt;P&gt;if I want to download firepower updates its the firesight that goes to the internet and gets the update then it will deployed from firsight system to firepower ------pls correct me if I m wrong ??&lt;/P&gt;
&lt;P&gt;I have not brought the inside, outside, dmz interfaces of the ASA becz it will conflict the ip's with the existing live asa , so I will connect the management port to the network and try to add the realm ( AD servers ) to start work with user agent, all communication between the firepower and AD will be through management port of the firepower?????&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;thanks&lt;/P&gt;</description>
    <pubDate>Tue, 12 Mar 2019 12:58:12 GMT</pubDate>
    <dc:creator>adamgibs7</dc:creator>
    <dc:date>2019-03-12T12:58:12Z</dc:date>
    <item>
      <title>firepower Managment</title>
      <link>https://community.cisco.com/t5/network-security/firepower-managment/m-p/2899668#M1031261</link>
      <description>&lt;P&gt;Dears,&lt;/P&gt;
&lt;P&gt;I am replacing the legacy firewall to new 55XX-X I have migrated the configuration but not brought it live, I have some question below.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;management 0/0 is in different ip address than a inside interface, inside and management are connecting to the core switch where routing is happening in between them ----is it ok by design perspective.???&lt;/P&gt;
&lt;P&gt;if I want to download firepower updates its the firesight that goes to the internet and gets the update then it will deployed from firsight system to firepower ------pls correct me if I m wrong ??&lt;/P&gt;
&lt;P&gt;I have not brought the inside, outside, dmz interfaces of the ASA becz it will conflict the ip's with the existing live asa , so I will connect the management port to the network and try to add the realm ( AD servers ) to start work with user agent, all communication between the firepower and AD will be through management port of the firepower?????&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;thanks&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 12:58:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-managment/m-p/2899668#M1031261</guid>
      <dc:creator>adamgibs7</dc:creator>
      <dc:date>2019-03-12T12:58:12Z</dc:date>
    </item>
    <item>
      <title>Hi</title>
      <link>https://community.cisco.com/t5/network-security/firepower-managment/m-p/2899669#M1031263</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;You can do it.&amp;nbsp; Firepower will communicate via management port (ASA and firepower share the same management physical port)&lt;/P&gt;
&lt;P&gt;This article about different scenarios might help.&lt;/P&gt;
&lt;P&gt;http://www.cisco.com/c/en/us/support/docs/security/ips-sensor-software-version-71/113690-ips-config-mod-00.html&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Thanks&lt;/P&gt;
&lt;P&gt;Yogesh&lt;/P&gt;</description>
      <pubDate>Sat, 09 Apr 2016 05:24:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-managment/m-p/2899669#M1031263</guid>
      <dc:creator>yogdhanu</dc:creator>
      <dc:date>2016-04-09T05:24:10Z</dc:date>
    </item>
  </channel>
</rss>

