<?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 Vlan Select ? in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/vlan-select/m-p/2018312#M99278</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You must also be careful, because some devices may not know to request another ip address and this might cause you more issue.&amp;nbsp; Something you will need to test.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 28 Aug 2012 13:01:08 GMT</pubDate>
    <dc:creator>Scott Fella</dc:creator>
    <dc:date>2012-08-28T13:01:08Z</dc:date>
    <item>
      <title>Vlan Select ?</title>
      <link>https://community.cisco.com/t5/wireless/vlan-select/m-p/2018308#M99274</link>
      <description>&lt;P&gt;Is it possible to assign a single ssid to multiple interface groups by assigning the ssid to multiple AP groups?&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have buildings geographically dispersed that are configured with multiple vlans in interface groups so that I can maintain an addressing scheme of dhcp assigned addresses per building.&amp;nbsp; Each building is also further grouped as AP groups.&amp;nbsp; I'd like to know if by assigning the same wlan ssid to each of the &lt;/P&gt;&lt;P&gt;AP groups, will I maintain addressing integrity for each building?&amp;nbsp; I'm thinking it will work.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Do the buildings have to be outside AP range of each other to avoid problems?&lt;/P&gt;&lt;P&gt;What gotchas should I be aware of?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;5508 controller&lt;/P&gt;&lt;P&gt;7.2.110.0&amp;nbsp; code&lt;/P&gt;&lt;P&gt;6 buildings&lt;/P&gt;&lt;P&gt;6 interface groups&lt;/P&gt;&lt;P&gt;1 ssid&lt;/P&gt;</description>
      <pubDate>Sun, 04 Jul 2021 05:35:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/vlan-select/m-p/2018308#M99274</guid>
      <dc:creator>Evan Cameron</dc:creator>
      <dc:date>2021-07-04T05:35:00Z</dc:date>
    </item>
    <item>
      <title>Re: Vlan Select ?</title>
      <link>https://community.cisco.com/t5/wireless/vlan-select/m-p/2018309#M99275</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You can do this if your ap's are in local mode.or if they are in FlexConnect with the code you are running.&amp;nbsp; As far as I know, Layer 3 roaming is not supported on FlexConnect when using local switching.&amp;nbsp; So if there is a chance that a device from one building can roam to another that is configured for a different subnet, that will break.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.cisco.com/en/US/docs/wireless/controller/release/notes/crn7_2.html#wp919086" rel="nofollow"&gt;http://www.cisco.com/en/US/docs/wireless/controller/release/notes/crn7_2.html#wp919086&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 28 Aug 2012 03:00:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/vlan-select/m-p/2018309#M99275</guid>
      <dc:creator>Scott Fella</dc:creator>
      <dc:date>2012-08-28T03:00:46Z</dc:date>
    </item>
    <item>
      <title>Vlan Select ?</title>
      <link>https://community.cisco.com/t5/wireless/vlan-select/m-p/2018310#M99276</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Evan:&lt;/P&gt;&lt;P&gt;Yes you can do that. and Scott is right abotu L3 roaming. If you use local FlexConnect/Local switching then L3 roaming does not work. So you better manage your RF coverage accordingly.&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;Amjad&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: blue;"&gt;You want to say "&lt;SPAN style="color: green; text-decoration: underline; "&gt;Thank you&lt;/SPAN&gt;"? &lt;BR /&gt;&lt;SPAN style="color: red;"&gt;&lt;STRONG&gt;Don't&lt;/STRONG&gt;&lt;/SPAN&gt;. Just rate the useful answers, &lt;BR /&gt;that is more useful than "&lt;EM&gt;Thank you&lt;EM&gt;".&lt;/EM&gt;&lt;/EM&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 28 Aug 2012 08:40:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/vlan-select/m-p/2018310#M99276</guid>
      <dc:creator>Amjad Abdullah</dc:creator>
      <dc:date>2012-08-28T08:40:07Z</dc:date>
    </item>
    <item>
      <title>Vlan Select ?</title>
      <link>https://community.cisco.com/t5/wireless/vlan-select/m-p/2018311#M99277</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for confirming my belief.&amp;nbsp; I expected the L3 limitation with the expectation that an end device would not be able to&lt;/P&gt;&lt;P&gt;perform a seamless roam, but rather would re-associate to the same ssid and receive new addressing via dhcp.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 28 Aug 2012 11:57:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/vlan-select/m-p/2018311#M99277</guid>
      <dc:creator>Evan Cameron</dc:creator>
      <dc:date>2012-08-28T11:57:02Z</dc:date>
    </item>
    <item>
      <title>Vlan Select ?</title>
      <link>https://community.cisco.com/t5/wireless/vlan-select/m-p/2018312#M99278</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You must also be careful, because some devices may not know to request another ip address and this might cause you more issue.&amp;nbsp; Something you will need to test.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 28 Aug 2012 13:01:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/vlan-select/m-p/2018312#M99278</guid>
      <dc:creator>Scott Fella</dc:creator>
      <dc:date>2012-08-28T13:01:08Z</dc:date>
    </item>
  </channel>
</rss>

