Hello, it's an IAP207.
this AP was working into another vlan together with another IAP207 and formed a IA cluster
Original Message:
Sent: Feb 20, 2023 02:59 AM
From: Stefan Bartels
Subject: AP not joining the IAP cluster
Hi,
degraded state means one of the following causes:
1. When the Instant AP cannot be a master Instant AP because it has no IP address, and does not have an uplink connection.
2. When the Instant AP is unable to join the cluster because of a missing country code, image, or incorrect regulatory hardware.
3. When the Instant AP has been denied permission to the existing cluster based on the allowed AP whitelist or the auto-join configuration present in the cluster.
4. In a mixed class network, when the slave Instant APs join the master Instant AP with a different software version, causing the image sync from <madcap:conditionaltext data-mc-conditions="ArubaFrameStyles.ArubaCondition">the cloud or</madcap:conditionaltext> AirWave to fail.
Point 3. and 4. has been already discussed. 1. is unlikly because you are using SSH.
Can you please check if the 207 is an IAP or an AP (which means this has to be operated by an Wireless Controller): You can see it on the back of the AP.
Part Number JX925A means CAP = Wireless Controller is needed
Part Number Instant AP is depending on Country Code:
Original Message:
Sent: Feb 17, 2023 10:45 AM
From: Stefano Colombo
Subject: AP not joining the IAP cluster
Hello
I've upgraded the IAP207 to latest 8.10
ArubaOS (MODEL: 207), Version 8.10.0.5 LSR
and downgraded the AP505 to 8.10
ArubaOS (MODEL: 505), Version 8.10.0.5 LSR
But still the IAP207 do not join the cluster.
Logging in ssh I still get the following message
admin@172.31.255.4's password:
Warning: CLI module is running in a degraded state. Configuration, write memory, and support command are disabled; please debug with caution.
Original Message:
Sent: Feb 17, 2023 09:18 AM
From: cordless
Subject: AP not joining the IAP cluster
That´s what I am saying, you have to upgrade the IAP-207 first. Bring that 207 AP into another L2 Segment with DHCP and move through the GUI to Upgrade the 207. Best is to download it from Aruba Support Portal - therefore you need a valid Support contract - and after Upgrade joun the Clustern.
Original Message:
Sent: Feb 17, 2023 09:08 AM
From: Stefano Colombo
Subject: AP not joining the IAP cluster
From the cluster's master I see that the "AP CLASS" IS DIFFERENT.
The AP class of the cluster nodes is "GEMINI" and the ap class of the AP207 is VELA.
Do I need to upload the VELA Firmware into the Cluster ?
swarm upgrade status
--------------------
Mac IP Address Seed AP AP Class Status Image Info Error Detail
--- ---------- ------- -------- ------ ---------- ------------
34:8a:12:c7:91:e8 172.31.255.1 No Gemini image-ok From Seed none
34:8a:12:c7:9a:2c 172.31.255.3 No Gemini image-ok From Seed none
34:8a:12:c7:9a:8c 172.31.255.2 No Gemini image-ok From Seed none
Auto reboot :enable
Use external URL :disable
Conductor wait Time :0 secs 0 count
Switch Partition :enable
Upgrade in process :No
UAP convert process :No
Original Message:
Sent: Feb 17, 2023 09:05 AM
From: Stefano Colombo
Subject: AP not joining the IAP cluster
I'm not using Aruba central.
It seems that when the AP207 boots up it tries to upgrade the firmware but it stucks.
Logging in ssh I see the following
admin@172.31.255.4's password:
Warning: CLI module is running in a degraded state. Configuration, write memory, and support command are disabled; please debug with caution.
show tech-support and show tech-support supplemental are the two most useful outputs to collect for any kind of troubleshooting session.
ap04#
ap04# show upgrade
swarm upgrade status
--------------------
Mac IP Address Seed AP AP Class Status Image Info Error Detail
--- ---------- ------- -------- ------ ---------- ------------
44:48:c1:cf:4d:6a 172.31.255.4 N/A Vela image-ok -- none
Auto reboot :enable
Use external URL :disable
Conductor wait Time :0 secs 0 count
Switch Partition :enable
Upgrade in process :No
UAP convert process :No
ap04#
Original Message:
Sent: Feb 17, 2023 08:40 AM
From: cordless
Subject: AP not joining the IAP cluster
There is a "security Feature" that not all Aruba APs can join the Cluster. It is called "Auto-Join Mode" under Configuration > System > General
https://www.arubanetworks.com/techdocs/central/latest/content/nms/access-points/cfg/ap-settings/conf_sys_params.htm
Please verify that this is enabled. Than it should join the cluster even with 8.9.x
Original Message:
Sent: Feb 17, 2023 08:30 AM
From: Stefano Colombo
Subject: AP not joining the IAP cluster
The problem is that previously the cluster was running 8.09 but the AP207 didn't join anyway.
Original Message:
Sent: Feb 17, 2023 08:09 AM
From: cordless
Subject: AP not joining the IAP cluster
Yes, the AP-2xx will be parked in 8.10.x with 5 years of support.
You have to downgrade the existing cluster to latest 8.10.x and the 207 as well. Than you can form a cluster of those APs.
Original Message:
Sent: Feb 17, 2023 07:59 AM
From: Stefano Colombo
Subject: AP not joining the IAP cluster
The cluster is made of AP-505 running 8.11.0.1_85785, the other AP are IAP-207 running Version 8.9.0.2
I found this note in the release notes of 8.11
Deprecated Instant APs
The following Instant APs are no longer supported from Aruba Instant 8.11.0.0 onwards:
n 203H Series - AP-203H
n 203R Series - AP-203R and AP-203RP
n 207 Series - IAP-207
which may be the problem ?
Original Message:
Sent: Feb 17, 2023 07:36 AM
From: cordless
Subject: AP not joining the IAP cluster
What Type of APs are in the existing cluster and which type of AP are you wanting to join?
If they are different than we spoke about a mixed Instant AP Cluster. If those APs will be managed by Cloud - Aruba Central - or AirWave - on-Premise Management - you can provide Firmware over those systems.
If it is standalone than best would be to install the same Firmware manually on the new AP as on the existing Cluster. Than he is able to join.
See here instructions how to upgrade - example for Release 8.10.0.x:
https://www.arubanetworks.com/techdocs/Instant_8.x_RN_WebHelp/Content/8.10/upgrade-an-iap.htm
Original Message:
Sent: Feb 17, 2023 04:38 AM
From: Stefano Colombo
Subject: AP not joining the IAP cluster
We have a cluster of 3 APs and we tried to add another which was previously joined to another one.
We first reset the AP to factory default by pressing the reset button while powering it on.
The AP got it's IP and if we point to it through the browser we're redirected to the cluster master's IP.
However in the Instant access it does not shows up in the Access Points devices,
How can we successfully add it ?