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).
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.
The configuerd WLANs are also not beeing shown and are not working.
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>
This is the output of "show ap-group fem-ap-group":
AP group "fem-ap-group"
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 220.127.116.11.
If you can, please upgrade the MM and the MD (mobility controller) to 18.104.22.168 and test again.
I did upgrade the MM and the MD to 22.214.171.124, 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?
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...
Thanks, I will open a case for this and post the solution here.
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).
At Aruba, we believe that the most dynamic customer experiences happen at the Edge. Our mission is to deliver innovative solutions that harness data at the Edge to drive powerful business outcomes.
© Copyright 2020 Hewlett Packard Enterprise Development LPAll Rights Reserved.