EAP PPSK Incompatible Feature Issue
EAP PPSK Incompatible Feature Issue
In reviewing the incompatible features of my EAP610 (v3.0) and EAP650-Desktop (v1.0) devices, the PPSK feature states in the capability description the following:
The device does not support Rate Limit and expiration settings
The device supports 1024 (or 128) items
When expanding the feature with the + icon, under Name, I am seeing some SSIDs being duplicated and other SSIDs that no longer exist in the network. For example, in the screenshot below the WiFi_4880 SSID is listed twice and the WiFi_2880_5G SSID no longer exists.
After doing a Force Provision, reboot, and power cycle, the EAP continues to show the same results. I also have rebooted the OC300 controller. Can someone confirm that this is a firmware compatibility issue with the controller’s v6.2 firmware?
On a related matter, the expanded description states “The device does not support the Rate Limit and expiration settings configured in this configuration entry. The entry will not be delivered to the device.” Does this mean that only these two settings are not sent to the device or does it mean the entire configuration entry is not delivered? If it is only the two settings that are affected, then the wording should be changed to “These settings will not be delivered to the device.”
Update: I managed to clear out the bogus descriptions by forgetting each device and re-adopting. The PPSK feature no longer appears in the list of incompatible features for the EAP650-Desktop devices. It still appears for the EAP610 but no longer has the + icon with the erroneous entries.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
I have the same on all 8 of my EAP650 v1 units on two sites since the 1.3.6 / 1.3.7 updates (i think, didnt really check this before)
Whats the concensus here? Forget and readopt?
To be honest they seem to be working perfectly fine with my PPSKs
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
I took a more careful look at the incompatible entries themselves and i think i have a conclusion
I think whats causing them is too many things are lumped into one check, and if any fail, the entry appears.
For example, in my case the entry lists MLO amongst other things, and even though the device supports other stuff mentioned, because this is included in a check, and the device doesnt support it, it flags the whole entry
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 502
Replies: 13
Voters 0
No one has voted for it yet.