This is the situation. We have multiple NV-160 access points in various buildings around our campus. All of them are connected to different Netvanta switches, but all are controlled by one 1638. We were forced to power-cycle one of our 1335s that has one of these APs connected to it. Since it came back up, the 1638 says the AP is controlled by another AC. This is not the case, as I have checked all of our Adtran switches and found NONE of them are enabled to act as ACs. Today, I was forced to power-cycle the 1638 due to a PoE issue. When the switch came back up, the AP connected directly to it is reporting the same error.
I need to know what the proper procedure is to reset the NV-160 to factory default. I have found nothing in any documentation available to me on the site that explains how this is done.
I believe I found the source of the problem. In a last-ditch effort to reset the APs, I disabled the AC on the 1638 and enabled AC on a different 1335 on our network. As soon as the 1638 dropped out, the 1335 picked up all of our APs (with their current configurations) and everything is now good. I can only assume our 1638 somehow suffered some internal problem that power cycling could not remedy.
So the moral of this story; even if it causes you a massive headache, try a different AC before assuming the AP is the problem.
Is the only solution to reflash the firmware on the AP?
Each time a 160 boots it has no memory of what it was doing previously. It reaches out over AWCP and asks for a controller to take ownership of it the same way every time. I have encountered the "other AC" issue in some versions of 160 software but there were resolved by power-cycling the 160. Assuming your 160s are connected to powered switch ports, have you tried a shut/no shut?
If you have physical access there is a pinhole reset button on the side of the 160, near the console port. If you don't see the console port then both are under a sticker.
- Jeff
This has not worked for me yet. The 160's must be retaining SOME of the configuration, because even though my 1638 claims it isn't in control, I can still connect to the APs with my laptop.
Well, that was until I just took the one that is connected directly to the 1638 down to try to address this problem. It no longer shows up in the "AC/AP Discovery" page. It's as though it has vanished, but I was still able to connect to the AP with my laptop. So I took it down and held the reset switch in for about 60 seconds to see if I could get a rise out of the unit and now the SSID is gone completely. Added bonus; the 160 STILL doesn't show up in the "AC/AP Discovery" page.
This is starting to affect my workplace. I've had to put a Linksys AP up as a temporary solution. I need to get this resolved as soon as possible. How do I manually kick this thing into recovery mode? I thought holding the reset switch for as long as I did would have done it, but nothing...
I believe I found the source of the problem. In a last-ditch effort to reset the APs, I disabled the AC on the 1638 and enabled AC on a different 1335 on our network. As soon as the 1638 dropped out, the 1335 picked up all of our APs (with their current configurations) and everything is now good. I can only assume our 1638 somehow suffered some internal problem that power cycling could not remedy.
So the moral of this story; even if it causes you a massive headache, try a different AC before assuming the AP is the problem.