schedule reboot for er7212pc itself
Hi,
I still cannot find a way to schedule the reboot for the ER7212PC itself.
I can only schedule the APs, but the ER7212PC router cannot be scheduled.
I can only reboot ER7212PC manually.
Please make it possible.
br
Peter
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hi @peter021
peter021 wrote
I have read your response and understand that it is a 3 in 1 system, but I don't understand why it can't perform a reboot.
I have a PPPoE WAN connection and a dynamic IP address. The Internet Service Provider typically assigns a new IP address every 7 days during working hours.
I requested that they complete the task during the night, but they were unable to do so. Fix IP is not possible.
This is why I want to reboot internally.
If it were possible to schedule the WAN reconnection, it would also be a nice solution.
The smart plug would be a really basic, primitive solution. I don't think this should be solved that way.
regards
Peter
The Omada Controller does not reboot itself. This applies to the 3-in-1, it means the built-in controller cannot reboot itself. In essence, it is the entity of the ER7212P.(I left C as it stands for Controller).
Or you can enter the system and manually reboot it.
The simple mechanism would stay before OC200/300 can schedule itself a reboot. But it is not likely to be that. I explained this somewhere before, as it needs to be the headquarter of the whole system and the NTP for the rest of products, it does not or is supposed to reboot on schedule as it breaks the control and rest of other device NTP sync. Also, it would reboot a longer time as the config increases. This is why a controller is not built for a schedule reboot. If you can understand this, I hope so.
- Copy Link
- Report Inappropriate Content
Hi @peter021
Thanks for posting in our business forum.
As it is a 3-in-1 product, it is considered as part of the controller so it cannot be rebooted based on the schedule.
This is similar to the Omada Controller as it is played as a controller(mind of the whole network). If you need to reboot the controller, you probably try the smart plug which can be scheduled.
- Copy Link
- Report Inappropriate Content
I have read your response and understand that it is a 3 in 1 system, but I don't understand why it can't perform a reboot.
I have a PPPoE WAN connection and a dynamic IP address. The Internet Service Provider typically assigns a new IP address every 7 days during working hours.
I requested that they complete the task during the night, but they were unable to do so. Fix IP is not possible.
This is why I want to reboot internally.
If it were possible to schedule the WAN reconnection, it would also be a nice solution.
The smart plug would be a really basic, primitive solution. I don't think this should be solved that way.
regards
Peter
- Copy Link
- Report Inappropriate Content
Hi @peter021
peter021 wrote
I have read your response and understand that it is a 3 in 1 system, but I don't understand why it can't perform a reboot.
I have a PPPoE WAN connection and a dynamic IP address. The Internet Service Provider typically assigns a new IP address every 7 days during working hours.
I requested that they complete the task during the night, but they were unable to do so. Fix IP is not possible.
This is why I want to reboot internally.
If it were possible to schedule the WAN reconnection, it would also be a nice solution.
The smart plug would be a really basic, primitive solution. I don't think this should be solved that way.
regards
Peter
The Omada Controller does not reboot itself. This applies to the 3-in-1, it means the built-in controller cannot reboot itself. In essence, it is the entity of the ER7212P.(I left C as it stands for Controller).
Or you can enter the system and manually reboot it.
The simple mechanism would stay before OC200/300 can schedule itself a reboot. But it is not likely to be that. I explained this somewhere before, as it needs to be the headquarter of the whole system and the NTP for the rest of products, it does not or is supposed to reboot on schedule as it breaks the control and rest of other device NTP sync. Also, it would reboot a longer time as the config increases. This is why a controller is not built for a schedule reboot. If you can understand this, I hope so.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 147
Replies: 3
Voters 0
No one has voted for it yet.