05-28-2021 08:29 AM
Hi folks,
I have a RoomKit and a RoomKitPro with a fairly outdated software (9.5.1). I'd like to update to the newest 9.15 but both RoomKits decline the file saying "file too large". Okay, checking the release notes I need to update to a version <9.10 first (e. g. 9.9.1) but unfortunately I can't download these anymore for Cisco saying "Dereferred".
Lowest version to download is 9.12.4 so I got this and tried it on the RoomKits. I was able to upload this file and to start the installation but after a few moments it aborted saying "Installation failed!".
Is there any way to get this to work or does anyone know where I can get an old version to upgrade first?
Thanks a lot
Stephan
Solved! Go to Solution.
05-28-2021 08:42 AM
You can try this that I found in some other post a few weeks ago.
There is a good workaround to this that can be used and many admins controls or knows how to set up a HTTP server (which can also be done on your workstation).
1. If you have a web server (Apache, Nginx, IIS or similar in your network that has connectivity to the device), you can put the software on that web server and push the command:
Your web server (maybe hosting other files as well, this can be used as a resource for upgrading)
xCommand SystemUnit SoftwareUpgrade URL: http(s)://yourcustomhttpserver/filename.k9.cop.sgn
If you have a CUCM or TMS, these should be used to manage upgrades regardless, but if you are not you
can use them as a hosting resource for the files:
xCommand SystemUnit SoftwareUpgrade URL: http(s)://yourtmsserver/public/pathtofile/filename.k9.cop.sgn
CUCM can also be used as a http server resource, but if you have a CUCM, you should be using it to manage
the software upgrades anyway:
xCommand SystemUnut SoftwareUpgrade URL: http(s)://yourcucmserver:6970/s53300ce9_15_0_11-aec227943ed.loads
The loads file contains pointers to the whereabouts of the peripheral software. The device will download the software
based on what it has connected.
Or (but careful):
xCommand SystemUnut SoftwareUpgrade URL: http(s)://yourcucmserver:6790/53300ce9_15_0_11-aec227943ed.pkg
Careful with upgrading using PKG files as this will cause camera upgrades and peripheral upgrades to fail.
This can be fixed by upgrading again using the cop file. For older devices, the peripheral software is included
in the pkg.
Please note that I have not tried this myself, I just saved it for future use.
05-28-2021 09:25 AM - edited 05-30-2021 01:41 AM
Haha, this is ridiculous.
I found this thread stating you have to append ".pkg" to the update-file within the Device Defaults.
https://community.cisco.com/t5/other-collaboration-subjects/upgrade-of-sx20-from-ce8-x-to-ce9-x-via-cucm/td-p/4144499
Having nothing to lose I tried this and now the update went smooth and our RoomKits are up-to-date.
Thanks for the help and have a nice day...
Note: Remove the „.pkg“-extension after successful upgrade. Otherwise you will get lots of errors in the logs of the RoomKits.
05-28-2021 08:42 AM
You can try this that I found in some other post a few weeks ago.
There is a good workaround to this that can be used and many admins controls or knows how to set up a HTTP server (which can also be done on your workstation).
1. If you have a web server (Apache, Nginx, IIS or similar in your network that has connectivity to the device), you can put the software on that web server and push the command:
Your web server (maybe hosting other files as well, this can be used as a resource for upgrading)
xCommand SystemUnit SoftwareUpgrade URL: http(s)://yourcustomhttpserver/filename.k9.cop.sgn
If you have a CUCM or TMS, these should be used to manage upgrades regardless, but if you are not you
can use them as a hosting resource for the files:
xCommand SystemUnit SoftwareUpgrade URL: http(s)://yourtmsserver/public/pathtofile/filename.k9.cop.sgn
CUCM can also be used as a http server resource, but if you have a CUCM, you should be using it to manage
the software upgrades anyway:
xCommand SystemUnut SoftwareUpgrade URL: http(s)://yourcucmserver:6970/s53300ce9_15_0_11-aec227943ed.loads
The loads file contains pointers to the whereabouts of the peripheral software. The device will download the software
based on what it has connected.
Or (but careful):
xCommand SystemUnut SoftwareUpgrade URL: http(s)://yourcucmserver:6790/53300ce9_15_0_11-aec227943ed.pkg
Careful with upgrading using PKG files as this will cause camera upgrades and peripheral upgrades to fail.
This can be fixed by upgrading again using the cop file. For older devices, the peripheral software is included
in the pkg.
Please note that I have not tried this myself, I just saved it for future use.
05-28-2021 08:46 AM - edited 05-28-2021 09:04 AM
Thanks for the hint.
Speaking of CUCM, we do have a CUCM in use and both RoomKits are registered to it. Is it possible to upgrade via OSAdministration like we do with all the other phones?
05-28-2021 09:09 AM
Upgrade:
I managed to install the cop-file to the cluster and provide it to the RoomKit. But when I check the logs it says:
2021-05-28T18:04:30.201+02:00 SEP00778D9008B6 appl[1512]: SoftwareUpgrade[0]: [4113878816] SWUH::operator()() {s1,p0,afalse,h170,dtrue,pMtrue,tT0,iLfalse,iSfalse,iDfalse} httpRetryTimer_ httpRetryTimer fired 2021-05-28T18:04:30.201+02:00 SEP00778D9008B6 appl[1512]: SoftwareUpgrade[0]: [4097102512] SWUH::_start() {s1,p0,afalse,h170,dtrue,pMtrue,tT0,iLfalse,iSfalse,iDfalse} autoComplete_=false 2021-05-28T18:04:30.201+02:00 SEP00778D9008B6 appl[1512]: SoftwareUpgrade I: Starting normal download 2021-05-28T18:04:30.201+02:00 SEP00778D9008B6 appl[1512]: SoftwareUpgrade I: Starting download from http://10.48.5.11:6970/s53300ce9_15_3_17 to /upgrade/pkg.tmp 2021-05-28T18:04:30.202+02:00 SEP00778D9008B6 appl[1512]: SoftwareUpgrade I: Download #2 starting: http://10.48.5.11:6970/s53300ce9_15_3_17 -> /upgrade/pkg.tmp 2021-05-28T18:04:30.202+02:00 SEP00778D9008B6 appl[1512]: SoftwareUpgrade[0]: Download #2 progress: 0/0 bytes from 2021-05-28T18:04:30.203+02:00 SEP00778D9008B6 appl[1512]: SoftwareUpgrade[0]: [4097102512] XAPI::downloading() string("http://10.48.5.11:6970/s53300ce9_15_3_17"), string("Retrying"), 2021-05-28T18:04:30.203+02:00 SEP00778D9008B6 appl[1512]: SoftwareUpgrade[0]: [4097102512] SWUH::_start() {s1,p5,afalse,h170,dtrue,pMtrue,tT0,iLfalse,iSfalse,iDfalse} <- startDownload 2021-05-28T18:04:30.203+02:00 SEP00778D9008B6 appl[1512]: SoftwareUpgrade[0]: [4097102512] SWUH::operator()() {s1,p5,afalse,h170,dtrue,pMtrue,tT0,iLfalse,iSfalse,iDfalse} httpRetryTimer_ <- 2021-05-28T18:04:30.211+02:00 SEP00778D9008B6 appl[1512]: SoftwareUpgrade I: Download #2 complete (HTTP 404) 2021-05-28T18:04:30.211+02:00 SEP00778D9008B6 appl[1512]: SoftwareUpgrade[0]: [4097102512] SWUH::handleDownloadDone() {s1,p5,afalse,h170,dtrue,pMtrue,tT0,iLfalse,iSfalse,iDfalse} result(id=2, status=3, http_code=404, retry_after=60, error_msg='HTTP 404') 2021-05-28T18:04:30.211+02:00 SEP00778D9008B6 appl[1512]: SoftwareUpgrade I: Download failed 2021-05-28T18:04:30.211+02:00 SEP00778D9008B6 appl[1512]: SoftwareUpgrade I: Failed on all servers [c:404] 'http://10.48.5.11:6970/s53300ce9_15_3_17': HTTP 404 2021-05-28T18:04:30.211+02:00 SEP00778D9008B6 appl[1512]: SoftwareUpgrade I: Retrying in 14 minutes and 13 seconds. 2021-05-28T18:04:30.211+02:00 SEP00778D9008B6 appl[1512]: SoftwareUpgrade[0]: [4097102512] XAPI::setStatus() int64(3), int64(0), string("Download failed on all servers: HTTP 404. Retrying in 14 minutes and 13 seconds."), 2021-05-28T18:04:30.211+02:00 SEP00778D9008B6 appl[1512]: SoftwareUpgrade ERROR: Download failed (code 404): HTTP 404. Will retry download later 2021-05-28T18:04:30.211+02:00 SEP00778D9008B6 appl[1512]: SoftwareUpgrade[0]: [4097102512] SWUH::handleDownloadDone() {s1,p0,afalse,h853,dtrue,pMtrue,tT0,iLfalse,iSfalse,iDfalse} <-
So I assume the upgrade failed again because of a failed download? What can I do?
05-28-2021 09:25 AM - edited 05-30-2021 01:41 AM
Haha, this is ridiculous.
I found this thread stating you have to append ".pkg" to the update-file within the Device Defaults.
https://community.cisco.com/t5/other-collaboration-subjects/upgrade-of-sx20-from-ce8-x-to-ce9-x-via-cucm/td-p/4144499
Having nothing to lose I tried this and now the update went smooth and our RoomKits are up-to-date.
Thanks for the help and have a nice day...
Note: Remove the „.pkg“-extension after successful upgrade. Otherwise you will get lots of errors in the logs of the RoomKits.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide