NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
M4300 and Timer Schedules / time-range Status always goes to Inactive - How to fix?
We have several M4300 (52G/96x) and switches and I am trying to setup working schedules to switch off POE for several ports during the night and the weekends when the offices are empty. The invo...
This...
Time Start: 00:00
Time Stop: 00:00
...does not sound meaningful to a network device, for an all-day schedule.
schumaku First of all thank you for you answer, however
as I wrote previously, the whole timer schedule goes to inactive as soon as I enter the first entry, so this already invalidates your comment.
I've documented the behaviour with a few screenshots:
Add a new Timer Schedule
Add new Timer Schedule
The Timer Schedule is active
The new Timer Schedule is active - but with no Schedules attached yet
Add a periodic Schedule to the Timer Schedule
Add the new periodic schedule to the Timer Schedule by clicking on the <Add> button (not in the screenshot). It makes no difference if I use a day in the past, todays date or some day in the future for "Day Start".
According to the documentation this schedule will run (ie switch off POE) Mon-Fri from one minute past midnight until 7am.
However:
The Timer Schedule has become inactive
Now the Timer Schedule has become inactive.
What is wrong here ? How to switch on the schedule?
Coming back to your posting, why should 00:00-00:00 not be a meaningful entry?
How else should I qualify that POE should be down on the port for the whole day?
00:00 - 24:00 is not a valid entry and results in an error:
"Error! Invalid 'Time End' format: 24:00"
Switching on POE for one minute per day (23:59 - 00:00) by setting it to 00:00 - 23:59 seems kind of non-sensical.
The devices (mostly, but not exclusively IP telephones) would start to boot, just to be choked off again almost immediately - not exactly very healthy for the hardware.
MikeNeuffer wrote:
Coming back to your posting, why should 00:00-00:00 not be a meaningful entry?.
You re arguing with the wrong person here my friend. Just another community member here, I can just answer based on some longer experience with several Netgear switch generations which don't support continuous and 24h schedules.
MikeNeuffer wrote:
How else should I qualify that POE should be down on the port for the whole day?
00:00 - 24:00 is not a valid entry and results in an error:
"Error! Invalid 'Time End' format: 24:00"
This would make more sense, however - your result is predictable ...
MikeNeuffer wrote:
Switching on POE for one minute per day (23:59 - 00:00) by setting it to 00:00 - 23:59 seems kind of non-sensical.
It won't kill any hardware if its powered up for one minute only. Not nice, I admit. Let's see of you can get some better answers from the Netgear side...
MikeNeuffer wrote:
The devices (mostly, but not exclusively IP telephones) would start to boot, just to be choked off again almost immediately - not exactly very healthy for the hardware.
Not nice, I admit. Let's see of you can get some better answers from the Netgear side...
Had lengthy discussion in the past over this oddity already.
I order to document my findings:
We have undocumented behaviour here:
Once a schedule has been configured for a Timer Schedule, the status of the timer schedule (active/inactive) is determined by wether one of the schedules is _currently_ triggering/running or not. Before it is always active.
I found a severe bug in the current FW release 12.0.17.13 (not sure if it is also present in older releases):
If you update a Schedule of a Timer Schedule
it will immediately reset the affected ethernet ports
as soon as you click on <Apply>
if the schedule will trigger next in more then a handful minutes.
I didn't experiment in oder to find the exact required time differential,
but is was able to see the ports being reset when I was clicking on <Apply> about 10min before the Schedule would trigger, and it didn't reset them when the time differential was about 3 minutes.
Actually I first tested the 3 minutes differential, then with a modified schedule the 10min differential.
This is absolutely reproducible on the M4300 I did my tests on when I was discussing the active/inactive issue with 2nd/3rd level support.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
