<?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: FWSM &amp; vlan1 in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/fwsm-vlan1/m-p/1111997#M915313</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Craig,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I believe the reason for this is simply the enforcement of a best practice. It is assumed that VLAN1 will be used for management traffic only and not need to be firewalled. It is a best practice to move your production traffic into VLANs other than VLAN1 (though certainly not a requirement as you have seen in your case).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Mike&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 04 Aug 2008 20:58:07 GMT</pubDate>
    <dc:creator>robertson.michael</dc:creator>
    <dc:date>2008-08-04T20:58:07Z</dc:date>
    <item>
      <title>FWSM &amp; vlan1</title>
      <link>https://community.cisco.com/t5/network-security/fwsm-vlan1/m-p/1111994#M915310</link>
      <description>&lt;P&gt;Just installed the FWSM in our 6513. Was reading on its configuration. It states under assigning VLANs to the FWSM under VLAN guidelines that you can not use VLAN 1. We do use VLAN 1.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To change away from VLAN 1 would require a lot of changes on our campus edge switches. By default all switch ports were in VLAN 1 when our LAN was first setup.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What is the issue with VLAN 1 and is there nothing I can do other than start the process of moving away from using VLAN 1?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Craig&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 13:25:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/fwsm-vlan1/m-p/1111994#M915310</guid>
      <dc:creator>cef2lion2</dc:creator>
      <dc:date>2019-03-11T13:25:23Z</dc:date>
    </item>
    <item>
      <title>Re: FWSM &amp; vlan1</title>
      <link>https://community.cisco.com/t5/network-security/fwsm-vlan1/m-p/1111995#M915311</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Craig,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Unfortunately, as you noted, it is impossible to push VLAN 1 down to the FWSM.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Aside from redesigning your network to not use VLAN 1, you can try creating another SVI and routing your traffic through the MSFC before being sent down to the FWSM. So, the packet's path might look something like this:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;VLAN1---MSFC---VLAN2---FWSM---VLAN100---Internet&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;With this workaround, you can push VLAN2 and VLAN100 down to the FWSM and still keep your hosts on VLAN1.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope that helps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Mike&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 04 Aug 2008 19:48:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/fwsm-vlan1/m-p/1111995#M915311</guid>
      <dc:creator>robertson.michael</dc:creator>
      <dc:date>2008-08-04T19:48:25Z</dc:date>
    </item>
    <item>
      <title>Re: FWSM &amp; vlan1</title>
      <link>https://community.cisco.com/t5/network-security/fwsm-vlan1/m-p/1111996#M915312</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for the workaround. So what is the issue with VLAN 1?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Craig&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 04 Aug 2008 20:06:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/fwsm-vlan1/m-p/1111996#M915312</guid>
      <dc:creator>cef2lion2</dc:creator>
      <dc:date>2008-08-04T20:06:17Z</dc:date>
    </item>
    <item>
      <title>Re: FWSM &amp; vlan1</title>
      <link>https://community.cisco.com/t5/network-security/fwsm-vlan1/m-p/1111997#M915313</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Craig,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I believe the reason for this is simply the enforcement of a best practice. It is assumed that VLAN1 will be used for management traffic only and not need to be firewalled. It is a best practice to move your production traffic into VLANs other than VLAN1 (though certainly not a requirement as you have seen in your case).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Mike&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 04 Aug 2008 20:58:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/fwsm-vlan1/m-p/1111997#M915313</guid>
      <dc:creator>robertson.michael</dc:creator>
      <dc:date>2008-08-04T20:58:07Z</dc:date>
    </item>
  </channel>
</rss>

