Monitoring
Add or edit an OLT
Register a new OLT: IP, SNMP community, CLI login, ownership, port forwarding and sync interval.
Who can use it:
Super Admin, NOC Admin
Open this page in the app
What this page is for #
Here you tell the app how to reach an OLT. You need the OLT's IP address and its SNMP details (read-only is enough). A CLI login (SSH or Telnet) lets the app fetch data some OLTs do not give over SNMP.
- 1 Name as your team knows it, and the IP address next to it.
- 2 Port Forwarding IP: tick when the OLT sits behind a router / NAT and you reach it through forwarded ports.
- 3 Ownership is required: your own OLT, or one you run for a reseller.
- 4 Vendor: leave “Auto Detect”. Model and PON type are filled in by the app.
- 5 SNMP: version, port (normally 161) and community, exactly as configured on the OLT.
- 1 CLI access: username, password, SSH or Telnet and its port. “Enable password” only if the OLT asks for a second password.
- 2 Enable CLI enrichment lets the app log in on a schedule to read what SNMP does not give.
- 3 Sync interval: leave empty to follow the company schedule from Settings.
Add an OLT, step by step #
- Go to OLTs and press Add OLT.
- Enter the Name and IP Address.
- Choose the Ownership.
- Leave Vendor on Auto Detect (recommended).
- Fill in the SNMP Version, Port and Community.
- Enter the CLI Username, Password and Protocol if you have them (your company may require them).
- Press Save OLT. The app detects the vendor and queues the first sync.
- On the OLT page, press Test connection if the first sync does not succeed.
The fields explained #
| Field | What to enter |
|---|---|
| Port Forwarding IP | Tick it when several OLTs share one public IP on different ports. The SNMP port and the SSH / Telnet port then become required, because the defaults (161 / 22 / 23) will not be right. A Private IP field appears: the OLT's own LAN address, kept as a note for your team. |
| Vendor | Auto Detect asks the OLT what it is. Choose a vendor by hand only if detection picks the wrong one. |
| Model, PON type | Read-only: filled by Test connection or the first sync. |
| SNMP version | v2c for most OLTs. v3 asks for a user and passwords instead of a community. |
| CLI interval | How often the slower CLI collection runs. Empty = the company schedule. |
| Status | Active is polled. Inactive and Maintenance are not. |
| Include in continuous live sync | Leave ticked so the scheduler polls this OLT. |
Related topics
OLT list
Every monitored OLT with its status, ports, ONUs and last sync. Filter, sort, sync or bulk-set ownership.
OLT page
One OLT in detail: sync status, CPU / memory, PON ports with laser readings and the ONU list.
Settings
Company-wide choices: how often OLTs sync, CLI rules, ONU Add / Delete options and the sync plan.
Troubleshooting & FAQ
Quick answers: sync failed, no optical power, a menu is missing, ONU not found, and more.
Finished this topic?
Tick it off; the topic list shows what you have read.