Gå til innholdet
Blog

Remote Intelbras OLT Management with iManager

Dette innholdet er ikke tilgjengelig på ditt språk.

Summary
Step-by-step guide to manage Intelbras OLTs with iManager: connect to the device, discover and register ONUs, apply VLAN and bandwidth profiles, monitor status, and keep everything safe and consistent across sites.

Remote Intelbras OLT Management with iManager

If you deploy FTTH with Intelbras, sooner or later someone will say:

“Just drop it into iManager and it’s done.”

iManager is Intelbras’ management software for OLTs and GPON networks.
Instead of logging into each box by hand, you centralize configuration, ONU registration, and monitoring in a single tool.

In this article we’ll walk through:

  • The basic requirements to use iManager with Intelbras OLTs.
  • Default IPs and credentials you’ll find in the field.
  • How to connect the OLT in iManager.
  • How to discover and register ONUs (OMCI or bridge mode).
  • How to monitor status and save configuration correctly.
  • Where MKController and NATCloud fit when your network grows.

1. Requirements before you start

Make sure a few basics are in place before opening iManager.

You’ll need:

  • An Intelbras OLT (for example, 8820G or 8820L).
  • A network cable connected to the MGMT port of the OLT.
  • The iManager software installed on a computer.
  • A PC in the same IP range as the OLT’s management address.

Tip: Download the latest version of iManager from the official Intelbras website to avoid compatibility problems with new firmware versions.

2. Default IPs and credentials (field cheat sheet)

Fresh out of the box, many Intelbras devices come with factory defaults like these:

EquipmentDefault IPUserPassword
Intelbras OLT192.168.1.1adminadmin
Intelbras ONUGets IP via OLT / OMCIadminadmin

These are only starting points.
You should always:

  • Change admin/admin as soon as basic access is working.
  • Document the new password and store it in a safe place.
  • Move OLT management to a dedicated management VLAN in production.

3. Connecting the OLT in iManager

Let’s connect the OLT so iManager can control it.

3.1 Configure your PC IP

First, put your computer in the same network as the OLT management address.

Example configuration:

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

You can do this via the OS network adapter properties (Windows, Linux or macOS).

3.2 Add the device in iManager

  1. Open iManager.

  2. Click “Add Device” or the equivalent option.

  3. Fill in the form with the OLT data:

    • IP address: 192.168.1.1 (or the current management IP)
    • User: admin
    • Password: admin (factory default)

  4. Confirm and click Connect.

If everything is correct, the OLT will appear in the device list and show as online.

Note: If you can’t connect, double-check firewall rules on your PC, confirm the cable is in the MGMT port, and ping the OLT IP to rule out basic connectivity issues.

4. Discovering and registering ONUs via iManager

With the OLT online in iManager, it’s time to let it “see” the ONUs on the PON ports and properly register them.

4.1 Open the ONU discovery screen

Inside iManager, go to:

GPON → ONU Management → Discovery

On this screen, all ONUs connected to the optical ports but not yet registered will appear as Unregistered (or similar wording depending on firmware).

4.2 Connect the ONUs physically

  1. Connect Intelbras ONUs to the OLT PON ports via fiber.
  2. Wait a few seconds for the discovery process.

Each detected ONU should pop up in the Discovery list as an unregistered device.

If no ONUs show up:

  • Check the optical power levels and cleanliness of connectors.
  • Confirm the ONU model is compatible.
  • Make sure you’re looking at the correct PON port in iManager.

4.3 Register the ONUs and choose the service mode

For each unregistered ONU:

  1. Right-click the ONU entry.

  2. Select “Register ONU”.

  3. Choose the desired service mode, for example:

    • OMCI – The OLT controls service profiles (VLAN, bandwidth, etc.) using OMCI.
    • Bridge – The ONU acts primarily as a bridge; the router behind it handles PPPoE and routing.

  4. Configure the main parameters:

    • Data VLAN (e.g. 10 or the VLAN used in your design)
    • Optional voice VLAN (e.g. 20)
    • Bandwidth profile (upstream/downstream limits)
    • Description (customer name, address, contract ID, etc.)

  5. Click Apply or OK to confirm.

The ONU will move from Unregistered to Registered, and iManager will push the chosen profile to it.

Warning: Take extra care when editing shared templates or profiles. A wrong VLAN ID or bandwidth value applied to a common profile can break the service of dozens—or hundreds—of customers in one move.

5. Monitoring ONU status and saving configuration

Provisioning is just half the job.
You also need to keep an eye on the network and make sure your changes survive a reboot.

5.1 Check ONU status

In iManager, open the status section, usually:

Status → ONU Status or similar.

Here you can:

  • See which ONUs are Online or Offline.
  • Verify the PON and port where they are connected.
  • Check for alarms, flaps, or abnormal conditions.

Use this screen to confirm that newly registered ONUs are actually up and talking to the OLT.

5.2 Save the current configuration

Most Intelbras OLTs separate the running configuration (in RAM) from the saved configuration (in flash).

If you don’t save, a simple reboot can wipe out all your recent work.

In iManager:

  1. Go to System → Save Configuration or equivalent.
  2. Confirm that you want to persist the changes.

Tip: Make it a habit to save after every batch of changes—especially after mass ONU registration or big profile edits.

6. Where iManager ends and MKController begins

iManager is great at local OLT management:

  • It talks the right protocol.
  • It understands Intelbras GPON features.
  • It gives you a friendly interface for discovery and provisioning.

But as the network grows, you’ll feel some gaps:

  • Each OLT is managed separately.
  • There’s no global view of availability across sites.
  • Alerts and monitoring are limited to what runs near the OLT.
  • Remote access may depend on static IPs or port forwarding.

That’s where MKController and NATCloud come into play.

6.1 Centralizing OLT and ONU visibility with MKController

With MKController you can:

  • Integrate multiple Intelbras OLTs and ONUs into a single dashboard.
  • Get automatic disconnection alerts without babysitting every device.
  • Monitor availability and performance via SNMP, even without public IPs on all sites.
  • Track inventory and correlate devices with real customers and links.

6.2 Reaching devices behind NAT and CGNAT with NATCloud

Some networks have OLTs and other equipment behind:

  • Simple NAT
  • Double NAT
  • CGNAT from the provider

In these cases, classic remote access based on “just open a port” doesn’t scale—and often isn’t even possible.

NATCloud solves this by:

  • Creating outbound tunnels from the site to MKController.
  • Allowing technicians to access OLTs, routers and other gear without exposing ports.
  • Working even when there is no public IP directly assigned to the device.

Instead of juggling VPNs, port forwarding and spreadsheets of IPs, you:

  • Provision locally with iManager, where it shines.
  • Monitor, access and automate globally with MKController + NATCloud.

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.