<?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: Manage Interface Configuration Reservation in Active/Standy - ASA in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/manage-interface-configuration-reservation-in-active-standy-asa/m-p/4822137#M1099922</link>
    <description>&lt;P&gt;If you do not have L2 connectivity between the two sites then an ASA active/standby HA setup is probably not the way you should go.&amp;nbsp; Could you describe your network in more detail and what your end goal or expected result is?&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Is one DC active and the other a disaster recovery site?&lt;/LI&gt;
&lt;LI&gt;if both are active does one site use the other for access to all other network resources / users?&lt;/LI&gt;
&lt;LI&gt;Do you have the ability to set up a dedicated L2 connection for the ASA HA...if this is an absolute requirement?&lt;/LI&gt;
&lt;/UL&gt;</description>
    <pubDate>Wed, 26 Apr 2023 12:11:03 GMT</pubDate>
    <dc:creator>Marius Gunnerud</dc:creator>
    <dc:date>2023-04-26T12:11:03Z</dc:date>
    <item>
      <title>Manage Interface Configuration Reservation in Active/Standy - ASA</title>
      <link>https://community.cisco.com/t5/network-security/manage-interface-configuration-reservation-in-active-standy-asa/m-p/4822104#M1099914</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;
&lt;P&gt;I have two ASA FirePower-2140 in Active/Standby Configuration.&lt;/P&gt;
&lt;P&gt;I need to configure one IP addres for management in FirePower-1 and other distinct IP address for management in FirePower-2 because I need to access both devices independently via HTTP and SSH. So, I need this configuration:&lt;/P&gt;
&lt;P&gt;FirePower-2140-ASA-1# show running-config interface management 1/1&lt;BR /&gt;!&lt;BR /&gt;interface Management1/1&lt;BR /&gt;management-only&lt;BR /&gt;nameif management&lt;BR /&gt;security-level 100&lt;BR /&gt;ip address 10.140.7.65 255.255.255.128&lt;/P&gt;
&lt;P&gt;FirePower-2140-ASA-2# show running-config interface management 1/1&lt;BR /&gt;!&lt;BR /&gt;interface Management1/1&lt;BR /&gt;management-only&lt;BR /&gt;nameif management&lt;BR /&gt;security-level 100&lt;BR /&gt;ip address 10.140.7.165 255.255.255.128 &lt;BR /&gt;FirePower-2140-ASA#&lt;/P&gt;
&lt;P&gt;However, due to config syncronization from Active to Standby device, management IP address for FirePower-2140-ASA-2 change to management IP address configured in&amp;nbsp;FirePower-2140-ASA-1. In addition, is not possible to configure a standby IP addres for managemente interface because both IPs are in different networks.&lt;/P&gt;
&lt;P&gt;Is there any way to avoid this issue?&lt;/P&gt;</description>
      <pubDate>Wed, 26 Apr 2023 11:30:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/manage-interface-configuration-reservation-in-active-standy-asa/m-p/4822104#M1099914</guid>
      <dc:creator>4kalak4</dc:creator>
      <dc:date>2023-04-26T11:30:30Z</dc:date>
    </item>
    <item>
      <title>Re: Manage Interface Configuration Reservation in Active/Standy - ASA</title>
      <link>https://community.cisco.com/t5/network-security/manage-interface-configuration-reservation-in-active-standy-asa/m-p/4822113#M1099915</link>
      <description>&lt;P&gt;Why do you want to do this?&amp;nbsp; What is your end goal by having a management IP in a different subnet on the standby unit?&amp;nbsp; When using the same interface there is no way around it.&amp;nbsp; Also, you should not be managing the ASAs separately when they are in HA configuration as this will put the configuration out of sync and cause issues.&lt;/P&gt;
&lt;P&gt;Optionally, you could configure a second interface with an IP and standby IP in a different subnet and manage the ASA via this interface.&amp;nbsp; This is not recommended though.&lt;/P&gt;</description>
      <pubDate>Wed, 26 Apr 2023 11:37:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/manage-interface-configuration-reservation-in-active-standy-asa/m-p/4822113#M1099915</guid>
      <dc:creator>Marius Gunnerud</dc:creator>
      <dc:date>2023-04-26T11:37:39Z</dc:date>
    </item>
    <item>
      <title>Re: Manage Interface Configuration Reservation in Active/Standy - ASA</title>
      <link>https://community.cisco.com/t5/network-security/manage-interface-configuration-reservation-in-active-standy-asa/m-p/4822117#M1099917</link>
      <description>&lt;P&gt;Different subnet for&amp;nbsp; &amp;nbsp;management interface? Why you config it in this way?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 26 Apr 2023 11:47:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/manage-interface-configuration-reservation-in-active-standy-asa/m-p/4822117#M1099917</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2023-04-26T11:47:34Z</dc:date>
    </item>
    <item>
      <title>Re: Manage Interface Configuration Reservation in Active/Standy - ASA</title>
      <link>https://community.cisco.com/t5/network-security/manage-interface-configuration-reservation-in-active-standy-asa/m-p/4822121#M1099919</link>
      <description>&lt;P&gt;Hi Marius,&lt;/P&gt;
&lt;P&gt;The main reason is due to network design limitation. We have two different management networks, one in a data center (10.140.7.0/25) and the other (10.140.7.128/25) in a different data center location.&lt;/P&gt;
&lt;P&gt;Devices in both networks can comunicate one with other via different gateways. For example, gateway for&amp;nbsp;10.140.7.0/25 network is 10.140.7.1 and gateway for&amp;nbsp;10.140.7.128/25 is 10.140.7.129. So, as you can conclude, is necessary that FirePower-1 have configured&amp;nbsp;10.140.7.1 for gateway management and FirePower-2 have configured 10.140.7.129 for gateway management.&lt;/P&gt;</description>
      <pubDate>Wed, 26 Apr 2023 11:55:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/manage-interface-configuration-reservation-in-active-standy-asa/m-p/4822121#M1099919</guid>
      <dc:creator>4kalak4</dc:creator>
      <dc:date>2023-04-26T11:55:00Z</dc:date>
    </item>
    <item>
      <title>Re: Manage Interface Configuration Reservation in Active/Standy - ASA</title>
      <link>https://community.cisco.com/t5/network-security/manage-interface-configuration-reservation-in-active-standy-asa/m-p/4822137#M1099922</link>
      <description>&lt;P&gt;If you do not have L2 connectivity between the two sites then an ASA active/standby HA setup is probably not the way you should go.&amp;nbsp; Could you describe your network in more detail and what your end goal or expected result is?&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Is one DC active and the other a disaster recovery site?&lt;/LI&gt;
&lt;LI&gt;if both are active does one site use the other for access to all other network resources / users?&lt;/LI&gt;
&lt;LI&gt;Do you have the ability to set up a dedicated L2 connection for the ASA HA...if this is an absolute requirement?&lt;/LI&gt;
&lt;/UL&gt;</description>
      <pubDate>Wed, 26 Apr 2023 12:11:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/manage-interface-configuration-reservation-in-active-standy-asa/m-p/4822137#M1099922</guid>
      <dc:creator>Marius Gunnerud</dc:creator>
      <dc:date>2023-04-26T12:11:03Z</dc:date>
    </item>
    <item>
      <title>Re: Manage Interface Configuration Reservation in Active/Standy - ASA</title>
      <link>https://community.cisco.com/t5/network-security/manage-interface-configuration-reservation-in-active-standy-asa/m-p/4822141#M1099924</link>
      <description>&lt;P&gt;I have idea here it can work for you&lt;/P&gt;
&lt;P&gt;Use two interface one for each subnet, so even if the config is sync you can reach the Asa that have right subnet.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 26 Apr 2023 12:17:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/manage-interface-configuration-reservation-in-active-standy-asa/m-p/4822141#M1099924</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2023-04-26T12:17:40Z</dc:date>
    </item>
    <item>
      <title>Re: Manage Interface Configuration Reservation in Active/Standy - ASA</title>
      <link>https://community.cisco.com/t5/network-security/manage-interface-configuration-reservation-in-active-standy-asa/m-p/4822154#M1099927</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;Yes, It could be a possible solution. Not elegant but functional.&lt;/P&gt;
&lt;P&gt;In addition, in my network design, I only have two links for data; one for inside and the other for outside. So, I think it doesn't make sense configure monitored managed interfaces for failover. For example, if management interface in FirePower-1 comes down is not neccesary to make failover to the standby device if data interfaces are up.&lt;/P&gt;
&lt;P&gt;What is your oppinion about it?&lt;/P&gt;</description>
      <pubDate>Wed, 26 Apr 2023 12:36:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/manage-interface-configuration-reservation-in-active-standy-asa/m-p/4822154#M1099927</guid>
      <dc:creator>4kalak4</dc:creator>
      <dc:date>2023-04-26T12:36:27Z</dc:date>
    </item>
    <item>
      <title>Re: Manage Interface Configuration Reservation in Active/Standy - ASA</title>
      <link>https://community.cisco.com/t5/network-security/manage-interface-configuration-reservation-in-active-standy-asa/m-p/4822157#M1099928</link>
      <description>&lt;P&gt;Sorry I was must mention that you need to not monitor both mgmt interfaces.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks&amp;nbsp;&lt;/P&gt;
&lt;P&gt;MHM&lt;/P&gt;</description>
      <pubDate>Wed, 26 Apr 2023 12:39:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/manage-interface-configuration-reservation-in-active-standy-asa/m-p/4822157#M1099928</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2023-04-26T12:39:30Z</dc:date>
    </item>
  </channel>
</rss>

