<?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: Chain two FWSM contexts in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/chain-two-fwsm-contexts/m-p/803936#M1022158</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hey,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you need the cascading contexts one way to make it working is to insert a router (it can be a VRF on the MSFC) between the two context. You will then use two separate VLANs between the contexts instead of this problematic shared VLAN.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This has already been addresses in ASA software "Automatically Assigning MAC Addresses to Context Interfaces" but it still missing for the FWSM.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Has anybody infos about this last feature on FWSM ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Chris &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 14 Jun 2007 06:16:30 GMT</pubDate>
    <dc:creator>Christian Chautems</dc:creator>
    <dc:date>2007-06-14T06:16:30Z</dc:date>
    <item>
      <title>Chain two FWSM contexts</title>
      <link>https://community.cisco.com/t5/network-security/chain-two-fwsm-contexts/m-p/803931#M1022153</link>
      <description>&lt;P&gt;Hi!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is it possible to chain two contexts in one 6500 FWSM so that for example vlan60 is outside (x.y.36.98/29) for FW-one and vlan61 inside for FW-one (IP x.y.37.1/24) and vlan61 is also outside for FW-two(IP x.y.37.254/24). Vlan62 is inside(IP x.y.38.1/24) for FW-two. Outside = sec0, Inside = sec100.&lt;/P&gt;&lt;P&gt;I use no NAT. I have a PC in vlan61 with IP x.y.37.10 and it all works well when I only have FW-one configured. As soon as I go into context FW-two and starts to configure interface vlan61 FW-one stops working. The only way to get FW-one up-and-running again is to delete context FW-two.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I use FWSM-version 3.2(1)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is what I'm trying to do:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Internet-vlan60-FWone-vlan61-FWtwo-vlan62&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any ideas?&lt;/P&gt;&lt;P&gt;Can anyone try this in a lab?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Markus &lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 10:29:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/chain-two-fwsm-contexts/m-p/803931#M1022153</guid>
      <dc:creator>markus.segervall</dc:creator>
      <dc:date>2019-03-11T10:29:36Z</dc:date>
    </item>
    <item>
      <title>Re: Chain two FWSM contexts</title>
      <link>https://community.cisco.com/t5/network-security/chain-two-fwsm-contexts/m-p/803932#M1022154</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Markus &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I believe you can cascade contexts in version 3.x (you couldn't in v 2.x). What do you mean by stops working - does it stop passing traffic ? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;if you do cascade contexts then you need a static translation for all the destinations on the outside of FW-one as otherwise the classifier does not know which context to send the packet to. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jon&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 13 Jun 2007 11:59:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/chain-two-fwsm-contexts/m-p/803932#M1022154</guid>
      <dc:creator>Jon Marshall</dc:creator>
      <dc:date>2007-06-13T11:59:50Z</dc:date>
    </item>
    <item>
      <title>Re: Chain two FWSM contexts</title>
      <link>https://community.cisco.com/t5/network-security/chain-two-fwsm-contexts/m-p/803933#M1022155</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes it stop passing traffic.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I tried to configure the static translation for the FW-two inside net and the configuration of FW-one now looks like this:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;interface Vlan60&lt;/P&gt;&lt;P&gt; nameif outside&lt;/P&gt;&lt;P&gt; security-level 0&lt;/P&gt;&lt;P&gt; ip address x.y.36.98 255.255.255.248&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;interface Vlan61&lt;/P&gt;&lt;P&gt; nameif inside&lt;/P&gt;&lt;P&gt; security-level 100&lt;/P&gt;&lt;P&gt; ip address x.y.37.1 255.255.255.0&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;access-list inside-in extended permit ip any any&lt;/P&gt;&lt;P&gt;access-list outside-in extended permit icmp any any&lt;/P&gt;&lt;P&gt;pager lines 24&lt;/P&gt;&lt;P&gt;mtu outside 1500&lt;/P&gt;&lt;P&gt;mtu inside 1500&lt;/P&gt;&lt;P&gt;icmp permit any echo-reply outside&lt;/P&gt;&lt;P&gt;icmp permit any echo outside&lt;/P&gt;&lt;P&gt;icmp permit any echo inside&lt;/P&gt;&lt;P&gt;icmp permit any echo-reply inside&lt;/P&gt;&lt;P&gt;no asdm history enable&lt;/P&gt;&lt;P&gt;arp timeout 14400&lt;/P&gt;&lt;P&gt;nat (inside) 0 x.y.37.0 255.255.255.0&lt;/P&gt;&lt;P&gt;static (inside,outside) x.y.38.0 x.y.38.0 netmask 255.255.255.0&lt;/P&gt;&lt;P&gt;access-group outside-in in interface outside&lt;/P&gt;&lt;P&gt;access-group inside-in in interface inside&lt;/P&gt;&lt;P&gt;route outside 0.0.0.0 0.0.0.0 x.y.36.97 1&lt;/P&gt;&lt;P&gt;route inside x.y.38.0 255.255.255.0 x.y.37.254 1&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;With only FW-one configured I surf the Net but when I try to configure FW-two then traffic thru FW-one stops immediately.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Markus.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 13 Jun 2007 12:19:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/chain-two-fwsm-contexts/m-p/803933#M1022155</guid>
      <dc:creator>markus.segervall</dc:creator>
      <dc:date>2007-06-13T12:19:46Z</dc:date>
    </item>
    <item>
      <title>Re: Chain two FWSM contexts</title>
      <link>https://community.cisco.com/t5/network-security/chain-two-fwsm-contexts/m-p/803934#M1022156</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I could describe what I do when FW-one stops:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I write(in FWSM system):&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;int vlan 62&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;context FW-two&lt;/P&gt;&lt;P&gt; allocate-interface Vlan61&lt;/P&gt;&lt;P&gt; allocate-interface Vlan62&lt;/P&gt;&lt;P&gt; config-url disk:/FW-two.cfg&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;cha con FW-two&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;conf t&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;int vlan 61&lt;/P&gt;&lt;P&gt; nameif outside&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-&amp;gt; Then FW-one stops passing traffic. I don't even have to put any IP-address information to FW-two before FW-one stops.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is this a bug or am I doing something strange?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;(And by the way, anyone knows where to find ASDM 5.2 for FWSM?)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Markus.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 14 Jun 2007 03:10:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/chain-two-fwsm-contexts/m-p/803934#M1022156</guid>
      <dc:creator>markus.segervall</dc:creator>
      <dc:date>2007-06-14T03:10:20Z</dc:date>
    </item>
    <item>
      <title>Re: Chain two FWSM contexts</title>
      <link>https://community.cisco.com/t5/network-security/chain-two-fwsm-contexts/m-p/803935#M1022157</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Markus &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For every address you want to surf on the internet you have to have a static on fw-one for it. This is obviously not the most practical setup because in effect if you want to be able to surf to any internet site out there you would have to have static translations for every site on the internet.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is why cascading contexts to the internet is not a good thing to do. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Have i misunderstood what you are trying to do ? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jon &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 14 Jun 2007 05:46:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/chain-two-fwsm-contexts/m-p/803935#M1022157</guid>
      <dc:creator>Jon Marshall</dc:creator>
      <dc:date>2007-06-14T05:46:59Z</dc:date>
    </item>
    <item>
      <title>Re: Chain two FWSM contexts</title>
      <link>https://community.cisco.com/t5/network-security/chain-two-fwsm-contexts/m-p/803936#M1022158</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hey,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you need the cascading contexts one way to make it working is to insert a router (it can be a VRF on the MSFC) between the two context. You will then use two separate VLANs between the contexts instead of this problematic shared VLAN.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This has already been addresses in ASA software "Automatically Assigning MAC Addresses to Context Interfaces" but it still missing for the FWSM.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Has anybody infos about this last feature on FWSM ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Chris &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 14 Jun 2007 06:16:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/chain-two-fwsm-contexts/m-p/803936#M1022158</guid>
      <dc:creator>Christian Chautems</dc:creator>
      <dc:date>2007-06-14T06:16:30Z</dc:date>
    </item>
    <item>
      <title>Re: Chain two FWSM contexts</title>
      <link>https://community.cisco.com/t5/network-security/chain-two-fwsm-contexts/m-p/803937#M1022159</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks alot! So this is not yet possible in FWSM...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;At first I was going to put a vrf in between but I thought this way of sharing a vlan could be possible. Obviously not...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Markus&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 14 Jun 2007 09:52:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/chain-two-fwsm-contexts/m-p/803937#M1022159</guid>
      <dc:creator>markus.segervall</dc:creator>
      <dc:date>2007-06-14T09:52:56Z</dc:date>
    </item>
  </channel>
</rss>

