<?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 ASA Failover setup in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-failover-setup/m-p/2717494#M190577</link>
    <description>&lt;P&gt;I am trying to setup a pair of ASA5510's in an active/passive failover.&amp;nbsp; When I issue the failover command from the secondary 5510 I see these messages&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Detected an Active mate&lt;/P&gt;&lt;P&gt;Beginning configuration replication from mate.&lt;/P&gt;&lt;P&gt;Warning: no actions specified. All actions disabled.&lt;/P&gt;&lt;P&gt;Warning: no actions specified. All actions disabled.&lt;/P&gt;&lt;P&gt;End configuration replication from mate.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;When I use "show failover | include host"&amp;nbsp; I see this&lt;/P&gt;&lt;P&gt;&amp;nbsp; This host: Secondary -&lt;STRONG&gt; Failed&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp; Other host: Primary - Active&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The secondary node seems to have all the configuration from the primary.&amp;nbsp; At the time the primary had a few VPN connections active.&amp;nbsp; Those too seemed to be reflected on the secondary.&amp;nbsp; I think the status of the secondary&amp;nbsp;node needs to&amp;nbsp;be "Standby Ready".&amp;nbsp; &lt;STRONG&gt;Can anyone tell me where I went wrong or how to troubleshoot this?&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;e0/0 is the outside interface&lt;/P&gt;&lt;P&gt;e0/1 is the inside interface&lt;/P&gt;&lt;P&gt;e0/2 and e0/3 are the common ports&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Below are the commands I used to setup failover on the two nodes.&amp;nbsp; Outside IP addresses are fictional.&lt;/P&gt;&lt;P&gt;&lt;U&gt;On Primary node&lt;/U&gt;&lt;/P&gt;&lt;P&gt;interface Ethernet0/0&lt;/P&gt;&lt;P&gt;&amp;nbsp;mac-address 0003.000b.0001 standby 0003.000b.0002&lt;/P&gt;&lt;P&gt;&amp;nbsp;nameif outside&lt;/P&gt;&lt;P&gt;&amp;nbsp;security-level 0&lt;/P&gt;&lt;P&gt;&amp;nbsp;ip address 18.174.151.249 255.255.255.0 standby 18.174.151.152&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;interface Ethernet0/1&lt;/P&gt;&lt;P&gt;&amp;nbsp;mac-address 0003.000a.0001 standby 0003.000a.0002&lt;/P&gt;&lt;P&gt;&amp;nbsp;nameif inside&lt;/P&gt;&lt;P&gt;&amp;nbsp;security-level 100&lt;/P&gt;&lt;P&gt;&amp;nbsp;ip address 172.16.190.249 255.255.255.0 standby 172.16.190.149&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;interface Redundant1&lt;/P&gt;&lt;P&gt;&amp;nbsp;description LAN/STATE Failover Interface&lt;/P&gt;&lt;P&gt;&amp;nbsp;member-interface Ethernet0/2&lt;/P&gt;&lt;P&gt;&amp;nbsp;member-interface Ethernet0/3&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;failover&lt;/P&gt;&lt;P&gt;failover lan unit primary&lt;/P&gt;&lt;P&gt;failover lan interface FailoverLink Redundant1&lt;/P&gt;&lt;P&gt;failover polltime unit msec 200 holdtime msec 800&lt;/P&gt;&lt;P&gt;failover polltime interface msec 500 holdtime 5&lt;/P&gt;&lt;P&gt;failover link FailoverLink Redundant1&lt;/P&gt;&lt;P&gt;failover interface ip FailoverLink 192.168.168.173 255.255.255.252 standby 192.168.168.174&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;U&gt;On Secondary Node&lt;/U&gt;&lt;/P&gt;&lt;P&gt;Interface e0/2&lt;/P&gt;&lt;P&gt;No shut&lt;/P&gt;&lt;P&gt;Interface e0/3&lt;/P&gt;&lt;P&gt;No shut&lt;/P&gt;&lt;P&gt;Interface Redundant 1&lt;/P&gt;&lt;P&gt;&amp;nbsp;Member-interface et 0/2&lt;/P&gt;&lt;P&gt;&amp;nbsp;Member-interface et 0/3&lt;/P&gt;&lt;P&gt;Failover lan unit secondary&lt;/P&gt;&lt;P&gt;Failover lan interface FailoverLink Redundant1&lt;/P&gt;&lt;P&gt;failover interface ip FailoverLink 192.168.168.173 255.255.255.252 standby 192.168.168.174&lt;/P&gt;&lt;P&gt;failover&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 12 Mar 2019 06:07:27 GMT</pubDate>
    <dc:creator>BILL DUNN</dc:creator>
    <dc:date>2019-03-12T06:07:27Z</dc:date>
    <item>
      <title>ASA Failover setup</title>
      <link>https://community.cisco.com/t5/network-security/asa-failover-setup/m-p/2717494#M190577</link>
      <description>&lt;P&gt;I am trying to setup a pair of ASA5510's in an active/passive failover.&amp;nbsp; When I issue the failover command from the secondary 5510 I see these messages&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Detected an Active mate&lt;/P&gt;&lt;P&gt;Beginning configuration replication from mate.&lt;/P&gt;&lt;P&gt;Warning: no actions specified. All actions disabled.&lt;/P&gt;&lt;P&gt;Warning: no actions specified. All actions disabled.&lt;/P&gt;&lt;P&gt;End configuration replication from mate.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;When I use "show failover | include host"&amp;nbsp; I see this&lt;/P&gt;&lt;P&gt;&amp;nbsp; This host: Secondary -&lt;STRONG&gt; Failed&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp; Other host: Primary - Active&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The secondary node seems to have all the configuration from the primary.&amp;nbsp; At the time the primary had a few VPN connections active.&amp;nbsp; Those too seemed to be reflected on the secondary.&amp;nbsp; I think the status of the secondary&amp;nbsp;node needs to&amp;nbsp;be "Standby Ready".&amp;nbsp; &lt;STRONG&gt;Can anyone tell me where I went wrong or how to troubleshoot this?&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;e0/0 is the outside interface&lt;/P&gt;&lt;P&gt;e0/1 is the inside interface&lt;/P&gt;&lt;P&gt;e0/2 and e0/3 are the common ports&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Below are the commands I used to setup failover on the two nodes.&amp;nbsp; Outside IP addresses are fictional.&lt;/P&gt;&lt;P&gt;&lt;U&gt;On Primary node&lt;/U&gt;&lt;/P&gt;&lt;P&gt;interface Ethernet0/0&lt;/P&gt;&lt;P&gt;&amp;nbsp;mac-address 0003.000b.0001 standby 0003.000b.0002&lt;/P&gt;&lt;P&gt;&amp;nbsp;nameif outside&lt;/P&gt;&lt;P&gt;&amp;nbsp;security-level 0&lt;/P&gt;&lt;P&gt;&amp;nbsp;ip address 18.174.151.249 255.255.255.0 standby 18.174.151.152&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;interface Ethernet0/1&lt;/P&gt;&lt;P&gt;&amp;nbsp;mac-address 0003.000a.0001 standby 0003.000a.0002&lt;/P&gt;&lt;P&gt;&amp;nbsp;nameif inside&lt;/P&gt;&lt;P&gt;&amp;nbsp;security-level 100&lt;/P&gt;&lt;P&gt;&amp;nbsp;ip address 172.16.190.249 255.255.255.0 standby 172.16.190.149&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;interface Redundant1&lt;/P&gt;&lt;P&gt;&amp;nbsp;description LAN/STATE Failover Interface&lt;/P&gt;&lt;P&gt;&amp;nbsp;member-interface Ethernet0/2&lt;/P&gt;&lt;P&gt;&amp;nbsp;member-interface Ethernet0/3&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;failover&lt;/P&gt;&lt;P&gt;failover lan unit primary&lt;/P&gt;&lt;P&gt;failover lan interface FailoverLink Redundant1&lt;/P&gt;&lt;P&gt;failover polltime unit msec 200 holdtime msec 800&lt;/P&gt;&lt;P&gt;failover polltime interface msec 500 holdtime 5&lt;/P&gt;&lt;P&gt;failover link FailoverLink Redundant1&lt;/P&gt;&lt;P&gt;failover interface ip FailoverLink 192.168.168.173 255.255.255.252 standby 192.168.168.174&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;U&gt;On Secondary Node&lt;/U&gt;&lt;/P&gt;&lt;P&gt;Interface e0/2&lt;/P&gt;&lt;P&gt;No shut&lt;/P&gt;&lt;P&gt;Interface e0/3&lt;/P&gt;&lt;P&gt;No shut&lt;/P&gt;&lt;P&gt;Interface Redundant 1&lt;/P&gt;&lt;P&gt;&amp;nbsp;Member-interface et 0/2&lt;/P&gt;&lt;P&gt;&amp;nbsp;Member-interface et 0/3&lt;/P&gt;&lt;P&gt;Failover lan unit secondary&lt;/P&gt;&lt;P&gt;Failover lan interface FailoverLink Redundant1&lt;/P&gt;&lt;P&gt;failover interface ip FailoverLink 192.168.168.173 255.255.255.252 standby 192.168.168.174&lt;/P&gt;&lt;P&gt;failover&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 06:07:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-failover-setup/m-p/2717494#M190577</guid>
      <dc:creator>BILL DUNN</dc:creator>
      <dc:date>2019-03-12T06:07:27Z</dc:date>
    </item>
    <item>
      <title>Hi,I think possibly</title>
      <link>https://community.cisco.com/t5/network-security/asa-failover-setup/m-p/2717495#M190582</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I think possibly monitoring on one of the Data interfaces on this Ha are failing.&lt;/P&gt;&lt;P&gt;Check "show failover state" to find the interface which is failing.&lt;/P&gt;&lt;P&gt;Also , as you are using the redundant interface for failover , use a switch for connecting the failover interface.&lt;/P&gt;&lt;P&gt;Thanks and Regards,&lt;/P&gt;&lt;P&gt;Vibhor Amrodia&lt;/P&gt;</description>
      <pubDate>Tue, 16 Jun 2015 13:30:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-failover-setup/m-p/2717495#M190582</guid>
      <dc:creator>Vibhor Amrodia</dc:creator>
      <dc:date>2015-06-16T13:30:26Z</dc:date>
    </item>
  </channel>
</rss>

