OLT GPON for ISPs — Huawei, ZTE, FiberHome, Datacom, Parks, Nokia

OLT misconfigured means mass subscriber drops, silent optical alarms and ONU that provisions but does not deliver traffic. We configure, troubleshoot and monitor — monthly plan.

Supported OLT platforms

We work with any GPON OLT. The ones we operate day to day are Huawei, ZTE, FiberHome, Datacom, Parks and Nokia. Each has its own CLI, alarm model and VLAN behavior — experience with one does not automatically transfer to another.

  • Huawei MA5800-X7, X15 and X17: the most complete platform on the market, with granular QoS per DBA, detailed optical alarms and advanced VLAN configuration. High complexity; configuration errors have widespread impact.
  • ZTE C320 and C600: good cost-benefit for growing ISPs. ZTE CLI has significant differences from Huawei — provisioning a port wrong here causes subtler failures that show up under load.
  • FiberHome AN5516: common in regional ISPs; less documentation available in English. We have practical experience troubleshooting without vendor support.
  • Datacom DM4615 / DM4610: Brazilian OLTs with strong adoption among regional ISPs. DmOS CLI. Straightforward provisioning and documentation in Portuguese.
  • Parks Fiberlink: Brazilian product line present in small and mid-size ISPs. Local support and competitive cost.
  • Nokia 7360 ISAM FX: carrier-grade platform, found in larger networks and enterprise segments. ISAM CLI. High configuration granularity.

ONU provisioning: templates, profiles and manual optimization

We work with optimized manual provisioning using templates and automation via scripts. We do not promise deep ERP-integrated auto-provisioning with zero touch — the scope is OLT configuration and the technical layer between the OLT and the network, not CRM or billing integration.

  • Service profile and line profile configuration per subscriber type (residential, business)
  • Template-based provisioning scripts to reduce operator error
  • ONU type registration in the OLT and validation of T-CONT/GEM port
  • Optical signal level check on provisioning (RX power within acceptable range)

VLAN and service flow configuration

GPON VLAN architecture determines how subscriber traffic is segregated and what reaches the B-RAS/BNG. A poorly designed VLAN can cause inter-subscriber traffic leakage, routing loops and QoS that does not work as expected.

  • VLAN design per service type (internet, IPTV, VoIP) per OLT
  • SVLAN/CVLAN (QinQ) configuration for large-scale environments
  • Trunk port validation between OLT and aggregation switch
  • Traffic inspection to confirm that subscriber VLAN is properly reaching the B-RAS

Optical alarm monitoring and preventive action

Optical alarms (LOS, LOF, LOSi, LOFi) are the first sign of problems — dirty connectors, fiber bending, splitter degradation. The OLT records them all, but few ISPs actually read them proactively. We set up monitoring so alerts reach the NOC before the subscriber calls.

  • Zabbix SNMP/Telnet integration to collect optical RX power per ONU
  • Alert thresholds calibrated per platform and cable type
  • LOS history correlated with subscriber tickets to identify systematic problems
  • Preventive identification of ONUs with degraded but still operating signal (pre-failure)

OLT troubleshooting in production

Mass subscriber drops on an OLT chassis have multiple possible causes: PON card failure, OLT software bug after update, incorrect DBA configuration causing T-CONT starvation, or upstream switch with flapping trunk. We diagnose systematically without guessing.

  • Reading of OLT logs and alarm history (not just "what's in the display now")
  • Traffic isolation per PON port to confirm scope of impact
  • DBA and GEM port review for problematic ONUs
  • Firmware upgrade planning when OLT bug is confirmed

OLT expansion and multi-chassis environments

Adding a new OLT chassis or expanding an existing one without planning causes transient drops and provisioning inconsistencies. We plan expansions so the operational impact is minimal.

  • New OLT configuration before putting it in production
  • NNI port configuration and integration with the aggregation layer
  • Service profile and template replication from the existing OLT
  • Subscriber migration between OLTs or between PON ports with minimum downtime

How we work and how to get started

We work on a monthly plan — no one-off projects and no hourly-rate diagnostics. The first conversation is at no cost: we call, you share an AnyDesk session and show us the OLT live while we share observations. If it makes sense for both sides, we close the monthly plan and go from there. Full admin access from the start — we need it to work effectively.

Talk to us — initial conversation, no commitment. See also: Zabbix monitoring, 24x7 NOC.

FREQUENTLY ASKED QUESTIONS

How does the work start with you?

The first conversation is at no cost. You reach out, we call, you open an AnyDesk session and show us the OLT live. We share observations on the current configuration, alarm state and provisioning flow. If it makes sense for both sides, we close the monthly plan and start the following week.

Do you do zero-touch auto-provisioning integrated with ERP?

We work with optimized manual provisioning using templates and automation via scripts. Deep zero-touch integration with ERP or CRM is outside our scope — our work is at the OLT configuration and network layer, not billing system integration.

Do you work with OLTs from other vendors?

We work with any GPON OLT. Day to day we operate Huawei, ZTE, FiberHome, Datacom, Parks and Nokia — those we know in depth. Less common vendors are not a problem: GPON fundamentals are the same across vendors, what changes is the CLI and profile structure. If we have not handled that specific model yet, we read the manual and operate.

Do you charge a setup or onboarding fee?

No. The monthly plan covers everything: initial configuration, adjustments, monitoring and continuous support.

How long does it take to have monitoring working?

Basic optical alarm monitoring via Zabbix: 2 to 5 business days after closing the plan, depending on OLT access and SNMP MIB availability. Full configuration with calibrated thresholds and integrated dashboards: typically up to 2 weeks.