<?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 admin context cluster IP not reachable in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-admin-context-cluster-ip-not-reachable/m-p/3690562#M197227</link>
    <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://community.cisco.com/t5/security-documents/management-interface-in-the-asa-does-not-allow-the-traffic-to/tac-p/3690559#M5919" target="_blank"&gt;https://community.cisco.com/t5/security-documents/management-interface-in-the-asa-does-not-allow-the-traffic-to/tac-p/3690559#M5919&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Fri, 17 Aug 2018 17:47:22 GMT</pubDate>
    <dc:creator>telesign1</dc:creator>
    <dc:date>2018-08-17T17:47:22Z</dc:date>
    <item>
      <title>ASA admin context cluster IP not reachable</title>
      <link>https://community.cisco.com/t5/network-security/asa-admin-context-cluster-ip-not-reachable/m-p/2629208#M197226</link>
      <description>&lt;P&gt;I have a multi-context firewall configured and have recently lost the ability to log into the admin context cluster IP. I can still log into the physical interface IP of each firewall. I receive the below log message. I have two clusters and one of them is doing this. The other is working properly.&amp;nbsp;Has anyone else had this issue?&lt;/P&gt;&lt;P&gt;NOTE: I used to be able to change the cluster master and it would start working again. Now it works for a short time after changing the cluster master, and then starts producing this log and no connectivity. Actually, if I change the cluster master and log into the cluster IP before it stops working again, that session will stay up as long as I don't log out. Any new connections will produce the below message.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;%ASA-4-418001: Through-the-device packet to/from management-only network is denied: tcp src Management:10.2.2.142/51264 dst Management:10.1.1.110/22&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 05:28:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-admin-context-cluster-ip-not-reachable/m-p/2629208#M197226</guid>
      <dc:creator>MARK BAKER</dc:creator>
      <dc:date>2019-03-12T05:28:29Z</dc:date>
    </item>
    <item>
      <title>Re: ASA admin context cluster IP not reachable</title>
      <link>https://community.cisco.com/t5/network-security/asa-admin-context-cluster-ip-not-reachable/m-p/3690562#M197227</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://community.cisco.com/t5/security-documents/management-interface-in-the-asa-does-not-allow-the-traffic-to/tac-p/3690559#M5919" target="_blank"&gt;https://community.cisco.com/t5/security-documents/management-interface-in-the-asa-does-not-allow-the-traffic-to/tac-p/3690559#M5919&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 17 Aug 2018 17:47:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-admin-context-cluster-ip-not-reachable/m-p/3690562#M197227</guid>
      <dc:creator>telesign1</dc:creator>
      <dc:date>2018-08-17T17:47:22Z</dc:date>
    </item>
  </channel>
</rss>

