Fortinet black logo

FortiWLC Release Notes

Home Wireless Controller 8.6.7 FortiWLC Release Notes
8.6.7
8.6.7
8.6.6
8.6.5
8.6.4
8.6.3
8.6.2
8.6.1
8.6.0
8.5.5
8.5.4
8.5.3
8.5.2
8.5.1
8.5.0

Best Practices

Best Practices

The following best practices are recommended for enhanced user experience.

FNAC integration with FortiWLC

Configure lower lease time for isolation VLAN scope. This helps faster transition of IP address change after the station gets moved from isolation to registration VLAN.

Rogue AP Scanning

It is recommended not to enable rogue AP scanning on APs expected to serve dense user locations to avoid the impact of channel scan duration and wait period for the wireless users.

ARRP
  • It is recommended not to run channel plan with DFS enabled in presence of non DFS certified APs.
  • It is recommended to enable Freeze after ARRP planning is complete to avoid unplanned disruption due to channel change that can occur when the AP detects high interference.
  • In an existing deployment, if new APs are added, a re-plan is needed for the first time to add APs part of the ARRP cluster. Otherwise, the AP continues to operate in the default channel.
    Channel change won’t get triggered though high interference or high neighbour count is detected.
Multicast
  • The Multicast flag should be disabled on all ESS profiles unless it is needed for any multicast applications that do not support MDNS or SSDP. In such scenarios, it is recommended to use VLAN isolation for multicast application traffic to avoid flooding of data both in wired and wireless infrastructure.
  • IGMP snooping should be enabled in switching infrastructure when bridged data plane is configured in an ESS profile.
  • All UDP ports must be disabled and ports that are specifically needed for any application traffic should be used.
Others
  • In a deployment of 300 and more APs, it is recommended to configure Feature Group in FortiWLC or AP Groups in FortiWLM. Do not run ARRP globally (on all APs) in such a deployment as it is memory and processor intensive.
  • In case if boot script is installed, it is recommended to remove the boot script (if any being used) before Controller upgrade and configure a new valid boot script in accordance to the upgraded FortiWLC release.
Previous
Next

Best Practices

The following best practices are recommended for enhanced user experience.

FNAC integration with FortiWLC

Configure lower lease time for isolation VLAN scope. This helps faster transition of IP address change after the station gets moved from isolation to registration VLAN.

Rogue AP Scanning

It is recommended not to enable rogue AP scanning on APs expected to serve dense user locations to avoid the impact of channel scan duration and wait period for the wireless users.

ARRP
  • It is recommended not to run channel plan with DFS enabled in presence of non DFS certified APs.
  • It is recommended to enable Freeze after ARRP planning is complete to avoid unplanned disruption due to channel change that can occur when the AP detects high interference.
  • In an existing deployment, if new APs are added, a re-plan is needed for the first time to add APs part of the ARRP cluster. Otherwise, the AP continues to operate in the default channel.
    Channel change won’t get triggered though high interference or high neighbour count is detected.
Multicast
  • The Multicast flag should be disabled on all ESS profiles unless it is needed for any multicast applications that do not support MDNS or SSDP. In such scenarios, it is recommended to use VLAN isolation for multicast application traffic to avoid flooding of data both in wired and wireless infrastructure.
  • IGMP snooping should be enabled in switching infrastructure when bridged data plane is configured in an ESS profile.
  • All UDP ports must be disabled and ports that are specifically needed for any application traffic should be used.
Others
  • In a deployment of 300 and more APs, it is recommended to configure Feature Group in FortiWLC or AP Groups in FortiWLM. Do not run ARRP globally (on all APs) in such a deployment as it is memory and processor intensive.
  • In case if boot script is installed, it is recommended to remove the boot script (if any being used) before Controller upgrade and configure a new valid boot script in accordance to the upgraded FortiWLC release.
Previous
Next