topic Re: Configuration on the CAPWAP client was rolled back in Aerohive Migrated Content

Configuration on the CAPWAP client was rolled back

gavino_casu — Thu, 29 Aug 2019 19:34:57 GMT

Hello,

I have got a problem with an AP250.

When I try to Update the config I get two messages in the log of the device:

The configuration on the CAPWAP client was rolled back to an earlier version.
Default DTLS passphrase is in use. Push a complete config to update the passphrase automatically, or set it manually and push a complete or delta config.

I tried to hard reset the device through cli, which reseted the AP, but sending the config again did not work.

Even deleting the device from the hive did not work.

What can I do with the device?

Best regards

Gavino

Re: Configuration on the CAPWAP client was rolled back

samantha_lynn — Thu, 29 Aug 2019 20:17:08 GMT

The second message is just telling you the device has no configuration on it, so it's not broadcasting your network until it gets a complete configuration update. For the first error message, do you get this when trying a complete configuration update, delta configuration update, or both?

Re: Configuration on the CAPWAP client was rolled back

gavino_casu — Thu, 29 Aug 2019 22:30:29 GMT

I get the message when I send a complete config through the hive, through:

going to Monitor Tab in Hive
going to Access Points
selecting the Access Points
Choose Update and Update Devices
Activating the option Perform a complete configuration update for all selected devices
After automatically switching to the Configuration Tab I see the device is updating the config and automatically rebooting
After several minutes (ca. 10 minutes) I get the following message:

Upload Configuration: The config has been updated.
- Device Reboot: The configuration of device has been rolled back.

Can you help me fixing this problem?

Re: Configuration on the CAPWAP client was rolled back

samantha_lynn — Thu, 29 Aug 2019 22:35:13 GMT

Do you have other devices that are able to take the update with the same configuration? That would rule out the firewall and any configuration mismatch that could cause that issue. Also could you tell me what firmware version the device is using currently?

Re: Configuration on the CAPWAP client was rolled back

gavino_casu — Thu, 29 Aug 2019 22:45:39 GMT

We have about 37 devices that get the same config and work without any issues.

We have multiple offices with 3-4 different devicetypes.

At the office with the problematic device we have three other devices that work without issues.

Re: Configuration on the CAPWAP client was rolled back

samantha_lynn — Thu, 29 Aug 2019 22:47:52 GMT

Thank you for confirming that for me. Could you tell me what firmware version the device is using currently? Also I'd like to get some logs on the update failure, would you be able to SSH in to the device, enable capwap debugs, replicate the issue, pull tech data and send that to me at communityhelp@aerohive.com?

This guide reviews how to enable capwap debugs: https://thehivecommunity.aerohive.com/s/article/CAPWAP-debugs

Re: Configuration on the CAPWAP client was rolled back

gavino_casu — Thu, 29 Aug 2019 23:44:13 GMT

I activated the debugmode through ssh,

took the data through the hive interface

and sent them to you.

Re: Configuration on the CAPWAP client was rolled back

gavino_casu — Thu, 29 Aug 2019 23:46:16 GMT

The firmware version is HiveOS 8.2r6.228034.

The app version is ver 5.3.4.

Re: Configuration on the CAPWAP client was rolled back

samantha_lynn — Fri, 30 Aug 2019 01:50:38 GMT

Thank you for that data. Can you confirm the port this AP is connected to is set up properly (access if we're only using one VLAN, trunk if we're using multiple VLANs)? Also are we setting a static IP on this AP, or changing the management VLAN with this update?

Re: Configuration on the CAPWAP client was rolled back

gavino_casu — Thu, 05 Sep 2019 00:15:12 GMT

I will check this and report as soon as possible.