The same onboarder works for VSOL, CDATA, and OPTILINK out of the box. For any unknown vendor the AI learns the login and ONU page itself — you don't need a vendor-specific driver.
Open the AI onboarder
From the home dashboard tap OLT Management → Add OLT (AI). The screen title reads
Add OLT (AI).The intro card explains what's about to happen: the app points the AI at any OLT's management IP, fingerprints the device, and for new vendors reverse-engineers the login and reads the ONU table automatically.
ScreenshotAdd OLT (AI) screen — intro card, IP / credentials / VLAN fields.Enter the management IP
Fill the OLT management IP — for example
10.210.129.41. This is the IP your team uses to log into the vendor's web console.If the OLT sits behind the BSNL proxy (the common case), use the IP that resolves from your TIP's network, not the public address.
ScreenshotManagement IP field with example placeholder 10.210.129.41.Enter credentials per vendor
Defaults that ship with FNW Flow:
- VSOL —
admin/admin(placeholder text on the form). Change if your SSA rotated. - CDATA — vendor docs. Common:
admin/123456. - OPTILINK — vendor docs.
- Unknown vendor — anything you use to log in via the web console; the AI will try it.
The password field has a show/hide toggle.
ScreenshotUsername + Password fields with show/hide eye icon.- VSOL —
Set location + VLAN
- Location (optional) — free text. Use the exchange or building name. This is how it'll be labelled on the dashboard.
- VLAN — the data VLAN configured on this OLT for FTTH service. Numeric only.
ScreenshotLocation and VLAN fields side-by-side.Decide on monitoring
The Add to monitoring if it works switch decides whether the OLT joins background polling after onboarding succeeds. Keep it on — it's how the dashboard ONU count and live signal stay current.
Screenshot'Add to monitoring if it works' switch with description.Let the AI learn
Tap Learn this OLT. The button turns into a progress spinner with the message "AI is learning this OLT…" and a 12-second helper line: "This can take 20–60s — fingerprinting, logging in, and reading the ONU table over the BSNL proxy."
You'll get one of four results:
- Supported out of the box (green) — a built-in driver matched the device. Vendor + driver shown.
- AI can operate this OLT (violet) — vendor unknown; the AI learned the login and ONU page itself. Shows the ONU count read.
- Partially learned (amber) — login understood but ONU data couldn't be confirmed end-to-end. Sometimes the OLT uses an image captcha; vendor-specific OCR is needed.
- OLT unreachable (red) — couldn't reach through the BSNL proxy. Check the IP, or retry — the proxy is sometimes flaky.
ScreenshotFour possible result cards — green / violet / amber / red.
Now that the OLT is onboarded, the NC flow's Service Config step autocompletes the ONU details.
Helpful?
Did this guide help you finish the flow?