11-27-2021 06:37 AM - edited 11-27-2021 07:39 AM
Hi,
I'm facing a problem after firmware update from 2.5.8.12 to 2.5.8.15. After that update, the switch reboots and the system LED is permanent flashing (it is an higher frequency than during normal boot). Connected devices don't get an IP resp. the switch is not accessible.
After resetting (power on + hold reset for more than 10 sec) the switch, I can reload a backup of my config and everthing works again.
Some weeks ago, I've had the same problem with a former update from 2.5.7.85 to 2.5.8.12.
To be honest, it is my first smart switch from Cisco. This behaviour is not acceptable - or am I doing something wrong?
Thx + Regards,
Karsten
11-27-2021 08:19 AM
>the switch reboots and the system LED is permanent flashing
- That means the factory default IP address is again used , (192.168.1.254) , please remember to save the configuration before executing an upgrade.
M.
11-27-2021 08:44 AM
Mmmhh ... just an idea ... is it possible that the switch looses his config after firmware update?
In that case, I would try first the default config with the corresponding IP 192.168.1.254 after next update.
11-27-2021 09:05 AM
>is it possible that the switch looses his config after firmware update?
Normally it shouldn't as stated make sure a save-before is done , also when this is done (before the upgrade) , check the logs too - make sure no errors are seen (related to saving the configuration).
M.
11-27-2021 12:42 PM
@marce1000 wrote:
>is it possible that the switch looses his config after firmware update?
Normally it shouldn't as stated make sure a save-before is done , also when this is done (before the upgrade) , check the logs too - make sure no errors are seen (related to saving the configuration).
M.
Thank you. I've checked the log files, but there are no relevant entries. An yes, I've always a backup of the last running config. After next fw update, I'll check to use the default IP if there are any problems. But it remains strange ...
11-28-2021 12:09 AM
> I've always a backup of the last running config.
There's a difference between having a backup and saving the configuration (too)
M.
11-28-2021 02:00 AM
@marce1000 wrote:
> I've always a backup of the last running config.
There's a difference between having a backup and saving the configuration (too)
That sounds interesting, may I've something forgotten, but what?
I've no unsaved config changes (e.g. the save button is not flashing). Is there an additional task for me, e.g. before uprading to perform another file operation?
11-28-2021 02:45 AM
11-28-2021 03:42 AM
@marce1000 wrote:
Do you get a confirming-message when using the save button ? M.
Yes. The log file gets two entries for that:
%COPY-N-TRAP: The copy operation was completed successfully %COPY-I-FILECPY: Files Copy - source URL running-config destination URL flash://system/configuration/startup-config
11-28-2021 03:54 AM
11-28-2021 04:07 AM
Yes. If I power off and on, then the switch works as configured. The problem only occurs after firmware update.
11-28-2021 05:54 AM
- I don't mean the power off and on situation, which is not applicable when upgrading. I mean does it load the intended configuration upon 'simple' reboot.
M.
11-28-2021 08:34 AM
@marce1000 wrote:
- I don't mean the power off and on situation, which is not applicable when upgrading. I mean does it load the intended configuration upon 'simple' reboot.
M.
Great! Looks like, that you've the right instinct! After reboot, I've the same problems - even if I re-config my notebook (which is connected to the switch) to use a static IP in the default range of the switch (and for the switch itself the IP 192.168.1.254). I triggered the reboot via Web UI, but I did not check the checkboxes for "Restore to Factory Defaults" or "Clear Startup Configuration File".
But, I do not really understand what is going wrong (probably a misconfig by myself)?
Then there is another strange thing. As preface, some infos to my setup
Before I perform that reboot, I've backed-up running and startup config. I've compared them in a text editor: Both are identical.
After reboot, I've tried to recover the switch via re-import of the running-config a couple of times:
Port 1 (based on 2.5.8.15)
interface GigabitEthernet1 spanning-tree link-type point-to-point switchport mode trunk macro description switch !next command is internal. macro auto smartport dynamic_type switch
Port 1(based on 2.5.8.12)
interface GigabitEthernet1 switchport mode trunk switchport trunk native vlan none
I've not changed the config manually. These changes must be occured via re-import into the latest firmware version.
11-28-2021 09:22 AM
- I will not go into those port-configuration issues, but stick to the original problem which you are now experiencing for 'simple reboots' also, in that context : After making any reconfiguration, you need to 'commit' the changes by duplicating the 'Running Configuration' to the 'Startup Configuration'. See menu: Administration > File Management > File Operations
M.
11-28-2021 11:38 AM - edited 11-28-2021 11:58 AM
Before last "reboot test case", I've duplicated the runnning config to start config by file operation. It doesn' help.
I've even compared a backed-up running config with a backed-up start-config, both were identical (see former post 11-28-2021 08:34 AM)
And: There is no difference between pushing the save button and file operation to duplicate the config from running to start config (see former post, 11-28-2021 03:42 AM). Also the log entries for both ways are identical.
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