<?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: 1522 Connectivity Issue in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/1522-connectivity-issue/m-p/1150656#M96731</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The APs shouldn't be connected to trunk ports though.  If they are, that may indeed be the problem though.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Are your APs getting DHCP addresses?  You can tell by consoling into them once they've booted.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 11 Feb 2009 22:35:13 GMT</pubDate>
    <dc:creator>jeff.kish</dc:creator>
    <dc:date>2009-02-11T22:35:13Z</dc:date>
    <item>
      <title>1522 Connectivity Issue</title>
      <link>https://community.cisco.com/t5/wireless/1522-connectivity-issue/m-p/1150654#M96729</link>
      <description>&lt;P&gt;Hi There,&lt;/P&gt;&lt;P&gt;I have 4404 WLC running 5.2,I have connected this WLC to a switch using LAG.My AP and WLC are on seprate segment.For illustration i can say Controller is on 192.168.50 and all my ap are on 142.240.83.0,Now 35 of my ap's connect to controller(i am sending dhcp option 43),but 6 of my ap's do not connect but if change the segment for these 6 ap to 142.240.82.0 than they also connect to same contoller without an issue.I am clueless why it is happening&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;</description>
      <pubDate>Sun, 04 Jul 2021 00:07:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/1522-connectivity-issue/m-p/1150654#M96729</guid>
      <dc:creator>prabhjots</dc:creator>
      <dc:date>2021-07-04T00:07:29Z</dc:date>
    </item>
    <item>
      <title>Re: 1522 Connectivity Issue</title>
      <link>https://community.cisco.com/t5/wireless/1522-connectivity-issue/m-p/1150655#M96730</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Maybe the trunk port are prunning what VLAN is/are allowed. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 11 Feb 2009 22:26:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/1522-connectivity-issue/m-p/1150655#M96730</guid>
      <dc:creator>Leo Laohoo</dc:creator>
      <dc:date>2009-02-11T22:26:59Z</dc:date>
    </item>
    <item>
      <title>Re: 1522 Connectivity Issue</title>
      <link>https://community.cisco.com/t5/wireless/1522-connectivity-issue/m-p/1150656#M96731</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The APs shouldn't be connected to trunk ports though.  If they are, that may indeed be the problem though.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Are your APs getting DHCP addresses?  You can tell by consoling into them once they've booted.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 11 Feb 2009 22:35:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/1522-connectivity-issue/m-p/1150656#M96731</guid>
      <dc:creator>jeff.kish</dc:creator>
      <dc:date>2009-02-11T22:35:13Z</dc:date>
    </item>
  </channel>
</rss>

