No, there is no trace of it in the controller after it was reprovisioned. This confirms what I've suspected, that it doesn't register with the controller at all after receiving a lease. Is there a command I can give in the AP cli to force it to attempt a connection, or maybe to see if it's even been attempted and the outcome of such attemtps?
Our access points rely, as far as I've understood, on resolving 'aruba-master' to find their controller. Pasted below is the log of me checking name resolution and connection at various stages after the command prompt comes up. (emphasized for convenience). There may be something there though. I forgot to mention that the ap is a converted IAP-105, and when converting it using convert-aos-ap CAP, I had to specify the ip address of the controller rather than the hostname, as with the latter it would accept the command, say it would reboot, but never actually do. Could this possibly be a factor?
I should probably also, for completeness, note that there is a firewall between the subnets, but this is currently wide open in both directions, and the access point works perfectly fine on the same subnet and same switch if it doesn't have to do 802.1x first.
---
<<<<< Welcome to the Access Point >>>>>
~ # ping aruba-master
ping: aruba-master: Unknown host
~ # ag7100_ring_alloc Allocated 4800 at 0x86f1a000
ag7100_ring_alloc Allocated 3024 at 0x866ee000
AG7100: cfg1 0xf cfg2 0x7014
ATHRF1: Port 0, Neg Success
ATHRF1: unit 0 phy addr 0 ATHRF1: reg0 3100
AG7100: unit 0 phy is up...RGMii 1000Mbps full duplex
AG7100: pll reg 0x18050010: 0x110000 AG7100: cfg_1: 0x1ff0000
AG7100: cfg_2: 0x3ff
AG7100: cfg_3: 0x18001ff
AG7100: cfg_4: 0xffff
AG7100: cfg_5: 0xfffef
AG7100: done cfg2 0x7215 ifctl 0x0 miictrl 0x22
Writing 4
~ # ping aruba-master
ping: aruba-master: Unknown host
~ # 802.1X: User 'aruba' authentication success
~ # ping aruba-master
PING aruba-master.emgs.com (192.168.0.77): 56 data bytes
64 bytes from 192.168.0.77: icmp_seq=0 ttl=60 time=1.2 ms
64 bytes from 192.168.0.77: icmp_seq=1 ttl=60 time=0.9 ms
64 bytes from 192.168.0.77: icmp_seq=2 ttl=60 time=1.0 ms
--- aruba-master.emgs.com ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 0.9/1.0/1.2 ms