Wireless client unpredicatably roaming to other AP's

Hi all,
I just recently started working in a new environment and they asked me to look at some weird wireless issues that are occuring. It is a campus environment, but all wireless issues seem to be occurring in the newest building, which just opened in May. Symptoms are extreme slowness accessing the network for a client and the client next to him has no problems at all. Also, I've been doing large file copies for testing, and on occassion I'll start out with good speed, maybe 2 Mbit/sec copy speed and in the middle of the copy with me sitting in the same spot, i'll automatically associate to another access point and it will drop to maybe 120 Kbit/sec. I was not walking around.
All AP's in the environment are 1142's and they were forced to full power on the radios. The first thing I did to troubleshoot was turn on RRM. I would have expected some of the radios to drop power levels, but all are still at 1. Is this expected? Do I need to reboot or reset AP's to accept the change in RRM?
Pretty much all wireless cards are Intel Centrino Ultimate-N 6300's running what I think are the latest drivers from Intel.
I'm centering my troubleshooting on a couple of AP's that I can pretty consistently re-create the slowness with. My testing with these AP's shows that they are able to detect like 20-25 other AP's. Is this normal? It seems to me that I should just have to turn down the radios and I should stop seeing all of these AP's. I thought RRM would have an affect, but it appears not.
I'm kind of a wireless noob, so any thoughts or help would be appreciated. I can upload any info to help, i didn't want to dump the sho run-config up here as it's pretty big..
Thanks for any help or suggestions.
Steve

All AP's in the environment are 1142's and they were forced to full power on the radios. The first thing I did to troubleshoot was turn on RRM. I would have expected some of the radios to drop power levels, but all are still at 1. Is this expected? Do I need to reboot or reset AP's to accept the change in RRM?
RRM will monitor every 600 seconds (default).
My testing with these AP's shows that they are able to detect like 20-25 other AP's. Is this normal?
Sounds like you have 802.11b channel interferrence to me. Disable the 802.11b radio (just to test) and see if you get any result. If you do, enable it back but disable 802.11b data rates. Enable 802.11g data rates.

Similar Messages

Routing issues roaming wireless clients?

Hello,
I have a site with wireless roaming printers that have static ip addresses and can roam throughout the building. Several times an hour the print server (in another building / subnet) cannot ping the printer therefore cannot send its print job. Whats odd is that they can ping the printer from the associated AP and can ping from a laptop associated to the same AP. Communication can go down from the server to the printer(s) for several minutes and then just reconnect. I see syn packets leaving the printer but not getting any syn/ack back. I also cannot ping the printer from a different subnet / my vpn connection. Is there any issues with roaming wireless clients and routing protocols / spanning tree that could cause a problem? I can only imagine with mac addresses moving from one AP to another that something could break. The AP's are 1210's with b radios running 12.3(2)JA2.
Thanks in advance.

Hi
Thanks for ur reply the problem has been taken care of by configuring the smartports as others and getting the arp inspection disabled

Wireless Clients getting DHCP IP from other WLAN

Hi,
My client has a wireless setup consisting of a WLC 2112 and about 7 1131AG LWAPPs. There are two SSIDs, say CORP(mapped to VLAN 900) and GUEST(mapped to VLAN 901). Wireless clients get IP through DHCP. DHCP IP is configured in the Dynamic interface.
The problem is sometimes (not always), clients connecting to SSID CORP get a DHCP IP assigned for GUEST VLAN(VLAN 901).
Since it is happening randomly, clueless as to what is causing the problem.
Any inputs?
Regards
Gnan.
P.S Just to add though this could be irrelevant, only after making VLAN ID of the admin interface and AP Manager interface as '0', the APs could talk to the WLC and i was able to http to the WLC from the LAN.(WLC Mgmt, AP Mgmt IPs and AP Manager interface are in same VLAN).

It sounds like the client may be connecting to the guest WLAN first, then connecting to the Corp WLAN.
As to the VLAN setting. 0 in the WLC means untagged. If your switchport has the switchport trunk native valn < x > command you would need to be untagged. Otherwise the switch would get a packet tagged with the native vlan, and then drop the traffic.
***if your management is in VLAN 1, the above is true with out the native setting, as VLAN 1 is native by default
HTH,
Steve
Please remember to rate helpful posts or to mark the question as answered so that it can be found later.

-1 (Minus One) Wireless Client Rate for networked PCs with Ariport Express

Trying to figure out connection problems...
Under Airport Utility > Advanced > Logs and Statistics > Wireless Clients...
My MBP gets a Rate 54Mbps when I am beside it in my room, but sometimes drops down to 11 or so and then goes back up. I think this is why I am losing my AirTunes connection.
Both PCs on the network are farther away but are showing a Rate of -1Mbps, even when they are brought into the same room as the APX.
Any thoughts.

1. How does the client device know which Airport to connect to?
The Mac computer will automatically connect to the wireless access point with the strongest signal...which is probably the closest AirPort. An iPhone or iPad may not do this and will tend to stay connected to one AirPort.
2. How can I tell which of the Airports the attached client device is using?
On a Mac, open Macintosh HD > Applications > Utilities > AirPort Utility. Click on one of AirPorts. In the area to the right, locate the AirPort ID and jot that down. Then do the same for your other AirPort.
Move your Mac near one of the AirPorts and log on to the wireless. Hold down the option key on the Mac while you click the fan shaped AirPort icon at the top of the screen. Look for the BSSID. That is the AirPort ID of the device to which you are connected.
If you are close to the "remote" AirPort, and you see the AIrPort ID of the "main" router when you are testing, then you know that the network is not configured correctly.
Can I use this second Airport Express to extend the wireless network via "Extended Wireless Network" while the other two are in "Roaming Netowrk" configuration? Without bogging down??
There will be a modest 10-15% bandwidth loss with the "extend" setup, assuming that the Express is located where it can receive a strong wireless signal from the AirPort to which it is associated. You can avoid the bandwidth loss if the Express is also connected via Ethernet as part of the roaming configuration.

WLC 5760 - show client ccx roam-history

Hi,
We're running an WLC 5760 with the latests version (3.3.1). We have several wlans, with diferent authentication methods, and they are all working fine.
However we noticed that the roaming is working correctly but no information is displayed if the "show ccx roam-history".
WLC1#sh wireless client mac-address 8853.2e9e.f70a det | i CCX
Client CCX version : 4
WLC1#debug dot11 ccx-roam all
Dec 12 17:11:40.963: %IOSXE-7-PLATFORM: 1 process wcm: 8853.2e9e.f70a Mobile 8853.2e9e.f70a associated
Dec 12 17:11:40.963: %IOSXE-7-PLATFORM: 1 process wcm: 8853.2e9e.f70a Sending Neighbor List packet to Mobile 8853.2e9e.f70a
Dec 12 17:11:40.963: %IOSXE-7-PLATFORM: 1 process wcm: 8853.2e9e.f70a Sending L2Roam Packet to mobile 8853.2e9e.f70a
Dec 12 17:11:40.963: 00000000: 1 wcm: 01 1a 33 81 88 53 2e 9e f7 0a c0 25 5c 68 50 50 ..3..S.....%\hPP
Dec 12 17:11:40.963: 00000010: 1 wcm: 28 11 c0 25 5c 68 50 50 01 00 02 01 06 ab 0d 0d (..%\hPP........
Dec 12 17:11:40.963: 00000020: 1 wcm: 03 b8 05 28 11 c0 25 5c ec 05 a0 0b 00 07 01 06 ...(..%\........
Dec 12 17:11:40.963: %IOSXE-7-PLATFORM: 1 process wcm: 00000030: ab 0d 0d 03 b8 05 28 11 0c 68 03 ea 52 10 06 00 ......(..h..R...
Dec 12 17:11:40.963: %IOSXE-7-PLATFORM: 1 process wcm: 00000040: 07 01 06 ab 0d 0d 03 b8 05 28 11 0c 68 03 d6 e4 .........(..h...
Dec 12 17:11:40.963: %IOSXE-7-PLATFORM: 1 process wcm: 00000050: 00 0b 00 07 01 06 ab 0d 0d 03 b8 05 28 11 0c 68 ............(..h
Dec 12 17:11:40.963: %IOSXE-7-PLATFORM: 1 process wcm: 00000060: 03 4d d0 60 01 00 07 01 06 ab 0d 0d 03 b8 05 28 .M.`...........(
Dec 12 17:11:40.963: %IOSXE-7-PLATFORM: 1 process wcm: 00000070: 11 0c 68 03 ea 40 70 01 00 07 01 06 ab 0d 0d 03 ..h..@p.........
Dec 12 17:11:40.963: %IOSXE-7-PLATFORM: 1 process wcm: 00000080: b8 05 28 11 0c 68 03 ea 4b 10 01 00 07 01 06 ab ..(..h..K.......
Dec 12 17:11:40.963: 00000090: 1 wcm: 0d 0d 03 b8 05 28 11 c0 25 5c 68 50 5f 3c 01 04 .....(..%\hP_<..
Dec 12 17:11:40.964: 000000a0: 1 wcm: 01 06 ab 12 12 03 b8 05 28 11 c0 25 5c ec 05 af ........(..%\...
Dec 12 17:11:40.964: %IOSXE-7-PLATFORM: 1 process wcm: 000000b0: 24 01 07 01 06 ab 12 12 03 b8 05 28 11 0c 68 03 $..........(..h.
Dec 12 17:11:40.964: %IOSXE-7-PLATFORM: 1 process wcm: 000000c0: ea 52 1f 24 01 07 01 06 ab 12 12 03 b8 05 28 11 .R.$..........(.
Dec 12 17:11:40.964: %IOSXE-7-PLATFORM: 1 process wcm: 000000d0: 0c 68 03 ea 4b 1f 38 01 07 01 06 ab 12 12 03 b8 .h..K.8.........
Dec 12 17:11:40.964: %IOSXE-7-PLATFORM: 1 process wcm: 000000e0: 05 28 11 0c 68 03 d6 e4 0f 38 01 07 01 06 ab 12 .(..h....8......
Dec 12 17:11:40.964: 000000f0: 1 wcm: 12 03 b8 05 28 11 c0 25 5c a3 f4 8f 30 01 07 01 ....(..%\...0...
WLC1#
Dec 12 17:11:40.964: %IOSXE-7-PLATFORM: 1 process wcm: 00000100: 06 ab 12 12 03 b8 05 28 11 0c 68 03 ea 40 7f 30 .......([email protected]
Dec 12 17:11:40.964: %IOSXE-7-PLATFORM: 1 process wcm: 00000110: 01 07 01 06 ab 12 12 03 b8 05                    ..........
Dec 12 17:12:51.006: %IOSXE-7-PLATFORM: 1 process wcm: 8853.2e9e.f70a Received Neighbor List Request from Mobile 8853.2e9e.f70a
Dec 12 17:12:51.006: %IOSXE-7-PLATFORM: 1 process wcm: 8853.2e9e.f70a Sending Neighbor List packet to Mobile 8853.2e9e.f70a
Dec 12 17:12:51.006: %IOSXE-7-PLATFORM: 1 process wcm: 8853.2e9e.f70a Sending L2Roam Packet to mobile 8853.2e9e.f70a
Dec 12 17:12:51.006: 00000000: 1 wcm: 01 1a 33 81 88 53 2e 9e f7 0a c0 25 5c 68 50 50 ..3..S.....%\hPP
Dec 12 17:12:51.006: 00000010: 1 wcm: 28 11 c0 25 5c 68 50 50 01 00 02 01 06 ab 0d 0d (..%\hPP........
Dec 12 17:12:51.006: 00000020: 1 wcm: 03 b8 05 28 11 c0 25 5c ec 05 a0 0b 00 07 01 06 ...(..%\........
Dec 12 17:12:51.006: %IOSXE-7-PLATFORM: 1 process wcm: 00000030: ab 0d 0d 03 b8 05 28 11 0c 68 03 ea 52 10 06 00 ......(..h..R...
Dec 12 17:12:51.006: %IOSXE-7-PLATFORM: 1 process wcm: 00000040: 07 01 06 ab 0d 0d 03 b8 05 28 11 0c 68 03 d6 e4 .........(..h...
Dec 12 17:12:51.006: %IOSXE-7-PLATFORM: 1 process wcm: 00000050: 00 0b 00 07 01 06 ab 0d 0d 03 b8 05 28 11 0c 68 ............(..h
Dec 12 17:12:51.006: %IOSXE-7-PLATFORM: 1 process wcm: 00000060: 03 4d d0 60 01 00 07 01 06 ab 0d 0d 03 b8 05 28 .M.`...........(
Dec 12 17:12:51.006: %IOSXE-7-PLATFORM: 1 process wcm: 00000070: 11 0c 68 03 ea 40 70 01 00 07 01 06 ab 0d 0d 03 ..h..@p.........
Dec 12 17:12:51.006: %IOSXE-7-PLATFORM: 1 process wcm: 00000080: b8 05 28 11 0c 68 03 ea 4b 10 01 00 07 01 06 ab ..(..h..K.......
Dec 12 17:12:51.006: 00000090: 1 wcm: 0d 0d 03 b8 05 28 11 c0 25 5c 68 50 5f 3c 01 04 .....(..%\hP_<..
Dec 12 17:12:51.006: 000000a0: 1 wcm: 01 06 ab 12 12 03 b8 05 28 11 c0 25 5c ec 05 af ........(..%\...
Dec 12 17:12:51.006: %IOSXE-7-PLATFORM: 1 process wcm: 000000b0: 24 01 07 01 06 ab 12 12 03 b8 05 28 11 0c 68 03 $..........(..h.
Dec 12 17:12:51.006: %IOSXE-7-PLATFORM: 1 process wcm: 000000c0: ea 52 1f 24 01 07 01 06 ab 12 12 03 b8 05 28 11 .R.$..........(.
Dec 12 17:12:51.006: %IOSXE-7-PLATFORM: 1 process wcm: 000000d0: 0c 68 03 ea 4b 1f 38 01 07 01 06 ab 12 12 03 b8 .h..K.8.........
Dec 12 17:12:51.006: %IOSXE-7-PLATFORM: 1 process wcm: 000000e0: 05 28 11 0c 68 03 d6 e4 0f 38 01 07 01 06 ab 12 .(..h....8......
Dec 12 17:12:51.006: 000000f0: 1 wcm: 12 03 b8 05 28 11 c0 25 5c a3 f4 8f 30 01 07 01 ....(..%\...0...
Dec 12 17:12:51.006: %IOSXE-7-PLATFORM: 1 process wcm: 00000100: 06 ab 12 12 03 b8 05 28 11 0c 68 03 ea 40 7f 30 .......([email protected]
Dec 12 17:12:51.006: %IOSXE-7-PLATFORM: 1 process wcm: 00000110: 01 07 01 06 ab 12 12 03 b8 05                    ..........
Dec 12 17:15:48.712: %IOSXE-7-PLATFORM: 1 process wcm: 8853.2e9e.f70a Received Neighbor List Request from Mobile 8853.2e9e.f70a
Dec 12 17:15:48.712: %IOSXE-7-PLATFORM: 1 process wcm: 8853.2e9e.f70a Sending Neighbor List packet to Mobile 8853.2e9e.f70a
Dec 12 17:15:48.712: %IOSXE-7-PLATFORM: 1 process wcm: 8853.2e9e.f70a Sending L2Roam Packet to mobile 8853.2e9e.f70a
Dec 12 17:15:48.712: 00000000: 1 wcm: 01 07 33 81 88 53 2e 9e f7 0a c0 25 5c 68 81 20 ..3..S.....%\h..
Dec 12 17:15:48.712: 00000010: 1 wcm: 28 11 c0 25 5c 68 81 20 01 00 02 01 06 ab 0d 0d (..%\h..........
Dec 12 17:15:48.712: %IOSXE-7-PLATFORM: 1 process wcm: 00000020: 03 b8 05 28 11 0c 68 03 ea 52 10 06 00 07 01 06 ...(..h..R......
Dec 12 17:15:48.712: %IOSXE-7-PLATFORM: 1 process wcm: 00000030: ab 0d 0d 03 b8 05 28 11 0c 68 03 ea 4a f0 0b 00 ......(..h..J...
Dec 12 17:15:48.713: %IOSXE-7-PLATFORM: 1 process wcm: 00000040: 07 01 06 ab 0d 0d 03 b8 05 28 11 0c 68 03 d6 eb .........(..h...
Dec 12 17:15:48.713: %IOSXE-7-PLATFORM: 1 process wcm: 00000050: 20 01 00 07 01 06 ab 0d 0d 03 b8 05 28 11 c0 25 ............(..
Dec 12 17:15:48.713: %IOSXE-7-PLATFORM: 1 process wcm: 00000060: 5c ec 05 a0 0b 00 07 01 06 ab 0d 0d 03 b8 05 28 \..............(
Dec 12 17:15:48.713: %IOSXE-7-PLATFORM: 1 process wcm: 00000070: 11 0c 68 03 d6 e4 00 0b 00 07 01 06 ab 0d 0d 03 ..h.............
Dec 12 17:15:48.713: 00000080: 1 wcm: b8 05 28 11 c0 25 5c 68 50 50 01 00 07 01 06 ab ..(..%\hPP......
Dec 12 17:15:48.713: 00000090: 1 wcm: 0d 0d 03 b8 05 28 11 c0 25 5c 68 81 2f 38 01 04 .....(..%\h./8..
Dec 12 17:15:48.713: %IOSXE-7-PLATFORM: 1 process wcm: 000000a0: 01 06 ab 12 12 03 b8 05 28 11 0c 68 03 ea 4a ff ........(..h..J.
Dec 12 17:15:48.713: %IOSXE-7-PLATFORM: 1 process wcm: 000000b0: 2c 01 07 01 06 ab 12 12 03 b8 05 28 11 0c 68 03 ,..........(..h.
Dec 12 17:15:48.713: %IOSXE-7-PLATFORM: 1 process wcm: 000000c0: ea 52 1f 24 01 07 01 06 ab 12 12 03 b8 05 28 11 .R.$..........(.
Dec 12 17:15:48.713: %IOSXE-7-PLATFORM: 1 process wcm: 000000d0: 0c 68 03 d6 e4 0f 38 01 07 01 06 ab 12 12 03 b8 .h....8.........
Dec 12 17:15:48.713: 000000e0: 1 wcm: 05 28 11 c0 25 5c ec 05 af 24 01 07 01 06 ab 12 .(..%\...$......
Dec 12 17:15:48.713: %IOSXE-7-PLATFORM: 1 process wcm: 000000f0: 12 03 b8 05 28 11 0c 68 03 d6 eb 2f 3c 01 07 01 ....(..h.../<...
Dec 12 17:15:48.713: %IOSXE-7-PLATFORM: 1 process wcm: 00000100: 06 ab 12 12 03 b8 05                              .......
WLC1#show wireless client mac-address 8853.2e9e.f70a ccx roam-history
Shouldn't the output be the same as the AireOS command "show client roam-history client-mac"?
Kind regards,
Vasco Costa

Obtaining CCX Client Roaming Information (CLI)
Step 1
View the current RF parameters configured for client roaming for the 802.11a or 802.11b/g network by entering this command:show {802.11a | 802.11b} l2roam rf-param
Step 2
View the CCX Layer 2 client roaming statistics for a particular access point by entering this command:show {802.11a | 802.11b} l2roam statistics ap_mac
This command provides the following information:
The number of roam reason reports received
The number of neighbor list requests received
The number of neighbor list reports sent
The number of broadcast neighbor updates sent
Step 3
View the roaming history for a particular client by entering this command:show client roam-history client_mac
This command provides the following information:
The time when the report was received
The MAC address of the access point to which the client is currently associated
The MAC address of the access point to which the client was previously associated
The channel of the access point to which the client was previously associated
The SSID of the access point to which the client was previously associated
The time when the client disassociated from the previous access point
The reason for the client roam
Debugging CCX Client Roaming Issues (CLI)
If you experience any problems with CCX Layer 2 client roaming, enter this command:
debug l2roam [detail | error | packet | all] {enable | disable}

Wireless Clients

I am trying to setup the clients on our network with the Intel Wireless Utility package and in the administrative tool gives an option to setup Roaming Aggressiveness and i am not quite sure which option to use:
Default: Balanced between not roaming and performance
Â· Lowest: Your WiFi client will not roam unless significant link quality degradation occurs
Â· Highest: Your WiFi client continuously tracks the link quality and, if any degradation occurs, it tries to find and roam to a better access point
Thank you
Vic

You should test each setting. Here are the trade-offs:
Lowest: This will prevent your clients from roaming too much, which can cause degradation of performance. Each time a client roams, it could lose 1-2 seconds of network connectivity. However, your clients might cling to an AP that's far away and use lower data rates than it could have if it would roam.
Highest: This will prevent your clients from "sticking" to a particular AP by roaming early and often. This is beneficial since you don't want to be clinging to an AP down the hall at 11Mbps when you're standing directly under another one and could be running at 54Mbps. However, your client might be roam-happy and roam too much, causing a lot of network interruptions.
I hope this helps. You really need to decide which you prefer for your environment, and then run some tests. You might not even notice a big difference.

Any extra fine tuning / configuration to be done for Client / Voice Roaming .

Dear Folks,
Is there any additional configuration to be done on the 5508 WLC for Wireless Laptop / Voice Roaming ? I tested with Wireless IP Phone and found some blankness in voice , whereas i have other access point nearby , which wasn't switching over easily .
Regards,
SID

Hi,
When working with Cisco IP phones as mention before, we need to comply with the following
configuration on the WLC to avoid connectivity issues as per the deployment
guide of the 7921 and 7925 IP phones.
Here is the link for the deployment guide of the 7921 and 7925.
http://www.cisco.com/web/strategy/docs/healthcare/7921dply.pdf
http://www.cisco.com/en/US/docs/voice_ip_comm/cuipph/7925g/7_0/english/deplo
yment/guide/7925dply.pdf
The WLC version must be 4.0 or higher (show sysinfo)
The current phone version is under: Status > Firmware Version
App Load ID CP7921G-1.0.2.LOADS 1.0.5 is available on the web & should be
used: http://www.cisco.com/cgi-bin/tablebuild.pl/ip-7900ser-crypto
The 11M rate should be set for 'basic' & the 18-54M rates as optional
This will show up in the "802.11B Configuration" "Operational Rates" section
of the 'show run' as:
802.11b/g 1M Rate & others............................ Disabled
802.11b/g 11M Rate........................... Mandatory
802.11g 54M Rate & others............................. Supported
If the rates lower than 11 (such as 5.5) are needed, the lowest rates should
be the 'Mandatory'
The 12M rate should be set for 'basic' & the 18-54M rates as optional
This will show up in the "802.11A Configuration" "Operational Rates" section
of the 'show run' as:
802.11a Operational Rates
    802.11a 6M Rate.............................. Disabled
    802.11a 9M Rate.............................. Disabled
    802.11a 12M Rate............................. Mandatory
    802.11a 18M Rate............................. Supported
    802.11a 24M Rate............................. Supported
    802.11a 36M Rate............................. Supported
    802.11a 48M Rate............................. Supported
    802.11a 54M Rate............................. Supported
If 802.1X authentication is in use, CCKM should be employed.
This will show up in 'show wlan ' as:
CCKM.................................... Enabled
TKIP encryption is recommended.
This will show up in 'show wlan ' as:
    WPA (SSN IE)............................... Enabled
         TKIP Cipher............................. Enabled
         AES Cipher.............................. Disabled
      WPA2 (RSN IE).............................. Disable
         TKIP Cipher............................. Disabled
         AES Cipher.............................. Disabled
The DTIM period should be set for '2' under the wireless/network settings.
This will show up in 'show run' as:
DTIM Period...................................... 2
The beacon interval should be set for '100' under the wireless/network
settings.
This will show up in 'show run' as:
Beacon Interval.................................. 100
WMM should be enabled on the wlan.
This will show up in 'show wlan ' as:
WMM.............................................. Allowed
The wlan QOS should be set to platinum.
This will show up in 'show wlan ' as:
Quality of Service............................... Platinum (voice)
Under Controller, arp unicast should be disabled
This will be in 'show network' as:
ARP Unicast Mode........Disabled
Under Controller > QOS, the platinum QOS setting should have 802.1p chosen
and the tag set to '6'
This will show up in 'show qos platinum' as:
protocol......................................... dot1p
dot1p............................................ 6
Per WLAN CAC is set under the wlan - 'AP CAC limit'.
This will show up in 'show wlan ' as:
Dot11-Phone Mode .......................... ap-cac-limit
LAN "dhcp address assignment required" should be 'disabled'.
This will show up in 'show wlan ' as:
DHCP Address Assignment Required................. Disabled
Aggressive load-balancing should be disabled (under 'network'
settings).
DTPC should be enabled under wireless > network
This will show up in 'show run' as:
DTPC Status..................................... Enabled
If no legacy clients need long preamble, set the preamble for 'short'
under wireless > network.
This will show up in 'show run' as:
Short Preamble mandatory......................... Enabled
If using eap-fast with the WLC, the 802.1x timeout is 2
seconds. This is not enough time for the IP phone to download and process
the PAC. The timeout can be increased:
"config advanced eap request-timeout 20"
"save config:
In the 7921 phone, unlike with the 7920 phone, 'auto' does not mean eap-fast
or leap, it means 'leap' with wpa2, leap with wpa2, or wpa-psk.
If you want to use EAP-FAST, then use EAP-FAST mode, not 'auto'.
For 7921-7921 conversations to work, 'peer-to-peer blocking' needs to be
'off' under the 'controller' tab (this is off by default).
In later code, the DFS settings under Wireless > 802.11A/N
DFS(802.11H) should be:
Power Constraint off
Channel Announcement on
Channel quiet mode on.
These values will appear in 'show 802.11h' as:
802.11h ......................................... powerconstraint : 0
802.11h ......................................... channelswitch : Enable
802.11h ......................................... channelswitch mode : 1
Do *not* turn on 802.11b/g/n > EDCA parameters 'low latency mac' -
make sure that is disabled.
This will appear in the output of 'show 802.11b|802.11a' as:
Voice MAC optimization status.................... Disabled
802.11b/g/n > EDCA parameters - set for WMM
'Single AP Mode' should be disabled on the phones (unless there *is*
only a single AP).
The RF values seen by the phone are under Settings > Status > Site Survey

Wireless Client Hardware/Software requirements

We are building a new wireless network full of the 3500 series LWAP. Along with this new wireless network, my boss wants me to provide her with minimum hardware/software specifications for all new wireless clients purchased. I know the basic stuff such as 802.11n dual band, etc... I was wondering if anyone had a good list of detailed requirements that would provide me with a best case connection for my wireless clients on the new network that they would share with me.
Thanks for any Help
In a nut shell, i need to make sure the wireless clients we purcahse for our new network can take full advantage of our wireless network. i want to make sure i'm educated on more details besides the basic requirements of 802.11n dual band specification. There must be more detailed technical requiremetns i need to be aware of so I can be sure i don't end up with a bunch of flaky half working wireless clients.

thanks for you help. I got the following infomration from sales team
at Cisco. They say it should be sufficient requirements of any proposed wireless clients:
o   Provide options to control roaming between wireless access points.
o   Dual-band support
o   AES support
o   802.1x supplicant support
o   CCX (Information can be found at the following link: http://www.cisco.com/web/partners/pr46/pr147/partners_pgm_partners_0900aecd800a7907.html)

BEFW11S4 as Wireless Client

I have a wireless network, using a WRT54G as my router. I have a spare BEFW11S4 and I want to be able to use this as a wireless client so that I can connect a couple of non-wireless devices (including an Xbox 360) to it via Ethernet so I can share my internet connection with them.
Will it be possible to do this with a BEFW11S4, and if so how?

I don't know the prices but for Linksys devices you can do wireless bridging with the dedicated bridges WETxxx, the versatile access points WAPxxx, and the WRTxxx with 3rd party firmware. I guess the WETs should be the cheapest but also the most limited in function that it is only a bridge and nothing else. The WAPs or WRTs have the advantage that you can later use them otherwise if your setup changes. For instance, if you decide to run a wire everywhere for performance then the WET would become fairly useless. You could still use the WAP or WRT as access point to increase the wireless coverage and create a roaming network.
As a sidenote: please also remember that connecting "a couple of ... devices" through a wireless link. If you have some distance between the base station and the remote station the link will be fairly slow and with a lot of traffic through the link (e.g. during gaming) you may experience a lot of packet loss. Wireless consumer routers are O.K. to connect a few devices. But don't expect too much... After a while with mediocre wireless connections I ended up running wires everywhere...

The master extreme does not seem to be able to accept wireless clients.

I have a roaming network setup with several extremes/express devices. The probem I am having is the master extreme which is in the garage does not want to accept new wireless clients. I have 3 other devices which work just fine. They hand off clients as you move around the house. You can see the wireless network on your device and when you select it you get a pop up window prompting you for the password??? You enter the passwork/key and nothing seems to happen.

Yes all of my base stations have the same network name, same password and same security setting. I have Comcast as my network provider. I have the latest airport extreme connected directly to the cable modem in the garage. I have 2 other base stations of the previous verison in house. One in my office and one in the living room. If I am moving around in the house I can use the airport utilitiy to look at those base stations and see which wireless clients they have. If I go out into the garage and try and connect to the wireless network the device appears to be trying (spinning dial icon) and then comes back with the pop up requesting a password. I have tried entering it and again it will appear to try and connect for a few seconds and then the pop up will appear again. I I walk into the house the device will connect with one of the other base stations.
Also all of the base stations are connected via ethernet cable to the main base station in the garage. They are connected directly with no switch or router between them.

Can I use ASA to be a DHCP Server use in WLC wireless Client

I want to use ASA to be a DHCP Server for Wireless Client not it can't.
I check the debug log in WLC, I confirm the WLC have send the request to ASA.
In the ASA, it don't have any hits in the rule when the WLC send the DHCP relay request.
I have try don't use dhcp relay in WLC but don't success. Anybody have the same case with me? And Is the ASA can't support DHCP relay agent to request to get the IP Addr.
P.S. In the Network Design limitation so I can't use WLC to be DHCP Server.
Equipment:
ASA5510
WLC4402
How can I fix it.
Thank you very much

The issue is that the ASA doesn't accept DHCP requests from a relay agent, only broadcast DHCP requests. In the 4.2 version for the controllers there is now an option so you can change the way the controller forwards DHCP requests so that it is sent as a broadcast and not from a relay agent.

Some wireless clients can't discover or connection to local wired systems

Hi,
I've just upgraded my home wireless from an NetComm NB5540 + modem to a LinkSys X3000.
Internet access works fine for all devices, but some wireless devices can't "see" my Win7 desktop system that's on a wired connections to the router.
I've tried three devices...
Galaxy Note phone (running ICS 4.0.4) can discover and connect to file shares on my desktop system without any problems.
Asus Transformer Prime tablet (running JellyBean 4.1.1) can see the router on the local network, but can't see my desktop. Even if I manually type in the IP address it can't connect to it
Likewise my old WinXP laptop can see the router but can't see or connect to any other devices.
Any suggestions welcome.
Hugh
ps. I tried connecting the NetComm router with just Wifi configured to one of the ethernet ports on the X3000, so I've got two Wifi networks running in parallel. If I connect to this second WiFi network with any of the above devices then they can all discover and connect to my desktop system on the wired connection to the X3000.

Just to test network connectivity, why don't you ping the wired client from the wireless devices that are not able access it? Do post your results so we can further analyze this scenario. By the way, when you cascaded another access point (using the NetComm router) to the X3000, was it via LAN- LAN? Was the X3000 still the DHCP server for the wireless clients?

Unable to set up base station as wireless client

I have a network with one Airport Extreme (UFO-shape) and three Airport Express base stations. Now I had to do a hard reset of all the base stations, and want to use Airport utility to set up the network again.
I have no problems setting up the Airport extreme as the main base station, and the first Airport express as a remote base station (extending the network). I want to set up the other two Airport Express stations as wireless clients (I only use them for iTunes via Airtunes).
My problem is that when I reach the point where I can choose between setting them up to either extend the network or as a wireless client, I am not able to proceed if I choose the latter (nothing happens when I press "continue"). I can only go through the setup process if I choose the Airport Express to be an extension of the network (a remote base station).
For one of the Airport express, I then later manually changed the setup from "be a part of a WDS network" to "connect to a wireless network". But when I try this for the last Airport Express, I am no longer able to contact the base station if I try to do the same. I have chosen channel 11 for the network, and I think in some way or another, after I manually change the settings for the last Airport express, it switches to another channel. After this I can no longer read the base station configuration or connect to it via airtunes.
When I do a hard reset again, and go through the process once more, everything is OK as long as I keep it as a remote base station. But I really would like it to be connected as a wireless client
Any ideas?

The basic wiring setup would include connecting an Ethernet cable from one of the available LAN <-> Ethernet ports to the WAN "O" port on the Time Capsule.
You can run an Ethernet cable up to 100 meters or 300+ feet so the trick will be locate the Time Capsule in the middle of the area where you need more wireless signal coverage.
To have the Time Capsule "extend" the wireless from the gateway, you would need to configure it to create a new wireless network using the same wireless network name, same wireless security setting and same password as the gateway's wireless network.
The final configuration step would be to make sure that the Time Capsule is setup to operate in Bridge Mode, so that it will function as a client for the gateway router.
The specifics of how to do this will depend on the version of AirPort Utility that you are using on your Mac. Post back if you need more details on this.

Bridge does not work for wireless clients - connecting to existing network.

Hi - I really hope somebody can help out here, after hours of trial & error, I have finally given up
I need to connect my Airport Extreme Base Station to my existing network. I have a linksys router (192.168.15.1) connected to my modem and this linksys router acts as DHCP server too.
I suppose I have to use "bridge mode" for that to work. But should the linksys be connected to the AEBS using the AEBS's WAN or LAN port?
If I use "bridge mode", then wired computers to the AEBS works fine - getting an IP from the linksys etc. BUT, the wireless clients will have a self-assigned IP and not get through to the internet. It's like the AEBS will not allow wireless clients to "get through" unless AEBS itself is handing out IP addresses.
Page 36 of this manual ( http://manuals.info.apple.com/en/DesigningAirPort_Networks10.5-Windows.pdf ) shows the setup I want. But in the picture, it says "Ethernet WAN port" but the text says: "The Apple wireless device (in this example, a Time Capsule) uses your Ethernet network to communicate with the Internet through the Ethernet LAN port ( <--> )." I don't know which one to use, WAN or LAN - they show WAN but say LAN?
When I set it up as "share an IP address", the AEBS status tells me "double nat" and to change from "shared IP" to "bridge mode". I do that, and everything seems fine - for the wired clients. Now the wireless clients cannot connect, Airport on the MacBook Pro just say "Connection failed" and the MacBook says "Invalid password" (translated from danish), even though I set the Airport Utlity to save the password in keyring, so it should be correct... If I disable wireless encryption, the wireless clients will connect but get a self-assigned IP, and therefor not work (cannot get online)...
It seems the only way I can get wireless to work, is if I set AEBS up as DHCP, but then it won't be on the "same network" as the linksys (192.168.15.1), but rather on 10.0.x.x as I select. If I select 192.168.x.x within AEBS, I'm also getting some error messages, conflict/subnet thing.
Anyway - I really hope somebody knows how to get wireless clients to get an IP address from existing ethernet when connected to the AEBS.
Thanks!!

I've given up and had to go back to running "Double NAT" which also reports as a "problem" within the AEBS, but I just "ignore" it so the light will always be green.
It still ***** though, as "Double NAT" is also a reason for "Back to my Mac" not working properly, but how the ** am I supposed to avoid Double NAT when the wireless will not work in bridged mode?!

I cannot get my Airport Express to accept wireless clients.

I cannot get my Airport Express to accept wireless clients. After resetting to factory default and reconfiguring, it works briefly but then stops again.
The Airport Express is on the second floor of my house and is seen by Airport Utility. Using a LAN cable with the Express works no problem.
My network is created by an Airport Extreme (ground floor) and extended by a Time Capsule (first floor)
Have run through all settings repeatedly and as I said I can get it to work briefly by resetting and then reconfiguring, but after a short while again my iOS devices can no longer connect and revert to cellular.

I cannot get my Airport Express to accept wireless clients. After resetting to factory default and reconfiguring, it works briefly but then stops again.
The Airport Express is on the second floor of my house and is seen by Airport Utility. Using a LAN cable with the Express works no problem.
My network is created by an Airport Extreme (ground floor) and extended by a Time Capsule (first floor)
The issue is most likely due to the fact that the AirPort Express may be too far from the AirPort Extreme to properly extend it with enough bandwidth to be useful.
It is important to understand that with Apple 802.11n or 802.11ac base station an extended network works in a wheel-like fashion with the base station to be extended at the hub and each extending base station along one of the spokes. This type of configuration does not allow for daisy chaining the base stations. That is, in your case, both the Time Capsule and AirPort Express are attempting to extend the AirPort Extreme.
Each extending base station must be within a certain signal quality range in order to extend the network properly. Please check out the following AirPort User tip for details.

Wireless client unpredicatably roaming to other AP's

Similar Messages

Maybe you are looking for