<?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: firewall contexts in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/firewall-contexts/m-p/1383627#M731186</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for the great link. Another query though, since the firewall is in an HA mode, how do we allocate public ip address on its internet facing interface.&lt;/P&gt;&lt;P&gt;viz, would the admin context also need to be put in with ip address or is it only for the other 3 contexts interface. If so, would each context on active firewall have different public ip address and would same apply to standby firewall.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Appreciate any assistance!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 01 Feb 2010 15:51:41 GMT</pubDate>
    <dc:creator>suthomas1</dc:creator>
    <dc:date>2010-02-01T15:51:41Z</dc:date>
    <item>
      <title>firewall contexts</title>
      <link>https://community.cisco.com/t5/network-security/firewall-contexts/m-p/1383624#M731153</link>
      <description>&lt;P&gt;Gurus,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have a requirement to create 2 contexts &amp;amp; 1 admin context on a HA based ASA. The local ip range i have is 192.168.100.0 /24.&lt;/P&gt;&lt;P&gt;Internet traffic will be coming on to this context, although there will be only one single internet line and not two different ones for each context.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please help me as to how the ip assignments on these contexts must be made wrt to HA pair.A brief overall config including ip address would be very much appreciated.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank You.&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 17:03:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-contexts/m-p/1383624#M731153</guid>
      <dc:creator>suthomas1</dc:creator>
      <dc:date>2019-03-11T17:03:38Z</dc:date>
    </item>
    <item>
      <title>Re: firewall contexts</title>
      <link>https://community.cisco.com/t5/network-security/firewall-contexts/m-p/1383625#M731162</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;(EDIT): these also need to have a DMZ interface on each of them. How is that also be incorporated in this.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 31 Jan 2010 07:25:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-contexts/m-p/1383625#M731162</guid>
      <dc:creator>suthomas1</dc:creator>
      <dc:date>2010-01-31T07:25:24Z</dc:date>
    </item>
    <item>
      <title>Re: firewall contexts</title>
      <link>https://community.cisco.com/t5/network-security/firewall-contexts/m-p/1383626#M731170</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Pls. see an example here:&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://www.cisco.com/en/US/docs/security/asa/asa80/configuration/guide/examples.html#wp1009684"&gt;http://www.cisco.com/en/US/docs/security/asa/asa80/configuration/guide/examples.html#wp1009684&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-KS&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 31 Jan 2010 17:50:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-contexts/m-p/1383626#M731170</guid>
      <dc:creator>Kureli Sankar</dc:creator>
      <dc:date>2010-01-31T17:50:41Z</dc:date>
    </item>
    <item>
      <title>Re: firewall contexts</title>
      <link>https://community.cisco.com/t5/network-security/firewall-contexts/m-p/1383627#M731186</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for the great link. Another query though, since the firewall is in an HA mode, how do we allocate public ip address on its internet facing interface.&lt;/P&gt;&lt;P&gt;viz, would the admin context also need to be put in with ip address or is it only for the other 3 contexts interface. If so, would each context on active firewall have different public ip address and would same apply to standby firewall.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Appreciate any assistance!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 01 Feb 2010 15:51:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-contexts/m-p/1383627#M731186</guid>
      <dc:creator>suthomas1</dc:creator>
      <dc:date>2010-02-01T15:51:41Z</dc:date>
    </item>
    <item>
      <title>Re: firewall contexts</title>
      <link>https://community.cisco.com/t5/network-security/firewall-contexts/m-p/1383628#M731193</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Good question. We do recommend to add a standby IP for all interfaces. If you have available addresses I would add a standby IP address for the outside interface for all the contexts. Otherwise you can leave it just with the active IP. Failover will still work. Just monitoring interface will not work.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When you issue sh fail, active unit will show up with an IP address but the standby unit will show up as 0.0.0.0. That is all.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-KS&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 01 Feb 2010 16:31:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-contexts/m-p/1383628#M731193</guid>
      <dc:creator>Kureli Sankar</dc:creator>
      <dc:date>2010-02-01T16:31:41Z</dc:date>
    </item>
    <item>
      <title>Re: firewall contexts</title>
      <link>https://community.cisco.com/t5/network-security/firewall-contexts/m-p/1383629#M731201</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;thanks for the prompt help. to make it more easily digestible to me, below is the &lt;BR /&gt;sample config i have done to enact this scenario:&lt;/P&gt;&lt;P&gt;each context will have a different organisation on it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;FWA(Active) - Context 1 &amp;amp; Context 2&lt;BR /&gt;FWB(Standby) - Context 1 &amp;amp; Context 2&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Assuming public ip's to be 192.168.100.4 /29&lt;/P&gt;&lt;P&gt;Gw: 192.168.100.5&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;On FWA- context1: i assign IP 192.168.100.6 /29 on public interface&lt;BR /&gt;On FWA- context2: i assign IP 192.168.100.7 /29 on public interface&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;(Or does it mean that Context2 doesnt have to be assigned any ip or the same as Context1) ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;On FWB- context1: Unassigned&lt;BR /&gt;On FWB- context2: Unassigned&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is this correct as per my understanding of your post.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Tons of thanks to you!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 01 Feb 2010 17:17:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-contexts/m-p/1383629#M731201</guid>
      <dc:creator>suthomas1</dc:creator>
      <dc:date>2010-02-01T17:17:58Z</dc:date>
    </item>
    <item>
      <title>Re: firewall contexts</title>
      <link>https://community.cisco.com/t5/network-security/firewall-contexts/m-p/1383630#M731206</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;That is correct. You did understand it correct.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-KS&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 01 Feb 2010 17:22:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-contexts/m-p/1383630#M731206</guid>
      <dc:creator>Kureli Sankar</dc:creator>
      <dc:date>2010-02-01T17:22:19Z</dc:date>
    </item>
    <item>
      <title>Re: firewall contexts</title>
      <link>https://community.cisco.com/t5/network-security/firewall-contexts/m-p/1383631#M731210</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Ok. that means Context1 &amp;amp; Context2 will have seperate translation tables ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Thanks.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 01 Feb 2010 17:32:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-contexts/m-p/1383631#M731210</guid>
      <dc:creator>suthomas1</dc:creator>
      <dc:date>2010-02-01T17:32:22Z</dc:date>
    </item>
    <item>
      <title>Re: firewall contexts</title>
      <link>https://community.cisco.com/t5/network-security/firewall-contexts/m-p/1383632#M731217</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes that is correct. Context 1 and context 2 are two different firewalls.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-KS&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 01 Feb 2010 17:39:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-contexts/m-p/1383632#M731217</guid>
      <dc:creator>Kureli Sankar</dc:creator>
      <dc:date>2010-02-01T17:39:21Z</dc:date>
    </item>
  </channel>
</rss>

