Wireless Access

The 'show activate' output isn't particularly useful.

AP-735# show ap debug cloud-connectivity

AP-735# show ap debug cloud-server

Also take a look at the log for anything interesting.  If you aren't finding anything pointing at the issue, then I'd recommend contacting TAC.

We are having the same problem today with 735s. We've been rolling out to various sites over the past month, no issues. Same steps completed today and the APs never show up in Central. Same output as you for activate status. 

show ap debug cloud-connectivity results in no errors.
show ap debug cloud-server shows that the ap is running in local-mgmt mode. 

I have a case opened with TAC, will share if I have any update from them.

Hello,

Did you managed to get tech-support logs out from ap?
TAC asked me to send those but 734 reboot itself after about 10-15KB's of log data (without running sh tech-support, ap seems to stay on...) 
Another observation is that "sh log debug" seems to contain Bad Requests :
"Aug  7 07:25:57   awc[9895]: [activate] Message over SSL from device.arubanetworks.com, SSL_read() returned 317, errstr=Success, Message is "HTTP/1.1 400 Bad Request^M Date: Thu, 07 Aug 2025 07:25:56 GMT^M Content-Type: text/plain^M Content-Length: 36^M Connection: close^M X-Type: provision-update^M X-Session-Id: 3517757183650451902^M X-Status-Code: authenticated^M Strict-Transport-Security: max-age=3600; includeSubDomains^M ^M X-Status-Code: fail-fw-key-not-found", AWC response: (null)
Aug  7 07:25:57   awc[9895]: [activate] sending isc response"

We are having the same problem today with 735s. We've been rolling out to various sites over the past month, no issues. Same steps completed today and the APs never show up in Central. Same output as you for activate status. 

show ap debug cloud-connectivity results in no errors.
show ap debug cloud-server shows that the ap is running in local-mgmt mode. 

I have a case opened with TAC, will share if I have any update from them.

We managed to get ours online with a workaround of upgrading the firmware via CLI to 10.7.1 but I've asked for the case to be escalated as its not a fix and was working absolutely fine until yesterday. We also saw the SSL error - and the APs were running in "upgrade only" mode but not doing this automatically even though all connectivity checks show that is connected to Central.

In case you need it whilst we wait for a fix/more info from TAC, here is the upgrade firmware command we've used;

upgrade-image http://common.cloud.hpe.com/ccssvc/ccs-system-firmware-registry/IAP/ArubaOS_Aquila_10.7.1.1_92045

Hello,

Did you managed to get tech-support logs out from ap?
TAC asked me to send those but 734 reboot itself after about 10-15KB's of log data (without running sh tech-support, ap seems to stay on...) 
Another observation is that "sh log debug" seems to contain Bad Requests :
"Aug  7 07:25:57   awc[9895]: [activate] Message over SSL from device.arubanetworks.com, SSL_read() returned 317, errstr=Success, Message is "HTTP/1.1 400 Bad Request^M Date: Thu, 07 Aug 2025 07:25:56 GMT^M Content-Type: text/plain^M Content-Length: 36^M Connection: close^M X-Type: provision-update^M X-Session-Id: 3517757183650451902^M X-Status-Code: authenticated^M Strict-Transport-Security: max-age=3600; includeSubDomains^M ^M X-Status-Code: fail-fw-key-not-found", AWC response: (null)
Aug  7 07:25:57   awc[9895]: [activate] sending isc response"

We managed to get ours online with a workaround of upgrading the firmware via CLI to 10.7.1 but I've asked for the case to be escalated as its not a fix and was working absolutely fine until yesterday. We also saw the SSL error - and the APs were running in "upgrade only" mode but not doing this automatically even though all connectivity checks show that is connected to Central.

In case you need it whilst we wait for a fix/more info from TAC, here is the upgrade firmware command we've used;

upgrade-image http://common.cloud.hpe.com/ccssvc/ccs-system-firmware-registry/IAP/ArubaOS_Aquila_10.7.1.1_92045

Hello,

Did you managed to get tech-support logs out from ap?
TAC asked me to send those but 734 reboot itself after about 10-15KB's of log data (without running sh tech-support, ap seems to stay on...) 
Another observation is that "sh log debug" seems to contain Bad Requests :
"Aug  7 07:25:57   awc[9895]: [activate] Message over SSL from device.arubanetworks.com, SSL_read() returned 317, errstr=Success, Message is "HTTP/1.1 400 Bad Request^M Date: Thu, 07 Aug 2025 07:25:56 GMT^M Content-Type: text/plain^M Content-Length: 36^M Connection: close^M X-Type: provision-update^M X-Session-Id: 3517757183650451902^M X-Status-Code: authenticated^M Strict-Transport-Security: max-age=3600; includeSubDomains^M ^M X-Status-Code: fail-fw-key-not-found", AWC response: (null)
Aug  7 07:25:57   awc[9895]: [activate] sending isc response"

We managed to get ours online with a workaround of upgrading the firmware via CLI to 10.7.1 but I've asked for the case to be escalated as its not a fix and was working absolutely fine until yesterday. We also saw the SSL error - and the APs were running in "upgrade only" mode but not doing this automatically even though all connectivity checks show that is connected to Central.

In case you need it whilst we wait for a fix/more info from TAC, here is the upgrade firmware command we've used;

upgrade-image http://common.cloud.hpe.com/ccssvc/ccs-system-firmware-registry/IAP/ArubaOS_Aquila_10.7.1.1_92045

Original Message:
Sent: Aug 07, 2025 03:31 AM
From: JL24
Subject: AP730 series access point does not appear in Central

Hello,

Did you managed to get tech-support logs out from ap?
TAC asked me to send those but 734 reboot itself after about 10-15KB's of log data (without running sh tech-support, ap seems to stay on...) 
Another observation is that "sh log debug" seems to contain Bad Requests :
"Aug  7 07:25:57   awc[9895]: [activate] Message over SSL from device.arubanetworks.com, SSL_read() returned 317, errstr=Success, Message is "HTTP/1.1 400 Bad Request^M Date: Thu, 07 Aug 2025 07:25:56 GMT^M Content-Type: text/plain^M Content-Length: 36^M Connection: close^M X-Type: provision-update^M X-Session-Id: 3517757183650451902^M X-Status-Code: authenticated^M Strict-Transport-Security: max-age=3600; includeSubDomains^M ^M X-Status-Code: fail-fw-key-not-found", AWC response: (null)
Aug  7 07:25:57   awc[9895]: [activate] sending isc response"

------------------------------
Jori Luoto
AV-IT Specialist

We have the same issue this week when we started working with recently purchased 735. We are also located in EU data centers.

Same software version 10.7.0.0

show activate status shows same incomplete info.

show ap debug cloud-server

Hello Christoffer,

Yeah that definitely sounds like broken device credentials database which only applies to 730-devices (wonder whats up with 720/740/750's?!?) which breaks redirection... I assume that if it would be "global" redirection issue then also 630 series would be suffering about this.

Anyway it would be great to get information when issue is fixed.

We have the same issue this week when we started working with recently purchased 735. We are also located in EU data centers.

Same software version 10.7.0.0

show activate status shows same incomplete info.

show ap debug cloud-server

Yeah something is definitely broken. In the 10.7.0.0 code or in Activate/Central.

I have created a TAC-case now aswell. Let's see what that gives

Hello Christoffer,

Yeah that definitely sounds like broken device credentials database which only applies to 730-devices (wonder whats up with 720/740/750's?!?) which breaks redirection... I assume that if it would be "global" redirection issue then also 630 series would be suffering about this.

Anyway it would be great to get information when issue is fixed.

Good to hear!

I don't think it's in 10.7.0.0 because I have deployed almost 100pcs of 730-series devices within last two months without any problems and problems started couple of days ago.

Yeah something is definitely broken. In the 10.7.0.0 code or in Activate/Central.

I have created a TAC-case now aswell. Let's see what that gives

Hello Christoffer,

Yeah that definitely sounds like broken device credentials database which only applies to 730-devices (wonder whats up with 720/740/750's?!?) which breaks redirection... I assume that if it would be "global" redirection issue then also 630 series would be suffering about this.

Anyway it would be great to get information when issue is fixed.

We have the same issue this week when we started working with recently purchased 735. We are also located in EU data centers.

Same software version 10.7.0.0

show activate status shows same incomplete info.

show ap debug cloud-server

Ok I see. Guess they changed something in Central or something else broke.

Good to hear!

I don't think it's in 10.7.0.0 because I have deployed almost 100pcs of 730-series devices within last two months without any problems and problems started couple of days ago.

Yeah something is definitely broken. In the 10.7.0.0 code or in Activate/Central.

I have created a TAC-case now aswell. Let's see what that gives

Hello Christoffer,

Yeah that definitely sounds like broken device credentials database which only applies to 730-devices (wonder whats up with 720/740/750's?!?) which breaks redirection... I assume that if it would be "global" redirection issue then also 630 series would be suffering about this.

Anyway it would be great to get information when issue is fixed.

The root issue for this should be resolved now.

The root issue for this should be resolved now.