Extreme Networks

Anonymous · ‎03-03-2021

Hello,

we switched our wlan infrastructure at one of our warehouses from old Motorola Symbol Aps using a WEP SSID to our new wlan infrastructure using the XIQ Cloud, with primarily AP410 and a PPSK SSID, using one PPSK for every forklift in the warehouse. (They use an old Win7 embedded OS).

After the switch we noticed several disconnects within the Logistics Software we are using on the terminals to manage the warehouse. We Software keeps losing the connection to the server for a few seconds (from 2-3 seconds to 15-20) and then reconnects. It seems like it’s happening all over the warehouse, even at locations where i can see with our other devices that the wlan connections seems good and stable. What i’ve noticed is that it looks like some sort of roaming problem to me. It seems to me like it is some sort of roaming problem. Maybe the terminals take too long to roam between the aps or having problems with PPSK authentication?

I checked the client monitor to check the clients and noticed a poor client health. Seeing many issues displayed as “The client is configured with an incorrect static IP address or gateway.” Which in fact, seems not to be correct. The forklifts are configured with a static ip, dns and gateway (we dont use DHCP in this VLAN). So what is the cause of this error? Could the be also a hint to our main wlan problem?

If you need any more information, dont hesitate to ask. I appreciate every help. 🙂

Anonymous · ‎03-12-2021

Ah, missed that one. Thanks. 🙂

I am currently at max DB 14. Do you have any recommendations on how low i should minimum go? This already seems to be pretty low.

dpanev · ‎03-12-2021

Try what i told you some posts ago 🙂

Anonymous · ‎03-12-2021

So this one is from our “main ap” in the truck loading street. This is a very long hall with three aps in it. Its pretty empty besides the trucks in the middle of it getting loaded.

AC=access category; be=best-effort; bg=background; vi=video; vo=voice;
AIFS=Arbitration Inter-Frame Space; Txoplimit=transmission opportunity limit;
IDP=Intrusion detection and prevention; BGSCAN=background scan; PS=Power save;
HT=High throughput; A-MPDU=Aggregate MAC protocol data unit;
DFS=Dynamic Frequency Selection; CU=Channel Utilization;
EIRP=Effective Isotropic Radiated Power (Transmit Power + Max Antenna Gain + Max TX Chains Gain);
OFDMA=Orthogonal Frequency Division Multiple Access;
BSS_Color= Basic Service Set Color; TWT=Target Wake Time;

Summary state=Fair;
Mode=access; Radio disabled=no;
Admin state=enabled; Operational state=up;
MAC addr=bcf3:103f:6690; MTU=1500;
Freq(Chan)=2462Mhz(11); EIRP power=17.01dBm(10dBm + 4.00dBi + 3.01dBi); Diversit y=disabled;
Tx range=300m; Noise floor=-96dBm; Tx power control=disabled;
Radio profile=default_2.4ghz_gn; IDP profile=N/A;
Application Essentials profile=N/A;
Presence profile=N/A; Presence state=disabled;
Beacon interval=100; Max clients number=100;
Phymode=11ng; Short preamble mode=enabled;
Tx Chain=static 2; Rx Chain=static 2;
A-MPDU=enabled; Short guard interval=enabled;
Channel width=20Mhz; HT-protection=Legacy protect; Deny client=none;
AC=be; CWmin=4; CWmax=6; AIFS=3; Txoplimit=0; NoACK=disabled;
AC=bg; CWmin=4; CWmax=10; AIFS=7; Txoplimit=0; NoACK=disabled;
AC=vi; CWmin=3; CWmax=4; AIFS=1; Txoplimit=3008; NoACK=disabled;
AC=vo; CWmin=2; CWmax=3; AIFS=1; Txoplimit=1504; NoACK=disabled;
Rx packets=296832799; errors= 49058; dropped= 8;
Tx packets= 35562590; errors=4567503; dropped=30648;
Rx bytes=1675601068 (1.561 GB); Tx bytes=2871104053 (2.674 GB);
ACSP use last selection=disabled;
BGSCAN allow=enabled; BGSCAN during voice=disabled; BGSCAN interval=20 minutes;
BGSCAN with client=enabled; BGSCAN with PS client=disabled;
Number of BGSCAN=30911; Number of BGSCAN requested=36029; Number of BGSCAN misse d=5118;
DFS=disabled; Number of detected radar signals=0; DFS static-channel restore=dis abled;
LLDP state=N/A; CDP state=N/A;
Rx airtime=3234.11 s; Tx airtime=17740.56 s; CRC error airtime=1896.51 s;
Rx airtime percent=0.01%; Tx airtime percent=0.05%; CRC error airtime percent=0. 29%;
Tx utilization=1%; Rx utilization=3%; Interference utilization=0%; Total utiliza tion=4%;
Backhaul failover=disable;
Radio-share mode=off; channel-change=disable;
Running average Tx CU=2%; Rx CU=4%; Interference CU=2%; Noise=-95dBm;
Short term means average Tx CU=1%; Rx CU=4%; Interference CU=1%; Noise=-95dBm;
Snapshot Tx CU=1%; Rx CU=4%; Interference CU=2%; Noise=-95dBm;
CRC error rate=49%;
Benchmark 11a score=222000; 11b score=50500; 11g score=222000; 11n score=501000; 11ac score=889000; 11ax score=889000;
OFDMA downlink=disabled;
OFDMA uplink=disabled;
TWT=disabled;
BSS Color=0;
A-MSDU=disabled; A-MPDU limit=1048575;
VHT support in 2.4G interface=disabled;
Frameburst=enabled;
Alternate radio profile=disabled;
Primary radio profile=default_2.4ghz_gn;
DSSS 20Mhz power:
Board limit=20dBm(1) 20dBm(2) -(3) -(4); Regulatory limit=18dBm(1) 19dBm(2) -(3) -(4);
Spectral scan=off;
The signal by pass BPF.

I am currently noticing a very high crc rate. If i check the acsp neighbors he can see the other aps in the street maybe too good?

Bssid Mode Ssid/Hive Chan Rssi(dBm) Aerohive AP CU CRC STA Channel-width VID NVID
bcf3:103f:2dd4 Access 8021X 1 -81 yes 0 0 0 20 6 1
bcf3:103f:2dd5 Access MDM 1 -81 yes 0 0 0 20 6 1
bcf3:103f:2dd6 Access PPSK 1 -81 yes 0 0 0 20 6 1
bcf3:103f:2c96 Access PPSK 6 -84 yes 0 0 0 20 6 1
bcf3:103f:2c94 Access 8021X 6 -84 yes 0 0 0 20 6 1
bcf3:103f:2c95 Access MDM 6 -84 yes 0 0 0 20 6 1
bcf3:103f:1814 Access 8021X 6 -61 yes 0 0 0 20 6 1
bcf3:103f:1815 Access MDM 6 -60 yes 0 0 0 20 6 1
bcf3:103f:1816 Access PPSK 6 -59 yes 0 0 1 20 6 1
bcf3:103f:1f54 Access PPSK 1 -60 yes 0 0 0 20 6 1
bcf3:103f:1f55 Access 8021X 1 -58 yes 0 0 0 20 6 1
bcf3:103f:1f56 Access MDM 1 -62 yes 0 0 0 20 6 1
bcf3:103f:0c16 Access PPSK 6 -80 yes 0 0 0 20 6 1
bcf3:103f:0c14 Access 8021X 6 -81 yes 0 0 0 20 6 1
bcf3:103f:0c15 Access MDM 6 -80 yes 0 0 0 20 6 1
bcf3:103f:6394 Access 8021X 11 -80 yes 0 0 0 20 6 1
bcf3:103f:6395 Access MDM 11 -80 yes 0 0 0 20 6 1
bcf3:103f:6396 Access PPSK 11 -80 yes 0 0 1 20 6 1
bcf3:103f:2bd5 Access MDM 11 -84 yes 0 0 0 20 6 1
bcf3:103f:1994 Access 8021X 11 -83 yes 0 0 0 20 6 1
bcf3:103f:1995 Access MDM 11 -83 yes 0 0 0 20 6 1
bcf3:103f:1996 Access PPSK 11 -83 yes 0 0 0 20 6 1
bcf3:103f:2756 Access PPSK 6 -89 yes 0 0 1 20 6 1
bcf3:103f:2295 Access MDM 11 -91 yes 0 0 0 20 6 1
bcf3:1062:36d6 Access MDM 11 -87 yes 0 0 0 20 6 1
bcf3:103f:2bd4 Access 8021X 11 -85 yes 0 0 0 20 6 1
bcf3:103f:2bd6 Access PPSK 11 -84 yes 0 0 1 20 6 1
bcf3:1062:36d4 Access 8021X 11 -87 yes 0 0 0 20 6 1
bcf3:103f:2296 Access PPSK 11 -90 yes 0 0 0 20 6 1
bcf3:103f:2294 Access 8021X 11 -90 yes 0 0 0 20 6 1
bcf3:103f:1894 Access 8021X 1 -86 yes 0 0 0 20 6 1
bcf3:103f:1896 Access PPSK 1 -86 yes 0 0 0 20 6 1
bcf3:103f:1b95 Access MDM 1 -84 yes 0 0 0 20 6 1
bcf3:103f:1b94 Access 8021X 1 -83 yes 0 0 0 20 6 1
bcf3:103f:1b96 Access PPSK 1 -89 yes 0 0 0 20 6 1
bcf3:1062:36d5 Access PPSK 11 -87 yes 0 0 0 20 6 1
bcf3:103f:1895 Access MDM 1 -86 yes 0 0 0 20 6 1
bcf3:103f:1094 Access 8021X 11 -86 yes 0 0 0 20 6 1
bcf3:103f:1095 Access MDM 11 -86 yes 0 0 0 20 6 1
bcf3:103f:1096 Access PPSK 11 -87 yes 0 0 0 20 6 1
bcf3:103f:1997 Access Stapler 11 -79 yes 0 0 0 20 6 1
bcf3:103f:1b97 Access Stapler 1 -87 yes 0 0 0 20 6 1
bcf3:103f:0c17 Access Stapler 6 -82 yes 0 0 0 20 6 1
bcf3:103f:2bd7 Access Stapler 11 -81 yes 0 0 0 20 6 1
bcf3:103f:1817 Access Stapler 6 -60 yes 0 0 0 20 6 1
bcf3:1062:36d7 Access Stapler 11 -89 yes 0 0 0 20 6 1
bcf3:103f:2797 Access Stapler 11 -90 yes 0 0 0 20 6 1
bcf3:103f:2c97 Access Stapler 6 -84 yes 0 0 0 20 6 1
bcf3:103f:2297 Access Stapler 11 -88 yes 0 0 0 20 6 1
bcf3:103f:2757 Access Stapler 6 -85 yes 0 0 0 20 6 1
bcf3:103f:1f57 Access Stapler 1 -59 yes 0 0 0 20 6 1
bcf3:103f:1097 Access Stapler 11 -86 yes 0 0 0 20 6 1
bcf3:103f:6397 Access Stapler 11 -81 yes 0 0 0 20 6 1
bcf3:103f:2dd7 Access Stapler 1 -81 yes 0 0 0 20 6 1
bcf3:103f:1897 Access Stapler 1 -85 yes 0 0 1 20 6 1
bcf3:103f:2755 Access MDM 6 -87 yes 0 0 0 20 6 1
bcf3:1068:f797 Access Stapler 6 -86 yes 0 0 0 20 6 1
bcf3:103f:1157 Access Stapler 11 -88 yes 0 0 0 20 6 1
bcf3:103f:1156 Access PPSK 11 -89 yes 0 0 0 20 6 1
bcf3:1058:7797 Access Stapler 1 -88 yes 0 0 0 20 6 1
bcf3:103f:1155 Access MDM 11 -90 yes 0 0 0 20 6 1
bcf3:103f:1154 Access 8021X 11 -89 yes 0 0 0 20 6 1
bcf3:1058:7796 Access MDM 1 -90 yes 0 0 0 20 6 1
bcf3:103f:2754 Access 8021X 6 -87 yes 0 0 0 20 6 1
bcf3:103f:2794 Access 8021X 11 -90 yes 0 0 0 20 6 1
bcf3:1068:f796 Access PPSK 6 -88 yes 0 0 0 20 6 1
bcf3:1058:7794 Access PPSK 1 -88 yes 0 0 0 20 6 1
bcf3:1058:7795 Access 8021X 1 -88 yes 0 0 0 20 6 1
bcf3:103f:2795 Access MDM 11 -90 yes 0 0 0 20 6 1
bcf3:103f:2796 Access PPSK 11 -91 yes 0 0 0 20 6 1
bcf3:1068:f795 Access MDM 6 -87 yes 0 0 0 20 6 1
bcf3:1068:f794 Access 8021X 6 -87 yes 0 0 0 20 6 1
bcf3:1068:f8d7 Access Stapler 1 -90 yes 0 0 0 20 6 1
bcf3:1068:f8d5 Access MDM 1 -91 yes 0 0 0 20 6 1
10e7:c657:7063 Access DIRECT-62-HP OfficeJe... 6 -70 no -- -- -- 20 - -
8807:4bb2:1f80 Access LG V10 6 -59 no -- -- -- 20 - -
bcf3:1068:f8d4 Access 8021X 1 -89 yes 0 0 0 20 6 1
bcf3:1068:f8d6 Access PPSK 1 -93 yes 0 0 0 20 6 1
bcf3:1062:6797 Access Stapler 6 -87 yes 0 0 0 20 6 1

I guess the power rate on all Aps is still too high? I noticed many of the aps got a pretty high crc rate, even though their summary state says “fair”. Shouldn’t they say “high collision” like written in this guide? https://extremeportal.force.com/ExtrArticleDetail?an=000079422

Anonymous · ‎03-12-2021

Well ok. Seems like the community page just deletes replies when they are above 3000 letters so my reply just got deleted before it was posted. So i will keep this one a little shorter.

The motorolas used external antennas.

Four

So i checked the acsp neighbor stats from my aps. Most of them can see one / two aps within the range of -50 to -65, the othe aps had above -70 / -80 dbm.

But i came across some aps like this one (he was in channel 11 on 2,4)

Bssid Mode Ssid/Hive Chan Rssi(dBm) Aerohive AP CU CRC STA Channel-width VID NVID
bcf3:103f:3f14 Access 8021X 11 -86 yes 0 0 0 20 6 1
bcf3:103f:3f15 Access MDM 11 -86 yes 0 0 0 20 6 1
bcf3:103f:3f16 Access PPSK 11 -86 yes 0 0 0 20 6 1
bcf3:103f:2794 Access 8021X 11 -68 yes 0 0 0 20 6 1
bcf3:103f:2795 Access MDM 11 -68 yes 0 0 0 20 6 1
bcf3:103f:2796 Access PPSK 11 -68 yes 0 0 0 20 6 1
bcf3:103f:1b94 Access 8021X 1 -83 yes 0 0 0 20 6 1
bcf3:103f:1b95 Access MDM 1 -86 yes 0 0 0 20 6 1
bcf3:103f:1b96 Access PPSK 1 -87 yes 0 0 0 20 6 1
bcf3:103f:2dd4 Access 8021X 1 -80 yes 0 0 0 20 6 1
bcf3:103f:2dd5 Access MDM 1 -80 yes 0 0 0 20 6 1
bcf3:103f:2dd6 Access PPSK 1 -80 yes 0 0 0 20 6 1
bcf3:103f:2294 Access 8021X 11 -65 yes 0 0 0 20 6 1
bcf3:103f:2296 Access PPSK 11 -65 yes 0 0 0 20 6 1
bcf3:103f:2295 Access MDM 11 -65 yes 0 0 0 20 6 1
bcf3:103f:32d4 Access 8021X 6 -77 yes 0 0 0 20 6 1
bcf3:103f:32d5 Access MDM 6 -78 yes 0 0 0 20 6 1
bcf3:103f:32d6 Access PPSK 6 -79 yes 0 0 0 20 6 1
bcf3:103f:6394 Access 8021X 11 -77 yes 0 0 0 20 6 1
bcf3:103f:6395 Access MDM 11 -77 yes 0 0 0 20 6 1
bcf3:103f:6396 Access PPSK 11 -77 yes 0 0 0 20 6 1
bcf3:1062:6795 Access PPSK 6 -82 yes 0 0 0 20 6 1
bcf3:1062:6796 Access MDM 6 -82 yes 0 0 0 20 6 1
bcf3:1062:6794 Access 8021X 6 -82 yes 0 0 0 20 6 1
bcf3:103f:6695 Access MDM 11 -89 yes 0 0 0 20 6 1
bcf3:103f:6696 Access PPSK 11 -88 yes 0 0 1 20 6 1
bcf3:103f:6694 Access 8021X 11 -88 yes 0 0 0 20 6 1
bcf3:103f:2c95 Access MDM 6 -83 yes 0 0 0 20 6 1
bcf3:103f:2c94 Access 8021X 6 -83 yes 0 0 0 20 6 1
bcf3:103f:2c96 Access PPSK 6 -83 yes 0 0 0 20 6 1
bcf3:103f:1b97 Access Stapler 1 -86 yes 0 0 0 20 6 1
bcf3:103f:2797 Access Stapler 11 -71 yes 0 0 0 20 6 1
bcf3:1062:6797 Access Stapler 6 -82 yes 0 0 0 20 6 1
bcf3:103f:2c97 Access Stapler 6 -83 yes 0 0 0 20 6 1
bcf3:103f:2297 Access Stapler 11 -72 yes 0 0 0 20 6 1
bcf3:103f:6397 Access Stapler 11 -74 yes 0 0 0 20 6 1
bcf3:103f:3f17 Access Stapler 11 -85 yes 0 0 0 20 6 1
bcf3:103f:2dd7 Access Stapler 1 -79 yes 0 0 0 20 6 1
bcf3:103f:6697 Access Stapler 11 -88 yes 0 0 0 20 6 1
bcf3:103f:32d7 Access Stapler 6 -76 yes 0 0 0 20 6 1
bcf3:103f:4195 Access MDM 1 -90 yes 0 0 0 20 6 1
bcf3:103f:1897 Access Stapler 1 -86 yes 0 0 0 20 6 1
bcf3:103f:1896 Access PPSK 1 -86 yes 0 0 0 20 6 1
bcf3:1058:7797 Access Stapler 1 -88 yes 0 0 0 20 6 1
bcf3:1058:7795 Access 8021X 1 -87 yes 0 0 0 20 6 1
bcf3:1058:7796 Access MDM 1 -89 yes 0 0 0 20 6 1
bcf3:1058:7794 Access PPSK 1 -87 yes 0 0 1 20 6 1
bcf3:1068:fb57 Access Stapler 11 -88 yes 0 0 0 20 6 1
bcf3:103f:1895 Access MDM 1 -86 yes 0 0 0 20 6 1
bcf3:103f:1894 Access 8021X 1 -86 yes 0 0 0 20 6 1
bcf3:1068:fb56 Access PPSK 11 -89 yes 0 0 0 20 6 1
bcf3:1068:fb54 Access 8021X 11 -88 yes 0 0 0 20 6 1
bcf3:1068:fb55 Access MDM 11 -89 yes 0 0 1 20 6 1
bcf3:103f:1817 Access Stapler 6 -88 yes 0 0 1 20 6 1
bcf3:103f:1816 Access PPSK 6 -89 yes 0 0 2 20 6 1
bcf3:103f:1814 Access 8021X 6 -88 yes 0 0 1 20 6 1
bcf3:103f:1815 Access MDM 6 -87 yes 0 0 1 20 6 1
bcf3:103f:4197 Access Stapler 1 -88 yes 0 0 0 20 6 1
bcf3:103f:2e17 Access Stapler 11 -88 yes 0 0 0 20 6 1
bcf3:103f:2e14 Access 8021X 11 -89 yes 0 0 0 20 6 1
bcf3:103f:2e16 Access PPSK 11 -91 yes 0 0 0 20 6 1

Why did he chose channel 11 even though the other two aps who are nearby are on the same. Is it because they have a too low signal strength for him to change it and he doesn’t see a problem in it?

I will try to get a packet capture and will visit the plant in two weeks to get some more information from the client side.

Ovais_Qayyum · ‎03-09-2021

Were you using external antennas on AP5131? How high are the APs mounted?

How many SSIDs do you have in total?

From the RF plan perspective, it does not look that bad apart from the upper right corner of the screenshot where most of the APs are using channel 6 (purple area). But again, this is not 100% realistic and we need to have some RF packet capture taken from a client to figure out if there are excessive retransmissions of the frames probably due to the height of the APs, integrated antenna, and metallic objects in the warehouse.

bbdb2d169151457385960026fbf2bc9d_ecb65aca-d6cf-4d0e-8639-0ac0a5932f00.png

Some helpful commands to verify channel/power issues:

#sho int // to see BSSID

#sho hive // to see hive name which can be used to identify Cloud APs on the same channel

#sho acsp neigh // to see background scan list and then look for VHM hive name to easily identify BSSID of Cloud AP on the same channel

This should give you an output similar to the following, that will allow you to see how many of your APs are on the same channel and how well can they see each other, if its too strong of a signal you have too many APs (or high Tx power) and you should either reduce the Tx power or turn off some of the APs (but I doubt this would be the case), if the signal is too low you have less APs.

wifi1(6) ACSP neighbor list (17/384): Bssid           Mode     Ssid/Hive                Chan Rssi(dBm) Aerohive AP  CU  CRC STA Channel-width VID  NVID be4d:fbbf:9860  Access   3sCompany-5G             36   -87       no           --  --  --  40+           -    -    206c:8a05:1924  Access   AOA                      36   -58       yes          7   17  2   20            1    1    206c:8a05:1920  Backhaul VHM-CYRUJRGN             36   -57       yes          7   17  1   20            1    1    989d:5de9:77aa  Access   kikobull-5G              40   -77       no           --  --  --  80            -    -    2405:8823:8f8b  Access   google                   149  -85       no           --  --  --  80            -    -    2405:8823:8546  Access   google                   149  -62       no           --  --  --  80            -    -    2405:8823:9b67  Access   google                   149  -75       no           --  --  --  80            -    -    3894:edf2:c882  Access   NETGEAR77-5G             149  -77       no           --  --  --  80            -    -    4065:a3ab:1097  Access   BELL918                  157  -89       no           --  --  --  80            -    -    989d:5de9:77ab  Access                            40   -76       no           --  --  --  80            -    -    989d:5de9:77af  Access                            40   -76       no           --  --  --  80            -    -    989d:5de9:77ad  Access                            40   -76       no           --  --  --  80            -    -    989d:5de9:77b0  Access                            40   -76       no           --  --  --  80            -    -    2605:8823:8f89  Access                            149  -86       no           --  --  --  80            -    -    2605:8823:8545  Access                            149  -61       no           --  --  --  80            -    -    bcf3:102b:80b0  Backhaul hive0                    36   -48       yes          0   0   0   20            1    1    36f1:50c4:47c0  Access   DIRECT-roku-L0J-417A8... 36   -54       no           --  --  --  20            -    -

To solve this issue, you need to first determine if it the application disconnect or client disassociation/disconnect. if its client disassociation/disconnect, the cause could be roaming, bad coverage etc. If its only application disconnect, it could be due to bad RF, retransmission to being with, and the best way to check it would be to connect a client to an AP, don't move the client and check if the application still disconnects.

While doing it take packet capture, without it we can’t determine the issues in an effective way.

Regards,

Ovais

Extreme Networks

Problems with old WLAN Clients after changing the WLAN infrastructure

Problems with old WLAN Clients after changing the WLAN infrastructure