Need help getting CNUT to upgrade ePMP

Products ePMP
1

Hello,

   I've used CNUT for years upgrading our PMP100 radios and over the last few releases of ePMP firmware I have tried several times to use it to upgrade my ePMP radios but have thus far been unsuccessful.. I'm reaching a point however where I have enough ePMP radios installed that I really need CNUT to work with them.

CNUT Version 4.8.1
Firware package:  ePMP-2.5.1.pkg3
 
I have tried this on 3 seperate machines and 2 fresh installs of the newest version of CNUT.  My last/current attempt is using the same PC / CNUT (v4.8.1) that I use daily to upgrade PMP100 radios. It is on the same subnet as the ePMP radios management interface (10.10.#.# 255.255.0.0) and I get the same results I always get:
 
10/06/15 15:01:42 INFO   Canopy Network Updater Build Version:4.8.1 Loaded.
10/06/15 15:01:42 INFO   Current User: Owner
10/06/15 15:01:42 INFO   Java Version: 1.6.0_15
10/06/15 15:01:42 INFO   Platform: x86
10/06/15 15:01:42 INFO   Operating System: Windows 7
10/06/15 15:01:42 INFO   OS Version: 6.1
10/06/15 15:01:42 INFO   Loading prefs from: C:\Canopy\NetworkUpdater\pref\canopy_swupdater_pref.txt
10/06/15 15:01:43 INFO   Starting Http Server on host:fe80:0:0:0:f583:3e60:6b8f:2535%10
10/06/15 15:01:43 INFO   Generating certificate for host:fe80:0:0:0:f583:3e60:6b8f:2535%10 ...
10/06/15 15:01:45 INFO   Starting server on HTTP...
10/06/15 15:01:45 INFO   Server on HTTP started
10/06/15 15:01:45 INFO   CNUT Http Server started.
10/06/15 15:05:03 INFO   Network Element:10.10.156.52 added.
10/06/15 15:05:07 INFO   Refresh Selected Network Elements process start ..
10/06/15 15:05:07 INFO   Refreshing NE at:10.10.156.52
10/06/15 15:05:07 INFO   SNMP Session Manager pool size = 10
10/06/15 15:05:07 INFO   SNMP session Listening on 10.10.0.2/0
10/06/15 15:05:08 WARN   NE at:10.10.156.52 Type corrected from AP to ePMP_STA
10/06/15 15:05:08 INFO   Refreshing NE at:10.10.156.52
10/06/15 15:05:08 INFO   NE at:10.10.156.52 refreshed.
10/06/15 15:05:08 INFO   Refresh Selected Network Elements process has completed.
10/06/15 15:05:45 INFO   Software package :C:\Canopy\NetworkUpdater\ePMP-2.5.1.pkg3 added.
10/06/15 15:05:48 INFO   HTTP(s) server loading package:C:\Canopy\NetworkUpdater\ePMP-2.5.1.pkg3
10/06/15 15:06:00 INFO   Updating Selected Network Elements process start ..
10/06/15 15:06:00 INFO   ePMP-2.5.1.pkg3 loaded.
10/06/15 15:06:00 INFO   Starting Update Process ..
10/06/15 15:06:00 INFO   Queue NE:10.10.156.52 for updating
10/06/15 15:06:01 INFO   Host: 10.10.156.52;ESN: 000456C93E82;Message: Checking Network Element Status (SITE= CambiumNetworks)
10/06/15 15:06:01 INFO   Host: 10.10.156.52;ESN: 000456C93E82;Message: Current = 2.4.1, U-Boot 9344_PX 1.1.4.a (Mar 9 2014 - 22:20:53), 2.4 Ghz Integrated (SITE= CambiumNetworks)
10/06/15 15:06:01 INFO   Host: 10.10.156.52;ESN: 000456C93E82;Message: Using Package C:\Canopy\NetworkUpdater\ePMP-2.5.1.pkg3 (SITE= CambiumNetworks)
10/06/15 15:06:01 WARN   Host: 10.10.156.52;ESN: 000456C93E82;Message: Sending Upgrade command with URL: http://fe80:0:0:0:f583:3e60:6b8f:2535%10:80/1579512806/ePMP-NonGPS_Synced-v2.5.1.tar.gz (SITE= CambiumNetworks)
10/06/15 15:06:01 INFO   Host: 10.10.156.52;ESN: 000456C93E82;Message: Upgrade command sent successfully. (SITE= CambiumNetworks)
10/06/15 15:06:01 INFO   Host: 10.10.156.52;ESN: 000456C93E82;Message: Monitoring the device for Update. (SITE= CambiumNetworks)
10/06/15 15:06:02 INFO   Host: 10.10.156.52;ESN: 000456C93E82;Message: ActiveVersion: 2.4.1 CurrentVersion: 2.4.1 (SITE= CambiumNetworks)
10/06/15 15:06:02 WARN   Host: 10.10.156.52;ESN: 000456C93E82;Message: Failed to upgrade device to 2.5.1 (SITE= CambiumNetworks)
10/06/15 15:06:02 INFO   Node: 10.10.156.52 Update Completed.
10/06/15 15:06:02 INFO   Refreshing NE at:10.10.156.52
10/06/15 15:06:04 INFO   Updating Selected Network Elements process has completed.
 
 
Thanks in advance for any help
2

IIRC, you have to manually upgrade those older, pre-2.4.3 SM's to 2.4.3, and then you can use cnut/WM4 to do updates? You might want to try that on one and see if it works. Of course, if that is the case, you might as well upgrade all the ePMP to 2.5.1 by hand. Alternativly, maybe the CNS could automate the update of these radios?

3

Exact same results updating a 2.4.3 radio:

10/06/15 16:24:29 INFO Refresh Selected Network Elements process start ..
10/06/15 16:24:29 INFO Refreshing NE at:10.10.156.47
10/06/15 16:24:30 WARN NE at:10.10.156.47 Type corrected from AP to ePMP_STA
10/06/15 16:24:30 INFO Refreshing NE at:10.10.156.47
10/06/15 16:24:30 INFO NE at:10.10.156.47 refreshed.
10/06/15 16:24:30 INFO Refresh Selected Network Elements process has completed.
10/06/15 16:24:40 INFO Updating Selected Network Elements process start ..
10/06/15 16:24:40 INFO ePMP-2.5.1.pkg3 loaded.
10/06/15 16:24:40 INFO Starting Update Process ..
10/06/15 16:24:40 INFO Queue NE:10.10.156.47 for updating
10/06/15 16:24:41 INFO Host: 10.10.156.47;ESN: 000456C89477;Message: Checking Network Element Status (SITE= CambiumNetworks)
10/06/15 16:24:41 INFO Host: 10.10.156.47;ESN: 000456C89477;Message: Current = 2.4.3, U-Boot 9344_PX 1.1.4.a (Dec 7 2013 - 01:24:01), 5 Ghz Connectorized (SITE= CambiumNetworks)
10/06/15 16:24:41 INFO Host: 10.10.156.47;ESN: 000456C89477;Message: Using Package C:\Canopy\NetworkUpdater\ePMP-2.5.1.pkg3 (SITE= CambiumNetworks)
10/06/15 16:24:41 WARN Host: 10.10.156.47;ESN: 000456C89477;Message: Sending Upgrade command with URL: http://fe80:0:0:0:f583:3e60:6b8f:2535%10:80/1579512806/ePMP-NonGPS_Synced-v2.5.1.tar.gz (SITE= CambiumNetworks)
10/06/15 16:24:41 INFO Host: 10.10.156.47;ESN: 000456C89477;Message: Upgrade command sent successfully. (SITE= CambiumNetworks)
10/06/15 16:24:41 INFO Host: 10.10.156.47;ESN: 000456C89477;Message: Monitoring the device for Update. (SITE= CambiumNetworks)
10/06/15 16:24:41 INFO Host: 10.10.156.47;ESN: 000456C89477;Message: Uploading image to device (SITE= CambiumNetworks)
10/06/15 16:24:46 INFO Host: 10.10.156.47;ESN: 000456C89477;Message: ActiveVersion: 2.4.3 CurrentVersion: 2.4.3 (SITE= CambiumNetworks)
10/06/15 16:24:46 WARN Host: 10.10.156.47;ESN: 000456C89477;Message: Failed to upgrade device to 2.5.1 (SITE= CambiumNetworks)
10/06/15 16:24:46 INFO Node: 10.10.156.47 Update Completed.
10/06/15 16:24:46 INFO Refreshing NE at:10.10.156.47
10/06/15 16:24:50 INFO Updating Selected Network Elements process has completed.

4

Hello brubble1,

Have you been able to get your SM to upgrade with CNUT? The process should work (see log below). This was done with CNUT 4.8.1. Do you have syslog for the SM? Have you attempted to reboot the SM prior to the upgrade?

Regards

10/07/15 10:30:13 INFO NE at:172.16.0.12 refreshed.
10/07/15 10:30:13 INFO Refreshing NE at:172.16.0.14
10/07/15 10:30:14 INFO NE at:172.16.0.14 refreshed.
10/07/15 10:30:14 INFO Refresh Entire Network process has completed.
10/07/15 10:30:14 INFO HTTP(s) server loading package:C:\Users\batwings\Desktop\2.5.1\PKG3\ePMP-2.5.1.pkg3
10/07/15 10:30:49 INFO Updating Selected Network Elements process start ..
10/07/15 10:30:49 INFO ePMP-2.5.1.pkg3 loaded.
10/07/15 10:30:49 INFO Starting Update Process ..
10/07/15 10:30:49 INFO Queue NE:172.16.0.14 for updating
10/07/15 10:30:50 INFO HTTP Server: request received from SM,MAC:unknown, requested Image:ePMP-NonGPS_Synced-v2.5.1.tar.gz
10/07/15 10:30:50 INFO Host: 172.16.0.14;ESN: 000456C36074;Message: Checking Network Element Status (SITE= CambiumNetworks)
10/07/15 10:30:50 INFO Host: 172.16.0.14;ESN: 000456C36074;Message: Current = 2.4.1, U-Boot 9344_PX 1.1.4.a (Nov 8 2013 - 23:54:33), 5 Ghz Connectorized (SITE= CambiumNetworks)
10/07/15 10:30:50 INFO Host: 172.16.0.14;ESN: 000456C36074;Message: Using Package C:\Users\batwings\Desktop\2.5.1\PKG3\ePMP-2.5.1.pkg3 (SITE= CambiumNetworks)
10/07/15 10:30:50 WARN Host: 172.16.0.14;ESN: 000456C36074;Message: Sending Upgrade command with URL: http://172.16.0.199:80/1053525069/ePMP-NonGPS_Synced-v2.5.1.tar.gz (SITE= CambiumNetworks)
10/07/15 10:30:50 INFO Host: 172.16.0.14;ESN: 000456C36074;Message: Upgrade command sent successfully. (SITE= CambiumNetworks)
10/07/15 10:30:50 INFO Host: 172.16.0.14;ESN: 000456C36074;Message: Monitoring the device for Update. (SITE= CambiumNetworks)
10/07/15 10:30:50 INFO Host: 172.16.0.14;ESN: 000456C36074;Message: Uploading image to device (SITE= CambiumNetworks)
10/07/15 10:30:55 INFO Host: 172.16.0.14;ESN: 000456C36074;Message: Uploading image to flash (SITE= CambiumNetworks)
10/07/15 10:32:15 INFO Host: 172.16.0.14;ESN: 000456C36074;Message: Rebooting (SITE= CambiumNetworks)
10/07/15 10:33:54 INFO Host: 172.16.0.14;ESN: 000456C36074;Message: ActiveVersion: 2.5.1 CurrentVersion: 2.5.1 (SITE= CambiumNetworks)
10/07/15 10:33:54 INFO Host: 172.16.0.14;ESN: 000456C36074;Message: Device successfully upgraded to 2.5.1 (SITE= CambiumNetworks)
10/07/15 10:33:54 INFO Node: 172.16.0.14 Update Completed.
10/07/15 10:33:54 INFO Refreshing NE at:172.16.0.14
10/07/15 10:34:08 INFO Updating Selected Network Elements process has completed.

5

Luis,

  Nothing shows up in Syslog when I attempt to update the radio via CNUT. I even just now logged into the managment interface, brought up the syslog page (display syslog is enabled) and watched the syslog while I attempted to update it with CNUT. Nothing new appeared in the syslog display and even refresed it to make sure I was seeing the current syslog and there was nothing new there.    I tried to update another radio with CNUT that I have on my desk here, so not doing it via the WAN , I'm plugged into it accessing via the LAN port and LAN IP (all my radios are configured to do do NAT/DHCP on the LAN and PPPoE on the WAN). Anyway, cnut says the exact same thing and nothing showed up in the syslog other than what was already there.

The radio I have on my desk here that I'm trying to update is V2.4.3, CNUT is v4.8.1 .  I have tried updating multible customer radios and this radio on my desk I'm trying to update now has been rebooted several times while I've messed with it.

I had also installed a fresh install of CNUT 4.8.1 on another PC and get the exact same results when I try to update any customer radios (most our radios are 2.4.3 ).

Thanks 

6

Hello brubble1,

I just noticed something in your log that I did not see before... It looks that in your case, the process fails to transfer the firmware into the device to be upgraded. Do you have a firewall in the PC where CNUT is installed that could be preventing the device from transferring the firmware? If you do, could you try disabling the firewall on the CNUT PC?

Regards

7

Why, if I set the HTTP port on t he unit from 80 to anything else, ie. 8088, I am unable to get any information from CNUT (refresh etc.). I though that SNMP is on port 161 and CNUT will read information on this port, but it uses HTTP (port 80) for retrieving information. Once I set my unit back to p.80 I can read the unit info smoothly.

In CNUT there is no direct setting how to use another port for HTTP/HTTPS as 80/443.

How to proceed when my unit uses other port from the default one (80)?

8

Luis,

   The only firewall on the PC I normally use CNUT on (to update PMP100 radios) is the windows firewall.  No AV or anti-anything on this machine other than windows build in AV.  I disabled the windows firewall but the problem is unchanged, cnut log says the exact same thing, nothing in syslog.

  I can update PMP100 radios just fine on this machine, what is different about the ePMP radios  ? 

Edit:   I factory defaulted the radio here on my desk and tried updating it via the 169.254.1.1  admin/admin  private (SNMP read write string)  but the results are the same,  I can refresh the radio with CNUT but not update it. I also tried using the Tools > Reboot  opiton in CNUT and it doesn't work on the ePMP radio.

9

Hello brubble1,

If you can arrange remote access to your CNUT PC maybe I can take a look and try to help. Send me a PM with the information, if you can do so.

Regards

10

Luis,

 Sent PM with info, let me know if you have any problems accessing it.  

Thanks!

11

I am having the same exact issue. I can comunicate with the SMs and see what the current version is but in trying to upgrade it gives me Message: Failed to upgrade device to 2.5.1. Did you find what settings need to be fixed to get the upgrade to work?

12

brubble1,

I looked at your setup. I found couple issues with the configuration of CNUT:

- When updating ePMP, you may need to modify the Network Element Access parameters (user account/passwd, Community string) to match the device (see figures 1 and 2)

- If your CNUT PC has multiple IPs in the same interface, make sure the HTTP server is using an IP that the ePMP device can route to (figure 3 and 4)

In your lab setup, the HTTP server was using the public IP, not the local IP, so the ePMP device could not reach it. This is critical, since the ePMP device needs to get the fw using that address. This may not have been the case for an ePMP device that was already deployed in your network, so if you want to try that next, let me know.

Regards,

Luis

3 Likes
13

Luis,

   The dual IP thing can't be the problem because I only set the dual IP up so that you could log in from the Internet and access that radio. The NIC did not previously have two IP's assigned to it.
  
   The other solution offered isn't working for me either so I must be missing some simple step or something.  To access a customer radio and attempt to update it in CNUT this is what I just tried:


(1) First I changed the IP address of my NIC because my customer radios are in 10.10.#.# / 255.255.0.0 so I changed the IP of my desktop to 10.10.156.2 (not in use by any customer radios) 255.255.0.0   and I verify that the second IP is gone from the NIC.
(2) I open CNUT  right click on the Network Root and "Add Network Element" and I enter the IP, Username / Password , and RW string .  The customer radio at 10.10.156.47 is added under root network and I select it.

Note: Our customer radios are configure as NAT, DHCP with PPPoE and Separate Wireless Management Interface.  The 10.10.156.# address I am using to access the radios in CNUT is the Seperate Wireless Management Interface IP address.  So the radio has a LAN interface (static IP doing NAT/DHCP to customer equipment) , a PPPoE Wan Interface IP, and the Management Interface.

(3) I "refresh selected network elements" the radio is refreshed and CNUT shows it is running v2.4.3 of the firmware.
(4) Per your suggesting I go to "Edit>Prefrences" and I change the Username/Password and RW string to match that of the customer radio I just added (it is the exact same username/password/string I entered when I added the radio via Add Network Element).
(5) I check to make sure that epmp-2.5.1.pkg3 is the only update package selected (it is).
(6) I go to/select  "Update Selected Network Elements"

It gives the exact same results, same log text it always gives. 

(7) I go to Update>HTTP Server Configure  and that looks like I assume it should , HTTP is selected, Port 80 is selected and the IP address is the 10.10.156.2 of my PC.

Also tried changing the order on (2) and (4). That is , I went in and set up the Network Preferences first and when I added the subscriber radio I just left "Use Defaults" selected and entered the IP of the customer radio.  Same results.

Just to make sure my CNUT was still working I added one of my PMP100 radios (they are also in the 10.10.0.0 subnet) to the default network (I did "Add Network Device, I unselected "use default settings, I entered the username/password/rw string and IP of the PMP100 radio) , changed the update package to the 13.1.3 pkg3 for the pmp100 radios,  updated selected network elements (the PMP100 radio) and, it worked, the PMP100 radio was updated from 11.1 to 13.1.3. 

 I immediately  changed update package back to 2.5.1.pkg3 for the epmp, selected the epmp radio, refreshed it (it refreshed) then hit update selected network elements and again, failed, same results in the log I always get trying to update ePMP.

So this has almost got to be I'm missing some small step needed to update epmp that isn't needed to update pmp100 or something in the way our installed ePMP customer radios are set up.


Thanks

14

Hello brubble1,

Do you see this same entry in the log for your latest attempts?

10/06/15 15:06:01 WARN   Host: 10.10.156.52;ESN: 000456C93E82;Message: Sending Upgrade command with URL: http://fe80:0:0:0:f583:3e60:6b8f:2535%10:80/1579512806/ePMP-NonGPS_Synced-v2.5.1.tar.gz (SITE= CambiumNetworks)

If you do, could you try disabling IPv6 from the properties of the NIC you are using with CNUT?

Regards

1 Like
15

I removed ipv6 from the properties, still gave the error.  I stopped and restarted the nic, still gave the error . I closed CNUT and restarted it, still error.  I rebooted the machine...

That fixed it. I can now update ePMP radios with CNUT.

Thanks for all of the time and effort you put into solving this !

1 Like
16

Awesome! Actually, thanks for your patience with this issue.

Regards

1 Like
17

Hi,

I'm am having very similar issues as indicated by others in this thread.  However, after making the adjustment under the HTTP Server Configure\HTTP Server Host menu options and selecting the correct IP address for which the ePMP devices are under,  I was able to upgrade 1 AP and 3 SMs successfully out of 2 APs and 5 SMs.

The problem I'm now receiving in the error is this:-

"016-01-01 23:29:29    Daemon.Error    172.17.24.1    1 2016-01-01T23:29:29-05:00 Client_Pharmacy snmpd 9269 - [meta sequenceId="3"] SW Update ERROR: File Size is too big
2016-01-01 23:29:29    Daemon.Error    127.0.0.1    1 2016-01-01T23:29:29-05:00 Client_TPP-MS snmpd 5922 - [meta sequenceId="9"] SW Update ERROR: File Size is too big
2016-01-01 23:29:29    Daemon.Error    172.17.24.3    1 2016-01-01T23:29:29-05:00 The snmpd 6211 - [meta sequenceId="9"] SW Update ERROR: File Size is too big
2016-01-01 23:29:29    Daemon.Error    127.0.0.1    1 2016-01-01T23:29:29-05:00 Client_Domi snmpd 31783 - [meta sequenceId="9"] SW Update ERROR: File Size is too big"

So, I was trying to update  all the units to v2.4.1.  After repeated unsuccessful attempts I manually updated from the WebGUI per device.  The manual updating of the firmware from the browser worked fine.  CNUT refuses to update the SMs and APs.  

I'm hoping to be able to use CNUT as the network will be growing shortly and it will be a major task to manually update the entire ePMP network.

FYI:   Using the same server/computer and CNUT version i.e. v4.8.1, we're able to upgrade the Canopy FSK series with no problems.  The FSK series have much more devices than the current ePMP network.

I've been using this small ePMP network as the environment to test the CNUT and management features of the ePMP series before increasing the network size.

Regards.