cancel
Showing results for 
Search instead for 
Did you mean: 

New AP250's not accepting the (old) config.

New AP250's not accepting the (old) config.

technical2
New Contributor

Hello,

 

A client of ours is running Hivemanager NG and has about 20 AP's mostly AP120's and 330's running older firmware (6.5r8b).

We're trying to add new AP250 AP's with new firmware (8.0 & 8.2 atm), and the onboarding works, up to the point where the AP reboots and tries to load the config. The logs show the following:

2018-09-26 14:57:26 err ah_scd: system: Config rollback execute, reboot AP

2018-09-26 14:57:24 err last message repeated 3 times

2018-09-26 14:56:51 err last message repeated 6 times

2018-09-26 14:55:44 err last message repeated 6 times

2018-09-26 14:54:38 err last message repeated 6 times

2018-09-26 14:53:33 err last message repeated 6 times

2018-09-26 14:52:26 err last message repeated 6 times

2018-09-26 14:51:20 err last message repeated 6 times

2018-09-26 14:50:14 err last message repeated 6 times

2018-09-26 14:49:08 err last message repeated 6 times

2018-09-26 14:48:02 err last message repeated 3 times

2018-09-26 14:47:29 err hiawatha: system: [Hiawatha] check_configuration fled!

2018-09-26 14:47:18 notice ah_top: system: System is initialized

 

In attach you'll find the current config that is uploaded.

Please advise on what could be causing this, or how we can increase logging on the AP to see what part of the config it is tripping over.

 

Thank you,

Dirk

 

1 ACCEPTED SOLUTION

samantha_lynn
Esteemed Contributor III

Thank you for that screen shot, that confirms what I was thinking. In the tech data you can see that the AP is trying to reach capwap client server name cloud-ie-cws-0.aerohive.com, which is not the address we want to use for your HiveManager based on the screen shot you've sent me. I've emailed you the commands we will want to run on your AP, if you could console in to the AP and give those a try I would appreciate it.

View solution in original post

3 REPLIES 3

samantha_lynn
Esteemed Contributor III

Thank you for that screen shot, that confirms what I was thinking. In the tech data you can see that the AP is trying to reach capwap client server name cloud-ie-cws-0.aerohive.com, which is not the address we want to use for your HiveManager based on the screen shot you've sent me. I've emailed you the commands we will want to run on your AP, if you could console in to the AP and give those a try I would appreciate it.

samantha_lynn
Esteemed Contributor III

Thank you for that tech data, I was able to find a few things in there that may indicate the issue. I want to confirm for you, would you be able to email me a screen shot of the information you see when you go in to the HiveManager> Click on the silhouette icon in the top right hand corner> About HiveManager? I'd like to compare that information to what the AP is trying to use, to make sure it doesn't have any contradictory settings.

samantha_lynn
Esteemed Contributor III

Could you enable the following debugs on an AP having this issue:

 

_debug capwap info

_debug capwap basic

_debug capwap stat

 

Once we've enabled these debugs, please replicate the issue and then pull tech data. If you are using HiveManager (formerly NG, cloud.aerohive.com), you'll want to go to Tools> Utilities> Get tech data> Check the box next to the AP with the debugs running> Get tech data (at the top of the page this time). If you want to share the tech data with me directly, please feel free to send it to communityhelp@aerohive.com.

GTM-P2G8KFN