<?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 secondary failed in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-secondary-failed/m-p/1238145#M860161</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have 2 ASA pairedup.failover state on the primary shows the secondary as "failed".Management interface is used for failover, which is up.Failover reason states inside:no Link.&lt;/P&gt;&lt;P&gt;Any reasons for this?Any directions on how to check further to bring it back to normal state.&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;</description>
    <pubDate>Mon, 11 Mar 2019 15:27:25 GMT</pubDate>
    <dc:creator>suthomas1</dc:creator>
    <dc:date>2019-03-11T15:27:25Z</dc:date>
    <item>
      <title>ASA secondary failed</title>
      <link>https://community.cisco.com/t5/network-security/asa-secondary-failed/m-p/1238145#M860161</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have 2 ASA pairedup.failover state on the primary shows the secondary as "failed".Management interface is used for failover, which is up.Failover reason states inside:no Link.&lt;/P&gt;&lt;P&gt;Any reasons for this?Any directions on how to check further to bring it back to normal state.&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 15:27:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-secondary-failed/m-p/1238145#M860161</guid>
      <dc:creator>suthomas1</dc:creator>
      <dc:date>2019-03-11T15:27:25Z</dc:date>
    </item>
    <item>
      <title>Re: ASA secondary failed</title>
      <link>https://community.cisco.com/t5/network-security/asa-secondary-failed/m-p/1238146#M860163</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;it sounds like your inside interfaces are having problems. The ASA checks all of your interfaces with a "heartbeat" to see if the standby device is fully functional. I experienced a similar issue once, it turned out the switchport that the inside interface was plugged into was having problems. Although it could be the firewall itself, don't hesitate to look at your switching infrastructure as well.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 05 May 2009 12:22:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-secondary-failed/m-p/1238146#M860163</guid>
      <dc:creator>chip.wagner</dc:creator>
      <dc:date>2009-05-05T12:22:36Z</dc:date>
    </item>
    <item>
      <title>Re: ASA secondary failed</title>
      <link>https://community.cisco.com/t5/network-security/asa-secondary-failed/m-p/1238147#M860166</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks.Assuming the switchport is having issues, will changing the switchport solve the problem &amp;amp; ASA will see secondary as standby by itself? Or will i have to physically reset the ASA after switchport is taken care of? Will there be any disruption to the ASA operation.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 05 May 2009 14:05:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-secondary-failed/m-p/1238147#M860166</guid>
      <dc:creator>suthomas1</dc:creator>
      <dc:date>2009-05-05T14:05:49Z</dc:date>
    </item>
  </channel>
</rss>

