Hello

I have a 2860ac with two AP902s and want a single 5GHz WLAN with roaming throughout the area served by them.

When setting them up, I was unable to successfully create and apply a WLAN profile to the devices as described in the documentation. It seemed to insist on enabling the 2.4GHz WLAN. In the end, I gave up, manually configured each AP and turned off auto provisioning.

When I look at the Central Management > AP > Dashboard, the APs show up but they are red. The event log also shows errors:

2000-01-01 00:00:10 [APM] [Factory_3E66F2] Query Status failed
2000-01-01 00:00:12 [APM] [Office_3E65C2] Query Status failed
2000-01-01 00:00:12 [APM] [Office_3E65C2] Query Status failed
2000-01-01 00:00:13 [APM] [Factory_3E66F2] Apply Load Balance settings failed
2000-01-01 00:00:15 [APM] [Office_3E65C2] Apply Load Balance settings failed
2020-06-19 11:37:14 [APM] [Factory_3E66F2] Apply Load Balance settings failed
2020-06-19 11:37:16 [APM] [Office_3E65C2] Apply Load Balance settings failed
2020-06-19 11:37:17 [APM] [Factory_3E66F2] Apply Rogue AP Detection settings failed
2020-06-19 11:37:18 [APM] [Office_3E65C2] Apply Rogue AP Detection settings failed
2020-06-19 11:37:35 [APM] [Factory_3E66F2] Apply Load Balance settings failed
2020-06-19 11:37:37 [APM] [Office_3E65C2] Apply Load Balance settings failed
2020-06-19 11:37:56 [APM] [Factory_3E66F2] Apply Load Balance settings failed
2020-06-19 11:37:57 [APM] [Office_3E65C2] Apply Load Balance settings failed
2020-06-19 11:43:42 [APM] [Factory_3E66F2] Query Status failed
2020-06-19 11:43:43 [APM] [Factory_3E66F2] Query Status failed
2020-06-19 11:43:44 [APM] [Office_3E65C2] Query Status failed
2020-06-19 11:47:11 [APM] [Factory_3E66F2] Query Status failed
2020-06-19 11:47:12 [APM] [Office_3E65C2] Query Status failed
2020-06-19 11:48:15 [APM] [Factory_3E66F2] Query Status failed

If I look at the Status tab, I get [Warn: Unauthorized] under each device name. When I click on the password button, it seems to have the default admin/admin combination. Supplying the correct passwords still doesn’t allow them to go green.

I must be doing something wrong, but I have no idea what. Any suggestions please?

The 2860 GUI infers that it uses Port 4944 for Discovery and HTTP for actual access...
You've definitely got UDP Port 4944 access - because the APs are in 'the list'. I assume you've got no firewalling in place that would stop HTTP?

The username/password would be the obvious reason for failure. Have you used a really long password on either of these units? Draytek seem to have a track record, of letting you enter long passwords - and then not checking them in their entirety (but using different lengths on different devices).

Also, check the "Rogue AP Detection" page. I can't remember if you have to specifically mark your own APs as "Friendly", for them to be manageable. I can imagine that they opposite is true, if they were to be marked as "Rogue"

Thanks for responding hornbyp.

I managed to work out what was wrong and was just coming back to post the answer in case it helps anyone else.

It was indeed the username/password combination. The AP902 has a 16-character limit on the admin password. The 2860ac has a 23-character limit. I had set a maximum 23 character password for the 2860ac and was happily pasting it into the WLAN profile in an effort to make it consistent across all the devices. I wasn't aware that some parts of the interface were taking the 23-character password and happily truncating it to sixteen characters, whereas other parts would accept the whole 23-character string and causing the authentication to fail.

Once I did a hardware reset on all the Ads and managed to get a 16-character password into the WLAN profile and the devices, it all resolved itself.

There also seems to be some sort of delay after you change some settings in either access point or reset them for it all to settle down and start displaying things correctly. At one point it was applying the new password to the APs, but then not able to reconnect with them and retaining the old name I had set.

I think the implementation is crude.