Cloud Managed Networks

Hi, We have a lot of customers experiencing this issue since the last Aruba Central update a week or two back. None of our customers have utilised 6Ghz yet so we have no SSIDs with this enabled yet.

 Up until now, we have not had an issue with leaving the flexible Dual Band mode set to automatic on the AP-615's but now we do. Some APs seem to be dropping either the 2.4 or 5Ghz radios in favour of 6Ghz, even though this isn't enabled on any of the SSID's but this is effecting some of the older clients that are only 2.4Ghz compatible.

Luckily, I have managed to utilise the API's to change the flexible dual band mode in bulk for a few of our customers to set them to 2.4 and 5 GHz but this is becoming a pain. Has anybody else experienced this issue and if so, any suggestions on resolving it? I have also logged a case with TAC.

Thanks

were the AP-615s running Instant firmware or AOS10?

Hi, We have a lot of customers experiencing this issue since the last Aruba Central update a week or two back. None of our customers have utilised 6Ghz yet so we have no SSIDs with this enabled yet.

 Up until now, we have not had an issue with leaving the flexible Dual Band mode set to automatic on the AP-615's but now we do. Some APs seem to be dropping either the 2.4 or 5Ghz radios in favour of 6Ghz, even though this isn't enabled on any of the SSID's but this is effecting some of the older clients that are only 2.4Ghz compatible.

Luckily, I have managed to utilise the API's to change the flexible dual band mode in bulk for a few of our customers to set them to 2.4 and 5 GHz but this is becoming a pain. Has anybody else experienced this issue and if so, any suggestions on resolving it? I have also logged a case with TAC.

Thanks

They're running AOS10

I have since had an update from TAC. This is supposedly expected behaviour for AirMatch to push clients to use the 6GHz radio, even if you have no SSID's utilising 6GHz, therefore dropping the APs down to one useable radio. I have requested this be reported as a bug/issue.

Thanks,

Josh

were the AP-615s running Instant firmware or AOS10?

Hi, We have a lot of customers experiencing this issue since the last Aruba Central update a week or two back. None of our customers have utilised 6Ghz yet so we have no SSIDs with this enabled yet.

 Up until now, we have not had an issue with leaving the flexible Dual Band mode set to automatic on the AP-615's but now we do. Some APs seem to be dropping either the 2.4 or 5Ghz radios in favour of 6Ghz, even though this isn't enabled on any of the SSID's but this is effecting some of the older clients that are only 2.4Ghz compatible.

Luckily, I have managed to utilise the API's to change the flexible dual band mode in bulk for a few of our customers to set them to 2.4 and 5 GHz but this is becoming a pain. Has anybody else experienced this issue and if so, any suggestions on resolving it? I have also logged a case with TAC.

Thanks

Hi Josh,

Can you share the case number? 

They're running AOS10

I have since had an update from TAC. This is supposedly expected behaviour for AirMatch to push clients to use the 6GHz radio, even if you have no SSID's utilising 6GHz, therefore dropping the APs down to one useable radio. I have requested this be reported as a bug/issue.

Thanks,

Josh

were the AP-615s running Instant firmware or AOS10?

Hi, We have a lot of customers experiencing this issue since the last Aruba Central update a week or two back. None of our customers have utilised 6Ghz yet so we have no SSIDs with this enabled yet.

 Up until now, we have not had an issue with leaving the flexible Dual Band mode set to automatic on the AP-615's but now we do. Some APs seem to be dropping either the 2.4 or 5Ghz radios in favour of 6Ghz, even though this isn't enabled on any of the SSID's but this is effecting some of the older clients that are only 2.4Ghz compatible.

Luckily, I have managed to utilise the API's to change the flexible dual band mode in bulk for a few of our customers to set them to 2.4 and 5 GHz but this is becoming a pain. Has anybody else experienced this issue and if so, any suggestions on resolving it? I have also logged a case with TAC.

Thanks

Hi,

Yes sure it is 5381324406

Thanks

Hi Josh,

Can you share the case number? 

They're running AOS10

I have since had an update from TAC. This is supposedly expected behaviour for AirMatch to push clients to use the 6GHz radio, even if you have no SSID's utilising 6GHz, therefore dropping the APs down to one useable radio. I have requested this be reported as a bug/issue.

Thanks,

Josh

were the AP-615s running Instant firmware or AOS10?

Hi, We have a lot of customers experiencing this issue since the last Aruba Central update a week or two back. None of our customers have utilised 6Ghz yet so we have no SSIDs with this enabled yet.

 Up until now, we have not had an issue with leaving the flexible Dual Band mode set to automatic on the AP-615's but now we do. Some APs seem to be dropping either the 2.4 or 5Ghz radios in favour of 6Ghz, even though this isn't enabled on any of the SSID's but this is effecting some of the older clients that are only 2.4Ghz compatible.

Luckily, I have managed to utilise the API's to change the flexible dual band mode in bulk for a few of our customers to set them to 2.4 and 5 GHz but this is becoming a pain. Has anybody else experienced this issue and if so, any suggestions on resolving it? I have also logged a case with TAC.

Thanks

thanks for sharing, I might be hitting this issue too.

Hi,

Yes sure it is 5381324406

Thanks

Hi Josh,

Can you share the case number? 

They're running AOS10

I have since had an update from TAC. This is supposedly expected behaviour for AirMatch to push clients to use the 6GHz radio, even if you have no SSID's utilising 6GHz, therefore dropping the APs down to one useable radio. I have requested this be reported as a bug/issue.

Thanks,

Josh

were the AP-615s running Instant firmware or AOS10?

Hi, We have a lot of customers experiencing this issue since the last Aruba Central update a week or two back. None of our customers have utilised 6Ghz yet so we have no SSIDs with this enabled yet.

 Up until now, we have not had an issue with leaving the flexible Dual Band mode set to automatic on the AP-615's but now we do. Some APs seem to be dropping either the 2.4 or 5Ghz radios in favour of 6Ghz, even though this isn't enabled on any of the SSID's but this is effecting some of the older clients that are only 2.4Ghz compatible.

Luckily, I have managed to utilise the API's to change the flexible dual band mode in bulk for a few of our customers to set them to 2.4 and 5 GHz but this is becoming a pain. Has anybody else experienced this issue and if so, any suggestions on resolving it? I have also logged a case with TAC.

Thanks

The customers that impacted by this, were anyone of them running 10.5.1.0 firmware? and with gateways too?

thanks for sharing, I might be hitting this issue too.

Hi,

Yes sure it is 5381324406

Thanks

Hi Josh,

Can you share the case number? 

They're running AOS10

I have since had an update from TAC. This is supposedly expected behaviour for AirMatch to push clients to use the 6GHz radio, even if you have no SSID's utilising 6GHz, therefore dropping the APs down to one useable radio. I have requested this be reported as a bug/issue.

Thanks,

Josh

were the AP-615s running Instant firmware or AOS10?

Hi, We have a lot of customers experiencing this issue since the last Aruba Central update a week or two back. None of our customers have utilised 6Ghz yet so we have no SSIDs with this enabled yet.

 Up until now, we have not had an issue with leaving the flexible Dual Band mode set to automatic on the AP-615's but now we do. Some APs seem to be dropping either the 2.4 or 5Ghz radios in favour of 6Ghz, even though this isn't enabled on any of the SSID's but this is effecting some of the older clients that are only 2.4Ghz compatible.

Luckily, I have managed to utilise the API's to change the flexible dual band mode in bulk for a few of our customers to set them to 2.4 and 5 GHz but this is becoming a pain. Has anybody else experienced this issue and if so, any suggestions on resolving it? I have also logged a case with TAC.

Thanks