<?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 I don't really understand, in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/vlan-s-and-wism/m-p/2575375#M162358</link>
    <description>&lt;P&gt;I don't really understand, but here is my 2 cents.&lt;/P&gt;&lt;P&gt;Its best to separate wired and wireless in different subnets. &amp;nbsp;This allows for ACL's and QoS and also keeps these two type of traffic separate. VLAN ID's should be identical in each site if possible. For example, wired data, wireless data, management, wired voice, wireless voice, etc. this way it's consistent and troubleshooting is a bit easier.&lt;/P&gt;&lt;P&gt;-Scott&lt;/P&gt;</description>
    <pubDate>Fri, 09 Jan 2015 21:14:26 GMT</pubDate>
    <dc:creator>Scott Fella</dc:creator>
    <dc:date>2015-01-09T21:14:26Z</dc:date>
    <item>
      <title>VLAN's and WISM</title>
      <link>https://community.cisco.com/t5/wireless/vlan-s-and-wism/m-p/2575374#M162355</link>
      <description>&lt;P&gt;Can someone give me a simple explanation for why unique subnets would be necessary in a multi-site deployment when using WiSM?&lt;/P&gt;&lt;P&gt;Are there any other situations other than WiSM where using unique subnets as opposed to a standardized scheme would be beneficial to network design.&lt;/P&gt;&lt;P&gt;Thanks in advance for any information.&lt;/P&gt;</description>
      <pubDate>Mon, 05 Jul 2021 09:14:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/vlan-s-and-wism/m-p/2575374#M162355</guid>
      <dc:creator>snared04drummer</dc:creator>
      <dc:date>2021-07-05T09:14:51Z</dc:date>
    </item>
    <item>
      <title>I don't really understand,</title>
      <link>https://community.cisco.com/t5/wireless/vlan-s-and-wism/m-p/2575375#M162358</link>
      <description>&lt;P&gt;I don't really understand, but here is my 2 cents.&lt;/P&gt;&lt;P&gt;Its best to separate wired and wireless in different subnets. &amp;nbsp;This allows for ACL's and QoS and also keeps these two type of traffic separate. VLAN ID's should be identical in each site if possible. For example, wired data, wireless data, management, wired voice, wireless voice, etc. this way it's consistent and troubleshooting is a bit easier.&lt;/P&gt;&lt;P&gt;-Scott&lt;/P&gt;</description>
      <pubDate>Fri, 09 Jan 2015 21:14:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/vlan-s-and-wism/m-p/2575375#M162358</guid>
      <dc:creator>Scott Fella</dc:creator>
      <dc:date>2015-01-09T21:14:26Z</dc:date>
    </item>
    <item>
      <title>What you've stated I would</title>
      <link>https://community.cisco.com/t5/wireless/vlan-s-and-wism/m-p/2575376#M162360</link>
      <description>&lt;P&gt;What you've stated I would consider best practice.&lt;/P&gt;&lt;P&gt;However, my client's Cisco support rep, while in the process of trying to get them to purchase and adopt a WiSM into their network, stated that they would have to create unique VLAN's at each site, and not use a standardized scheme as you've described. &amp;nbsp;I'm trying to figure out why.&lt;/P&gt;</description>
      <pubDate>Fri, 09 Jan 2015 21:18:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/vlan-s-and-wism/m-p/2575376#M162360</guid>
      <dc:creator>snared04drummer</dc:creator>
      <dc:date>2015-01-09T21:18:27Z</dc:date>
    </item>
    <item>
      <title>Why??? It's a lack of</title>
      <link>https://community.cisco.com/t5/wireless/vlan-s-and-wism/m-p/2575377#M162362</link>
      <description>&lt;P&gt;Why??? It's a lack of understanding the difference between subnets and vlan's:) &amp;nbsp;&lt;/P&gt;&lt;P&gt;Your the consultant and its your responsibility to design the proper solution. If this means correcting a Cisco SE or even your own peer, then so be it. &amp;nbsp;At the end, your providing the solution that will work well for the customer.&amp;nbsp;&lt;/P&gt;&lt;P&gt;-Scott&lt;/P&gt;</description>
      <pubDate>Fri, 09 Jan 2015 21:24:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/vlan-s-and-wism/m-p/2575377#M162362</guid>
      <dc:creator>Scott Fella</dc:creator>
      <dc:date>2015-01-09T21:24:50Z</dc:date>
    </item>
    <item>
      <title>In today's cycle of hardware</title>
      <link>https://community.cisco.com/t5/wireless/vlan-s-and-wism/m-p/2575378#M162363</link>
      <description>&lt;P&gt;In today's cycle of hardware I would purchase 5508s. This is coming from a guy who has 6 wism2 farms ..&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;As Scoot points out. This not only best practice this is how it's done almost everywhere ! If the customer opens a tac case for an issue in the future I bet one of the remendations would be break up the vlans.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 10 Jan 2015 15:42:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/vlan-s-and-wism/m-p/2575378#M162363</guid>
      <dc:creator>George Stefanick</dc:creator>
      <dc:date>2015-01-10T15:42:12Z</dc:date>
    </item>
  </channel>
</rss>

