<?xml version="1.0" encoding="UTF-8"?>

<rss version="2.0" xmlns:blogChannel="http://backend.userland.com/blogChannelModule">

<channel>
<title>Recurring 802.11a Dual-Band Lockups (Cisco Aironet, Dell) in Wireless Networking</title>
<link>http://www.dslreports.com/forum/r20914116</link>
<description></description>
<language>en</language>
<pubDate>Wed, 11 Nov 2009 04:02:29 EDT</pubDate>
<lastBuildDate>Wed, 11 Nov 2009 04:02:29 EDT</lastBuildDate>

<item>
<title>Re: Recurring 802.11a Dual-Band Lockups (Cisco Aironet, Dell)</title>
<link>http://www.dslreports.com/forum/remark,20933842</link>
<description><![CDATA[<A HREF="/useremail/u/229804"><b>B</b></A> : Very good; thanks!  I may get a chance to try this later this afternoon.<br><br>Edit: Windows is weird -- I finally found the location where it caches SSIDs.  It stores them in the binary data of entries at<br><br>HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WZCSVC\Parameters\Interfaces\{some-long-hex-sequence-ID -of-which-the-freakin-registry-is-so-fond-in-this-case-NIC-ID}<br><br>In there are names of the form "Static#0000", "Static#0008", etc.  Each of these binary entries includes the SSID in question (plaintext) and who knows what else (apparently WEP keys but not WPA keys).  It would be nice to find the documentation for these reg keys.<br><br>-- B<br><small>--<br>In a realm outside causality and function</small>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,20933842</guid>
<pubDate>Mon, 11 Aug 2008 14:10:30 EDT</pubDate>
</item>

<item>
<title>Re: Recurring 802.11a Dual-Band Lockups (Cisco Aironet, Dell)</title>
<link>http://www.dslreports.com/forum/remark,20933831</link>
<description><![CDATA[<A HREF="/useremail/u/1520629"><b>tubbynet</b></A> : typically, corporations will use the same SSID for both (a) and (g) bands (at least thats how they had me deploy them).  in some instances i have delineated between (a) and (g) only for the sake of using (a) for wireless voice (cisco 7921) and (g) for wireless data.  this shouldn't be an issue, but i'm trying to determine if we're fighting configuration or ios version issues.<br><br>you may try to remove your current SSID in windows, remove the SSID config from the dot11Radio1 interface, and see what happens.  additionally, try the (a) active/(g) disabled and see what happens.<br><br>if one of the above two works, at least you may run two different SSIDs so that those who are messing with tri-band cards don't have the same issue.<br><br>q.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,20933831</guid>
<pubDate>Mon, 11 Aug 2008 14:08:10 EDT</pubDate>
</item>

<item>
<title>Re: Recurring 802.11a Dual-Band Lockups (Cisco Aironet, Dell)</title>
<link>http://www.dslreports.com/forum/remark,20933720</link>
<description><![CDATA[<A HREF="/useremail/u/229804"><b>B</b></A> : <div class="bquote"><small>said by  tubbynet <A HREF="/useremail/u/1520629"><IMG SRC="http://i.dslr.net/bb/profile.gif" ALT="See Profile" BORDER=0 WIDTH=16 HEIGHT=11></A> :</small><br><br>it looks like you have the configuration applied to the Dot11Radio1 interface for the SSID as well.  is there any specific reason for this? </div>Well, yeah, the way I originally set it up I had the same SSID set for both bands.  Is that a no-no?  Do most places use two SSIDs, e.g., "CompanyWLAN-g" and "CompanyWLAN-a" ?  (I don't think I've ever seen that.)<br><br>In any case, on the latest iterations of my testing I removed the SSID from the .a radio settings, as mentioned in my OP.<br><br><div class="bquote">  are you planning to use 802.11a for other clients? </div>Not really; the clients will always have 802.11g, though they may have dual-band cards, so I thought I should leave both radios running.  More efficient use of spectrum, resiliency, etc.<br><br><div class="bquote"> have you tried enabling a only (disabling b/g) and see if everything manifests?  </div>Nope, not yet, but that's not a bad idea for testing.<br><br><div class="bquote">have you cleared any "cached" SSIDs in your wireless utility?</div>Again, nope but not a bad idea.  I did try to figure out where Windows keeps/caches associations between SSIDs and particular bands or other info (channel, etc.), if it even does this, but was unsuccessful.  All it seems to care about / remember is the SSID per se.... but if it really is caching something funny stemming from my original connection state then this idea might clear things up!  (I suppose even better would be changing the AP's SSID just in case Windows caching is perniciously persistent even after deleting the SSID...)<br><br>-- B<br><small>--<br>In a realm outside causality and function</small>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,20933720</guid>
<pubDate>Mon, 11 Aug 2008 13:43:40 EDT</pubDate>
</item>

<item>
<title>Re: Recurring 802.11a Dual-Band Lockups (Cisco Aironet, Dell)</title>
<link>http://www.dslreports.com/forum/remark,20933649</link>
<description><![CDATA[<A HREF="/useremail/u/1520629"><b>tubbynet</b></A> : it looks like you have the configuration applied to the Dot11Radio1 interface for the SSID as well.  is there any specific reason for this?  are you planning to use 802.11a for other clients?  have you tried enabling a only (disabling b/g) and see if everything manifests?  have you cleared any "cached" SSIDs in your wireless utility?<br><br>q.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,20933649</guid>
<pubDate>Mon, 11 Aug 2008 13:29:45 EDT</pubDate>
</item>

<item>
<title>Re: Recurring 802.11a Dual-Band Lockups (Cisco Aironet, Dell)</title>
<link>http://www.dslreports.com/forum/remark,20933561</link>
<description><![CDATA[<A HREF="/useremail/u/229804"><b>B</b></A> : <div class="bquote">Cisco IOS Software, C1240 Software (C1240-K9W7-M), Version 12.4(3g)JA1, RELEASE SOFTWARE (fc1)</div>But everything works once I disable 802.11a <b>at the client side</b>.  That is, this problem doesn't occur when I force my client side to use 802.11b/g only.<br><br>I don't understand how any of the AP timeouts come into play -- the 802.11a radio's completely off at the AP.<br><br>Any theory on this?  (Thanks for the input to date.)<br><br>-- B<br><small>--<br>In a realm outside causality and function</small>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,20933561</guid>
<pubDate>Mon, 11 Aug 2008 13:11:13 EDT</pubDate>
</item>

<item>
<title>Re: Recurring 802.11a Dual-Band Lockups (Cisco Aironet, Dell)</title>
<link>http://www.dslreports.com/forum/remark,20933252</link>
<description><![CDATA[<A HREF="/useremail/u/1520629"><b>tubbynet</b></A> : <textarea name="code" class="text" cols=50 rows=10>dot11 activity-timeout unknown default 60000&#012;dot11 activity-timeout client default 60000&#012;dot11 activity-timeout repeater default 60000&#012;dot11 activity-timeout workgroup-bridge default 60000&#012;dot11 activity-timeout bridge default 60000&#012;</textarea><!--end code block--><br>i don't think that i've ever set something like this up before (i usually do multi-AP deployments using a WLC), and the defaults have always worked well for me.  i can see where this is an issue as if there is an activity timeout (or say the station associates but will not pull dhcp, etc) that may lead to the drop packet condition<br><br><textarea name="code" class="text" cols=50 rows=10>packet retries 128 drop-packet&#012;</textarea><!--end code block--><br>i assume this means repeat a packet send 128 times before dropping the packet?<br>if so, i really think you are dealing with some sort of timeout issues causing packet loss.<br><br>additionally, what code are you running?<br><br>q.<br>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,20933252</guid>
<pubDate>Mon, 11 Aug 2008 12:16:28 EDT</pubDate>
</item>

<item>
<title>Re: Recurring 802.11a Dual-Band Lockups (Cisco Aironet, Dell)</title>
<link>http://www.dslreports.com/forum/remark,20932000</link>
<description><![CDATA[<A HREF="/useremail/u/229804"><b>B</b></A> : Yes, originally I did use the web GUI.  (Coincidentally or not, one of the AP's GUIs is acting poorly under Seamonkey lately; it seems like the browser is screwing up the Javascript that loads settings when clicking, for example, the SSID name).<br><br>I then used the telnet CLI to copy and save the configuration settings.  I may have also set some parameters via the CLI, but I don't think I did.<br><br>Come to think of it, I may have tweaked that timeout feature (drop packet) when trying to avoid this ongoing (as posted) problem, wherein it thinks the signal is too weak.  The idea was to NOT drop the station merely because it didn't echo quickly enough.  It didn't appear to help much though.<br><br>Still looking for earlier config samples...<br><br>-- B<br><small>--<br>In a realm outside causality and function</small>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,20932000</guid>
<pubDate>Mon, 11 Aug 2008 05:21:00 EDT</pubDate>
</item>

<item>
<title>Re: Recurring 802.11a Dual-Band Lockups (Cisco Aironet, Dell)</title>
<link>http://www.dslreports.com/forum/remark,20915941</link>
<description><![CDATA[<A HREF="/useremail/u/1520629"><b>tubbynet</b></A> : i'm curious, did you use the web-based application to configure the access point?<br>something seems fishy about the dot11 timeout features.  something strikes me as this is not doing its job correctly.<br>if you did not use the web utility, where did you pull the information for some of the config used?<br><br>q.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,20915941</guid>
<pubDate>Thu, 07 Aug 2008 18:13:14 EDT</pubDate>
</item>

<item>
<title>Re: Recurring 802.11a Dual-Band Lockups (Cisco Aironet, Dell)</title>
<link>http://www.dslreports.com/forum/remark,20915924</link>
<description><![CDATA[<A HREF="/useremail/u/229804"><b>B</b></A> : Sure.  I wasn't going to fill up the thread unless someone asked.  Thank you!<br><br>I can't access the APs right now, but here's one of the last configs I have (unfortunately the second 802.11a radio was already turned off):<br><br><div class="bquote">XXXX_AP1#show run<br>Building configuration...<br><br>Current configuration : 2156 bytes<br>!<br>version 12.4<br>no service pad<br>service timestamps debug datetime msec<br>service timestamps log datetime msec<br>service password-encryption<br>!<br>hostname XXXX_AP1<br>!<br>enable secret 5 $xxxx<br>!<br>no aaa new-model<br>!<br>resource policy<br>!<br>ip subnet-zero<br>!<br>!<br>dot11 activity-timeout unknown default 60000<br>dot11 activity-timeout client default 60000<br>dot11 activity-timeout repeater default 60000<br>dot11 activity-timeout workgroup-bridge default 60000<br>dot11 activity-timeout bridge default 60000<br>!<br>dot11 ssid xxxxxxxxxxxxxxxxxxxxxxx<br>   authentication open<br>   authentication key-management wpa<br>   guest-mode<br>   infrastructure-ssid optional<br>   wpa-psk ascii 7 xxxxxxxxxxxxxxxxxxx<br>   information-element ssidl<br>!<br>dot11 network-map<br>power inline negotiation prestandard source<br>!<br>!<br>username Cisco privilege 15 password 7 xxxxxxxxxxxxxxxxx<br>!<br>bridge irb<br>!<br>!<br>interface Dot11Radio0<br> no ip address<br> no ip route-cache<br> !<br> encryption mode ciphers tkip<br> !<br> ssid xxxxxxxxxxxxxxxxxxxxxxx<br> !<br> packet retries 128 drop-packet<br> channel 2462<br> station-role root<br> bridge-group 1<br> bridge-group 1 subscriber-loop-control<br> bridge-group 1 block-unknown-source<br> no bridge-group 1 source-learning<br> no bridge-group 1 unicast-flooding<br> bridge-group 1 spanning-disabled<br>!<br>interface Dot11Radio1<br> no ip address<br> no ip route-cache<br> shutdown<br> !<br> encryption mode ciphers tkip<br> !<br> ssid xxxxxxxxxxxxxxxxxxxxxxx<br> !<br> dfs band 3 block<br> packet retries 128 drop-packet<br> channel dfs<br> station-role root<br> bridge-group 1<br> bridge-group 1 subscriber-loop-control<br> bridge-group 1 block-unknown-source<br> no bridge-group 1 source-learning<br> no bridge-group 1 unicast-flooding<br> bridge-group 1 spanning-disabled<br>!<br>interface FastEthernet0<br> no ip address<br> no ip route-cache<br> duplex auto<br> speed auto<br> bridge-group 1<br> no bridge-group 1 source-learning<br> bridge-group 1 spanning-disabled<br>!<br>interface BVI1<br> ip address 192.168.10.xxx 255.255.255.0<br> no ip route-cache<br>!<br>ip default-gateway 192.168.10.1<br>ip http server<br>no ip http secure-server<br>ip http help-path &raquo;<A HREF="http://www.cisco.com/warp/public/779/smbiz/prodconfig/help/eag" >www.cisco.com/warp/public/779/sm&middot;&middot;&middot;help/eag</A><br>bridge 1 route ip<br>!<br>!<br>!<br>line con 0<br>line vty 0 4<br> login local<br>!<br>end<br><br>XXXX_AP1#<br><br></div>-- B<br><small>--<br>In a realm outside causality and function</small>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,20915924</guid>
<pubDate>Thu, 07 Aug 2008 18:10:19 EDT</pubDate>
</item>

<item>
<title>Re: Recurring 802.11a Dual-Band Lockups (Cisco Aironet, Dell)</title>
<link>http://www.dslreports.com/forum/remark,20915878</link>
<description><![CDATA[<A HREF="/useremail/u/1520629"><b>tubbynet</b></A> : not too be picky, but would you mind posting the configuration of the AP when both the A and G spectrums are live and active?<br><br>q.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,20915878</guid>
<pubDate>Thu, 07 Aug 2008 18:01:34 EDT</pubDate>
</item>

<item>
<title>Recurring 802.11a Dual-Band Lockups (Cisco Aironet, Dell)</title>
<link>http://www.dslreports.com/forum/remark,20914116</link>
<description><![CDATA[<A HREF="/useremail/u/229804"><b>B</b></A> : Can someone assist?  This has stumped me.<br><br>Access Point: Cisco Aironet 1240AG.<br><br>SSID associated on both bands, 802.11a and 802.11b/g.<br><br>Client: Dell Latitude with Dell Wireless 1490 Dual Band card<br><br>OS: XP SP2<br><br>WPA/TKIP<br><br>WZC manages connection.<br><br>I can associate for some time between 10 seconds and an hour before things just... stop working.  The connection <b>appears</b> to be valid -- the system tray icon shows a connected status on the desired SSID -- but the connection doesn't work, no ping/ICMP, etc.  Sometimes, but not always, errors shown in the log (below) act as if the station has lost radio signal, but I'm right near the AP and have tried it with two different units.  Sometimes these errors do NOT appear during such lockups.<br><br>But what <b>does</b> work is if I go into the client NIC and <b>disable</b> 802.11a at the client.  Then the connection becomes rock solid.<br><br>The kicker: this situation applies <b>even when on the Access Point the 802.11a radio is completely disabled and removed from the SSID scope</b>.<br><br>It's as if the <b>client</b> side keeps thinking that 802.11a is valid for the SSID and keeps flapping between the two, even though one band is completely off at the AP.  (Yes, I know the log shows only 1 radio involved.)  Any thoughts?<br><br>-- B<br><br>(Some errors may stem from testing:)<br><div class="bquote">9&#9;Jul 3 21:23:23.078&#9;Information&#9;Interface Dot11Radio0, Deauthenticating Station xxxx.xxx.xxx.b27 Reason: Previous authentication no longer valid<br><br>Interface Dot11Radio0, Deauthenticating Station xxxx.xxxx.xxxx Reason: Previous authentication no longer valid<br>10&#9;Jul 3 21:23:23.077&#9;Warning&#9;Packet to client xxx.xxxx.xx27 reached max retries, removing the client<br>11&#9;Jul 3 21:18:57.686&#9;Information&#9;Interface Dot11Radio0, Station AP yyy.yyy.ceb Reassociated KEY_MGMT[WPA PSK]<br>12&#9;Jul 3 21:17:10.969&#9;Information&#9;Interface Dot11Radio0, Deauthenticating Station xxxx.xxxx.x082 Reason: Sending station has left the BSS<br>13&#9;Jul 3 21:16:59.048&#9;Information&#9;Interface Dot11Radio0, Deauthenticating Station xxx.xxx.xxxceb Reason: Sending station has left the BSS<br>14&#9;Jul 3 21:07:38.622&#9;Information&#9;Interface Dot11Radio0, Station AP xxx.xxx.b27 Associated KEY_MGMT[WPA PSK]<br>15&#9;Jul 3 21:07:38.228&#9;Debugging&#9;Station xxx.xxx.b27  Authentication failed<br>16&#9;Jul 3 21:07:37.344&#9;Information&#9;Interface Dot11Radio0, Deauthenticating Station xxx.xxx.b27 Reason: Sending station has left the BSS<br>17&#9;Jul 3 21:00:43.874&#9;Information&#9;Interface Dot11Radio0, Station AP xxx.xxx.b27 Associated KEY_MGMT[WPA PSK]<br>18&#9;Jul 3 21:00:43.609&#9;Information&#9;Interface Dot11Radio0, Deauthenticating Station xxx.xxx.b27 Reason: Sending station has left the BSS<br>19&#9;Jul 3 20:37:55.003&#9;Information&#9;Interface Dot11Radio0, Station AP xxx.xxx.b27 Associated KEY_MGMT[WPA PSK]<br>20&#9;Jul 3 20:37:54.959&#9;Information&#9;Interface Dot11Radio0, Deauthenticating Station xxx.xxx.b27 Reason: Sending station has left the BSS<br></div><br><small>--<br>In a realm outside causality and function</small>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,20914116</guid>
<pubDate>Thu, 07 Aug 2008 12:58:55 EDT</pubDate>
</item>

</channel>
</rss>
