Handheld scanner wireless issues
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎09-24-2018 03:49 PM
We have an issue which we cannot seem to figure out. We recently upgraded our AP's to 7522's in all of our buildings (370+ AP's). Users are complaining that their handhelds keep dropping their connection (mainframe and RDP). Whats interesting is that users say that it was better on the older 650's we had in place before the upgrade. We have had site surveys done in several of our buildings and added AP's where recommended.
Inventory SSID is WPA2-CCMP
Using smart-rf policay
g-rates disabled
Any idea on what to look at next?
Thanks
Inventory SSID is WPA2-CCMP
Using smart-rf policay
g-rates disabled
Any idea on what to look at next?
Thanks
21 REPLIES 21
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎09-26-2018 01:21 AM
If you have changed the allowed data rates, can you share the custom configuration for data rates ?
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎09-24-2018 06:51 PM
Was going to mention as well:
Neighbor Recovery:
Neighbor Recovery is used to automatically expand one or more AP's coverage area by increasing an AP's power when a WiNG neighbor AP’s signal has deteriorated/degraded. This is essentially a recovery mode whereby the APs are detecting that another WiNG AP is basically 'down' or somehow seriously affected. Either failed, antennas broken off, or some large RF obstacle has moved in the way of the AP such that it appears that it's down. The default settings in the SmartRF policy is -70dBm. This value is adjustable...so if your environment is such that you would expect for periodic large blockages of APs to occur...such that the Neighbor recovery mechanism would kick in, you should probably alter that value or just disable the Neighbor Recovery option altogether. There are different ways of dealing with this.
Coverage Hole Recovery:
This is a recovery method that allows for neighboring APs to increase their radio transmit power to compensate for what is seen as a coverage hole. It's possible that whatever is causing the frequent Neighbor Recovery instances is also responsible for causing the coverage hole recoveries.
Neighbor Recovery:
Neighbor Recovery is used to automatically expand one or more AP's coverage area by increasing an AP's power when a WiNG neighbor AP’s signal has deteriorated/degraded. This is essentially a recovery mode whereby the APs are detecting that another WiNG AP is basically 'down' or somehow seriously affected. Either failed, antennas broken off, or some large RF obstacle has moved in the way of the AP such that it appears that it's down. The default settings in the SmartRF policy is -70dBm. This value is adjustable...so if your environment is such that you would expect for periodic large blockages of APs to occur...such that the Neighbor recovery mechanism would kick in, you should probably alter that value or just disable the Neighbor Recovery option altogether. There are different ways of dealing with this.
Coverage Hole Recovery:
This is a recovery method that allows for neighboring APs to increase their radio transmit power to compensate for what is seen as a coverage hole. It's possible that whatever is causing the frequent Neighbor Recovery instances is also responsible for causing the coverage hole recoveries.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎09-24-2018 06:50 PM
Hi Dan
Can I recommend that you contact GTAC
https://www.extremenetworks.com/support/contact/
We have a very good wing team that will be able to assist in this matter.
I can see some changes in your WLAN setting that you have configured that could cause problems in old windows mobile devices roaming.
You have enabled 802.11r for example that is not support on windows mobile so will not help.
Can you also attached a copy of the tech support file
thank you
Andy
Can I recommend that you contact GTAC
https://www.extremenetworks.com/support/contact/
We have a very good wing team that will be able to assist in this matter.
I can see some changes in your WLAN setting that you have configured that could cause problems in old windows mobile devices roaming.
You have enabled 802.11r for example that is not support on windows mobile so will not help.
Can you also attached a copy of the tech support file
thank you
Andy
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎09-24-2018 06:25 PM
Dan, I see quite a bit of recovery activity. Neighbor recovery, coverage-hole recovery, much of it by AP "Ind-Exp-2ndFlShipping-AP-58". Anything special about that AP's location?
(Also seeing this type of activity on the 2.4GHz radios as well, but it doesn't appear to be nearly as frequent)
Question: When the 650's were being used, were the handhelds typically using the 2.4GHz radios?
If a survey was done for the deployment of the 650's, was the survey performed based on 2.4GHz coverage requirements? (not for 5GHz coverage)
What I'm getting at here is that the AP placements may have been surveyed based on 2.4GHz coverage...and then you've moved most of your clients over to 5GHz (all of your handhelds). Based on the SmartRF report and all the power recovery activity, I'm thinking that maybe the coverage doesn't look too good using 5GHz.
You could test this by taking 1 or 2 handhelds and re-configuring them to only use 2.4GHz ONLY and then put them into production for a day or two...or however long would prove if the change made a difference. If you see that the connection issues go away on those devices, then I would conclude that you're dealing with a 5GHz coverage problem.
(Also seeing this type of activity on the 2.4GHz radios as well, but it doesn't appear to be nearly as frequent)
Question: When the 650's were being used, were the handhelds typically using the 2.4GHz radios?
If a survey was done for the deployment of the 650's, was the survey performed based on 2.4GHz coverage requirements? (not for 5GHz coverage)
What I'm getting at here is that the AP placements may have been surveyed based on 2.4GHz coverage...and then you've moved most of your clients over to 5GHz (all of your handhelds). Based on the SmartRF report and all the power recovery activity, I'm thinking that maybe the coverage doesn't look too good using 5GHz.
You could test this by taking 1 or 2 handhelds and re-configuring them to only use 2.4GHz ONLY and then put them into production for a day or two...or however long would prove if the change made a difference. If you see that the connection issues go away on those devices, then I would conclude that you're dealing with a 5GHz coverage problem.
