<?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: Roaming issues in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/roaming-issues/m-p/494022#M103099</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Is your wirelesss network is large, you should configure a SWAN: Strutured Wireless Aware Network. This enable monitoring interference in the signals.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please, visit: &lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/products/sw/cscowork/ps3915/products_white_paper09186a00801d8630.shtml" target="_blank"&gt;http://www.cisco.com/en/US/products/sw/cscowork/ps3915/products_white_paper09186a00801d8630.shtml&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In the past, I have the same problem.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 08 Nov 2005 16:18:12 GMT</pubDate>
    <dc:creator>estebanep</dc:creator>
    <dc:date>2005-11-08T16:18:12Z</dc:date>
    <item>
      <title>Roaming issues</title>
      <link>https://community.cisco.com/t5/wireless/roaming-issues/m-p/494021#M103098</link>
      <description>&lt;P&gt;I have a customer that is having roaming issues.  The logs show the following message:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Interface Dot11Radio0, Deauthenticating Station 000f.f84e.ac6c Reason: Previous authentication no longer valid &lt;/P&gt;&lt;P&gt;Packet to client 000f.f84e.ac6c reached max retries, removing the client&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;According to Cisco could be a result of RF Interference.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The logs also show these messages:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Interface Dot11Radio0, Deauthenticating Station 000e.843b.fae9 Reason: Disassociated because sending station is leaving (or has left) BSS&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I was wondering if these too could be a result of RF Interference.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in Advance&lt;/P&gt;</description>
      <pubDate>Sun, 04 Jul 2021 18:18:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/roaming-issues/m-p/494021#M103098</guid>
      <dc:creator>psion</dc:creator>
      <dc:date>2021-07-04T18:18:17Z</dc:date>
    </item>
    <item>
      <title>Re: Roaming issues</title>
      <link>https://community.cisco.com/t5/wireless/roaming-issues/m-p/494022#M103099</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Is your wirelesss network is large, you should configure a SWAN: Strutured Wireless Aware Network. This enable monitoring interference in the signals.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please, visit: &lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/products/sw/cscowork/ps3915/products_white_paper09186a00801d8630.shtml" target="_blank"&gt;http://www.cisco.com/en/US/products/sw/cscowork/ps3915/products_white_paper09186a00801d8630.shtml&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In the past, I have the same problem.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 08 Nov 2005 16:18:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/roaming-issues/m-p/494022#M103099</guid>
      <dc:creator>estebanep</dc:creator>
      <dc:date>2005-11-08T16:18:12Z</dc:date>
    </item>
    <item>
      <title>Re: Roaming issues</title>
      <link>https://community.cisco.com/t5/wireless/roaming-issues/m-p/494023#M103100</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This message occours when a wireless client is out of range of the associated access point. This can be caused by radio interference disrupting the signal and causing blackspots, however it can also be caused simply because the network does not cover where the client is. If the client is roaming, depending on the architecture your using, you will either see an associate message from the next access point, or a 'roamed to' message. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To be certain, use the Site Survey tool and follow the client, check to see if the signal suddenly degrades (indicating interference) or if it gradualy degrades then drops out (indicating poor coverage).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Other possible causes could be that the two access points are using channels that are to close to each other (eg AP1 uses channel 11, and AP2 uses channel 10). Try and make adjacent access points use channels as far apart as possible (eg 1, 7, 11).&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 10 Nov 2005 16:03:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/roaming-issues/m-p/494023#M103100</guid>
      <dc:creator>will.shaw</dc:creator>
      <dc:date>2005-11-10T16:03:07Z</dc:date>
    </item>
    <item>
      <title>Re: Roaming issues</title>
      <link>https://community.cisco.com/t5/wireless/roaming-issues/m-p/494024#M103101</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It would be better to use 1,6,11 because 7 and 11 have overlap as well.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 07 Dec 2005 15:40:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/roaming-issues/m-p/494024#M103101</guid>
      <dc:creator>marv.rockhill</dc:creator>
      <dc:date>2005-12-07T15:40:54Z</dc:date>
    </item>
  </channel>
</rss>

