cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
10935
Views
100
Helpful
27
Replies

SG250 - Latest Firmware 2.5.7.85 will not load after upgrade and reboot.

Gordieee
Level 1
Level 1

I'm trying to install and test the latest firmware for my SG250 set of switches. The first switch I've tried is a SG250-10. It allows me to load the new FW file (image_tesla_hybrid_2.5.7.85_release_cisco_signed.bin) and on the swap image page it shows version 2.5.7.85 will be loaded after reboot. However after reboot, I am still on my current firmware version, 2.5.5.47. No errors or warnings are presented during the upgrade process and the switch seems to run fine the older version of the firmware without any changes. 

 

I also tired an USB upload of the firmware but get a checksum error just before the file finishes loading from the usb stick. I've checked the MD5 checksum and it matches the Cisco website.

 

As far as the switch logs go, I see a  %COPY-W-TRAP: The copy operation has failed for the USB attempts, but no entries at all for the http transfers, other then the normal %INIT-I-Startup: Warm Startup on reboot.

 

Anyone else having the same issue? I'm wondering if there is a file issue on the cisco site again? I will wait before attempting to upgrade any of my production sites and larger switches.

 

 

1 Accepted Solution

Accepted Solutions

Ok that is good news, I tested now also with the new loaded image and indeed no problems found, works perfect now.

Be aware the upload can take a while, and also the reload.

Greetings Christian.

View solution in original post

27 Replies 27

kgardas
Level 1
Level 1

I have exactly the same issue. I'm testing here with 250-08 HP and no matter what I tried, always switch reboots to previous firmware w/o any note about a new one. In fact the image which I upload is automatically deleted after reboot. I'm always using just http for file upload. I've also verified sha512 on the file and it's downloaded from cisco correctly.

 

So Cisco, what to do to upgrade SG250 correctly?

lglg
Level 1
Level 1

Same issue and other people on other forums have reported the issue with 200 series switches. Any advice is appreciated on how to resolve this. Or if it's a bad file, we will wait for re-upload.

@lglg 

@kgardas 

@Gordieee 

 

You may need to contact our technical support team and log a case for this issue. To me, It might be a bug but they would first investigate case by case. Unfortunately, we could not help you that much here in the forum with such an issue. Contact details are as follows:

 

https://www.cisco.com/c/en/us/support/web/tsd-cisco-small-business-support-center-contacts.html

 

Regards,

Martin

 

 @lglg 

@kgardas 

@Gordieee 

 

 - One might for instance, copy the current configuration to an external device and or repository, factory reset the SG and try the upgrade again on a maiden system.

 M.



-- Each morning when I wake up and look into the mirror I always say ' Why am I so brilliant ? '
    When the mirror will then always repond to me with ' The only thing that exceeds your brilliance is your beauty! '

Hi @marce1000 ,

 

I've already logged support case with cisco about this issue, so I guess to not derail this I'd wait and see what support engineer recommends. Anyway, thanks for the advice!
Karel

 

               - Good work, keep us informed !

 M.



-- Each morning when I wake up and look into the mirror I always say ' Why am I so brilliant ? '
    When the mirror will then always repond to me with ' The only thing that exceeds your brilliance is your beauty! '

Scott Frank
Level 1
Level 1

I've factory reset my SG250-10P and then upgraded and it still reverts to previous firmware version (2.5.5.47 on mine).  I then tried resetting with the reset button with the same results.  Have not tried CLI upgrade.

 

 - Try again , but before the upgrade configure a syslog server , then check the received logs during or after the upgrade process, watch for errors or problems being logged , if any.

 M.



-- Each morning when I wake up and look into the mirror I always say ' Why am I so brilliant ? '
    When the mirror will then always repond to me with ' The only thing that exceeds your brilliance is your beauty! '

I found a spare (not in use) SG250-08 switch to play around with on my home network. I did a factory reset and configured the syslog server and again there is no indication of any issues. Although the logging for the SG250s does seem to be a little lacking, as there is no entry for even a manually initiated reboot? I get an entry for the FW file being successfully loaded, and then just the normal startup log entries after I reboot. No indication of a new FW file or what config will be used during startup. 

 

2147483525 2021-Mar-10 15:33:47 Informational %INIT-I-Startup: Warm Startup
2147483526 2021-Mar-10 15:33:45 Informational %PNPAGENT-I-BYEREQ: Bye PnP Request
2147483527 2021-Mar-10 15:33:43 Informational %PNPAGENT-I-RESPSUCCESS: PnP Response Success
2147483528 2021-Mar-10 15:33:43 Informational %PNPAGENT-I-BACKOFFCALLBACKAFTER: Backoff PnP Request with <callbackAfter> has received: 24 Hours 0 Minutes 0 Seconds
2147483529 2021-Mar-10 15:33:42 Informational %PNPAGENT-I-PNPSRVRDETECT: PnP Server devicehelper.cisco.com was detected
2147483530 2021-Mar-10 15:33:35 Informational %SSL-I-CACERTINSTLD: CA Certificate type dynamic owner <pnp> name <cloud_redirect_ca_trustpool_14> is installed
2147483531 2021-Mar-10 15:33:35 Informational %SSL-I-CACERTINSTLD: CA Certificate type dynamic owner <pnp> name <cloud_redirect_ca_trustpool_13> is installed
2147483532 2021-Mar-10 15:33:35 Informational %SSL-I-CACERTINSTLD: CA Certificate type dynamic owner <pnp> name <cloud_redirect_ca_trustpool_12> is installed
2147483533 2021-Mar-10 15:33:34 Informational %SSL-I-CACERTINSTLD: CA Certificate type dynamic owner <pnp> name <cloud_redirect_ca_trustpool_11> is installed
2147483534 2021-Mar-10 15:33:34 Informational %SSL-I-CACERTINSTLD: CA Certificate type dynamic owner <pnp> name <cloud_redirect_ca_trustpool_10> is installed
2147483535 2021-Mar-10 15:33:34 Informational %SSL-I-CACERTINSTLD: CA Certificate type dynamic owner <pnp> name <cloud_redirect_ca_trustpool_9> is installed
2147483536 2021-Mar-10 15:33:34 Informational %SSL-I-CACERTINSTLD: CA Certificate type dynamic owner <pnp> name <cloud_redirect_ca_trustpool_8> is installed
2147483537 2021-Mar-10 15:33:34 Informational %SSL-I-CACERTINSTLD: CA Certificate type dynamic owner <pnp> name <cloud_redirect_ca_trustpool_7> is installed
2147483538 2021-Mar-10 15:33:33 Informational %SSL-I-CACERTINSTLD: CA Certificate type dynamic owner <pnp> name <cloud_redirect_ca_trustpool_6> is installed
2147483539 2021-Mar-10 15:33:33 Informational %SSL-I-CACERTINSTLD: CA Certificate type dynamic owner <pnp> name <cloud_redirect_ca_trustpool_5> is installed
2147483540 2021-Mar-10 15:33:33 Informational %SSL-I-CACERTINSTLD: CA Certificate type dynamic owner <pnp> name <cloud_redirect_ca_trustpool_4> is installed
2147483541 2021-Mar-10 15:33:33 Informational %SSL-I-CACERTINSTLD: CA Certificate type dynamic owner <pnp> name <cloud_redirect_ca_trustpool_3> is installed
2147483542 2021-Mar-10 15:33:33 Informational %SSL-I-CACERTINSTLD: CA Certificate type dynamic owner <pnp> name <cloud_redirect_ca_trustpool_2> is installed
2147483543 2021-Mar-10 15:33:33 Informational %SSL-I-CACERTINSTLD: CA Certificate type dynamic owner <pnp> name <cloud_redirect_ca_trustpool_1> is installed
2147483544 2021-Mar-10 15:33:32 Informational %SSL-I-CACERTINSTLD: CA Certificate type dynamic owner <pnp> name <cloud_redirect_ca_trustpool_0> is installed
2147483545 2021-Mar-10 15:32:37 Debug %SNTP-D-NTPBADVER: NTP server version not compatible
2147483546 2021-Mar-10 15:32:37 Debug %SNTP-D-NTPBADVER: NTP server version not compatible
2147483547 2021-Mar-10 15:32:30 Notice %SYSLOG-N-LOGGING: Logging started.
2147483548 2021-Mar-10 15:32:00 Informational %AAA-I-CONNECT: New http connection for user Admin, source 192.168.1.161 destination 192.168.1.54 ACCEPTED
2147483549 2020-May-06 05:28:00 Debug %SNTP-D-NTPBADVER: NTP server version not compatible
2147483550 2020-May-06 05:28:00 Debug %SNTP-D-NTPBADVER: NTP server version not compatible
2147483551 2020-May-06 05:27:54 Informational %BOOTP_DHCP_CL-I-DHCPCONFIGURED: The device has been configured on interface Vlan 1 , IP 192.168.1.54, mask 255.255.255.0, DHCP server 192.168.1.1
2147483552 2020-May-06 05:27:54 Informational %DHCPV6CLIENT-I-ADDR: DHCPv6 Address 2607:xxxx:xxxx:xxxx::xxxx received on vlan 1 from DHCP Server fe80::be4a:56ff:fe02:1a53 was declined
2147483553 2020-May-06 05:27:54 Warning %IPv6-W-DAD: Duplicated IPv6 address 2607:xxxx:xxxx:xxxx::xxxx detected on interface vlan 1
2147483554 2020-May-06 05:27:54 Informational %DHCPV6CLIENT-I-ADDR: DHCPv6 Address 2607:xxxx:xxxx:xxxx::xxxx received on vlan 1 from DHCP Server fe80::be4a:56ff:fe02:1a53 was added
2147483555 2020-May-06 05:27:52 Warning %BOOTP_DHCP_CL-W-DHCPIPCANDIDATE: The device is waiting for IP address verification on interface Vlan 1 , IP 192.168.1.54, mask 255.255.255.0, DHCP server 192.1 68.1.1
2147483556 2020-May-06 05:27:50 Informational %DHCPV6CLIENT-I-STATELESSDATA: DHCP Stateless information received on vlan 1 from DHCP Server fe80::be4a:56ff:fe02:1a53 was updated
2147483557 2020-May-06 05:27:47 Warning %STP-W-PORTSTATUS: gi1: STP status Forwarding
2147483558 2020-May-06 05:27:46 Informational %LINK-I-Up: Vlan 1
2147483559 2020-May-06 05:27:46 Informational %LINK-I-Up: gi1
2147483560 2020-May-06 05:27:43 Informational %LINK-I-Up: loopback1
2147483561 2020-May-06 05:27:43 Warning %LINK-W-Down: gi8
2147483562 2020-May-06 05:27:43 Warning %LINK-W-Down: gi7
2147483563 2020-May-06 05:27:43 Warning %LINK-W-Down: gi6
2147483564 2020-May-06 05:27:43 Warning %LINK-W-Down: gi5
2147483565 2020-May-06 05:27:43 Warning %LINK-W-Down: gi4
2147483566 2020-May-06 05:27:43 Warning %LINK-W-Down: gi3
2147483567 2020-May-06 05:27:43 Warning %LINK-W-Down: gi2
2147483568 2020-May-06 05:27:43 Warning %LINK-W-Down: gi1
2147483577 2021-Mar-10 15:28:45 Notice %COPY-N-TRAP: The copy operation was completed successfully
2147483578 2021-Mar-10 15:28:45 Debug %COPY-D-TRAP: The copy image operation was completed successfully
2147483579 2021-Mar-10 15:26:31 Informational %COPY-I-FILECPY: Files Copy - source URL HTTP://192.168.1.161/image_tesla_hybrid_2.5.7.85_release_cisco_signed.bin destination URL flash://system/images/image_t esla_hybrid_2.5.7.85_release_cisco_signed.bin
2147483580 2021-Mar-10 15:24:13 Notice %SYSLOG-N-SYSLOGCHANGE: syslog server 192.168.1.102 configuration changed
2147483581 2021-Mar-10 15:23:36 Notice %COPY-N-TRAP: The copy operation was completed successfully
2147483582 2021-Mar-10 15:23:35 Informational %COPY-I-FILECPY: Files Copy - source URL running-config destination URL flash://system/configuration/startup-config
2147483583 2021-Mar-10 15:23:07 Notice %SYSLOG-N-NEWSYSLOGSERVER: configure new syslog server 192.168.1.102
2147483584 2021-Mar-10 15:22:21 Informational %PNPAGENT-I-BYEREQ: Bye PnP Request
2147483585 2021-Mar-10 15:22:20 Informational %PNPAGENT-I-RESPSUCCESS: PnP Response Success
2147483586 2021-Mar-10 15:22:20 Informational %PNPAGENT-I-BACKOFFCALLBACKAFTER: Backoff PnP Request with <callbackAfter> has received: 24 Hours 0 Minutes 0 Seconds
2147483587 2021-Mar-10 15:22:20 Informational %PNPAGENT-I-PNPSRVRDETECT: PnP Server devicehelper.cisco.com was detected
2147483588 2021-Mar-10 15:19:56 Informational %INIT-I-Startup: Cold Startup

 

I've seen others with similar issues on other forums even upgrading from even older FW then 2.5.5.47, so that would rule out a problem with the previous FW not allowing the upgrade.

 

I will continue to wait for Cisco to come back with some update or new file.

 

Update: I tried upgrading with a USB drive but only got checksum errors.  I also tried to do a CLI upgrade and also got checksum errors.  Tried both several times so it wasn't just an interrupted upload.  To be sure the file wasn't corrupt I hashed it and it wasn't corrupted.

Another thing i noticed is that there isn't a reboot popup after the file upload in the web GUI.  Thinking there is supposed to be..?  Also the reboot after I do the firmware upgrade takes longer than normal.  Not by much but does seem longer.

Thought about downgrading but that will probably fail as well.  Really seems like its the "47" firmware that is preventing everything.  Although the new firmware has words in it like hybrid and signed.  What's that about..?

Update:2

I was able to downgrade.  I was surprised thinking that the firmware operations wouldn't work either way but downgrades are possible.  So firmware "47" doesn't seem to be the problem after all.  Has to be something wrong with the "85" firmware.

Just weird that there are no errors and the "85" firmware is no where to be found after rebooting.

I'm curious if anyone can upgrade using this file?

kgardas
Level 1
Level 1

@marce1000thanks for the idea with remote sysloging. Unfortunately even if I set minimum level to debug, I'm still not being able to see anything meaningful and that's while I keep switch configuration and does not reset it to factory state -- which if I would, the switch will loose remote syslog server config info.

 

2021-03-11T14:57:07.132355+01:00 10.0.30.253 %AAA-I-CONNECT: New https connection for user admin, source 10.0.30.5 destination 10.0.30.253 ACCEPTED  
2021-03-11T14:57:20.593125+01:00 10.0.30.253 %COPY-I-FILECPY: Files Copy - source URL running-config destination URL flash://system/configuration/startup-config  
2021-03-11T14:57:22.435269+01:00 10.0.30.253 %COPY-N-TRAP: The copy operation was completed successfully  
2021-03-11T15:02:35.847925+01:00 10.0.30.253 %COPY-I-FILECPY: Files Copy - source URL HTTP://10.0.30.5/image_tesla_hybrid_2.5.7.85_release_cisco_signed.bin destination URL flash://system/images/image_tesla_hybrid_2.5.7.85_release_cisco_signed.bin  
2021-03-11T15:04:36.381549+01:00 10.0.30.253 %COPY-D-TRAP: The copy image operation was completed successfully  
2021-03-11T15:04:36.385653+01:00 10.0.30.253 %COPY-N-TRAP: The copy operation was completed successfully  
2021-03-11T15:08:57.979906+01:00 10.0.30.253 %SYSLOG-N-LOGGING: Logging started.  
2021-03-11T15:08:59.877513+01:00 10.0.30.253 %STP-W-PORTSTATUS: gi8: STP status Forwarding  
2021-03-11T15:09:04.471035+01:00 10.0.30.253 %LINK-W-Down:  gi8  
2021-03-11T15:09:07.371885+01:00 10.0.30.253 %LINK-I-Up:  gi8  
2021-03-11T15:09:08.588077+01:00 10.0.30.253 %SNTP-D-NTPBADVER: NTP server version not compatible  
2021-03-11T15:09:08.610299+01:00 10.0.30.253 %SNTP-D-NTPBADVER: NTP server version not compatible  
2021-03-11T15:09:12.037559+01:00 10.0.30.253 %STP-W-PORTSTATUS: gi8: STP status Forwarding  
2021-03-11T15:09:16.477618+01:00 10.0.30.253 %STP-W-PORTSTATUS: gi8: STP status Blocking  
2021-03-11T15:09:46.477138+01:00 10.0.30.253 %STP-W-PORTSTATUS: gi8: STP status Forwarding  
2021-03-11T15:10:00.452603+01:00 10.0.30.253 %SSL-I-CACERTINSTLD: CA Certificate type dynamic owner <pnp> name <cloud_redirect_ca_trustpool_0> is installed  
2021-03-11T15:10:00.619755+01:00 10.0.30.253 %SSL-I-CACERTINSTLD: CA Certificate type dynamic owner <pnp> name <cloud_redirect_ca_trustpool_1> is installed  
2021-03-11T15:10:00.821387+01:00 10.0.30.253 %SSL-I-CACERTINSTLD: CA Certificate type dynamic owner <pnp> name <cloud_redirect_ca_trustpool_2> is installed  
2021-03-11T15:10:00.984682+01:00 10.0.30.253 %SSL-I-CACERTINSTLD: CA Certificate type dynamic owner <pnp> name <cloud_redirect_ca_trustpool_3> is installed  
2021-03-11T15:10:01.146787+01:00 10.0.30.253 %SSL-I-CACERTINSTLD: CA Certificate type dynamic owner <pnp> name <cloud_redirect_ca_trustpool_4> is installed  
2021-03-11T15:10:01.312478+01:00 10.0.30.253 %SSL-I-CACERTINSTLD: CA Certificate type dynamic owner <pnp> name <cloud_redirect_ca_trustpool_5> is installed  
2021-03-11T15:10:01.477584+01:00 10.0.30.253 %SSL-I-CACERTINSTLD: CA Certificate type dynamic owner <pnp> name <cloud_redirect_ca_trustpool_6> is installed  
2021-03-11T15:10:01.668335+01:00 10.0.30.253 %SSL-I-CACERTINSTLD: CA Certificate type dynamic owner <pnp> name <cloud_redirect_ca_trustpool_7> is installed  
2021-03-11T15:10:01.834609+01:00 10.0.30.253 %SSL-I-CACERTINSTLD: CA Certificate type dynamic owner <pnp> name <cloud_redirect_ca_trustpool_8> is installed  
2021-03-11T15:10:02.016875+01:00 10.0.30.253 %SSL-I-CACERTINSTLD: CA Certificate type dynamic owner <pnp> name <cloud_redirect_ca_trustpool_9> is installed  
2021-03-11T15:10:02.197192+01:00 10.0.30.253 %SSL-I-CACERTINSTLD: CA Certificate type dynamic owner <pnp> name <cloud_redirect_ca_trustpool_10> is installed  
2021-03-11T15:10:02.397378+01:00 10.0.30.253 %SSL-I-CACERTINSTLD: CA Certificate type dynamic owner <pnp> name <cloud_redirect_ca_trustpool_11> is installed  
2021-03-11T15:10:02.566756+01:00 10.0.30.253 %SSL-I-CACERTINSTLD: CA Certificate type dynamic owner <pnp> name <cloud_redirect_ca_trustpool_12> is installed  
2021-03-11T15:10:02.754199+01:00 10.0.30.253 %SSL-I-CACERTINSTLD: CA Certificate type dynamic owner <pnp> name <cloud_redirect_ca_trustpool_13> is installed  
2021-03-11T15:10:02.936926+01:00 10.0.30.253 %SSL-I-CACERTINSTLD: CA Certificate type dynamic owner <pnp> name <cloud_redirect_ca_trustpool_14> is installed  
2021-03-11T15:10:19.181806+01:00 10.0.30.253 %INIT-I-Startup: Warm Startup  
2021-03-11T15:15:25.791996+01:00 10.0.30.253 %PNPAGENT-I-DEVINFO: Device Info PnP Request with parameter all  
2021-03-11T15:15:25.795974+01:00 10.0.30.253 %PNPAGENT-I-RESPSUCCESS: PnP Response Success  
2021-03-11T15:15:27.147047+01:00 10.0.30.253 %PNPAGENT-I-BYEREQ: Bye PnP Request  

So looks like we really need to wait and see how cisco solves this.

Hello All,

Also i had exact the same problem, verified the checksum before updating, checksum was ok.

I now logged also a case for this problem.

Another switch SG350-28P i updated yesterday went fine without any problems, except that it was very slow in uploading the firmware an rebooting.

I noticed that the image for this switch was a lot bigger that for the SG250 but I really don’t know I a can compare them because it one model lower?

I wil update, if i know more form the case that i logged on this forum.

 

 

*** Disclaimer: I do not recommended anyone following what I did on any switch used for production. Try at your own risk.

 

I had a little time on my hands, even after loosing an hour to DST, so I decided to download the FW for the SG350 switches and it seems to work. I'm able to reboot and my SG250-08 comes up with 2.5.7.85 as the active version. This is just an extra switch I have lying around so I don't have an easy way to test allot of the features, but so far it seems to work. 

 

I still want and will wait for Cisco to update the official SG250 firmware page and file, before I look into upgrading any of my production switches.

 

Capture.JPG