Using CNUT 4.10.5 and cannot update a 3.65 PMP450 (non-i) AP from 15.0.3 to 15.1. The AP just reboots and shows "System Reset Exception -- Reset due to FatalError" in log file. Its done this on 3 different AP's but worked on some other ones. All the same type/model with very similiar config.
I seem to recall encountering this in past and had to use an older version of CNUT. Anyone else seen this issue?
We have not seen this before, and are investigating. We will try to reproduce, and will let you know the outcome.
We have spent time trying to reproduce this issue, but have not seen it occur. All upgrade scenarios worked without issue using CNUT 4.10.5.
Have you tried to upgrade a second time? Perhaps there was some kind of interruption in service or power at those particular APs?
Uninstalled and reinstalled CNUT 4.10.5 on my Windows 10 work PC. Certain 3.6 PMP450 AP's will still not update. Although on my home Windows 10 PC they would update with CNUT 4.10.5. Weird. Most update fine though with my work PC.
Correction, on my home PC with fresh install of CNUT they still will not update. Going to install older version of CNUT and give it a whack soon.
I am experiencing the same type of problem with only one PMP 450 AP. I am using CNUT 4.10.5 and trying to update a 5GHz PMP450 AP from 15.0.0.1 to 15.1 but with no luck. Here is the log that shows on CNUT:
06/01/17 13:56:44 INFO Updating Selected Network Elements process start ..
06/01/17 13:56:44 INFO CANOPY151BUILDOFFICIAL_PXP45x_S.pkg3 loaded.
06/01/17 13:56:44 INFO Starting Update Process ..
06/01/17 13:56:44 INFO Queue NE:172.16.x.x for updating
06/01/17 13:56:45 INFO Host: 172.16.x.x;ESN: 0A003EB3CFEC;Message: Checking Network Element Status (SITE= CamAP2)
06/01/17 13:56:45 INFO Host: 172.16.x.x;ESN: 0A003EB3CFEC;Message: Current = CANOPY 15.0.0.1 AP-DES, CANOPYBOOT 1.0, 061716 (SITE= CamAP2)
06/01/17 13:56:45 INFO Host: 172.16.x.x;ESN: 0A003EB3CFEC;Message: Using Package N:\Network\Network-Engineers\Cambium Wireless\PMP 450 Software\15.1\CANOPY151BUILDOFFICIAL_PXP45x_S.pkg3 (SITE= CamAP2)
06/01/17 13:56:45 INFO Host: 172.16.x.x;ESN: 0A003EB3CFEC;Message: Detect registered slave device link (SITE= CamAP2)
06/01/17 13:56:45 INFO Host: 172.16.x.x;ESN: 0A003EB3CFEC;Message: Transferring Files 5x_20_cf200.img to host:172.16.x.x by http (SITE= CamAP2)
06/01/17 13:56:59 INFO Host: 172.16.x.x;ESN: 0A003EB3CFEC;Message: Programming ... (SITE= CamAP2)
06/01/17 13:58:28 WARN Host: 172.16.x.x;ESN: 0A003EB3CFEC;Message: No response returned.Attempting 2 of 5 to connect to the device... (SITE= CamAP2)
06/01/17 13:58:48 WARN Host: 172.16.x.x;ESN: 0A003EB3CFEC;Message: Update not started. (SITE= CamAP2)
06/01/17 13:58:48 INFO Node: 172.16.x.x Update Completed.
06/01/17 13:58:48 INFO Refreshing NE at:172.16.x.x
06/01/17 13:58:48 INFO No SMs registered to AP 172.16.x.x
06/01/17 13:58:48 INFO Updating Selected Network Elements process has completed.
Here is the Event Log from the AP itself:
System Reset Exception -- Reset due to FatalError
Software Version : CANOPY 15.0.0.1 AP-DES
Board Type : P12
Boot Bank : 0
Board Temperature : 38 C / 101 F
Device Setting : 5.7GHz MIMO OFDM - Access Point - 0a-00-3e-b3-cf-ec - 5800.0 MHz - 20.0 MHz - 1/16 - CC 2 - 2.5 ms - North America/United States
FPGA Version : 061716
FPGA Features : DES, Sched, US/ETSI;
06/01/2017 : 13:58:00 MST : :t_ident(NTP
06/01/2017 : 13:58:33 MST : :Time Set
06/01/2017 : 13:58:59 MST : Acquired sync pulse from Power Port
Any progress on this? Have another one right now that will not update from 15.0.2 too 15.1. Reboots with "Reset due to FatalError" on every attempt.
I. Performed CNUT software updates/rollbacks using CNUT per the description posted by "hci" 3 weeks ago.
My test setup:
AP: PMP 450 3.6-GHz
SM: PMP 450 3.6-GHz registered to above AP.
CNUT Version: 4.10.5
Software packages: Canopy 15.0.3 Build Official (CANOPY150_3BUILDOFFICIAL_PXP45x_S.pkg3), Canopy 15.1 Build Official (CANOPY151BUILDOFFICIAL_PXP45x_S.pkg3)
II. Performed CNUT software updates/rollbacks using CNUT per the description posted by "timb" 2 weeks ago.
My test setup:
AP: PMP 450 5.4-GHz
SM: PMP 450 5.4-GHz registered to above AP.
CNUT Version: 4.10.5
Software packages: Canopy 15.0.0.1 Build Official (CANOPY150_0_1BUILDofficial_PXP45x_S.pkg3), Canopy 15.1 Build Official (CANOPY151BUILDOFFICIAL_PXP45x_S.pkg3)
CNUT scenarios performed for I. and II. above:
A. Performed software update/rollback twice, updating the AP first, then letting CNUT update the SM.
B. Performed software update/rollback twice, updating the SM first via the AP, then next updating the AP in a separate CNUT operation.
(Many customers have informed Cambium Networks of their preference for software updating via scenario B, that is, SMs first.)
Both I. and II. above were successful with my setup, however I have some CNUT steps (gained from experience) that may prove useful in the field when difficulties are encountered:
1. On field PCs, store a list of network APs as a text (.txt) file, one line per AP IP Address. Save and maintain this file for future use.
Example:
10.122.86.2
10.122.86.32
10.122.86.68
10.122.86.114
10.122.86.145
10.122.86.185
10.122.86.207 <--- This is the last line. Don't press [Enter] or [Return] after the last IP address.
(Use of this file will become apparent below.)
2. After a period of time using CNUT for repetitive tasks, communication errors have been known to occur. I've personally observed SNMP errors arise causing the Progress bar (9th column on GUI screen) to turn red. The CNUT log posted by "timb" is another occurrence that has been seen, though not as common.
3. At this point, stop and exit CNUT (File > Exit). Don't save any Active Network should the popup window ask. Don't save any configuration file should the popup window ask.
4. Restart CNUT fresh.
5. Select File > New Network Archive.
6. Select Edit > Add Elements to Network Root
7. In Add Network Element To Network Root: Enter the Device Login ID, Device Password, Retype Device Password should they differ from the Parent Element.
8. Under Discovery Targets select Element Host Name(s)/IP Address(s) button.
9. Copy-and-paste the AP IP addresses from the list of network APs stored in the text (.txt) file (Step 1.). Use of this file saves a lot of time keyboarding.
10. Perform the CNUT software update/rollback.
May success be yours!
I am having this same issue. Has a solution been found?
Trying to update using CNUT 4.10.5. Following is output from CNUT:
06/29/17 12:11:10 INFO Canopy Network Updater Build Version:4.10.5 Loaded.
06/29/17 12:11:10 INFO Current User: Todd
06/29/17 12:11:10 INFO Java Version: 1.6.0_15
06/29/17 12:11:10 INFO Platform: x86 06/29/17 12:11:10 INFO Operating System: Windows 7
06/29/17 12:11:10 INFO OS Version: 6.1
06/29/17 12:11:10 INFO Loading prefs from: C:\Cambium\NetworkUpdater\pref\canopy_swupdater_pref.txt
06/29/17 12:11:10 INFO Load network from file:\\Mac\Home\Documents\Edgar.net
06/29/17 12:11:14 INFO Starting Http Server on host:10.211.55.4
06/29/17 12:11:14 INFO Generating certificate for host:10.211.55.4 ...
06/29/17 12:11:15 INFO Starting server on HTTP...
06/29/17 12:11:15 INFO Server on HTTP started
06/29/17 12:11:15 INFO CNUT Http Server started.
06/29/17 12:11:19 INFO No changes to be saved.
06/29/17 12:12:43 INFO Network Element:10.250.0.116 added.
06/29/17 12:12:43 INFO Network Element:10.250.0.117 added.
06/29/17 12:12:43 INFO Network Element:10.250.0.118 added.
06/29/17 12:12:43 INFO Network Element:10.250.0.119 added.
06/29/17 12:12:43 INFO Network Element:10.250.0.120 added.
06/29/17 12:12:43 INFO Network Element:10.250.0.121 added.
06/29/17 12:12:57 INFO Updating Selected Network Elements process start ..
06/29/17 12:13:01 INFO CANOPY151BUILDOFFICIAL_PXP45x_S.pkg3 loaded.
06/29/17 12:13:01 INFO Starting Update Process ..
06/29/17 12:13:01 INFO Queue NE:10.250.0.116 for updating
06/29/17 12:13:01 INFO SNMP Session Manager pool size = 10
06/29/17 12:13:01 INFO SNMP session Listening on 10.211.55.4/0
06/29/17 12:13:02 INFO Host: 10.250.0.116;ESN: 0A003E4852D0;Message: Checking Network Element Status (SITE= <Not Available>)
06/29/17 12:13:02 INFO Host: 10.250.0.116;ESN: 0A003E4852D0;Message: Current = CANOPY 15.0.0.1 AP-None, CANOPYBOOT 1.0, 061716 (SITE= <Not Available>)
06/29/17 12:13:02 INFO Host: 10.250.0.116;ESN: 0A003E4852D0;Message: Using Package \\Mac\Home\Downloads\CANOPY151BUILDOFFICIAL_PXP45x_S.pkg3 (SITE= <Not Available>)
06/29/17 12:13:02 INFO Host: 10.250.0.116;ESN: 0A003E4852D0;Message: Detect registered slave device link (SITE= <Not Available>)
06/29/17 12:13:02 INFO Host: 10.250.0.116;ESN: 0A003E4852D0;Message: Transferring Files 5x_20_cf200.img to host:10.250.0.116 by http (SITE= <Not Available>)
06/29/17 12:13:54 INFO Host: 10.250.0.116;ESN: 0A003E4852D0;Message: Programming ... (SITE= <Not Available>)
06/29/17 12:15:23 WARN Host: 10.250.0.116;ESN: 0A003E4852D0;Message: No response returned.Attempting 2 of 5 to connect to the device... (SITE= <Not Available>)
06/29/17 12:15:42 WARN Host: 10.250.0.116;ESN: 0A003E4852D0;Message: Update not started. (SITE= <Not Available>)
06/29/17 12:15:42 INFO Node: 10.250.0.116 Update Completed.
06/29/17 12:15:42 INFO Refreshing NE at:10.250.0.116
06/29/17 12:15:42 WARN NE at:10.250.0.116 Type corrected from AP to PMP450AP
06/29/17 12:15:42 INFO NE at:10.250.0.116 refreshed.
06/29/17 12:15:43 INFO No SMs registered to AP 10.250.0.116
06/29/17 12:15:43 INFO Updating Selected Network Elements process has completed.
A couple I had this issue with I updated all SM's to 15.1 first and then the AP updated. They were all on 15.0.2 or 15.0.3 though.
I'm literally working on this issue with Cambium engineers right now. I've directed them to this thread. This is an ongoing issue we're investigating. You're not alone!
Thanks! That is my scenario as well. Working through your suggestion as we speak. Will advise outcome.
Just updated another AP that would not update earlier. Would not update until all SM's were updated first.
This procedure worked! Thanks for the tip!
My process in the past had been to enter the APs, then let them search for SMs. I then updated the SMs, then went back for the APs. But, as mentioned, when I tried to do this earlier, I kept getting SNMP errors and the SMs would not show up in CNUT.
So this time I just did a search for equipment on the IP subnet where our SMs are located, once identified they appeared in CNUT. I ran the update, then added APs and updated them next. Worked like a champ.
Although it makes me wonder why/how this process got messed up? It's not like my network, APs, SMs or the VM that I use for running CNUT changed. Had to be the software. Cambium? Any comment?
The other work around ATM is to set the AP not to transmit (set channel to none) reboot so there are no SM's connected, and you'll be able to update the AP.
Any chance we will ever get this fixed? Cannot update another 3.6 450 AP from 15.1.1 too 15.1.2 now. Will have to follow steps of upgrading all SM's first but is there a technical reason we must do it that way?
I spent several hours and was down to my last attempt before swapping out the AP.
This simple yet intrusive method worked like a charm. I simply went into the AP, changed the radio frequency to NONE and rebooted.
As soon as it came up, I went to CNUT, performed the update and it worked. Total time down for Customers was 4 minutes. Once the update was over, I went back in, entered teh radio frequency and all SMs came back. I then used CNUT to enable the SM Autoupdate.
Hope this saves you guys some time. I spent hours trying different things.
Any updates on fixing this bug? Updating from 15.1.3 to 15.1.5 still seems to cause it. Yes, the work around above does seem to solve it but not very conveniant.