Wireless Access

last person joined: 4 hours ago 

Access network design for branch, remote, outdoor and campus locations with Aruba access points, and mobility controllers.
Expand all | Collapse all

Aruba OS 6.3.1.3 issue with regulatory domain

  • 1.  Aruba OS 6.3.1.3 issue with regulatory domain

    Posted Apr 01, 2014 02:19 AM

     

     

    I recently updated Aruba controller 3200 to the latest 6.3.1.3 OS, however after the reboot some APs has turned to Air monitor mode and showing Domain missmatch flag.

     

    Downgrading back to 6.1.3.12 OS the APs went back to AP mode, does anyone has any idea why this issue is happening only on the latest OS and what would be the solution to force those APs to AP mode instead of Air monitors.


    #3200


  • 2.  RE: Aruba OS 6.3.1.3 issue with regulatory domain

    Posted Apr 01, 2014 02:37 AM

    What domain are they configured for?



  • 3.  RE: Aruba OS 6.3.1.3 issue with regulatory domain

    Posted Apr 01, 2014 02:38 AM

    The AP profile is configured for US domain



  • 4.  RE: Aruba OS 6.3.1.3 issue with regulatory domain

    Posted Apr 01, 2014 02:43 AM

    Let us know the AP modal and the country code of the controller and regulatory domain country code. 

     

    also try 

     

    #show ap allowed-channels ap-name <name of ap>

       or  

    # show ap allowed-channels country-code <Code> ap-type <AP> 

     

    #  Show ap details adv ap-name <name>

     



  • 5.  RE: Aruba OS 6.3.1.3 issue with regulatory domain

    Posted Sep 03, 2014 01:35 PM

    # show ap allowed-channels country-code <Code> ap-type <AP>

     

    Thanks for this command -- very useful!

     

    We have some AP-103Hs and couldn't get them working on a 620 controller running 6.4.1.0 - this command showed an empty list for that model in the GB regulatory domain.  The AP booted but remained in AirMonitor mode (because no channels were available).

     

    Upgrading the 620 to 6.4.2.0 gives a full list and and the AP-103H springs into life properly, in regular AP mode.  Looking more closely at the 6.4.2.0 release notes, support for this AP in the United Kingdom (= GB) area was only added then, requiring that as a minimum release.

     

    [I also note that 6.4.2.0 adds support for separate updating of the regulatory domain, not requiring new ArubaOS releases.]