Intelbras FTTH Management with OMCI

Summary OMCI (ONU Management and Control Interface, ITU-T G.988) is the protocol Intelbras OLTs use to discover, register, and configure ONUs over the optical link — no per-ONU IP, no per-ONU login. This guide covers OLT access, ONU auto-discovery, OMCI registration with VLAN and Bridge/PPPoE profiles, end-to-end connectivity testing, and where MKController and NATCloud fit when the FTTH plant grows past a handful of customers.

What is OMCI in a GPON network?

OMCI is the ONU Management and Control Interface standard (ITU-T G.988) that lets a GPON OLT discover and provision the ONUs on its PON ports automatically. Instead of treating each ONU as a separate device with its own IP and login, the OLT pushes configuration over the optical link: it discovers new ONUs, applies service profiles (VLAN, bandwidth, PPPoE parameters), changes settings remotely, runs firmware upgrades in bulk, and monitors status and alarms — all without an IP-routed management session to each ONU.

In Intelbras deployments, the practical implication is that ONUs are rarely accessed directly by IP for day-to-day work. The heavy lifting happens through OMCI right from the OLT, which means the OLT is the source of truth and the choke point for any provisioning automation. For the cloud-managed alternative to local OLT operations, see our iOLT Cloud guide; for the desktop tool that runs this workflow locally, see the iManager guide.

Default Intelbras IPs and credentials

Equipment	Default IP	User	Password
OLT 8820G / 8820L	192.168.1.1	admin	admin
Intelbras ONU G120 / G240	Provisioned via OLT (OMCI)	admin	admin

Most Intelbras ONUs in GPON deployments are provisioned via OMCI — you’ll rarely need to browse directly into the ONU’s web interface. Once remote access is stable, change all default passwords, place the OLT management IP in a documented management VLAN, and restrict who can reach the management interface.

Step 1: Reach the OLT management interface

1. Plug a PC into the MGMT port of the Intelbras OLT with a straight Ethernet cable.
2. Set a static IP on the PC: 192.168.1.10, 255.255.255.0, gateway blank.
3. Open a browser and navigate to http://192.168.1.1.
4. Log in as admin / admin (change the password after the first successful login).

If the page doesn’t load, check cabling and link LEDs first, confirm the PC IP is on 192.168.1.x/24, and temporarily disable any host firewall to rule it out.

Step 2: Discover ONUs via auto-discovery

With the OLT panel open, navigate to PON → ONU Management → Auto Discovery (names vary slightly by firmware, but the function is the same).

1. Connect an Intelbras ONU (G120, G240, or compatible model) to a PON port on the OLT.
2. Wait a few seconds for the discovery process to complete.
3. The ONU appears in the list as Unregistered ONU.

If nothing appears, three things are usually the cause: optical signal levels are off (check the optical power, connector cleanliness, fiber bend radius), the ONU model is incompatible or unpowered, or you’re viewing the wrong PON port in the interface.

Step 3: Register the ONU in OMCI mode

When the unregistered ONU appears in the list:

1. Select the entry.
2. Click Register ONU (or equivalent action).
3. Choose OMCI mode as the management method.
4. Define the base service profile:
   • Data VLAN (e.g., 10)
   • Voice VLAN (e.g., 20)
   • Service type:
     • Bridge — the ONU acts as a simple Layer-2 bridge; the customer router behind it handles PPPoE and routing.
     • PPPoE — the ONU itself manages the PPPoE session based on the OMCI profile.
5. Save and apply.

The ONU receives its profile automatically over OMCI and transitions to Registered or OMCI Active. Be deliberate when editing shared templates — a wrong VLAN or service-type value on a common profile can disconnect dozens of customers in one save.

Step 4: Test connectivity through the ONU

Provisioning without testing is closing a ticket without reading it — it comes back.

Connect a router to the ONU LAN port. Use a customer router or a test router. Configure the WAN according to the service mode you chose: if the ONU is in Bridge mode, set the router WAN to PPPoE (typical for ISP setups) or DHCP depending on your BRAS or edge; if the ONU is handling PPPoE itself, verify the PPPoE credentials are correct in the OMCI profile.

Check IP assignment or PPPoE authentication. On the customer router, confirm it receives an IP (DHCP) or that the PPPoE session reaches Connected state. Run a quick reachability test to an external address.

Verify ONU status on the OLT. Back in the OLT interface, open PON Status → ONU Online and find the ONU you provisioned. It should show Status: Online / OMCI Active, Rx/Tx power within acceptable levels, and traffic counters increasing as you run tests. A simple activation checklist saves field-team back-and-forth: registered → online → IP/PPPoE → ping → speed test.

Scaling OMCI without losing your mind

Managing a handful of ONUs through the OLT GUI is straightforward. Managing hundreds or thousands across multiple sites and possibly multiple hardware vendors is where manual clicks and spreadsheets fail. The common pain points are predictable: hard to see overall availability of ONUs and OLTs, no unified view across vendors, no easy way to tie ONU status to tickets and real customers, and the need for secure remote access when sites sit behind CGNAT or carrier NAT.

This is where the orchestration layer matters at least as much as the OLT. MKController centralizes monitoring for Intelbras and multi-vendor networks, pulling data via SNMP, LLDP, CDP, and other protocols. Combined with NATCloud, it gives technicians access to equipment even without a public IP on site, while keeping uptime and availability dashboards visible. For the broader monitoring pattern, see our SNMP monitoring guide and the TR-069 management guide.

Take the next step

OMCI covers the last-mile configuration between OLT and ONU. Daily operations involve much more: tracking which sites are up or down at a glance, seeing which ONUs and routers are flapping, remotely accessing devices behind the ONU with no static IP and no exposed ports, and detecting new devices automatically as they appear on the network.

MKController plus NATCloud delivers that: one dashboard for Intelbras OLTs, ONUs, and other network gear; automatic device discovery; remote access without public IPs through secure outbound tunnels; and availability views that surface problems before customer complaints land. Instead of opening ports across the network or juggling dozens of web panels, you get a single control plane to operate the FTTH plant.

Start your free MKController trial