<?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 About the event that cannot communicate with Active machine after ASA Failover in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/about-the-event-that-cannot-communicate-with-active-machine/m-p/3906534#M5702</link>
    <description>&lt;P&gt;I set Failover on ASA, but the following events occur.&lt;/P&gt;&lt;P&gt;If you have similar experience, I would appreciate it if you could tell me the cause and the solution.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;■ ASA Failover Problems&lt;BR /&gt;・ After Act-Stby is switched from ASA # 1 to ASA # 2 by Failover due to link down, communication such as ping from other devices does not reach ASA # 2.&lt;BR /&gt;* It can see your opponent on the ASA # 2 arp table.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;・ After switching to Act-Stby, if It&lt;SPAN&gt;&amp;nbsp;ping from each multi-context on Act side (ASA # 2), ping will be returned. Then It can ping from other devices.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;However, it does not return even if pinged from the admin context. It can't SSH into the admin context.&lt;BR /&gt;* The admin context is the admin port only.&lt;/P&gt;</description>
    <pubDate>Fri, 21 Feb 2020 17:23:28 GMT</pubDate>
    <dc:creator>HITOSHIYAMADA8041</dc:creator>
    <dc:date>2020-02-21T17:23:28Z</dc:date>
    <item>
      <title>About the event that cannot communicate with Active machine after ASA Failover</title>
      <link>https://community.cisco.com/t5/network-security/about-the-event-that-cannot-communicate-with-active-machine/m-p/3906534#M5702</link>
      <description>&lt;P&gt;I set Failover on ASA, but the following events occur.&lt;/P&gt;&lt;P&gt;If you have similar experience, I would appreciate it if you could tell me the cause and the solution.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;■ ASA Failover Problems&lt;BR /&gt;・ After Act-Stby is switched from ASA # 1 to ASA # 2 by Failover due to link down, communication such as ping from other devices does not reach ASA # 2.&lt;BR /&gt;* It can see your opponent on the ASA # 2 arp table.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;・ After switching to Act-Stby, if It&lt;SPAN&gt;&amp;nbsp;ping from each multi-context on Act side (ASA # 2), ping will be returned. Then It can ping from other devices.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;However, it does not return even if pinged from the admin context. It can't SSH into the admin context.&lt;BR /&gt;* The admin context is the admin port only.&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 17:23:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/about-the-event-that-cannot-communicate-with-active-machine/m-p/3906534#M5702</guid>
      <dc:creator>HITOSHIYAMADA8041</dc:creator>
      <dc:date>2020-02-21T17:23:28Z</dc:date>
    </item>
  </channel>
</rss>

