Intelbras iOLT Cloud GPON Management

Summary Intelbras iOLT Cloud is a hosted browser console that manages an Intelbras GPON plant remotely — registering OLTs, auto-provisioning ONUs over OMCI, pushing VLAN and bandwidth profiles, watching optical signal, and running batch firmware upgrades. This guide covers the requirements, the OLT registration flow, ONU provisioning, monitoring patterns, and when MKController and NATCloud complement iOLT Cloud in multi-vendor networks.

How does iOLT Cloud manage Intelbras GPON networks?

Intelbras iOLT Cloud is the hosted command center for Intelbras GPON — a browser-based panel that registers compatible OLTs, discovers and provisions ONUs over OMCI, pushes service profiles in bulk, and monitors optical signal, bandwidth, and alarms across the plant. Instead of opening per-site VPNs, SSH-ing into each OLT individually, or clicking through ONU menus manually, you plug the OLT into the cloud once and operate everything through https://ioltc.intelbras.com.br.

The platform sits in the same family as Remotizze but is specifically engineered for ISP GPON workflows. It is strongest when the network is Intelbras-only — every OLT, every ONU, every PON port managed through a single console. In multi-vendor networks (Intelbras alongside Huawei, ZTE, or FiberHome), iOLT Cloud handles the Intelbras layer cleanly while a higher-level orchestration tool such as MKController unifies cross-vendor visibility.

Requirements

Three prerequisites have to be in place before iOLT Cloud is useful:

A compatible Intelbras OLT. The 8820G, 8820L, and 8840G are the typical iOLT Cloud-ready models. Check the firmware version against the current iOLT Cloud compatibility matrix on the Intelbras portal.

Active internet, DNS, and NTP on the OLT. The OLT initiates outbound connections to Intelbras cloud endpoints — these need clean DNS resolution and accurate time for TLS handshakes.

An Intelbras Cloud account. Register at https://ioltc.intelbras.com.br, confirm by email, and you have a dashboard ready to receive OLTs.

Default OLT credentials

Factory defaults for most Intelbras OLTs:

Equipment	Default IP	User	Password
Intelbras OLT	192.168.1.1	admin	admin

Change the default password as soon as basic connectivity works, move the management IP into a documented management VLAN, and restrict which networks can reach the management interface. Defaults left in place are a recurring source of incidents.

Step 1: Register the OLT in iOLT Cloud

In the iOLT Cloud panel, click Add OLT and enter the Serial Number (S/N) of the device. The serial is on a sticker on the chassis and also visible in the local interface under system information. After clicking save, the cloud is waiting for that OLT to check in — the next step happens on the OLT itself.

Step 2: Enable Cloud mode on the OLT

Locally:

1. Connect a PC to the MGMT port of the OLT.
2. Set the PC IP to 192.168.1.10/24.
3. Open http://192.168.1.1 and log in with admin / admin (or whatever you changed it to).
4. Navigate to Network → Cloud / iOLT.
5. Enable Cloud mode (typically a checkbox labeled “Enable Cloud”).
6. Save and apply.

If internet and DNS are healthy, the OLT appears in the iOLT Cloud panel within a minute with status Online or Connected. If it doesn’t show up, the cause is almost always one of four things: blocked internet access on the management uplink, broken DNS resolution, an inaccurate clock breaking the TLS handshake, or a firewall between the OLT and Intelbras’s cloud endpoints. Check those before re-running the registration.

Step 3: Provision ONUs remotely

With the OLT connected, ONU provisioning happens entirely from the cloud panel — no need to touch the local interface.

Discover the ONUs. Under ONUs → Discovered (or Pending), connect ONUs to the OLT PON ports in the field. New ONUs appear within a few seconds as discovered or unprovisioned. If they don’t show up, check optical signal and connector cleanliness first, verify the ONU model is compatible and powered, and confirm you’re viewing the correct OLT and PON.

Provision and apply service profiles. For each discovered ONU, click Provision and fill in:

• ONU name — customer name, address, or identifier.
• Service VLANs — data VLAN, voice VLAN, IPTV VLAN as needed.
• Bandwidth profile — download and upload rate limits.
• Location — optional but very useful when troubleshooting later.

Save the configuration. The OLT pushes the profile to the ONU over OMCI and the ONU transitions to provisioned and online.

Be disciplined with naming and profile structure from day one. Ad-hoc labels and improvised VLAN combinations turn into an unmanageable GPON jungle by the time the plant grows past a few hundred ONUs.

Step 4: Monitor and manage from the cloud

Once ONUs are provisioned, iOLT Cloud becomes the main console for plant operations:

• Bandwidth usage in near real-time, per ONU and per PON port.
• Optical signal per ONU and per PON — the leading indicator of fiber degradation.
• Alarms for loss of signal, high error rates, or unexpected reboots.
• Batch firmware upgrades for selected OLTs and ONUs.
• Availability reports exportable as CSV or PDF for customer SLAs and internal review.

For firmware specifically: always test new firmware on a small pilot group of devices first, schedule rollouts during off-peak windows, and keep a record of versions per device or per site. Firmware upgrades are the most powerful feature and the most dangerous — discipline pays for itself the first time it saves you from a fleet-wide regression.

For complementary remote-access patterns when iOLT Cloud isn’t enough, see our TR-069 management guide and the Intelbras OMCI FTTH guide.

Where MKController complements iOLT Cloud

iOLT Cloud excels in the Intelbras-only GPON world. Most real networks are multi-vendor — Intelbras OLTs alongside Huawei, ZTE, or FiberHome plant; MikroTik or Cisco routers providing BRAS or PPPoE; access switches and Wi-Fi gear from multiple manufacturers. iOLT Cloud doesn’t reach across those vendor boundaries.

MKController does. It monitors Intelbras, Huawei, ZTE, FiberHome, MikroTik, and others in one dashboard, tracking uptime, ping, packet loss, and cross-vendor correlations. It discovers equipment via SNMP, LLDP, and CDP, so you see GPON health in context with upstream router, core switch, and CPE status — not in isolation.

NATCloud handles the cases where the OLT or surrounding equipment sits behind CGNAT, double NAT, or a policy that forbids opening ports. It creates secure outbound tunnels from the customer site to MKController, enabling technician access without port forwarding, even when ISP addressing changes underneath you.

Start your free MKController trial