Hi.
You need to open TAC case with Central so that they archive your AP in GreenLake inventory and detach subscription. Looks like your AP was used by Central in previous life. It happen quite often with refurbish/spare part APs. Usually it's resolved in a few hours.
Original Message:
Sent: Sep 26, 2024 06:28 PM
From: vvajpeyi
Subject: Factory 515 not discovering conductor after setting enviroment with console
Hello, yes I have tried the paper clip factory reset and connected on a non wireless vlan and just with POE. The console shows its getting af power. But when it gets close to the instant mode which flashes each symbol as if it trying to get a dhcp and connect to the instant dashboard. The device is in instant mode now with a SetMeUp SSID. When I get to the gui and am forced to change the password I get the message "Configuration denied by Aruba Central Management" I logged into my orgs GreenLake account and searched by SN but it not in my inventory device list.
Original Message:
Sent: Sep 26, 2024 06:15 PM
From: chulcher
Subject: Factory 515 not discovering conductor after setting enviroment with console
The AP should be able to discover just using the existing discovery (DNS or DHCP) method that you have in place. You should also be able to allow the AP to boot into Instant mode and then perform a manual conversion from there.
------------------------------
Carson Hulcher, ACEX#110
Original Message:
Sent: Sep 26, 2024 05:36 PM
From: vvajpeyi
Subject: Factory 515 not discovering conductor after setting enviroment with console
I got an RMA replacement running 8.10.0.8-8.10.0. It is not connecting and discovering my conductor. At the console I have tried setenv servername:aruba-master, aruba-conductor, setenv master [ip address]. I made sure the DNS name for my conductor reflected the name change. Are there any changes to recognized parameters? I changed my dns to be aruba-conductor to onboard 635s. But it doesn't seem to respond with an RMA 515
Thanks.