USG40W with WAX510D Allowed WTP number is FULL. retval = -82000
danyedinak
Posts: 51 Ally Member
After initially having no problems adding this AP USG40W as a managed device that could be queried, rebooted, and otherwise showed powered up and online, albeit with zero stations (on either 2.4 or 5GHz), when I prepared to move the AP (for this site only - several others have worked without major incident) into an active ap-group-profile (via the web gui) I began running into a number of problems with this one site after trying to add the AP to an ap-group-profile and changing the local-ap to a different group (effectively forcing the devices to disconnect from the local-ap and re-connect to the new wax510d). Symptoms included :
The error is the same whether trying to add through the GUI, or via SSH using capwap ap add <mac address>.
Currently, the USG40W is running 4.60(AALB.0), with an upgrade to V4.60(AALB.1) scheduled to occur tonight. The AP is running V6.10(ABTF.8), which was manually installed directly on the AP before it was added to mgmt.
Other unusual issues were that running :
The only other item that was strange was, at some point during troubleshooting, I ran :
Licensing Registration in the USSG did, inaccurately, show the router as unregistered, but a quick refresh resolved that, and has not allowed the AP to be managed, once again.
Nothing appears from the following :
Once the router firmware update has completed, I will make another attempt to add the AP and will update this post. That said, if there's any little nook or cranny that someone can suggest look at in hopes of poking this thing into behaving would greatly appreciated - and would save 2 hours of driving. So far I only see one other reference to this error, and that one ( posted here : https://businessforum.zyxel.com/discussion/999/allowed-wtp-number-is-full ) has had no updates since 2018. Curiously, it was also a USG40.
- No devices were showing as connected
- Device logs show no attempts to connect
- Presumption that the radio was not broadcasting
- Confirmed that the AP group appeared to be stuck in "Unclassified"
- Logs shows that a capwap interaction occurred between the USG40W and the WAX510D with "partial" success.
- Rebooting the AP
- Powering off and the port on the GS1350-12HP switch and then powering back on
- Rebooting the router
- Removing the AP "rule"
Allowed WTP number is FULL.
retval = -82000
ERROR: Allowed WTP number is FULL.
retval = -82000
ERROR: Allowed WTP number is FULL.
The error is the same whether trying to add through the GUI, or via SSH using capwap ap add <mac address>.
<div>Router# show capwap ap info</div><div>Online mgnt ap: 1</div><div>Offline mgnt ap: 0</div><div>Un-mgnt ap: 1</div><div>Station : 8</div><div><br><div></div></div>
<div>Router# show capwap ap wait-list</div><div>index: 1</div><div> IP: 192.168.31.6, MAC: <mac address></div><div> Model: WAX510D, Description: AP-<mac address></div><div> NebulaFlex PRO: Yes</div><br>show capwap ap all <br>index 1 : ... local-ap.
Currently, the USG40W is running 4.60(AALB.0), with an upgrade to V4.60(AALB.1) scheduled to occur tonight. The AP is running V6.10(ABTF.8), which was manually installed directly on the AP before it was added to mgmt.
Other unusual issues were that running :
show capwap ap <mac address> showed the desired AP Group Profile : <name>. However, running :
show ap-group-profile <name> Lists nothing in "apgroup profile member list:"
The only other item that was strange was, at some point during troubleshooting, I ran :
capwap show statisticand it did bring up 3 indices, two of which were for this AP that I am trying to regain control over. Everything was the same on index 2 and 3 : the AP Mac, TX, RX, Description, Radio, AP Status ... all of it. Now, however, only 1 index shows, and that is the local-ap.
Licensing Registration in the USSG did, inaccurately, show the router as unregistered, but a quick refresh resolved that, and has not allowed the AP to be managed, once again.
Nothing appears from the following :
show rogue-ap containment listI did attempt a :
capwap ap factory default <mac address> but, predictably, this had no impact as the AP is not currently managed.
Once the router firmware update has completed, I will make another attempt to add the AP and will update this post. That said, if there's any little nook or cranny that someone can suggest look at in hopes of poking this thing into behaving would greatly appreciated - and would save 2 hours of driving. So far I only see one other reference to this error, and that one ( posted here : https://businessforum.zyxel.com/discussion/999/allowed-wtp-number-is-full ) has had no updates since 2018. Curiously, it was also a USG40.
0
Comments
-
Hi @danyedinakAfter you upgrade to V4.60(AALB.1),what is your update status now?I think you may manually config your AP profile and reboot your USG40W again.Yon can refer to this KB which I found on Zyxel.
0
Categories
- All Categories
- 415 Beta Program
- 2.4K Nebula
- 146 Nebula Ideas
- 96 Nebula Status and Incidents
- 5.7K Security
- 262 USG FLEX H Series
- 271 Security Ideas
- 1.4K Switch
- 74 Switch Ideas
- 1.1K Wireless
- 40 Wireless Ideas
- 6.4K Consumer Product
- 250 Service & License
- 387 News and Release
- 84 Security Advisories
- 29 Education Center
- 10 [Campaign] Zyxel Network Detective
- 3.5K FAQ
- 34 Documents
- 34 Nebula Monthly Express
- 85 About Community
- 73 Security Highlight