Wireless Access

 View Only
Expand all | Collapse all

Don't trust Airmatch or reported values. Validate with other tools like Ekahau or Aruba UXI sensors

This thread has been viewed 31 times
  • 1.  Don't trust Airmatch or reported values. Validate with other tools like Ekahau or Aruba UXI sensors

    Posted Jan 24, 2025 02:09 PM

    We have two clusters, each cluster has two 7240XM controllers. Cluster is L2 connected. Environment is managed by an active Mobility Conductor. We have a standby MC.Everything is running 8.10.0.14.  TAC Case open for issue noted below. We are advised by Aruba ERT engineer that they are escalating issue to a higher level engineering team. TAC has confirmed our findings during multiple remote session. HPE/Aruba has not sent anyone onsite.

    The issue:

            Airmatch is not honoring 5GHz channel assignment as defined in AP groups. In addition, and most worrisome, the channels reported by the MD, MC and Airwave may be incorrect. This is not restricted to any one specific AP group, cluster or location. We have multiple AP groups configured across out hospitals. Standard AP group settings allow all 5 GHz channels except channels 36,144,165. We only use 20 MHz channel width.

           We discovered Airmatch (or maybe some other protocol) is assigning channels 36 and 165. We suspect channel 144 is also being assigned but have not confirmed that with Ekahau or the Aruba UXI sensors. TAC has confirmed our findings. We can prove 100 % that an AP is using channel 36 (match BSSID) per UXI and Ekahau  whereas the Aruba infrastructure, MDs, MC and Airwave all report the AP is using another channel. Example, Aruba infrastructure may show the AP on channel 64.

           When we associate a Win11 device or a Vocera badge, we see channel 36 displayed on GUI of each yet the Aruba infrastructure shows the client is connected to the channel the Aruba infrastructure is reporting the AP is using, say channel 64 to use the example above.

           How does anyone manage the environment if the Aruba Infrastructure information is incorrect / hence invalid? Needless to say, this issue is monitored by our IT leaders as we wait resolution and root cause information.

           Email me directly and I will share additional information such as screen snippets, tech logs case notes as applicable.



    ------------------------------
    Lenny Vigneault
    Informatics & Technology
    Baystate Health, Inc.


    ------------------------------


  • 2.  RE: Don't trust Airmatch or reported values. Validate with other tools like Ekahau or Aruba UXI sensors

    Posted Feb 04, 2025 02:15 PM

    After three weeks of troubleshooting and multiple remote sessions with multiple TAC Engineers,  this issue is being tracked via internal ticket# AOS-262499.