Tried to update CANOPY 7.2.9 to 8.1.5
Get this error
02/03/07 16:00:40 INFO Refresh Entire Network process has completed.
02/03/07 16:00:57 INFO CANOPY8151_DES.pkg2 loaded.
02/03/07 16:00:57 INFO Starting Update Process …
02/03/07 16:00:57 INFO Using Active FTP for File Transfer
02/03/07 16:00:57 INFO Queue NE:AP:[10.0.0.20].LUID:[002] for updating
02/03/07 16:00:57 WARN SNMPIOException:, error code: -1, varbind index: -1
request varbinds: null
response varbinds: null
other message:sendSync failed.
02/03/07 16:00:58 INFO Host: AP:[10.0.0.20].LUID:[002];ESN: 0A003E2398DB;Message: Checking Network Element Status ( SITE= 400 Advantage SM )
02/03/07 16:00:58 WARN Host: AP:[10.0.0.20].LUID:[002];ESN: 0A003E2398DB;Message: Unable to communicate with Network Element (Possibly Connect/Login Failure), status/version unknown ( SITE= 400 Advantage SM )
02/03/07 16:00:58 INFO Node: AP:[10.0.0.20].LUID:[002] Update Completed.
02/03/07 16:00:58 INFO Update process has completed
PWH wrote: Tried to update CANOPY 7.2.9 to 8.1.5
Get this error
02/03/07 16:00:40 INFO Refresh Entire Network process has completed.
02/03/07 16:00:57 INFO CANOPY8151_DES.pkg2 loaded.
02/03/07 16:00:57 INFO Starting Update Process ..
02/03/07 16:00:57 INFO Using Active FTP for File Transfer
02/03/07 16:00:57 INFO Queue NE:AP:[10.0.0.20].LUID:[002] for updating
02/03/07 16:00:57 WARN SNMPIOException:, error code: -1,
I have no idea what the error means but I couldn't help but notice -
8.1.5 ! Just looked and it's on the DL page now !
Off to read the tech notes ! Hope they fixed a lot !
You need to upgrade to 8.1.4 before upgradeing to 8.1.5.1 and have to be set to HARDWARE Shecduleing before attempting the upgrade.
You also have to be using CNUT 2.20. But remember to backup your Network file before upgradeing to CNUT 2.20.
From what i read in the notes, there is very little fixed in this release.
They do not appear to have sorted out the NAT issues. 50% of our clients are behind NAT which basically means that we cannot upgrade till the NAT issues that plague release 8 are resolved.
vanilla wrote: From what i read in the notes, there is very little fixed in this release.
They do not appear to have sorted out the NAT issues. 50% of our clients are behind NAT which basically means that we cannot upgrade till the NAT issues that plague release 8 are resolved.
Do they acknowledge the problem exists ?
When I talked to tech support and mentioned I was concerned about upgrading to 8.1.4 and they said v8 did not have any problems with NAT. When I mentioned people on various forums reporting NAT issues they acted like it was the first they had heard of it.
I got the impression that they think it is a non-issue that a small number of people have reported and others have blown it out of proportion.
They always do that…There has been numerous time we have called with problems and they say it work fine in the lab, then i see a Field Alert about it a few days later…