Thank you for your indication.
I usually work with standard configuration in my Wi-Fi systems. I just configure RF (20 MHz Channels Width, and minimun powers) and disable standards (11ax, 11r) if I am not sure clients can support those standars and protocols.
With Honeywell devices from Honeywell technicians I have received the following Honeywell official document about AOS-6 "Aruba Backbone Best Practices - Solution number KB-000011578" (see attached pdf).
The document says:
A: Aruba has stated that some BG radios will fail to operate correctly if the Legacy Station
Workaround parameter is not enabled. This problem has been seen while using the Summit 30AG
radio as well. If the parameter is left disabled the user can expect to see multiple missed pings and
retries will be much higher.
o To locate this parameter go to: Configuration |AP Configuration |Select the profile that
you want to edit |RF Management |802.11g radio Profile |High-Throughput Radio
Profile |Enable Legacy Station Workaround
o This setting allows all clients to receive data through two ports when the box is not checked.
If the box is checked there will be no change on how the 802.11n clients operate, but
communication to the 802.11b/g clients will happen through a single port. The exception to
this is all broadcast traffic, even to 802.11n clients will also happen through a single port.
B: By default Aruba enables several scanning features in the controller. When these are enabled the
controller may miss or not acknowledge messages sent by the radio. To correct this problem disable the
Scanning, Power Save Aware Scan and Multi-Band Scan features.
o To locate these parameters go to: Configuration |AP Configuration |Select the profile that
you want to edit |RF Management |802.11g radio Profile |Adaptive-Radio Management |
Verify that the Scanning, Power Save Aware Scan and Multi-Band Scan boxes are not
checked.
o When enabled the controller will perform background scans to try and to perform RF channel
optimization. (Note: These settings operate in a similar way as the RRM feature on the Cisco
controller.)
By default the number of retries on the Aruba controller is much lower than that of the Cisco
controller.
o To adjust the numbers of retries that the controller makes go to: Configuration | AP
Configuration |Wireless LAN | Virtual AP | Select the proper profile |SSID Profile
Advanced |Maximum Transmit Failures = 20
o Will increase the number of retries that the controller will make to get the message through.
c: The Aruba controller by default tries to send the EAPOL frames at the highest possible data rate. In
some cases this may cause the authentication process to fail since the Aruba controller never tries
802.11b data rates if needed. If left unchecked the customer may see long delays in roaming if the
max retry limit is exceeded. This in turn may cause an 8 second (Auth Timeout default value for
Summit) or longer delay in roaming.
o To allow the controller to send EAPOL frames at the lower data rates go to: Configuration
| AP Configuration |Wireless LAN | Virtual AP | Select the proper profile |SSID Profile
Advanced |Enable "Rate Optimization for Delivering EAPOL Frames"
o Enable the Rate Optimization for Delivering EAPOL Frames setting to allow EAPOL
packets to be sent at 1 Mb/sec. (Note: Cisco also sends their EAPOL packets at 1Mb/sec.)
D: The customer is not able to ping the wireless device immediately after the terminal is rebooted or
before IP traffic from the client is sent. Once IP traffic from the client is sent, then communication
in both directions can take place with no issues.
o Aruba has added a new feature to the 6.1.3.x code (Suppress ARP) that will prevent ARP
tables from being updated until IP traffic is passed by the client. By default this IP traffic is
not present on terminals like the Thor and Tecton when the device is simply booted.
o Disable the setting shown below to allow ARP packets to pass even if no IP traffic has been
sent. The CLI command below is an example on how this feature can be disabled.
Example:
o (local-2) (config) #interface vlan 192
o (local-2) (config-subif)#no suppress-arp
Original Message:
Sent: Sep 23, 2024 07:40 AM
From: GorazdKikelj
Subject: Aruba and Honeywell Barcode reader guns handheld computers compatibility
If you are back on the FW versions there are many improvements made on wireless drivers. So I would first try to get to latest LSR version or at least to latest version of your current branch.
Best, Gorazd
------------------------------
Gorazd Kikelj
MVP Guru 2024
Original Message:
Sent: Sep 22, 2024 03:57 AM
From: lbrune
Subject: Aruba and Honeywell Barcode reader guns handheld computers compatibility
Hi all !!
Thank you in advance for your sharing.
One of my customer has an Aruba Instant Wi-Fi infrastructure in his warehouses and his wi-fi
clients are old Honeywell CK3 (Windows) and new Honeywell CK65 (Android) Barcode reader guns handheld computers.
The issue is the old Honeywell CK3 (Windows) are working well, the new Honeywell CK65 (Android) lost connection to the server AS400.
The Honeywell technicians say they have no problem in other infrastructures.
Do you have info about Honeywell CK65 issue in aruba infrastructures?
I know there could be many and different reasons why I have the issue, not only Wi-Fi, so any suggestion will be interesting.
Thank you all