Look at the stickers on the APs. APs originally sold as IAP should show "IAP-277", APs locked to campus operation (CAP) originally would just be "AP-277".
If those "new" APs are really CAP that have been converted to IAP, then options are limited. Conversion of CAP to IAP is only supported when the APs are managed within Central. Part of the conversion process also stamps a country code into the AP, if the AP is locked to a domain different from what the VC is running then that could cause issues.
Original Message:
Sent: Feb 01, 2024 10:10 AM
From: EdCrane
Subject: Some AP 277 cannot join to master virtual controller
Cluster Security is disabled and that Auto Join Mode is enabled.
Is it possible that we have both IAP 277 and AP 277 devices, and AP 277 devices cannot join the IAP 277 cluster? I have uploaded the same firmware (ArubaInstant_Centaurus_8.6.0.23_88342) via TFTP for all of them, and it seems to work. However, some devices join the cluster while others do not.
Do IAP 277 and AP 277 have different hardware? How can I check if they are IAP 277 or AP 277?
Thanks!
Original Message:
Sent: Feb 01, 2024 09:27 AM
From: chulcher
Subject: Some AP 277 cannot join to master virtual controller
The environment variable would only be useful if using a Mobility Controller.
Assuming that all of the APs are IAP models and the VC is running software compatible with the AP model, there should be no restrictions for joining because of AP model.
Make sure that Cluster Security is disabled and that Auto Join Mode is enabled. Either of those could prevent negotiation of cluster membership or require manual configuration to add new APs.
------------------------------
Carson Hulcher, ACEX#110
Original Message:
Sent: Feb 01, 2024 03:54 AM
From: EdCrane
Subject: Some AP 277 cannot join to master virtual controller
No DHCP options 60 and 43 are configured. I don't see any controls on the Planet Network switch to which they are connected, but I'll also try changing the switch and using an Aruba one.
Can the AP boot console command setenv master <ipaddr> be useful?
Is it possible that this kind of AP hardware cannot join a virtual controller by design?
Thanks
Original Message:
Sent: Jan 31, 2024 03:25 PM
From: chulcher
Subject: Some AP 277 cannot join to master virtual controller
Do you have DHCP options 60 and 43 configured on the scope and instructing the AP to join a controller or any layer 2 controls in place on the AP connected ports? If so, remove those.
If you continue to have problems and have an active support contract, contact TAC with the issue.
------------------------------
Carson Hulcher, ACEX#110
Original Message:
Sent: Jan 31, 2024 03:21 AM
From: EdCrane
Subject: Some AP 277 cannot join to master virtual controller
Hi,
We have about 20 AP 277. Two of them work well: one acting as the master and the other joining successfully to the virtual controller.
However, I am unable to make the others function properly. Originally, they had firmware version 6.4.3.0. I updated all of them with this firmware: ArubaInstant_Centaurus_8.6.0.23_88342. The update is successful, they start up, but all of them become masters. None of them join the existing master.
They are all on the same network, and they can see each other by ping.
All APs are in cluster mode. show swarm mode = "Swarm Mode :Cluster"
What can I try? Is there a command that can instruct them to join an existing master?
They also keep rebooting:
show version
Aruba Operating System Software.
ArubaOS (MODEL: 277), Version 8.6.0.23
Website: http://www.arubanetworks.com
(c) Copyright 2023 Hewlett Packard Enterprise Development LP.
Compiled on 2023-10-29 at 03:31:29 PDT (build 88342) by jenkins
FIPS Mode :disabled
AP uptime is 3 minutes 22 seconds
Reboot Time and Cause: AP rebooted Sun Oct 29 03:47:18 UTC 2023; System cmd at uptime 0D 0H 17M 5S: UAP discovery reboot