Just to clarify this thread.
The limitation in question is regarding the web interface file upload which has a limitation of 1GB, this has later been increased to 2GB. It only affects devices that tries to upload a large file via the web interface, this means that you will not get to the step where the upgrade has actually started if you hit this issue - since then the package is already loaded on to the system.
In your case I would check that you loaded the correct platform package to the device as this is the kind of error you would see if you loaded, for example, s53200 software on a s53300 platform. - it could also be that the package is corrupted in some way or related to a bug in the older software version - but not related to the documented limitation about file size since this exists only in web.
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 or are able to spin up a web server 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.
Type
xStatus //Upgrade
To track the software upgrade status.. the device will upgrade as soon as the package is downloaded without the 60 seconds countdown. This method should effectively bypass the need for a step upgrade.
If you have multiple devices that needs to upgrade like this, you have tools like CE-Deploy or you can script your own distribution of the upgrade command to multiple devices at once. This is the method I recommend to save time.
You can try it by sending this using, for example, postman
HTTP POST: /putxml
HEADERS: Authorization: Basic <b64 encoded credentials>, Content-Type: text/xml
DATA:
<Command>
<SystemUnit>
<SoftwareUpgrade>
<URL>http://yourserver/upgradefile.cop.sgn</URL>
</SoftwareUpgrade>
</SystemUnit>
</Command>
TAC can in some cases provide deferred software packages to aid in resolution of the case or help you upgrading directly using the support shell.
Cisco is deferring software packages according to policy, and we will not re-release old software that has known vulnerabilities.
It is indeed a very unfortunate bug that was discovered too late, but there are good workarounds that skips the "step" upgrade.
