OLT Management
Go to OLT to manage your Optical Line Terminals.
Add an OLT
Click Tambah OLT (Add OLT) and fill in:
| Field | Description |
|---|---|
| Router | The router (NAS) that reaches this OLT — used to build a route to the OLT’s IP |
| Name | A friendly name (e.g. OLT-Gatel-01) |
| IP Address | The OLT’s management IP (must be valid IPv4) |
| SNMP Community | SNMP community string (default: public) |
| SSH / Telnet / Web Port | Access ports (defaults 22 / 23 / 80) |
| Web Scheme | http or https for the OLT GUI |
When an OLT is created/updated, Cloudman injects a route on MikroTik (via the chosen router) so the OLT’s IP is reachable without a VPN.
OLT Status
Up/Down status is page-driven (not a cron): the list shows the last-known status instantly, then runs a background reachability ping each time it’s opened. The page refreshes status about every 1 minute while the tab is visible.
| Status | Description |
|---|---|
| Up | OLT responded to the last reachability ping |
| Down | OLT did not respond |
| — | Never checked yet |
SNMP Detail
Opening an OLT’s detail dialog triggers a one-off SNMP poll (not stored): the system group (vendor, model, hostname, uptime, location) and physical ports (name, admin/oper status, speed). This is separate from the list’s Up/Down status.
Remote Access
Cloudman can open an OLT’s GUI and CLI from anywhere without a VPN — connections are routed through the router’s tunnel.
- Terminal — an SSH or Telnet session to the OLT straight from the browser (xterm.js). SSH credentials are prompted on the spot and never stored.
- Web GUI — open the OLT’s web interface through the Cloudman gateway. Because it shares an origin, only one active OLT per browser at a time.
Remote access uses the same path as reachability (the router’s tunnel). Make sure the chosen router actually reaches the OLT’s IP.