Administration
Settings
Company-wide choices: how often OLTs sync, CLI rules, ONU Add / Delete options and the sync plan.
What this page is for #
Company-wide choices. They apply to every OLT unless an OLT has its own value on its edit page. Only users with the “Change the company settings” permission (Super Admin) see this page. Press Save settings after any change.
- 1 OLT sync schedule: how often every OLT is polled for status, power and MACs.
- 2 CLI enrichment schedule: how often the slower SSH / Telnet collection runs, for OLTs that have it on.
- 3 Queue workers: how many syncs the server runs side by side. Must match what is really running on the server.
Choosing the sync interval #
- Tap a preset (15 minutes … 1 day) or type the minutes. 1 hour is the default.
- A shorter interval gives fresher data but more work for the server and the OLTs. With many or large OLTs, do not go below what the workers can finish: the Sync plan below tells you.
- If some OLTs have their own interval, they are listed. Make all OLTs follow this schedule clears those.
- A manual Sync now is always possible, whatever the schedule.
The sync plan #
OLTs do not all start at the same minute. Each gets its own start time, spread over the interval according to how long its syncs usually take.
- 1 Re-plan now spreads all OLTs again, for example after adding many OLTs or changing the workers.
- The bars show the load over the coming hours: green = workers have spare time, orange = busy, red = more work than workers.
- Mostly red? Lengthen the interval, or have the server administrator run more queue workers and raise Workers here.
- The list shows each OLT's next run, its interval and how long a run takes. A failed OLT is retried after 15, 30, 60… minutes.
OLT form rule #
CLI access (SSH / Telnet) is mandatory: when ticked, nobody can save an OLT without a CLI username, password and protocol, and CLI enrichment is always on. Existing OLTs are asked for it the next time they are edited. Tick it if your OLTs need CLI for complete data.
ONU Delete and ONU Add #
- 1 ONU Delete: how many days an ONU must be inactive before the Delete button is offered (default 30), and whether the OLT’s configuration is saved after each delete.
- 2 ONU Add: whether the OLT’s configuration is saved after each add.
- 3 Automatic delete: deletes ONUs past the cut-off days by itself; the summary under it shows what was deleted or failed.
Automatic delete
Tick Automatically delete ONUs after the cut-off days and press Save settings to let the app delete, by itself, every ONU that has been inactive for at least the number of days above. It works exactly like pressing ONU Delete, with the same safety checks, but nobody has to do it.
- The deletes run in the background, one at a time, and only after every other job: OLT syncs and people's own ONU changes always go first, and an OLT that is busy is left alone until it is free.
- An ONU that cannot be deleted is skipped and tried again a day later. After three failed attempts it is no longer tried; delete it by hand from Inactive ONUs.
- If every delete on one OLT keeps failing (for example the OLT is unreachable or its CLI password is wrong), that OLT is paused for a few hours while the others carry on.
- When the option is on, a summary appears under it: ONUs deleted and failed in the last 24 hours and 7 days, what is running now, paused OLTs, ONUs given up, OLT types that cannot delete, and the recent failures with the OLT's answer.
Related topics
Finished this topic?
Tick it off; the topic list shows what you have read.