Gå til indhold
Blog

Remote Intelbras FTTH Management with OMCI

Dette indhold er ikke tilgængeligt i dit sprog endnu.

Summary
Step-by-step guide to manage Intelbras FTTH networks with OMCI: understand how OLTs talk to ONUs, register and provision CPEs, push VLAN and service profiles, and verify connectivity, while keeping operations manageable with MKController and NATCloud.

Remote Intelbras FTTH Management with OMCI

If you work with FTTH and Intelbras, you’ve probably heard that “it’s all OMCI”.

But what does that actually mean in practice?

OMCI is the invisible “remote control” that lets your OLT configure ONUs automatically, push VLANs and services, and monitor status without logging into each CPE one by one.

In this article we’ll walk through:

  • What OMCI is (in plain language).
  • Default Intelbras IPs and credentials for OLTs and ONUs.
  • How to register an ONU via auto-discovery.
  • How to bind VLAN and service profiles (Bridge / PPPoE).
  • How to test if the ONU is really online and passing traffic.
  • Where MKController fits into this story when the network grows.

1. What is OMCI in a GPON network?

OMCI stands for ONU Management and Control Interface.

It’s defined by the ITU-T G.988 standard and is used by the OLT to:

  • Discover and register ONUs automatically.
  • Push configuration templates (VLANs, services, QoS).
  • Change profiles remotely, without logging into each ONU.
  • Upgrade ONU firmware in bulk.
  • Monitor status, traffic and alarms.

You can think of OMCI as a “remote API” between the OLT and each ONU.

Instead of treating every ONU like a separate router with its own IP and login, the OLT sends instructions down the fiber and the ONU obeys.

Note: In many Intelbras deployments, ONUs are not accessed directly by IP for day-to-day work. The heavy lifting happens through OMCI right from the OLT.

2. Default IPs and credentials (Intelbras OLT and ONUs)

Before touching OMCI settings, you need to reach the OLT.

Many Intelbras models use similar defaults:

EquipmentDefault IPUserPassword
OLT 8820G / 8820L192.168.1.1adminadmin
Intelbras ONU G120 / G240Gets IP via OLTadminadmin

Tip: Most Intelbras ONUs in GPON scenarios are provisioned via OMCI. In many setups you’ll never need to browse directly into the ONU’s web interface.

Of course, this is just the starting point.

As soon as remote access is stable, you should:

  • Change all default passwords.
  • Place the management IP of the OLT in a secure, documented VLAN.
  • Limit who can reach the management interface.

3. Connecting to the OLT management interface

Let’s start from the very beginning: getting into the OLT web interface.

3.1 Physical connection

  1. Plug your laptop into the MGMT (management) port of the Intelbras OLT.
  2. Use a straight Ethernet cable (no crossover voodoo needed on modern gear).

3.2 Configure your PC IP

Set a static IP on your computer in the same subnet as the default OLT address:

  • IP: 192.168.1.10
  • Netmask: 255.255.255.0
  • Gateway: can be blank for local access.

On Windows, you can do this in the adapter’s TCP/IP properties; on Linux/macOS, configure via Network Manager or CLI.

3.3 Access the web panel

  1. Open your browser.

  2. Type:

    http://192.168.1.1

  3. Log in with:

    • User: admin
    • Password: admin (factory default; change later!)

If you can’t reach the page:

  • Check cabling and LEDs.
  • Confirm your PC IP is in 192.168.1.x/24.
  • Temporarily disable local firewalls just to test.

4. Enabling OMCI and discovering ONUs automatically

With the OLT panel working, it’s time to let it “see” the ONUs on the PON port.

4.1 Open the ONU management screen

In the OLT interface, look for something like:

  • PON → ONU Management → Auto Discovery
    (names may vary slightly by firmware, but the idea is the same)

This page shows unregistered ONUs that are physically connected but not yet provisioned.

4.2 Connect an ONU to the optical port

  1. Connect an Intelbras ONU (for example, G120 or G240) to a PON port on the OLT.
  2. Wait a few seconds.

The ONU should appear on the screen as “Unregistered ONU” or similar.

If nothing appears:

  • Check optical levels (power, connectors, cleanliness).
  • Make sure the ONU is compatible and powered on.
  • Confirm that you’re on the correct PON port in the interface.

4.3 Registering the ONU in OMCI mode

Once the OLT has “seen” the ONU:

  1. Select the unregistered ONU on the list.
  2. Click “Register ONU” (or equivalent action).
  3. Choose the OMCI mode.

Here you’ll define the base service profile:

  • Data VLAN (e.g. 10)
  • Voice VLAN (e.g. 20)
  • Service type:
    • Bridge – ONU acts as a simple bridge; CPE/router behind it handles PPPoE and routing.
    • PPPoE – the ONU itself can manage PPPoE, depending on profile/design.
  1. Save and apply the changes.

If all goes well, the ONU will receive its profile automatically via OMCI and move to a state like “Registered” or “OMCI Active”.

Warning: Be careful when editing templates used by many ONUs at once. A small mistake in VLAN or service profiles can cut service to dozens of customers in a single click.

5. Testing connectivity through the ONU

Provisioning without testing is like closing a ticket without reading it: sooner or later it comes back.

5.1 Connect a router to the ONU LAN port

  1. Connect a customer router or test router to the LAN port of the newly registered ONU.

  2. On the router, configure the WAN according to the service type 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/edge.
    • If the ONU is handling PPPoE itself:
      • Make sure the PPPoE parameters are correctly set in the OMCI profile.

5.2 Check IP assignment or PPPoE authentication

On the CPE/router connected to the ONU:

  • Confirm it gets an IP (if DHCP) or PPPoE session goes to Connected.
  • Try to reach an external address like https://example.com for a quick test.

5.3 Verify ONU status on the OLT

Back in the OLT interface:

  1. Go to PON Status → ONU Online (or similar).
  2. Look for the specific ONU you just provisioned.

The ONU should show something like:

  • Status: Online / OMCI Active
  • Rx/Tx power: within acceptable levels
  • Traffic counters: increasing as you run tests

Tip: Keep a simple checklist for new ONU activation: “Registered? Online? IP/PPPoE? Ping OK? Speed test OK?” It saves a lot of back-and-forth with the field team.

6. Scaling OMCI management without losing your mind

Managing a few ONUs through the OLT GUI is easy.

Managing hundreds or thousands, across multiple sites and different hardware vendors? That’s where things get ugly if you rely only on manual clicks and spreadsheets.

Common pain points:

  • Hard to see overall availability of ONUs and OLTs.
  • No unified view if you use more than one brand or model.
  • No easy way to tie ONU status to tickets and real users.
  • Need for secure remote access even when there is no public IP (CGNAT, carrier NAT, etc.).

This is where extra tooling makes the difference.

Where MKController helps: 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 an eye on uptime and availability dashboards.

7. Using MKController and NATCloud with Intelbras OMCI

OMCI covers the last mile config between OLT and ONU.

But your daily operational life involves much more:

  • Tracking which sites are up or down at a glance.
  • Seeing which ONUs and routers are flapping.
  • Remotely accessing devices (for example, a router behind the ONU) with no static IP and no exposed ports.
  • Detecting new devices automatically as they appear on the network.

MKController’s platform and NATCloud tunnels bring a few practical wins:

  • Centralized monitoring:
    One dashboard to see Intelbras OLTs, ONUs and other network gear—no more jumping between islands of management.
  • Automatic discovery:
    Use LLDP, SNMP and CDP to find devices and build a live inventory map.
  • Remote access without public IP:
    NATCloud creates secure outbound tunnels, so you can access equipment even behind CGNAT or in private-only environments.
  • Availability and uptime views:
    See which links and CPEs misbehave, without waiting for customer complaints.

Instead of opening ports all over the place or keeping dozens of web panels open, you get a single control plane to operate the FTTH network.

About MKController

Hope the insights above helped you navigate your MikroTik and Internet universe a little better! 🚀
Whether you’re fine-tuning configs or just trying to bring some order to the network madness, MKController is here to make your life simpler.

With centralized cloud management, automated security updates, and a dashboard that anyone can master, we’ve got what it takes to upgrade your operation.

👉 Start your free 7-day trial now at mkcontroller.com — and see what effortless network control really looks like.