Wireless Access

last person joined: 5 hours ago 

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

No active or standby controller for APs

Jump to Best Answer
  • 1.  No active or standby controller for APs

    Posted Jan 10, 2019 01:12 PM
      |   view attached

    I have a VMM-Cluster and an 7210 MC. The VMM and MC are connected via VLAN10.

    There are two APs in VLAN20 (MC has IP 10.73.3.254 in VLAN20 and can ping the APs).

    In the WebUI of the VMM-Cluster I can see the APs at "Configuration" > "Access Points" but they do not show up at "Dashboard" > "Access Point".

    In the WebUI of the MC I can see the APs, but they do not have an active or standby controller (see attached image).



  • 2.  RE: No active or standby controller for APs

    Posted Jan 10, 2019 02:42 PM

    I belived I’ve seen this at older AOS8. It is more of a nuisance/cosmetic than problem. Upgrade the OS was fixed my issue.



  • 3.  RE: No active or standby controller for APs

    Posted Jan 10, 2019 03:08 PM

    The configuerd WLANs are also not beeing shown and are not working.



  • 4.  RE: No active or standby controller for APs

    Posted Jan 10, 2019 03:43 PM

    Are your MM and MC on the same code?  What version? 

    from MC can you post: 

    show ap-group fem-ap-group

    show ap-system profile <the profile attaches to fem-ap-group>

    show vrrp

     

     



  • 5.  RE: No active or standby controller for APs

    Posted Jan 11, 2019 05:00 AM

    This is the output of "show ap-group fem-ap-group":

     

    AP group "fem-ap-group"
    -----------------------
    Parameter                                Value
    ---------                                -----
    Virtual AP                               Test
    802.11a radio profile                    default
    802.11g radio profile                    default
    Ethernet interface 0 port configuration  default
    Ethernet interface 1 port configuration  default
    Ethernet interface 2 port configuration  shutdown
    Ethernet interface 3 port configuration  shutdown
    Ethernet interface 4 port configuration  shutdown
    AP system profile                        default
    AP multizone profile                     default
    802.11a Traffic Management profile       N/A
    802.11g Traffic Management profile       N/A
    Regulatory Domain profile                default
    RF Optimization profile                  default
    RF Event Thresholds profile              default
    IDS profile                              default
    Mesh Radio profile                       default
    Mesh Cluster profile                     N/A
    Provisioning profile                     N/A       
    AP authorization profile                 N/A

    The command "show ap-system profile" is not available at all.

    "show vrrp" gives no output (I do not have a redundant MC at the moment).

     

    The VMM and the MC are running ArubaOS 8.3.0.1.

     

     



  • 6.  RE: No active or standby controller for APs

    Posted Jan 11, 2019 05:03 AM

    If you can, please upgrade the MM and the MD (mobility controller) to 8.3.0.5 and test again.



  • 7.  RE: No active or standby controller for APs

    Posted Jan 11, 2019 11:20 AM

    I did upgrade the MM and the MD to 8.3.0.5, but nothing changed. The APs are showing up at the 7210 but do not appear in the MM. Also, no WLANs are visible.

    Does the MM need access to the AP VLAN?



  • 8.  RE: No active or standby controller for APs
    Best Answer

    Posted Jan 11, 2019 11:26 AM

    No, MM doesn't need the AP VLAN.  This is a good case for TAC.  Too many things can be wrong, licensing? RF profile? WLAN configurations...  

     



  • 9.  RE: No active or standby controller for APs

    Posted Jan 11, 2019 12:49 PM

    Thanks, I will open a case for this and post the solution here.



  • 10.  RE: No active or standby controller for APs

    Posted Jan 18, 2019 06:31 PM

    The problem is now solved. 

    I eval licenses for PEF and deactivate when using the proper licenses, appearently it requires a restart of all connected systems to properly deactivate PEF (see also: https://community.arubanetworks.com/t5/Wireless-Access/ArubaOS-8-2-1-cannot-create-Wlan-without-PEF-license/td-p/405492).