<?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 context causing issue in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-context-causing-issue/m-p/2769300#M166743</link>
    <description>&lt;P&gt;hi all&lt;/P&gt;&lt;P&gt;brief diagram:&lt;/P&gt;&lt;P&gt;PE ROUTER &amp;lt;&amp;gt; ASA &amp;lt;&amp;gt; INTERNET ROUTER &amp;lt;&amp;gt; ISP&lt;/P&gt;&lt;P&gt;we got an ASA 5525X using version 9.1.2 running security context. the ADMIN context is running a site-to-site IPsec VPN backup tunnel to our HQ.&lt;/P&gt;&lt;P&gt;when I created a new context (for static NAT and PAT) and put a nameif (i put 'outside'), it caused an outage towards our internet facing router.&lt;/P&gt;&lt;P&gt;outage meaning, ping from our management server and solarwinds NMS is dropped towards our internet router (TACACS was cut as well).&lt;/P&gt;&lt;P&gt;i tried using another public IP and other nameif (like outside1), also created ACL to allow management traffic towards the internet router but still the same.&lt;/P&gt;&lt;P&gt;when i removed the outside interface from system context, everything goes back to normal&lt;/P&gt;&lt;P&gt;is there a command that i might missed? or bug?&lt;/P&gt;</description>
    <pubDate>Tue, 12 Mar 2019 06:46:06 GMT</pubDate>
    <dc:creator>johnlloyd_13</dc:creator>
    <dc:date>2019-03-12T06:46:06Z</dc:date>
    <item>
      <title>ASA context causing issue</title>
      <link>https://community.cisco.com/t5/network-security/asa-context-causing-issue/m-p/2769300#M166743</link>
      <description>&lt;P&gt;hi all&lt;/P&gt;&lt;P&gt;brief diagram:&lt;/P&gt;&lt;P&gt;PE ROUTER &amp;lt;&amp;gt; ASA &amp;lt;&amp;gt; INTERNET ROUTER &amp;lt;&amp;gt; ISP&lt;/P&gt;&lt;P&gt;we got an ASA 5525X using version 9.1.2 running security context. the ADMIN context is running a site-to-site IPsec VPN backup tunnel to our HQ.&lt;/P&gt;&lt;P&gt;when I created a new context (for static NAT and PAT) and put a nameif (i put 'outside'), it caused an outage towards our internet facing router.&lt;/P&gt;&lt;P&gt;outage meaning, ping from our management server and solarwinds NMS is dropped towards our internet router (TACACS was cut as well).&lt;/P&gt;&lt;P&gt;i tried using another public IP and other nameif (like outside1), also created ACL to allow management traffic towards the internet router but still the same.&lt;/P&gt;&lt;P&gt;when i removed the outside interface from system context, everything goes back to normal&lt;/P&gt;&lt;P&gt;is there a command that i might missed? or bug?&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 06:46:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-context-causing-issue/m-p/2769300#M166743</guid>
      <dc:creator>johnlloyd_13</dc:creator>
      <dc:date>2019-03-12T06:46:06Z</dc:date>
    </item>
    <item>
      <title>Hi,If you are sharing</title>
      <link>https://community.cisco.com/t5/network-security/asa-context-causing-issue/m-p/2769301#M166744</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;If you are sharing physical interface for outside in these context, please check if you are using 'mac-address auto'&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Akshay Rastogi&lt;/P&gt;</description>
      <pubDate>Wed, 21 Oct 2015 14:16:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-context-causing-issue/m-p/2769301#M166744</guid>
      <dc:creator>Akshay Rastogi</dc:creator>
      <dc:date>2015-10-21T14:16:56Z</dc:date>
    </item>
    <item>
      <title>hi,you're right on the money</title>
      <link>https://community.cisco.com/t5/network-security/asa-context-causing-issue/m-p/2769302#M166745</link>
      <description>&lt;P&gt;hi,&lt;/P&gt;&lt;P&gt;you're right on the money!&lt;/P&gt;&lt;P&gt;this is already been fixed few days ago using the said command.&lt;/P&gt;</description>
      <pubDate>Wed, 21 Oct 2015 15:05:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-context-causing-issue/m-p/2769302#M166745</guid>
      <dc:creator>johnlloyd_13</dc:creator>
      <dc:date>2015-10-21T15:05:22Z</dc:date>
    </item>
  </channel>
</rss>

