upgrading SG500-52P

[it-marmalade]

Hello,

I'm running a stack of four SG500-52P switches:

Firmware Version (Active Image): 1.4.0.88

Boot Version: 1.4.0.02

and decided to upgrade them as the versions are now about 2 years old.
I only utilize IPV4 ATM.

The only issue I've had with the stack is horrible performance (50-70% packet loss in selected segments of the network).
It used to happen only once per month (around the 10th) and always around lunch time.
The problem was going away without any intervention after about 30-60 minutes.
This only happened when unit 1 was the master.
Since switching the master to unit 2 over a year ago network operation has been seamless.
So I'm hoping for this issue to go away with firmware upgrades and be able to run unit 1 as the master again.
If not it would drive me to a conclusion unit 1 is faulty.

My questions regarding the upgrade:

https://software.cisco.com/download/type.html?mdfid=284099563&catid=null

1. I'm assuming only stack master needs to be updated and rebooted and slaves will follow automatically, right?

2. Do I need to go through all the upgrade steps:

1.4.0.88 -> 1.4.1.03 -> 1.4.2.04 -> 1.4.5.02
or can they / any of them be skipped?

3. What happened to the boot image download?
Why is it not available?
I'm sure there has been something newer released over the past two years.
Even if it wasn't there should still be version 1.4.0.02 available for download.

4. What do I do with MIBs_Sx500_v1.4.1.03.zip?
I'm assuming it's related to SNMP.
Neither "show version" or "show snmp" is telling me what version I'm currently running.
Can I upgrade it from web GUI or only from CLI?

Please advise.

Thanks
Adam

[Michal Bruncko · Accepted solution]

> 1. I'm assuming only stack master needs to be updated and rebooted and slaves will follow automatically, right?

that's correct (see more details in SG500 Admin Guide, Page 38, "Upgrade/Backup Firmware/Language").

There are two different ways to update images across the stack:
• Image can be updated prior to connecting a unit to the stack. This is the
recommended method.
• Upgrade device or stack. If the stack is updated, the slave units are
automatically updated. This is done as follows:
- Copy image from TFTP/SCP server to master, using the Upgrade/Backup Firmware/Language page.
- Change the active image, using the Active Image page.
- Reboot, using the Reboot page

> Do I need to go through all the upgrade steps:

this can be always revealed from firmware release notes (link for latest release notes). Based on that contents you can upgrade directly to 1.4.5.02

> What happened to the boot image download? Why is it not available?

boot image doesn't need to have same version like switch firmware itself. New boot image get updated/released by Cisco only in case it is necessary to do it (fixing bug, implementing some improvement). Latest boot image version is 1.3.5.06 (at least on SG300 units). Anyway you can always check firmware release notes if the boot code needs to be updated prior to switch image upgrade.

> What do I do with MIBs_Sx500_v1.4.1.03.zip? 

this is only necessary in case you using SNMP monitoring incl. SNMP trap monitoring. This is something you have to use/update on your monitoring system/application. But this is basically not needed for usual switch working. SNMP MIB package version usually equals to switch firmware version as there could be changes in SNMP MIB between firmware versions.

[it-marmalade]

Thanks for a prompt reply Michal.

Let me follow up:

> Latest boot image version is 1.3.5.06

Mine is currently reporting 1.4.0.02 and last time I updated the switches was almost 2 years ago.
I'm still struggling to find boot images history and download page.
Can you provide me with a link please?

> this is only necessary in case you using SNMP monitoring

We do monitor the switches with PRTG and SNMPv3 (no traps) so MIBs update could actually be applicable.

[Michal Bruncko · Accepted solution]

> Can you provide me with a link please?

boot image is usually shipped as a part of switch firmware file. You can find that the package is ZIP-ped instead of provided just as single image file (*.ROS extension). For example latest boot image code for your switch model is shipped as a part with "Sx500 Firmware Version 1.4.1.03" - you can see that filename is "Sx500_FW_Boot_1.4.1.03.zip" - can be downloaded here. And right, for Cisco 500 Series switches the latest boot code is 1.4.0.02. No change/new version since that release.

> We do monitor the switches with PRTG and SNMPv3 (no traps) so MIBs update could actually be applicable.

if you updated your monitoring system with original Cisco MIB package, then it would be fine to do it for this new firmware as well. Othervise it could not be necessary.