Auto-update not working?

We've been using auto-update in our office to standardize the f/w version on SMs going out into the field, but we're running into a snag. CNUT 4.12.8, AP is running 16.0.1 Official, but my 450b Mid-Gain SMs running 16.0 from the factory don't ever update. Is this just me? Has anyone else seen this?

There are possible workarounds, but all require a massive increase in effort to get the radios updated. Anyone have any idea?

====================================

Update: here is a section of the CNUT log from yesterday and today - I was not seeing any of these errors yesterday when I wrote the above:

05/14/19 16:00:04 INFO   	Enabling SM Autoupdate on Selected Network Elements process has completed.
05/15/19 08:16:11 INFO   	Refresh Selected Network Elements process start ..
05/15/19 08:16:11 INFO   	Refreshing NE at:10.1.48.76
05/15/19 08:16:11 INFO   	NE at:10.1.48.76 refreshed.
05/15/19 08:16:11 INFO   	Refresh Selected Network Elements process has completed.
05/15/19 08:16:18 INFO   	Updating Selected Network Elements process start ..
05/15/19 08:16:18 INFO   	CANOPY160_1BUILDOFFICIAL_PXP45x_S.pkg3 loaded.
05/15/19 08:16:18 INFO   	Starting Update Process ..
05/15/19 08:16:18 INFO   	Queue NE:10.1.48.76 for updating
05/15/19 08:16:19 WARN   	Failed to find Element in update queue:0A003EA03255@10.1.4.5,Checking Network Element Status
05/15/19 08:16:19 WARN   	Failed to find Element in update queue:0A003EA03255@10.1.4.5,Current = CANOPY 16.0.1 AP, CANOPYBOOT 1.0, 020519
05/15/19 08:16:19 WARN   	Failed to find Element in update queue:0A003EA03255@10.1.4.5,Using Package C:\Users\Darren\Downloads\MotoCambium\CANOPY160_1BUILDOFFICIAL_PXP45x_S.pkg3
05/15/19 08:16:19 WARN   	Failed to find Element in update queue:0A003EA03255@10.1.4.5,Disabling Auto-Update
05/15/19 08:16:20 WARN   	Failed to find Element in update queue:0A003EA03255@10.1.4.5,Auto-Update Disabled.
05/15/19 08:16:20 WARN   	Failed to find Element in update queue:0A003EA03255@10.1.4.5,Transferring Files actionList.acl;5x_cat120.img; to host:10.1.4.5 by http
05/15/19 08:16:20 WARN   	Failed to find Element in update queue:0A003EA03255@10.1.4.5,Enabling Auto Update...
05/15/19 08:16:20 WARN   	Failed to find Element in update queue:0A003EA03255@10.1.4.5,Auto-Update Enabled
05/15/19 08:16:20 WARN   	Failed to find Element in update queue:0A003E783B1C@AP:[10.1.4.5]LUID:[3],Auto-Update Started(status:120).
05/15/19 08:16:20 WARN   	Failed to find Element in update queue:0A003E783B1C@AP:[10.1.4.5]LUID:[3],Invalid image(s) selected Or Failed to set max file size(status:256).

Darren - We will look into this for you... I can't think of anything off the top of my head.  Someone smarter than me will reply as soon as we find something.

1 Like

Darren-  Did you check Update--> Configure to see if the PMP 450b was selected in the Auto Update SM Type.  I ran the autoupdate from 16.0 to 16.0.1 with no issue.  Looking at your log messages it was missing the image.

Yours:

Transferring Files actionList.acl;5x_cat120.img; to host:10.1.4.5 by http

Mine:

Transferring Files actionList.acl;5x_cat120.img;upgrade.img;upgrade-p15.img; to host:10.120.200.22 by http 

1 Like

Dave,

    I hadn't even thought of that setting, so I turned the 450b checkbox on, and tried again.

The AP reports it is in auto-update mode, but the SMs still won't update 

******SYSTEM STARTUP******
System Reset Exception -- Reset due to applying new image
Software Version : CANOPY 16.0 SM
Board Type : P15
Board Temperature : 59 C / 137 F
Device Setting : 4.9/5.9GHz MIMO OFDM - Subscriber Module - 0a-00-3e-78-3b-1c
FPGA Version : 081518;
05/15/2019 : 14:56:44 UTC : Spectrum Analysis on boot up complete for 25 seconds.;
05/15/2019 : 08:58:15 CST : :Timezone set to CST;
05/15/2019 : 09:36:36 CST : :Time Set
05/15/2019 : 09:36:44 CST : :Burnfile App from AutoUpdate.
05/15/2019 : 09:36:44 CST : :Could not parse img file header
05/15/2019 : 09:36:44 CST : :Internal; user=autoupdate; POReset from AutoUpdate.;
05/15/2019 : 09:36:44 CST : :Rebooting to apply new image...
05/15/2019 : 09:36:44 CST : :Forced reset;
05/15/2019 : 15:36:44 UTC :

My next step is to revert the AP to 16.0 and see if that makes any difference (as suggested by Cambium support)

Darren-

   My PMP 450b was connected to a PMP 450i AP.  What AP are you using.  An engineer brought to my attention that if using a PMP 450 AP it may not have enough memory for all the images.  Can you try selecting one radio model at a time?  I have may lab set up for something else at this time.  If you are using a PMP 450 I can see if I can test it.

Dave

2 Likes

Dave - that's why I respect you so much, man! You saw the actual potential issues and limitations which could cause this result, and figured out how to work around them.

Yes, that was it! The 450 AP has limited RAM, so to make it have no issue when auto-updating, I need to load only the necessary images. Much obliged!

3 Likes

Darren-  Glad to help.  For the record, Charlie gave me the RAM idea as thoughts and test results were passed around.  

2 Likes