POE Shutdown Period "unexpected link change"

[Patagoche]

Hi everyone!

Currently it's still winter where I live and in a remote solar site we have, we've setup Shutdown periods in our WS-12-250-DC for some of our AP's during night hours.
I've also been implementing syslog in my libreNMS (check it out, it's a GREAT project) setup and I found that when I setup Shutdown Periods in the switch I get Unexpected link changes in my logs. Furthermore when I access the switch UI there is a red alert exclamation sign under Device -> Logs, as if there would be a problem which is not the case when you have set up shutdown periods. Could this be fixed and changed to something like "expected link change on port X", removing also the log alert?

Log transcript:

Code: Select all

Aug 26 07:00:00 switch[804]: Enabling PoE power on port 6 due to Shutdown Period
Aug 26 07:00:02 Port: link state changed to 'up' (10M-F) on port 6
Aug 26 07:00:02 STP: set port 6 to discarding
Aug 26 07:00:02 switch[862]: unexpected link change on port 6 100M-F


Thanks,

Andrés Rahn.

[sirhc]

ANd what version firmware are you running on the switch?

[Patagoche]

1.4.2rc4
Should it be resolved in newer versions?

[sirhc]

Well to be honest I am not entirely sure...but I would definitely upgrade to rc7 (Major bug fixes)

Tell you what please upgrade to v1.4.3rc7 and let me know and if not I will look into it.

[Patagoche]

Yep, yesterday i've upgraded to 1.4.3rc7 and the problem dissapeared! Even the alert in the webUI is gone.
Thank you.

Below log transcript.

Code: Select all

Aug 30 02:00:01 switch[1451]: Disabling PoE power on port 6 due to Shutdown Period
Aug 30 02:00:01 Port: link state changed to 'down' on port 6
Aug 30 02:00:01 STP: set port 6 to discarding
Aug 30 07:00:00 switch[1451]: Enabling PoE power on port 6 due to Shutdown Period
Aug 30 07:00:02 Port: link state changed to 'up' (10M-F) on port 6
Aug 30 07:00:02 STP: set port 6 to discarding
Aug 30 07:00:05 STP: set port 6 to learning
Aug 30 07:00:05 STP: set port 6 to forwarding
Aug 30 07:00:25 Port: link state changed to 'down' on port 6
Aug 30 07:00:25 STP: set port 6 to discarding
Aug 30 07:00:27 Port: link state changed to 'up' (100M-F) on port 6
Aug 30 07:00:27 STP: set port 6 to discarding
Aug 30 07:00:30 STP: set port 6 to learning
Aug 30 07:00:30 STP: set port 6 to forwarding


[sirhc]

I am very glad it fixed the problem for you but this is a repeating theme I have almost every day and I am not sure how to convince people that when I send out PM ALERTS about bugs and suggest they upgrade to latest code which sometimes is an RC version it is like pulling teeth.

[End User] We have this problem
[Me] Please upgrade to latest firmware
[End User] Yes that seems to fix the issue

For all those reading this post please follow these steps when you have a problem:
1) Identify a problem
2) Upgrade to latest Stable version (unless there is a warning to use the RC version instead because of BUGS)
3) If problem is still present then upgrade to latest RC version

Now at this point if you still have a bug then create a post asking for help. The reason for this is we can NOT fix bugs in code threads that are closed and if the version is FINAL then it is closed and no further development can be done on it to fix your issue.

Also if you receive a PM ALERT of bugs with a strong suggestion to upgrade even if to an RC version you should probably heed that warning or I would not have wasted my time sending it out.

Most times RC versions are mostly just bug fixes from the previous version with some minor enhancements but if there is a major change to the code in an RC version I am asking you to upgrade to I will let you know in the PM Alert.