10-25-2017 12:20 PM - edited 02-21-2020 06:34 AM
I am trying to upgrade a C3560X-48T-L to the code - c3560e-universalk9-mz.150-2.SE10a.bin
from current code - c3560e-universalk9-mz.122-55.SE5.bin
What could be the possible issues that I can see during or after the upgrade. Just trying to be cautious, I would like to know the most common issues that can occur during the IOS software upgrades! Thanks everyone for helping
Solved! Go to Solution.
10-25-2017 12:37 PM
@s k wrote:
What could be the possible issues that I can see during or after the upgrade.
10-25-2017 12:41 PM
SK,
The most common upgrade issue I've seen is an image being corrupted during the transfer. You can mitigate this by verifying the file checksum after it is uploaded to the device. When you mouse-over the file before downloading it from the Cisco site, it should show you the checksums (I usually use the MD5 one) which you can then copy for later comparison. Something like this would compute the checksum of the copied file:
Switch#verify /md5 flash:c3560e-universalk9-mz.150-2.SE10a.bin
If the checksums match, then you can be highly certain the file integrity was maintained and it will boot properly.
As a precaution, it's best to leave the previous file on the flash until you've verified the new one is working as expected. However, this is not always an option due to storage limitations. As a last resort, you can always boot from TFTP, so make sure to keep all your files on a TFTP server just in case.
10-25-2017 12:37 PM
@s k wrote:
What could be the possible issues that I can see during or after the upgrade.
10-25-2017 12:46 PM
10-25-2017 12:41 PM
SK,
The most common upgrade issue I've seen is an image being corrupted during the transfer. You can mitigate this by verifying the file checksum after it is uploaded to the device. When you mouse-over the file before downloading it from the Cisco site, it should show you the checksums (I usually use the MD5 one) which you can then copy for later comparison. Something like this would compute the checksum of the copied file:
Switch#verify /md5 flash:c3560e-universalk9-mz.150-2.SE10a.bin
If the checksums match, then you can be highly certain the file integrity was maintained and it will boot properly.
As a precaution, it's best to leave the previous file on the flash until you've verified the new one is working as expected. However, this is not always an option due to storage limitations. As a last resort, you can always boot from TFTP, so make sure to keep all your files on a TFTP server just in case.
10-25-2017 12:44 PM
10-25-2017 12:46 PM
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