Switch keeps stating "configuration has changed"

[cwachs]

I have a WS-8-150-DC running 1.4.8rc3. I went to upgrade firmware on it but am hesitant since the switch keeps popping up the "The configuration has changed on the device. You will not be able to save any configuration changes. Click here to reload the configuration" message. When I re-load the configuration using the link, that message pops right back up again. It has done this in a couple different browsers so I don't think I have some cache problem. I am hesitant to make any config changes to the switch or replace firmware for fear of loosing control of it. It sits at the top of our tower so getting at it is not trivial. Any thoughts on what is causing this and how to safely get past it?

[Eric Stern]

Usually if you reload the interface and quickly make a configuration change (doesn't matter what it is) and click Save/Apply before the warning appears that will fix it.

[Brough]

I just ran into a switch doing exactly this. It was repeatedly 5 seconds from my reload until it said "configuration has changed..."
The switch is running on 1.4.7 firmware. Going as fast as I could, I was able to follow your suggestions and, yes!, that fixed it.

But what is the problem??? Is it something in queue to be fixed?

[mike99]

The problem as been there for a long time but seem to be consider low priority since the're no impact except it's annoying.

[geolinks]

It's been a while since this post has been updated and I've seen this same error referenced in other posts as recently as early 2017.

Is this still a known issue? And if so has there been any mention of a change in Netonix's Firmware Upgrade Release Path?

[cwachs]

Still getting it on some (but not all) of my switches.

[sirhc]

When this occurs all you have to do is make an innocuous change such as port description or anything you want and hit "Save/Apply" and it will clear.

I know it can be annoying when it occurs but it is simple to clear.


It is on the list to be addressed but yes it is low priority as it rarely happens and is easy to clear.

[sirhc]

I asked Eric to look into this again.

i'll make a change in the next version that "might" fix this

We shall see if it does.

[Dawizman]

Any resolution on this? I didn't see anything in the changelog yet.

[Julian]

Not quite yet, no. Sorry. What we do know now is that it has something to do with syslog updating, and the workaround is: Shift-F5, log in, make a trivial change(Port name, etc) and apply before the popup shows.

Annoying, I know. We're working on it.