if you examined the default IAP setup, it should be in "cluster mode", meaning, if you have a IAP with compatible firmware, it will seek the VC and auto-join the cluster. therefore, if your 305 and 207 are both up, you see 207 is in the 305 cluster. furthermore, once it joined the cluster, it inherited the configuration of the VC, that is why your admin pwd works, you have do a factory reset to get out of it. to boot your IAP in standalone mode, you need to change the IAP model swarm-mode instead of cluster mode. see
https://community.arubanetworks.com/community-home/digestviewer/viewthread?MID=47005------------------------------
Peter Huang
------------------------------
Original Message:
Sent: Feb 20, 2020 08:36 AM
From: Jeff White
Subject: New IAP Login
Everyone,
I took the AP home where I have a 305. I plugged it in and when trying to browse to the IP it was given it kept redirecting to my VC, so I know it was doing what it was supposed to be doing. I was way behind on firmware so I upgraded to 8.5 on my AP. Once I was on the same version, I was able to see the 207. I unplugged the 305 and left the 207 online just to confirm that it would still work and it did. So as of now, I am able to access it since it inherited my admin password, but I am still unsure why it was not working previously.
So just to clarify, on this AP the serial number is CNH4JST4LM, so I am using username: admin and password: CNH4JST4LM
If that is correct, then I will chalk it up to a bug or something, but if that isn't correct, please correct me. I appreciate everyone's help with this. Thanks!