Intelbras OLT Management with iManager

Summary iManager is Intelbras’s local management software for OLTs and GPON networks — the tool that lets you discover, register, and provision ONUs without logging into each OLT through the CLI. This guide covers the prerequisites, the OLT connection flow in iManager, ONU discovery and registration with OMCI or bridge mode, service profile application, status monitoring, and the discipline of saving configuration so changes survive a reboot.

How does iManager manage Intelbras OLTs?

iManager is Intelbras’s Windows-based management software for GPON OLTs. It connects to an OLT over the management network, discovers the ONUs attached to the PON ports, and provisions them with VLAN, bandwidth, and service profiles using OMCI (or bridge mode for setups where the customer router handles PPPoE and routing). Instead of running CLI commands per OLT, you operate a graphical interface that understands Intelbras GPON features and pushes the right configuration in the right order.

The platform fits a specific niche cleanly: local operations on a single Intelbras OLT, with full feature coverage for ONU discovery, registration, and per-customer service profile management. It is not the right tool when you need a cloud-hosted browser console (that’s iOLT Cloud — see our iOLT Cloud guide), or when you need multi-vendor visibility across Intelbras alongside Huawei, ZTE, or MikroTik gear in a single dashboard.

Requirements

• An Intelbras OLT (8820G, 8820L, 8840G, or compatible model).
• An Ethernet cable connected to the OLT MGMT port.
• iManager installed on a Windows computer. Download the latest version from the official Intelbras website — older versions occasionally have compatibility gaps with new firmware.
• A PC configured with an IP in the OLT’s management subnet.

Default IPs and credentials

Equipment	Default IP	User	Password
Intelbras OLT	192.168.1.1	admin	admin
Intelbras ONU	Provisioned via OLT (OMCI)	admin	admin

Change the admin / admin password as soon as basic access works. Document the new credentials in your password manager — losing the OLT password on a production GPON plant is an expensive mistake. In production environments, move OLT management to a dedicated VLAN and restrict access to that VLAN at the upstream switch.

Step 1: Connect the OLT in iManager

Configure the PC IP

Put the PC on the OLT management subnet:

• IP: 192.168.1.10
• Netmask: 255.255.255.0
• Gateway: leave blank for direct-attached management

Do this through the Windows network adapter properties, or the equivalent on Linux/macOS.

Add the device in iManager

1. Open iManager.
2. Click Add Device (or equivalent).
3. Enter the OLT data: IP address (192.168.1.1 or current management IP), username (admin), password (factory admin or whatever you set).
4. Click Connect.

The OLT appears in the device list with status Online. If it doesn’t, check the obvious things first: host firewall blocking outbound, cable in the right port (MGMT, not a PON), and basic ICMP reachability with ping 192.168.1.1.

Step 2: Discover and register ONUs

With the OLT online in iManager, the ONUs need to be discovered and registered before they can provide service.

Open the discovery screen

Navigate to GPON → ONU Management → Discovery. ONUs connected to the OLT’s PON ports but not yet registered appear as Unregistered.

Connect the ONUs

Plug each Intelbras ONU into a PON port via fiber and wait a few seconds. Each detected ONU pops up in the Discovery list. If no ONUs appear, check optical power levels and connector cleanliness first, then verify the ONU model is compatible, and finally confirm you’re viewing the correct PON port in iManager.

Register and choose service mode

For each unregistered ONU:

1. Right-click the entry and select Register ONU.
2. Choose the service mode:
   • OMCI — the OLT controls service profiles (VLAN, bandwidth) using OMCI. Use this for end-customer ONUs where the OLT owns the service definition.
   • Bridge — the ONU acts purely as a Layer-2 bridge and the customer router (usually doing PPPoE) handles all logic above.
3. Configure the main parameters:
   • Data VLAN (e.g., 10)
   • Optional voice VLAN (e.g., 20)
   • Bandwidth profile (upstream/downstream rate limits)
   • Description — customer name, address, contract ID
4. Click Apply or OK.

The ONU transitions from Unregistered to Registered, and iManager pushes the chosen profile to it. Take extra care editing shared templates or profiles — a wrong VLAN ID or bandwidth value applied to a common profile can break service for hundreds of customers in one click.

Step 3: Monitor and save the configuration

Provisioning is half the job. Status monitoring catches problems early, and persisting the config protects you from losing work on the next reboot.

Check ONU status

Open Status → ONU Status (or the equivalent under your iManager version). The screen lists every ONU as Online or Offline, shows which PON and port each is connected to, and surfaces alarms and link flaps. Use it to confirm newly registered ONUs are actually up.

Save the running configuration

Most Intelbras OLTs separate the running configuration (in RAM) from the saved configuration (in flash). If you don’t save, a reboot wipes recent work.

In iManager: System → Save Configuration → confirm. Make saving a reflex after every batch of changes — especially after mass ONU registration or profile edits.

Where iManager ends and MKController begins

iManager is excellent at local OLT management — it speaks Intelbras GPON natively and gives you a friendly interface for discovery and provisioning. The limits show up as the network grows: each OLT is managed separately, there’s no global availability view across sites, alerts and monitoring are limited to what runs near each OLT, and remote access often depends on static IPs or port forwarding.

That’s where MKController and NATCloud complement iManager. MKController integrates multiple Intelbras OLTs and ONUs into a single dashboard, sends automatic disconnection alerts without per-device babysitting, monitors availability and performance via SNMP even without public IPs at every site, and tracks inventory correlated with real customers. For the cloud-native browser-console alternative to iManager, see our iOLT Cloud guide and the TR-069 management guide.

NATCloud handles the case where OLTs and other equipment sit behind simple NAT, double NAT, or CGNAT. It creates outbound tunnels from the customer site to MKController, allowing technicians to reach OLTs, routers, and other gear without exposing ports — even when there’s no public IP directly assigned to the device. The combined pattern works: provision locally with iManager where it shines; monitor, access, and automate globally with MKController plus NATCloud.

Start your free MKController trial