Known Issues
These are the known issues in this release of FortiWLM.
|
Bug ID |
Description |
Impact |
Workaround |
|---|---|---|---|
|
596798 |
[FortiGate] The rogue AP counts in FortiWLM and FortiGate do not match. |
|
|
| 673899 | [FortiWLC] ARRP profile synchronization fails after FortiWLM backup file is restored. | ||
|
676623 |
[FortiWLC] The Rogue AP profile cannot be synchronized from FortiWLM to the controller after reboot. |
|
|
| 681777 | [FortiWLC] Restoring sys-config files backed up before FortiWLM upgrade fails. |
|
|
|
690489 |
FortiWLC and FortiGate access points can be added to the same AP group. |
|
|
|
694995 |
[FortiWLC] The controller reboots every hour after applying the sysconfig of a different controller. |
|
Change the IP address and then apply sysconfig. |
|
696506 |
Sometimes, alert message is not received after applying controller configuration backup to different/same FortiWLC. |
|
|
|
700591 |
[FortiGate] Sometimes, live Spectrum data is not uploaded in FortiWLM. |
Spectrum Analyzer does not display data accurately. |
Reboot the AP/controller |
|
703351 |
The Locate Client option does not load the correct location in the stations dashboard. |
|
|
|
710943 |
[On upgarde from 8.6.0] Data is not displayed in the RF Planner page. |
|
|
|
711372 |
The locationing service restarts continously after restoring data ( with locationing service confiured). |
|
Disable locationing service. |