First upgrade to R11.0.4.2

[Westi]

Forcibly upgraded to this release and the uploads failed (like to many other times.

Then went into the embedded file management and uploaded the system files and AGAIN nasty errors due to missing files.

When do they get this finally right in more than 1 release and screw it up in the next 2.

I hope this is not a local problem but after acknowledging all the errors it uploads 3790 files which means it works but is missing files (some for 9600 sets and all of the J189 files)

Anyone have similar stuff happening or are you all not upgrading to this release yet?

Joe
FHandw, ACSS (SME)

Remembering intrigrant 2019

 

[lleeNC]

What is your method of upgrading? Also from what version are you upgrading from? Give us more details!

I just did a upgrade as a test on our demo Lab V2 and it went through without any issues from 11.0 SP2 to 11.0 FP4 SP2.

 

[biv343]

I upgraded our in house system yesterday from 11.0.4 SP1 to SP2 and no issues with the upgrade or any file transfers, but it wasn't that big of a jump for this system.

 

[Westi]

I upgraded from 8.1 to 9.0.12 then to 11

When uploading the files it came up with a lot of files missing, just like the 11.0.4.0 did

I upgraded my virtual server without any issues though but that is done via .iso upload so no issues there

Joe
FHandw, ACSS (SME)

Remembering intrigrant 2019

 

[CalgaryJeff]

I upgraded a test system from 11.0.4.1 to 11.0.4.2 and it had no issues. It uploaded over 4000 files.

http://www.atcomsystems.ca

ACSS,AIPS

 

[Westi]

In that case I hope it was a local issue.
Thanks for the information

I am sure that Avaya will bring out a PSN in a couple of months if this is an issue, LOL.

Joe
FHandw, ACSS (SME)

Remembering intrigrant 2019

 

[bignose21]

did a SE 11.0.0.0 (2 servers new install) with 3 IP500v2 Expansions to 11.0.4.2, just sftp the ISO file to /tmp on the primary then used the Web Manager to Transfer ISO from primary server path, upgraded Primary then once done did the rest at the same time, all went through without a hiccup.

 

[Travis Harper]

I've always done this through web manager. Upload ISO, and the system detected an update is available, simply hit the dropdown to click upgrade.

Never had an issue doing it this way... except the first time I ever did it, I used Safari web browser, and the upload was not supported. Now I use Firefox when I need to upload the ISO using Webmanager.

Travis

 

[bahmonkeys]

If you are missing phone bin files. You can upload them manually

 

[Albus2]

Interessting, many replys did not match to the original question...

Westi,
last week I did a remote update like this (to keep the down time minimal)

- Used Manager to update 500v2
- uncheck 'backup'
- uncheck 'upload files'
- uncheck 'restart phones'

After upgrade finished, I went into embedded file management and used 'upload system files'.
Among the first missing files errors was something about 9670 (never supported in IPO) followed by J189 (not releasen now).

But if using Manager and directly let it upload the files, or if using server edition with ISO upload, there is no such problem.

 

[bahmonkeys]

You are uploading them manually which i answered above so yes i did match the original question.

Also if the Admin suite installed has missing .bin files in the program files location you will get a ton of errors. A lot of these .bin files are not needed anyway.

You can also do a restore of system files as this will restore files that were backed up, so yes do check the "backup" when upgrading just in case.

 

[bicho86]

hi, guys. if you upload the ISO file first at the prymary server to /tmp, how do you know if the upgrade process is running?

thanks for your help

 

[Westi]

After uploading it you start it manually and there will be a progress bar

Uploading it usually via web interface.


Better to start your own thread especially after 5 months time
Also this upgrade was a regular IP500V2 not SE

Joe
FHandw, ACSS (SME)

Remembering intrigrant 2019