Netonix Forums

Running 1.5.2 on our WS-12-250. As we are approaching the low solar season, I set port 1 to power off at 12:01AM and powerup at 06:00AM. It did not work as expected:




Oct 9 09:22:38 UI: Port 1 Shutdown_Time: changed from '' to '12:01AM'
Oct 9 09:22:38 UI: Port 1 Startup_Time: changed from '' to '6AM'
Oct 9 12:01:01 switch[805]: Disabling PoE power on port 1 due to Shutdown Period

I expected the port to be shutdown at 12:01 AM, not 12:01 PM. Is this a problem or did I set it up wrong?

Well Stephen can check the feature to insure it is working but I would STRONGLY suggest using v1.5.5rc2 or soon v1.5.5rc3 as there were several LOng standing issues finally fixed in v1.5.5rc2 and rc3 fixes an issue discovered by Mayheart.

The issues fixed in v1.5.5rc2 and rc3 fix the switch restarting the vtts from restarting when doing innocuous changes such as turning POE on or even changing a port name. The restarting of vtts causes STP to cycle through the ports discarding/learning/passing or blocking and other blips.

Again STRONGLY suggest v1.5.5r2 or newer.

I do remember doing some work on that feature awhile back. I think it was on an rc release before 1.5.4 came out. I would definitely upgrade to see if that helps. I tested it and it is working for me.

However, to be certain please post a screenshot the Device->Config Tab, Power Tab, and the top right corner of the UI (starting at the end of Device Tab) and please let me know what model of switch you are using. (WS-12-250-AC or WS-12-250-DC ?)

We are using the DC version of the switch.

Doesn't the log I provided prove there is a problem? I set power off for 12:01AM and it shut down the port at 12:01PM?

I do not like upgrading firmware just because there is a new version available AND I do not like running rc firmware in our production environment.

Fine, then I will re-run the test please post the entire log for that switch.

rclark wrote:We are using the DC version of the switch.

Doesn't the log I provided prove there is a problem? I set power off for 12:01AM and it shut down the port at 12:01PM?

I do not like upgrading firmware just because there is a new version available AND I do not like running rc firmware in our production environment.

Did you not read what he said? He said he remembers working on that in v1.5.4 and your using v1.5.2 which is an old firmware.

Our procedure is if you have an issue try the latest firmware which right now is v1.5.5rc3 to see if the issue is still there. If the issue is there then ask us to look into it.

Besides development and any hope of fixing an issue/bug found would be in the current development thread which is v1.5.5rcX as v1.5.4 and older is closed to development and can not be fixed.

By your own statement above you say "Doesn't the log I provided prove there is a problem? " so you are assuming probably correctly that there is a BUG which Stephen said he thinks he did work to fix that in v1.5.4. How the heck do you expect us to resolve a BUG in v1.5.2 which is OLD firmware?

But if your going to upgrade I have told people there were long standing bugs and in some cases major issues in firmware that had been haunting us for years that were fixed in v1.5.5rc2 and then another bug discovered by Mayheart and then that fixed in v1.5.5rc3.

TRY v1.5.5rc3 and see what happens, it is our best and most stable code to date.

Sorry, my read of the note was that he remembers working in this area. He did not say he found and corrected an issue.

I don't expect you to resolve a bug in 1.5.2, I only wish to know if the problem is still in the current firmware before I interrupt customers internet to upgrade.

My sincere apologies for asking if this was indeed a problem.

rclark wrote:
My sincere apologies for asking if this was indeed a problem.

Sorry, been a bad day.......last couple weeks.

Ran out of FANs, production is ground to halt, people pestering me every day.

Just please try v1.5.5rc3, if still there let us know.