In the next entry we will describe the process of updating a CISCO switch from the Small Business series to the latest version currently available: version 1.4.86 (August 2017 version)
Whenever an update is made to the firmware of a computer, it is advisable to have a USB-Serial converter ready (almost no equipment has a native serial port) and a console cable. In the case of these SF300 and in general for the Small Business series, the cable is different from, for example, a higher-end Catalyst, it looks like this:
Well, once we have a way of rescue in case something goes wrong, download the signature from the Cisco website or here I leave a link as an alternative:
These files have to be put in a TFTP server (it can also be FTP) to load them to the equipment, we mount one in the machine with TFTPd32:
We install it and we run the server in an ip (in my case 10.183.72.64 and the switch has the 10.183.72.65), remember that if we do the update with the switch directly connected to the PC from which we launch the server the equipment should be in the same range of ip, it does not matter mask or gateway.
We have everything we need, we are going to start the update process: The first thing is to connect to the team by SSH and check which version we are in
# show ver
If we try the update directly by loading the new image, it will give an error; you have to update the boot first. We copy it from the TFTP
# copy tftp://10.183.72.64/sx300_boot-13506.rfb boot
Restart to take the new boot:
As we can see, it has updated the boot, let’s see now what images it has loaded:
# show bootvar
As we can see in the previous screenshot, it only has one image loaded and the 1 is active. Now we load the new image in the secondary one, the one not active:
# copy tftp://10.183.72.64/sx300_fw-1486.ros image
We wait for it to load it and we see that it has effectively loaded it as a secondary one, if now we restart the computer it would load again the 1 because it is the active one, we are going to change it.
We change the bootvar so that it starts with the secondary one and we do the reload.
# boot system image-2
We check that it changes the * to the secondary.
We see that it has already started with the new version.