Outstanding Issues for the AX411 Access Point

The following items describe the outstanding issues for the AX411 Access Point:

On SRX210, SRX240, and SRX650 devices, when you commit changes to the WLAN hierarchy in the command-line interface (CLI) or apply changes on the Wireless LAN tab of the J-Web interface, it might take up to several minutes before the new settings are reflected on the access point. The actual delay depends on the number of access points connected and the number of virtual access points (VAPs) configured on the access points. [PR/450230]
On SRX210, SRX240, and SRX650 devices, when you use the CLI to commit changes to WLAN settings, the services gateway might not respond immediately to the queries while it delivers the configuration to the access point. This might result in the following error message in response to show commands:
```
the wireless-lan-service subsystem is not responding to management requests
```
The device responds correctly after it finishes delivering the configuration to the access point. This process takes between 5 to 50 seconds, depending on the complexity of the access point configuration changes. [PR/460736]
On SRX210, SRX240, and SRX650 devices, when more than one AX411 Access Point is connected, both the J-Web and CLI interfaces show incorrect license usage information. The Licenses Used column correctly shows 0 if no access points are connected. However, if any access points are connected, this column always shows 1 even if two or more access points are connected. [PR/464268]
On SRX Series devices configured for Layer 3 mode, when the DHCP router is configured outside the DHCP pool, disconnecting one of the access points can cause continuous rebooting of the other access points. The workaround for this issue is to reconfigure DHCP so that the DHCP router is within the DHCP pool, as shown in the following configuration:
```
root@silver# show system services
dhcp {
    pool 10.1.1.1/24 {
        router {
            10.1.1.1;
        }
    }
}
```
[PR/464296]
On SRX210 devices with the default Power over Ethernet (PoE) configuration, a fourth access point connected to the services gateway does not boot. The workaround for this issue is to configure all PoE ports for a maximum power of 12.4 watts using the following command:
```
root@silver# set poe interface all maximum-power 12.4
```
[PR/465307]
When you are configuring a VAP with security that requires RADIUS authentication and the RADIUS server is not specified for the VAP, attempting to commit the configuration results in the following error message:
```
Missing mandatory statement: 'radius'
```
The workaround for this issue is to specify the RADIUS server in the VAP configuration. [PR/482040]
Depending on the country code setting, the AX411 Access Point supports different channel and bandwidth settings per radio. In the current software there is no restriction to avoid an incorrect setting. If the radio is set incorrectly, it might behave erratically or might not function at all. Use the procedures described in the section "Setting the AX411 Access Point Country-Specific Settings" in the AX411 Access Point Hardware Guide to apply settings that comply with regulations for radio frequency usage in your country. [PR/498374]
The access point prioritizes data traffic over management traffic.
When many VAPs are enabled (with the radios on) and/or the DHCP client needs to be restarted, the Web response times can fluctuate. Occasionally the browser might incompletely load a page and might not accept form submissions. This issue can be resolved by clearing the browser cache and reloading the page.
As additional VAPs are enabled, performance is impacted because of the additional control traffic.
With a large number of VLANs and clients, network users might experience client disassociations. The workaround is to increase the Group Key Timeout setting or to set it to zero.
The WPA2-AES/PSK fragmentation is 16 bytes larger than the configured threshold. The IEEE802.11-2007 standard allows +8 bytes.
When the access point is highly loaded (high data traffic volume, maximum number of VAPs, and maximum number of clients), a decrease in performance can result. This can include high management response times, slow data management retrieval, and generally slow access point operation.
The access point does not always randomize UDP source port numbers.
When the country code is set to IE, the power levels sent in the beacons are incorrect.
When the access point is heavily loaded with traffic, the J-Web interface on the services gateway that manages the access point becomes very slow.
The IEEE802.1X broadcast key refresh also sends the EAPOL frame tagged 'session' key.
The beacon interval might vary by up to +/-5 milliseconds from the expected 100 milliseconds.