IOS Upgrades in CiscoWorks failing

[barkerc123c]

We have just under 500 switches in production (various models but for this discussion we'll stick with 3750's). All are currently running tar IOS (web based). We want to upgrade the IOS from c3750-ipbasek9-tar.122-55.SE1.tar to.122-55.SE5 but some of our switches do not have enough flash to upgrade successfully.  We use CiscoWorks to distribute our software upgrades. I know you can lower the flash requirements on the IOS in CiscoWorks, which I have done (changed from 16Mb down to 12Mb) and the upgrade still fails.

1) How far can I lower the flash installation requirements in Ciscoworks and what are the ramifications?

2) If we decide to change from the tar IOS version to the bin IOS version because we don't even use the web based features anyway, is there an easy way to do this?  (CiscoWorks will not upgrade an image from tar to bin)

[Reza Sharifi]

IOS 12.2(55)SE5.bin is 11.5 MB and .tar is 12.1 MB.   If your flash is 16 MB, you should not have any problem loading it to your switches. You should not try to lower the flash requirement.  As you have already found out, it does not work.

HTH

[barkerc123c]

Although it SHOULD load, it DOESN'T on a 3750-24ps.  What about question #2?

2) If we decide to change from the tar IOS version to the bin IOS version because we don't even use the web based features anyway, is there an easy way to do this? (CiscoWorks will not upgrade an image from tar to bin)

[Reza Sharifi]

Are these switches stacked?  If yes, you should use the .tar file to push the image, if they are not than .bin.

Not very familar with CiscoWorks, but you are saying, with CiscoWorks, you can only upgrade from .bin to bin and tar to tar, but not tar to .bin?

[barkerc123c]

This test was done on a stack but we have both stacked and individual switches.

As far as CiscoWorks, yes, I am saying I cannot get CiscoWorks to push a bin file to a switch that currently is running a tar file.