Controllerless Networks

I've purchased some used AP-345-US APs to add to my existing cluster of IAP-315-US and AP-375-US APs, but I'm unable to get them to join.

I don't know the full history of the new APs I acquired. In preparation for adding these to the network, I intended to clear their configuration and update them to the same firmware level as the existing cluster (8.12.0.2_90468). What I accidentally did though was to issue the 'clear all' command instead of 'clear os' and I seem to have cleared some important configuration. Now when I boot any of the 345s, it will not join the cluster and instead starts its own virtual controller. (Yes, I am 100% sure that connectivity between the 345 and the cluster is good, same L2 network, etc.) 

When I log in to the 345's VC, I am greeted with a prompt to set my country code, and I can choose US from the drop-down menu, but it will not allow me to save the setting. The dialog window never closes and I cannot access any of the other configuration on the VC. When I log in via SSH (admin/admin) I do not have the ability to run most commands. Even 'logout' produces the message "Error: This command is not available for the current privilege level."

I have tried multiple firmware versions and I am not able to get past the country code dialog with any version. Running 'mfginfo' from apboot confirms it's a US model (CCODE-US-xxx).

Is there any way to recover from here? What other information can I provide?

I've purchased some used AP-345-US APs to add to my existing cluster of IAP-315-US and AP-375-US APs, but I'm unable to get them to join.

I don't know the full history of the new APs I acquired. In preparation for adding these to the network, I intended to clear their configuration and update them to the same firmware level as the existing cluster (8.12.0.2_90468). What I accidentally did though was to issue the 'clear all' command instead of 'clear os' and I seem to have cleared some important configuration. Now when I boot any of the 345s, it will not join the cluster and instead starts its own virtual controller. (Yes, I am 100% sure that connectivity between the 345 and the cluster is good, same L2 network, etc.) 

When I log in to the 345's VC, I am greeted with a prompt to set my country code, and I can choose US from the drop-down menu, but it will not allow me to save the setting. The dialog window never closes and I cannot access any of the other configuration on the VC. When I log in via SSH (admin/admin) I do not have the ability to run most commands. Even 'logout' produces the message "Error: This command is not available for the current privilege level."

I have tried multiple firmware versions and I am not able to get past the country code dialog with any version. Running 'mfginfo' from apboot confirms it's a US model (CCODE-US-xxx).

Is there any way to recover from here? What other information can I provide?

The AP-345, unfortunately, shares a platform (Draco) with one of the 500 series APs.  That means software is still being released for the platform (Draco) that is incompatible with the AP-345.  As mentioned, the AP-340 series is parked in AOS 8.10 and AOS 10.4.

I've purchased some used AP-345-US APs to add to my existing cluster of IAP-315-US and AP-375-US APs, but I'm unable to get them to join.

I don't know the full history of the new APs I acquired. In preparation for adding these to the network, I intended to clear their configuration and update them to the same firmware level as the existing cluster (8.12.0.2_90468). What I accidentally did though was to issue the 'clear all' command instead of 'clear os' and I seem to have cleared some important configuration. Now when I boot any of the 345s, it will not join the cluster and instead starts its own virtual controller. (Yes, I am 100% sure that connectivity between the 345 and the cluster is good, same L2 network, etc.) 

When I log in to the 345's VC, I am greeted with a prompt to set my country code, and I can choose US from the drop-down menu, but it will not allow me to save the setting. The dialog window never closes and I cannot access any of the other configuration on the VC. When I log in via SSH (admin/admin) I do not have the ability to run most commands. Even 'logout' produces the message "Error: This command is not available for the current privilege level."

I have tried multiple firmware versions and I am not able to get past the country code dialog with any version. Running 'mfginfo' from apboot confirms it's a US model (CCODE-US-xxx).

Is there any way to recover from here? What other information can I provide?

Interesting. I had already submitted this post once and it never made it out of moderation, so when I posted again, I also opened a ticket with TAC at the same time. After about an hour on a session with them yesterday, they intend to replace them under warranty to correct this issue. How did they miss this? I received the RMA form to fill out last evening.

The AP-345, unfortunately, shares a platform (Draco) with one of the 500 series APs.  That means software is still being released for the platform (Draco) that is incompatible with the AP-345.  As mentioned, the AP-340 series is parked in AOS 8.10 and AOS 10.4.

I've purchased some used AP-345-US APs to add to my existing cluster of IAP-315-US and AP-375-US APs, but I'm unable to get them to join.

I don't know the full history of the new APs I acquired. In preparation for adding these to the network, I intended to clear their configuration and update them to the same firmware level as the existing cluster (8.12.0.2_90468). What I accidentally did though was to issue the 'clear all' command instead of 'clear os' and I seem to have cleared some important configuration. Now when I boot any of the 345s, it will not join the cluster and instead starts its own virtual controller. (Yes, I am 100% sure that connectivity between the 345 and the cluster is good, same L2 network, etc.) 

When I log in to the 345's VC, I am greeted with a prompt to set my country code, and I can choose US from the drop-down menu, but it will not allow me to save the setting. The dialog window never closes and I cannot access any of the other configuration on the VC. When I log in via SSH (admin/admin) I do not have the ability to run most commands. Even 'logout' produces the message "Error: This command is not available for the current privilege level."

I have tried multiple firmware versions and I am not able to get past the country code dialog with any version. Running 'mfginfo' from apboot confirms it's a US model (CCODE-US-xxx).

Is there any way to recover from here? What other information can I provide?

Sometimes the little things get missed.

Interesting. I had already submitted this post once and it never made it out of moderation, so when I posted again, I also opened a ticket with TAC at the same time. After about an hour on a session with them yesterday, they intend to replace them under warranty to correct this issue. How did they miss this? I received the RMA form to fill out last evening.

The AP-345, unfortunately, shares a platform (Draco) with one of the 500 series APs.  That means software is still being released for the platform (Draco) that is incompatible with the AP-345.  As mentioned, the AP-340 series is parked in AOS 8.10 and AOS 10.4.

I've purchased some used AP-345-US APs to add to my existing cluster of IAP-315-US and AP-375-US APs, but I'm unable to get them to join.

I don't know the full history of the new APs I acquired. In preparation for adding these to the network, I intended to clear their configuration and update them to the same firmware level as the existing cluster (8.12.0.2_90468). What I accidentally did though was to issue the 'clear all' command instead of 'clear os' and I seem to have cleared some important configuration. Now when I boot any of the 345s, it will not join the cluster and instead starts its own virtual controller. (Yes, I am 100% sure that connectivity between the 345 and the cluster is good, same L2 network, etc.) 

When I log in to the 345's VC, I am greeted with a prompt to set my country code, and I can choose US from the drop-down menu, but it will not allow me to save the setting. The dialog window never closes and I cannot access any of the other configuration on the VC. When I log in via SSH (admin/admin) I do not have the ability to run most commands. Even 'logout' produces the message "Error: This command is not available for the current privilege level."

I have tried multiple firmware versions and I am not able to get past the country code dialog with any version. Running 'mfginfo' from apboot confirms it's a US model (CCODE-US-xxx).

Is there any way to recover from here? What other information can I provide?

This why I try to read release notes before upgrades. Been there with 345 when I try to upgrade the controller to 8.11. and read in RN it's not supported. Try it anyhow just to be sure :-)

Sometimes you will need to read also RN for other releases not just latest ones. For example for 345 you will find info in 8.11 RN https://www.arubanetworks.com/techdocs/Aruba-Instant-8.x-Books/Release-Notes/8112/Aruba-Instant-8.11.2.2-Release-Notes.pdf

Best, Gorazd

Sometimes the little things get missed.

Interesting. I had already submitted this post once and it never made it out of moderation, so when I posted again, I also opened a ticket with TAC at the same time. After about an hour on a session with them yesterday, they intend to replace them under warranty to correct this issue. How did they miss this? I received the RMA form to fill out last evening.

The AP-345, unfortunately, shares a platform (Draco) with one of the 500 series APs.  That means software is still being released for the platform (Draco) that is incompatible with the AP-345.  As mentioned, the AP-340 series is parked in AOS 8.10 and AOS 10.4.

I've purchased some used AP-345-US APs to add to my existing cluster of IAP-315-US and AP-375-US APs, but I'm unable to get them to join.

I don't know the full history of the new APs I acquired. In preparation for adding these to the network, I intended to clear their configuration and update them to the same firmware level as the existing cluster (8.12.0.2_90468). What I accidentally did though was to issue the 'clear all' command instead of 'clear os' and I seem to have cleared some important configuration. Now when I boot any of the 345s, it will not join the cluster and instead starts its own virtual controller. (Yes, I am 100% sure that connectivity between the 345 and the cluster is good, same L2 network, etc.) 

When I log in to the 345's VC, I am greeted with a prompt to set my country code, and I can choose US from the drop-down menu, but it will not allow me to save the setting. The dialog window never closes and I cannot access any of the other configuration on the VC. When I log in via SSH (admin/admin) I do not have the ability to run most commands. Even 'logout' produces the message "Error: This command is not available for the current privilege level."

I have tried multiple firmware versions and I am not able to get past the country code dialog with any version. Running 'mfginfo' from apboot confirms it's a US model (CCODE-US-xxx).

Is there any way to recover from here? What other information can I provide?

This why I try to read release notes before upgrades. Been there with 345 when I try to upgrade the controller to 8.11. and read in RN it's not supported. Try it anyhow just to be sure :-)

Sometimes you will need to read also RN for other releases not just latest ones. For example for 345 you will find info in 8.11 RN https://www.arubanetworks.com/techdocs/Aruba-Instant-8.x-Books/Release-Notes/8112/Aruba-Instant-8.11.2.2-Release-Notes.pdf

Best, Gorazd

Sometimes the little things get missed.

Interesting. I had already submitted this post once and it never made it out of moderation, so when I posted again, I also opened a ticket with TAC at the same time. After about an hour on a session with them yesterday, they intend to replace them under warranty to correct this issue. How did they miss this? I received the RMA form to fill out last evening.

The AP-345, unfortunately, shares a platform (Draco) with one of the 500 series APs.  That means software is still being released for the platform (Draco) that is incompatible with the AP-345.  As mentioned, the AP-340 series is parked in AOS 8.10 and AOS 10.4.

I've purchased some used AP-345-US APs to add to my existing cluster of IAP-315-US and AP-375-US APs, but I'm unable to get them to join.

I don't know the full history of the new APs I acquired. In preparation for adding these to the network, I intended to clear their configuration and update them to the same firmware level as the existing cluster (8.12.0.2_90468). What I accidentally did though was to issue the 'clear all' command instead of 'clear os' and I seem to have cleared some important configuration. Now when I boot any of the 345s, it will not join the cluster and instead starts its own virtual controller. (Yes, I am 100% sure that connectivity between the 345 and the cluster is good, same L2 network, etc.) 

When I log in to the 345's VC, I am greeted with a prompt to set my country code, and I can choose US from the drop-down menu, but it will not allow me to save the setting. The dialog window never closes and I cannot access any of the other configuration on the VC. When I log in via SSH (admin/admin) I do not have the ability to run most commands. Even 'logout' produces the message "Error: This command is not available for the current privilege level."

I have tried multiple firmware versions and I am not able to get past the country code dialog with any version. Running 'mfginfo' from apboot confirms it's a US model (CCODE-US-xxx).

Is there any way to recover from here? What other information can I provide?

Noted. I've been a happy Aruba customer for a little over 10 years now, dating back to the IAP-105. This is honestly the first time I've run into a portion of a hardware platform (Draco in the case) being left behind. When I saw a current Draco image posted for 8.12, I honestly thought I was in the clear. This probably explains the 'platform is obsolete' I was seeing from the serial console during boot.

Does Aruba specifically mention when a given software version will reach EOL? When would 8.10 stop receiving updates?

I have a small window left to return these. I really don't want roll back the rest of the campus to 8.10. I'm considering a separate L2 VLAN to create a separate cluster, but I'm guessing that's probably not a good idea? I'm sure this has been covered elsewhere, but I've had no time to look into this scenario yet. I expect that the two clusters would probably not coexist well within the same building if the radios can all hear one another?

This why I try to read release notes before upgrades. Been there with 345 when I try to upgrade the controller to 8.11. and read in RN it's not supported. Try it anyhow just to be sure :-)

Sometimes you will need to read also RN for other releases not just latest ones. For example for 345 you will find info in 8.11 RN https://www.arubanetworks.com/techdocs/Aruba-Instant-8.x-Books/Release-Notes/8112/Aruba-Instant-8.11.2.2-Release-Notes.pdf

Best, Gorazd

Sometimes the little things get missed.

Interesting. I had already submitted this post once and it never made it out of moderation, so when I posted again, I also opened a ticket with TAC at the same time. After about an hour on a session with them yesterday, they intend to replace them under warranty to correct this issue. How did they miss this? I received the RMA form to fill out last evening.

The AP-345, unfortunately, shares a platform (Draco) with one of the 500 series APs.  That means software is still being released for the platform (Draco) that is incompatible with the AP-345.  As mentioned, the AP-340 series is parked in AOS 8.10 and AOS 10.4.

I've purchased some used AP-345-US APs to add to my existing cluster of IAP-315-US and AP-375-US APs, but I'm unable to get them to join.

I don't know the full history of the new APs I acquired. In preparation for adding these to the network, I intended to clear their configuration and update them to the same firmware level as the existing cluster (8.12.0.2_90468). What I accidentally did though was to issue the 'clear all' command instead of 'clear os' and I seem to have cleared some important configuration. Now when I boot any of the 345s, it will not join the cluster and instead starts its own virtual controller. (Yes, I am 100% sure that connectivity between the 345 and the cluster is good, same L2 network, etc.) 

When I log in to the 345's VC, I am greeted with a prompt to set my country code, and I can choose US from the drop-down menu, but it will not allow me to save the setting. The dialog window never closes and I cannot access any of the other configuration on the VC. When I log in via SSH (admin/admin) I do not have the ability to run most commands. Even 'logout' produces the message "Error: This command is not available for the current privilege level."

I have tried multiple firmware versions and I am not able to get past the country code dialog with any version. Running 'mfginfo' from apboot confirms it's a US model (CCODE-US-xxx).

Is there any way to recover from here? What other information can I provide?

I've purchased some used AP-345-US APs to add to my existing cluster of IAP-315-US and AP-375-US APs, but I'm unable to get them to join.

I don't know the full history of the new APs I acquired. In preparation for adding these to the network, I intended to clear their configuration and update them to the same firmware level as the existing cluster (8.12.0.2_90468). What I accidentally did though was to issue the 'clear all' command instead of 'clear os' and I seem to have cleared some important configuration. Now when I boot any of the 345s, it will not join the cluster and instead starts its own virtual controller. (Yes, I am 100% sure that connectivity between the 345 and the cluster is good, same L2 network, etc.) 

When I log in to the 345's VC, I am greeted with a prompt to set my country code, and I can choose US from the drop-down menu, but it will not allow me to save the setting. The dialog window never closes and I cannot access any of the other configuration on the VC. When I log in via SSH (admin/admin) I do not have the ability to run most commands. Even 'logout' produces the message "Error: This command is not available for the current privilege level."

I have tried multiple firmware versions and I am not able to get past the country code dialog with any version. Running 'mfginfo' from apboot confirms it's a US model (CCODE-US-xxx).

Is there any way to recover from here? What other information can I provide?

The AP-345 won't run v8.12

8.10.0.x is the latest available.

Original Message:
Sent: Sep 17, 2024 01:10 PM
From: Ken Ellefson
Subject: AP-345 unable to join existing cluster

I've purchased some used AP-345-US APs to add to my existing cluster of IAP-315-US and AP-375-US APs, but I'm unable to get them to join.

I don't know the full history of the new APs I acquired. In preparation for adding these to the network, I intended to clear their configuration and update them to the same firmware level as the existing cluster (8.12.0.2_90468). What I accidentally did though was to issue the 'clear all' command instead of 'clear os' and I seem to have cleared some important configuration. Now when I boot any of the 345s, it will not join the cluster and instead starts its own virtual controller. (Yes, I am 100% sure that connectivity between the 345 and the cluster is good, same L2 network, etc.) 

When I log in to the 345's VC, I am greeted with a prompt to set my country code, and I can choose US from the drop-down menu, but it will not allow me to save the setting. The dialog window never closes and I cannot access any of the other configuration on the VC. When I log in via SSH (admin/admin) I do not have the ability to run most commands. Even 'logout' produces the message "Error: This command is not available for the current privilege level."

I have tried multiple firmware versions and I am not able to get past the country code dialog with any version. Running 'mfginfo' from apboot confirms it's a US model (CCODE-US-xxx).

Is there any way to recover from here? What other information can I provide?