Sonicwall “Error: Too small 802.11n Beacon Interval for Virtual Access Point.” June 18, 2012Posted by Samuel RIbeiro in Uncategorized.
Compartilhando um Troubleshooting para APs Sonicpoints da Sonicwall, no meu caso eu estava configurando dois perfis e adicionando no AP
Article Applies To:
Gen5: NSA E8500, NSA E7500, NSA E6500, NSA E5500, NSA 5000, NSA 4500, NSA 3500, NSA 2400, NSA 2400MX, NSA 240 Gen5 TZ Series: TZ 100, TZ 100 Wireless, TZ 200, TZ 200 W, TZ 210, TZ 210 Wireless, Firmware/Software Version: SonicOS Enhanced 5.5.x. and higher
The following error appears on a SonicWALL UTM firewall controller when the SonicPoint Provisioning Profile is configured with a too small Beacon Interval. “Error: Too small 802.11n Beacon Interval for Virtual Access Point.” This Knowledge Base article aims to be a succint guide to the SonicOS Administrator that needs to configure the beacon interval in the SonicOS wireless settings.
Resolution or Workaround:
If you are not segmenting your wireless network, by using no Virtual Access Points (VAPs) or a provisioning profile with a VAP Group including only one VAP configured, then the beacon interval is to be at least 100 ms, and not greater than 1000ms. If you are instead segmenting your wireless network, by making use of a provisioning profile with a VAP Group including multiple VAPs, then the beacon interval is to be at least 100ms multiplied by the number of the VAPs added to the VAP Group. For example, if you are using a VAP Group that groups 3 VAPs, then the minimum Beacon Interval is intended to be 300ms (i.e. 3x100ms). When segmenting the wireless network (using multiple VAPs), the maximim value for configuring the beacon interval is anyway set to be 1000ms.
If the administrator configure a too small beacon interval, then the SonicOS Enhanced will show the message: “Error: Too small 802.11n Beacon Interval for Virtual Access Point”, not validating the change to the settings.