We recenttly deployed a MM network with two managed devices.
Today we upgraded to 184.108.40.206.
When we try to create a new wlan we get a message that "creating a wlan rewuires a pef license" an we cannot deploy the new wlan.
Also, I cannot add the fordward-bridge mode.
Please open a case at Aruba TAC. PEF should not be needed to create an SSID.
If bridge mode is deprecated, the best approuch would be creating the VLANs on DC side and all SSID tunnlled?
The customer has the wireless VLANs spread all over the buildings.
The recommended way with controllers is to run in tunneled mode as much as possible and have the client VLANs only configured on the controller. That makes the configuration at the access point as simple as possible as there is no need to have those distributed access VLANs, and also security is enhanced as there is no access to those VLANs except at the controller. Having no WLAN client vlans at your access layer is one of the benefits/features of having a controller.
If you believe you need bridged VLANs, it could be that Aruba Instant (with Central or Airwave for central management/control/monitoring) is the better solution. Please work with your local Aruba partner or Aruba SE to get proper guidance for your specific scenario as exceptions may apply.
I noticed that in 8.2.1, the option to create bridged VLANs is available in the GUI again, it still is preferred to use tunneled SSID mode.
I am facing the same issue. Is there a workarround except configuring it manually with all profiles on the CLI?
we have the same problem here with a customer. Is this a bug in the firmware, that is likely to be fixed in the future, or is it intended beaviour in Aruba OS and PEF will be mandatory?
While PEF is highly recommended and provides many features like QoS, advanced security, Application visibility, and should be strongly recommended for every deployment, I'm not aware of any intention to make PEF mandatory.
Everyone who experiences this issue, please open an Aruba TAC case and ask them for a proper solution as you should be able to add WLANs without PEF license.
I just got a response from TAC:
Yes there has been a change in the Design starting from 220.127.116.11 which has made mandatory now. Unfortunately this has not yet documented.
It looks like the made it mandantory now, but I'm in contact with my Systems Engineer to get mor information about this. I'll keep you posted.
This will be getting corrected in the next 18.104.22.168 release
I'm dealing with a client who can't create a WLAN for this reason. They're on AOS 22.214.171.124.
Has this been corrected in newer releases or is this still the case?
according to my sales-rep this Issue should be fixed in 126.96.36.199 or 188.8.131.52. I just upgraded the MMs to 184.108.40.206 and removed my PEFNG License. This issue is still there.
According to my Aruba Systems Engineer this Issue occures, because the wizzard is trying to create a default-role for the SSID and as you need PEFNG to create such a role. Sadly it looks like there won't be a soultion to this.
What still works is to create a new VAP-Profile on the CLI, but it won't show up in the Configuration->WLANs section in the MM-UI.
according to Aruba SE team, this issue is considered as bug an will be fixed in future releases. Workaround ist to turn on PEF Feature without adding any PEF licence. In my lab with 220.127.116.11 the workaround did it.
watch out: after running some tests I recognized that an AP will not survive a reboot and get stuck with status "no License". To get this fixed you have to turn off the PEF feature after using the wizard. You may use the role "guest" instead of "authenticated".
We have an open ticket to get a this issue fixed.
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.