Hi All,
Lately I got some problems with cnut.
First is, snmp request time out
and the Second is, the cnut2.2 cant upgrade SM lite to 8.1.5.1
Below is the log:
07/19/07 20:25:32 INFO Starting Update Process …
07/19/07 20:25:32 INFO Using Active FTP for File Transfer
07/19/07 20:25:32 INFO Queue NE:169.254.100.100 for updating
07/19/07 20:25:33 INFO Host: 169.254.100.100;ESN: 0A003E23A163;Message: Checking Network Element Status ( SITE= <Not Available> )
07/19/07 20:25:38 WARN SNMP request timeout
07/19/07 20:25:44 INFO Host: 169.254.100.100;ESN: 0A003E23A163;Message: Current = CANOPY 8.1.4, CANOPYBOOT 3.0, 041006 ( SITE= <Not Available> )
07/19/07 20:25:44 INFO Host: 169.254.100.100;ESN: 0A003E23A163;Message: Using Package C:'Canopy’Firmware’CANOPY8151_DES.pkg2 ( SITE= <Not Available> )
07/19/07 20:25:48 INFO Host: 169.254.100.100;ESN: 0A003E23A163;Message: Transferring Files SMboot.bin to SM ( SITE= <Not Available> )
07/19/07 20:28:18 INFO Host: 169.254.100.100;ESN: 0A003E23A163;Message: Programming ( SITE= <Not Available> )
07/19/07 20:28:24 WARN Host: 169.254.100.100;ESN: 0A003E23A163;Message: Cannot upgrade: burnfile Failed Output from Telnet session: burnflash Burn Boot from file: SMboot.bin Validating Boot File… fread() of BootHdr failed File:SMboot.bin is not a valid image file Telnet+> ( SITE= <Not Available> )
07/19/07 20:28:24 INFO Node: 169.254.100.100 Update Completed.
07/19/07 20:28:24 INFO Update process has completed
Any help is appreciated,
Thanks in advance
I have had an issue that is similar that was solved by hardcoding the update application address on the AP? have you checked that ?
I am having the same trouble right now with a 5.7GHz AP-DES.
I have tried hardcoding update address, no luck.
I noticed CANOPYBOOT is 1.0 not 3.0? This may be true on a P10 AP now?
Here is a snippet:
08/29/07 14:03:37 INFO Host: 10.3.66.137;ESN: 0A003EFBEBC7;Message: Current = CANOPY 8.1.5 AP-DES, CANOPYBOOT 1.0, 102606 ( SITE= <Not Available> )
08/29/07 14:03:52 WARN Host: 10.3.66.137;ESN: 0A003EFBEBC7;Message: Cannot upgrade: burnfile Failed Output from Telnet session: burnflash Validating Image File: boot.image… File:boot.image is not a valid boot image Boot Image Update Failed: 11 Telnet+> ( SITE= <Not Available> )
I’ve tried upgrading to 8.2v2, no luck. Any resolution to this weird issue? Or something I overlooked?
I am having the same problem when I try and update my network remotely. However, when I upgrade SM’s before they go into the field locally everything works fine. Here’s what CNUT 2.20.r1 tells me:
09/04/07 09:22:25 INFO CANOPY736_DES.pkg2 loaded.
09/04/07 09:22:25 INFO Starting Update Process …
09/04/07 09:22:25 INFO Using Active FTP for File Transfer
09/04/07 09:22:25 INFO Queue NE:192.168.22.62 for updating
09/04/07 09:22:26 INFO Host: 192.168.22.62;ESN: 0A003E212471;Message: Checking Network Element Status ( SITE= DeWinton )
09/04/07 09:22:26 INFO Host: 192.168.22.62;ESN: 0A003E212471;Message: Current = CANOPY 7.2.9 Jul 23 2005 01:49:03, CANOPYBOOT 3.0, 070605 ( SITE= DeWinton )
09/04/07 09:22:26 INFO Host: 192.168.22.62;ESN: 0A003E212471;Message: Using Package C:'Documents and Settings’Brett Hugh’My Documents’Docs - FatBanana’Equipment’Canopy’temp’CANOPY736_DES.pkg2 ( SITE= DeWinton )
09/04/07 09:22:35 INFO Host: 192.168.22.62;ESN: 0A003E212471;Message: Transferring Files ( SITE= DeWinton )
09/04/07 09:23:53 INFO Host: 192.168.22.62;ESN: 0A003E212471;Message: Programming ( SITE= DeWinton )
09/04/07 09:23:59 WARN Host: 192.168.22.62;ESN: 0A003E212471;Message: Cannot upgrade: burnfile Failed Output from Telnet session: burnfile Burn Boot from file: APboot.bin Validating Boot File… fread() of BootHdr failed File:APboot.bin is not a valid image file Telnet+> ( SITE= DeWinton )
09/04/07 09:23:59 INFO Node: 192.168.22.62 Update Completed.
09/04/07 09:23:59 INFO Update process has completed
Any ideas as to why this is happening is greatly appreciated…
Cheers,
Brett
My original problem lies in trying to upgrade 7.2.9 radios to 7.3.6 or to 8.1.4. However, I just discovered that i can upgrade version 8.1.4 to 8.1.5 remotely. Any ideas why this would be? Do I need CNUT 2.0 instead of 2.2?
B.
i found that using passive FTP resolved my issue. (Update->Configure->Use Passive FTP for Transferring files…)