<?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: ASA management over IPsec VPN in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-management-over-ipsec-vpn/m-p/3810836#M1065630</link>
    <description>&lt;P&gt;Thanks Josue,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;But what will happen when the secondary(Standby) firewall initiates a traffic to a tacacs server for authentication, which is hosted over the vpn tunnel.&lt;/P&gt;&lt;P&gt;The solution you have provided will only work in one direction, from remote site to secondary firewall.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I heard of new feature in 9.5 version , &lt;SPAN&gt;Separate routing table for management-only interfaces , can we apply this concept here &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;if yes , please explain .&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;</description>
    <pubDate>Wed, 27 Feb 2019 12:56:45 GMT</pubDate>
    <dc:creator>GN974</dc:creator>
    <dc:date>2019-02-27T12:56:45Z</dc:date>
    <item>
      <title>ASA management over IPsec VPN</title>
      <link>https://community.cisco.com/t5/network-security/asa-management-over-ipsec-vpn/m-p/3195786#M1065627</link>
      <description>&lt;P&gt;Hi There!&lt;/P&gt;
&lt;P&gt;Has anyone configured a dedicated management IPsec tunnel for ASA management which is in Active / Standby mode?&lt;/P&gt;
&lt;P&gt;For a standalone device it is working fine as per the documentation by applying the management-access inside command etc...&lt;/P&gt;
&lt;P&gt;However, if I use a failover pair the tunnel is building up only the primary ASA, the Secondary device shows it as a "Standby" tunnel.&lt;/P&gt;
&lt;P&gt;I am able to ping / ssh to the primary ASA's inside interface, but not to the Secondary one. The secondary actually receives the traffic, however it is doing a route lookup and sending towards to the "outside" where the tunnel is actually in "Standby".&amp;nbsp;&lt;/P&gt;
&lt;P&gt;My goal would be that both devices are reachable from the management systems over the VPN, so it can&amp;nbsp;health checked / snmp polled / sshd&amp;nbsp;etc... Like if it were managed over a physical interface.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 14:27:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-management-over-ipsec-vpn/m-p/3195786#M1065627</guid>
      <dc:creator>attilafejes</dc:creator>
      <dc:date>2020-02-21T14:27:37Z</dc:date>
    </item>
    <item>
      <title>Re: ASA management over IPsec VPN</title>
      <link>https://community.cisco.com/t5/network-security/asa-management-over-ipsec-vpn/m-p/3196239#M1065628</link>
      <description>&lt;P&gt;Hi&lt;SPAN class="UserName lia-user-name lia-user-rank-New-Member lia-component-message-view-widget-author-username"&gt;,&lt;A id="link_14" class="lia-link-navigation lia-page-link lia-user-name-link" href="https://supportforums.cisco.com/t5/user/viewprofilepage/user-id/360040" target="_self"&gt;&lt;/A&gt; &lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You are right. The traffic will get to the standby unit and will try to be routed over the outside.&lt;BR /&gt;In order to fix this, you need to NAT the remote traffic to the inside interface of the primary ASA so the traffic will be returned over the inside network.&lt;BR /&gt;&lt;BR /&gt;Remote site: 192.168.2.0/24&lt;BR /&gt;Inside network of ASA's: 192.168.1.0/24&lt;BR /&gt;Inside inteface ip address standby ASA: 192.168.1.2&lt;BR /&gt;&lt;BR /&gt;object network Remote_site&lt;BR /&gt;network 192.168.2.0 255.255.255.0&lt;BR /&gt;object network standby_ASA&lt;BR /&gt;host 192.168.1.2&lt;BR /&gt;&lt;BR /&gt;nat (outside,inside) source dynamic Remote_site interface destination static Stanby_ASA Stanby_ASA&lt;BR /&gt;&lt;BR /&gt;management-access inside&lt;BR /&gt;ssh 192.168.2.0 255.255.255.0 inside&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Rate if it helps.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Josue Brenes&lt;BR /&gt;TAC - VPN Engineer.&lt;/P&gt;</description>
      <pubDate>Tue, 10 Oct 2017 02:39:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-management-over-ipsec-vpn/m-p/3196239#M1065628</guid>
      <dc:creator>Josue Brenes</dc:creator>
      <dc:date>2017-10-10T02:39:03Z</dc:date>
    </item>
    <item>
      <title>Re: ASA management over IPsec VPN</title>
      <link>https://community.cisco.com/t5/network-security/asa-management-over-ipsec-vpn/m-p/3196383#M1065629</link>
      <description>&lt;P&gt;Thanks for the reply Josue! I need to check it in my lab. I will test it soon and get back to you with the results.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards, Attila&lt;/P&gt;</description>
      <pubDate>Tue, 10 Oct 2017 10:44:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-management-over-ipsec-vpn/m-p/3196383#M1065629</guid>
      <dc:creator>attilafejes</dc:creator>
      <dc:date>2017-10-10T10:44:18Z</dc:date>
    </item>
    <item>
      <title>Re: ASA management over IPsec VPN</title>
      <link>https://community.cisco.com/t5/network-security/asa-management-over-ipsec-vpn/m-p/3810836#M1065630</link>
      <description>&lt;P&gt;Thanks Josue,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;But what will happen when the secondary(Standby) firewall initiates a traffic to a tacacs server for authentication, which is hosted over the vpn tunnel.&lt;/P&gt;&lt;P&gt;The solution you have provided will only work in one direction, from remote site to secondary firewall.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I heard of new feature in 9.5 version , &lt;SPAN&gt;Separate routing table for management-only interfaces , can we apply this concept here &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;if yes , please explain .&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;</description>
      <pubDate>Wed, 27 Feb 2019 12:56:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-management-over-ipsec-vpn/m-p/3810836#M1065630</guid>
      <dc:creator>GN974</dc:creator>
      <dc:date>2019-02-27T12:56:45Z</dc:date>
    </item>
  </channel>
</rss>

