Cloud Managed Networks

Hi all!

I have a working Airwave 8.3.0.2 with about 150 AP (207 and 303 models). But for some APs Airwave shows down status.

I've found that when I delete these down APs, they are rejoin again (so Airwave definitly sees them and could connect). But when I add APs to the desired groups their status changed to down. In the event logs there is a message like "PSK based authentication: swarm is not approved in Airwave." for all of the down APs. When I compare configuration with working APs there is no difference. 

I've tried to change the community string specifically for one AP (and on the AP side too), but without any effect.

Also I've tried solutions from these posts but with no result. 

https://community.arubanetworks.com/discussion/psk-based-authentication-swarm-is-not-approved-in-airwave

https://community.arubanetworks.com/discussion/unable-to-add-an-instant-ap-to-airwave

Is there anything I can check or change in my configuration to resolve this problem?

Hi all!

I have a working Airwave 8.3.0.2 with about 150 AP (207 and 303 models). But for some APs Airwave shows down status.

I've found that when I delete these down APs, they are rejoin again (so Airwave definitly sees them and could connect). But when I add APs to the desired groups their status changed to down. In the event logs there is a message like "PSK based authentication: swarm is not approved in Airwave." for all of the down APs. When I compare configuration with working APs there is no difference. 

I've tried to change the community string specifically for one AP (and on the AP side too), but without any effect.

Also I've tried solutions from these posts but with no result. 

https://community.arubanetworks.com/discussion/psk-based-authentication-swarm-is-not-approved-in-airwave

https://community.arubanetworks.com/discussion/unable-to-add-an-instant-ap-to-airwave

Is there anything I can check or change in my configuration to resolve this problem?

The PSK based authentication refers to the shared key between the VC and Airwave:

In Airwave you can check/change that on the VC. But as far as I know, if you manually approved/imported the APs in Airwave, it should not be needed; the secret is mainly used for automated onboarding of APs in Airwave.

One thing you should probably verify is if your Airwave version is new enough to support the 8.10.x AP firmware.

If this doesn't help, reaching out to your Aruba partner or TAC may provide a faster resolution.

Hi all!

I have a working Airwave 8.3.0.2 with about 150 AP (207 and 303 models). But for some APs Airwave shows down status.

I've found that when I delete these down APs, they are rejoin again (so Airwave definitly sees them and could connect). But when I add APs to the desired groups their status changed to down. In the event logs there is a message like "PSK based authentication: swarm is not approved in Airwave." for all of the down APs. When I compare configuration with working APs there is no difference. 

I've tried to change the community string specifically for one AP (and on the AP side too), but without any effect.

Also I've tried solutions from these posts but with no result. 

https://community.arubanetworks.com/discussion/psk-based-authentication-swarm-is-not-approved-in-airwave

https://community.arubanetworks.com/discussion/unable-to-add-an-instant-ap-to-airwave

Is there anything I can check or change in my configuration to resolve this problem?

Herman, thank you for the response.

My Airwave version is 8.3.0.2, almost the latest release. 

It just looks very strange that lower versions of IAP software have no problem with the connection to Airwave. But when I'd upgraded them, they become down.

As for the PSK I've tried to change it, no result. And I've tried to manually add IAP, also without success. 

Unfortunatelly I cannot open a TAC case because of the expired Service Contact. 

The PSK based authentication refers to the shared key between the VC and Airwave:

In Airwave you can check/change that on the VC. But as far as I know, if you manually approved/imported the APs in Airwave, it should not be needed; the secret is mainly used for automated onboarding of APs in Airwave.

One thing you should probably verify is if your Airwave version is new enough to support the 8.10.x AP firmware.

If this doesn't help, reaching out to your Aruba partner or TAC may provide a faster resolution.

Hi all!

I have a working Airwave 8.3.0.2 with about 150 AP (207 and 303 models). But for some APs Airwave shows down status.

I've found that when I delete these down APs, they are rejoin again (so Airwave definitly sees them and could connect). But when I add APs to the desired groups their status changed to down. In the event logs there is a message like "PSK based authentication: swarm is not approved in Airwave." for all of the down APs. When I compare configuration with working APs there is no difference. 

I've tried to change the community string specifically for one AP (and on the AP side too), but without any effect.

Also I've tried solutions from these posts but with no result. 

https://community.arubanetworks.com/discussion/psk-based-authentication-swarm-is-not-approved-in-airwave

https://community.arubanetworks.com/discussion/unable-to-add-an-instant-ap-to-airwave

Is there anything I can check or change in my configuration to resolve this problem?