Device configuration update keeps failing

  • 2
  • Question
  • Updated 4 years ago
  • Answered
  • (Edited)

Hi, I am brand new to AH and the HiveNation. I have an Access Point that when I try to push a configuration update out to it via MyHive, it always gets aborted at 33%. I selected 'Retry' several times but here is the error that I keep receiving:

"Unable to parse the CLI on the running configuration to perform a delta upload."

Has anyone seen this before? How to fix this? Any help would be greatly appreciated.

Photo of j.m


  • 11 Posts
  • 1 Reply Like

Posted 4 years ago

  • 2
Photo of Brian Powers

Brian Powers, Champ

  • 396 Posts
  • 92 Reply Likes
In the simplest terms, that is saying that the Hivemanager cannot issue a "show run" on the AP to compare what it expects it to be based on its own settings.

This is typically caused by a lack of SSH access from the Hivemanager to the AP.  If you go to the Configuration tab and select the AP.  Then go to Utilities and SSH Client.  Try to connect that.  If that fails, you will need to troubleshoot the link between the Hivemanager and the AP (firewall/content filters are where I'd start). 

If that succeeds, I'd do a reboot from there and restart the AP.  Then I would typically attempt a Complete upload and see if that goes through.
Photo of j.m


  • 11 Posts
  • 1 Reply Like

I was able to SSH to the device, and all pings responded yesterday and today.

With that being said I did as you advised - rebooted and did a Complete upload. Now it's update and running as it should!

Thank you, Brian!

Photo of Roberto Casula

Roberto Casula, Champ

  • 231 Posts
  • 111 Reply Likes
I have had this issue on a number of access points across multiple customers and have a support call open on it. The issue occurs because an error message is output in the middle of the "show run" output which prevents HiveManager from parsing the response correctly. You can verify this if you SSH to the device and manually do a "show run" - in my case there is an error displayed at the top of the output similar to:
ERROR: failed to send message to pm (attempt to send 52 bytes, actually sent -1 (err = 146 - Connection refused)
This error is also produced in other circumstances, possibly referring to a different process than "pm".

The problem is almost always resolved by a reboot, but may come back at a later stage. It seems to be very intermittent indeed. So far I have only seen this happen with 6.1r3 code.
Photo of Steven Bateman

Steven Bateman

  • 65 Posts
  • 12 Reply Likes
I have also seen the same issue, only on one AP actually, but the exact same error message at the top of "show run" as Roberto.

This is on an AP390 running 6.0r2d.

The rest of the APs are AP370 and AP390 running 6.0r2c and aren't having these issues. I'll see if downgrading HiveOS to r2c will help.