Product Overview
Design, validate, and monitor your fiber paths—from OLT to every ONU—visually.
Topology Designer
Drag‑drop OLT → Splitter → ONU; templates and cloning.
Path Trace & Audit
One‑click OLT↔ONU path, loop detection, impact analysis.
Optical Budget
Loss calculator (1310/1490/1550), thresholds and alerts.
Monitoring & Alerts
Expected vs actual dBm, outage heatmap, notifications.
GIS & Field View
Maps, closures/patch‑panel geotag, mobile read‑only.
Security & Compliance
Tenant isolation, SSO/SCIM, RBAC, data residency.
Integrations & Turn-Up
During the first onboarding step we add every OLT. Units that sit on a public IP are reachable instantly over Telnet, while OLTs behind private addressing need MikroTik port forwarding before OLTP can talk to them.
- Public OLTs: confirm TCP/23 is open and mapped to the OLT; no additional work.
- Private OLTs: create a dst-nat rule on the edge MikroTik so our Telnet probes reach the management IP.
MikroTik Port Forwarding
dst-address=103.X.X.X-> replace with the MikroTik public/WAN IP.dst-port=8585-> choose the external port you will expose for Telnet.to-addresses=172.16.X.X-> use the OLT management IP on the LAN.to-ports=23-> keep 23 for standard Telnet or change if the OLT listens elsewhere.
Update the fields below with your details, then copy the ready-to-run command (paste the single line directly in the MikroTik terminal).
/ip firewall nat add action=dst-nat chain=dstnat comment="OLT Telnet Port Forwarding" dst-address=103.0.0.10 dst-port=8585 protocol=tcp to-addresses=172.16.0.10 to-ports=23