Yes, experienced the same problem with 2 AP125's in my lab. They were working fine, converted them to RAP's (make a config mistake :-( ) and now they won't connect. Also tried al the purgeenv, saveenv, printenv even fiddeld around with setenv and saveenv but no luch so far.
- Boot process aborted
- AP in same vlan as 3400 controller
- Master is on 10.127.91.100
- DNS record rap.swdemo.nl -> 10.127.91.100
- dhcp:
Hit <Enter> to stop autoboot: 0
apboot> dhcp
en0: Up 1Gbs Full duplex, (port 1)
BOOTP broadcast 1
DHCP IP address: 10.127.91.23
DHCP subnet mask: 255.255.255.0
DHCP def gateway: 10.127.91.1
DHCP DNS server: 10.127.3.11
DHCP DNS domain: swdemo.loc
apboot>
- normal boot:
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
10.127.91.23 255.255.255.0 10.127.91.1
Running ADP...Done. Master is rap.swdemo.nl
However, it's not finding the controller.
I resolved my RAP config issue and was able to succesfully convert another, still working AP125 from CAP-mode to RAP. Then, out of curiosity, I converted the AP125 in RAP-mode back to CAP-mode and that worked fine as well.
Any suggestions would be welcome to get my old LAB equipment to work.
Bart