BDCOM OLT ONU Offline Fix (Step-by-Step Troubleshooting Guide 2026)

If you’re an ISP engineer or fiber technician staring at an offline ONU on your BDCOM OLT dashboard, you’re in the right place. ONU offline issues are one of the most common — and most frustrating — problems in GPON networks. Whether it’s a sudden fiber cut, a power loss, an authentication mismatch, or a bad splitter, this guide walks you through every possible cause and fix with real CLI commands you can run right now.

When a BDCOM ONU goes offline, your customer loses internet, phone, or IPTV service instantly. The OLT registers the ONU as “inactive” or “deregistered,” and without the right diagnostic approach, you can waste hours chasing the wrong problem. This step-by-step BDCOM OLT ONU offline fix guide is built from real-world ISP engineer experience, official BDCOM documentation, and GPON community troubleshooting knowledge — updated for 2026.

Let’s start by understanding what “ONU Offline” actually means and then systematically work through every fix.

📖 What does “ONU Offline” mean?
In a BDCOM GPON network, an ONU (Optical Network Unit) goes “offline” when the OLT can no longer communicate with it. The ONU disappears from the active ONU list and is shown as inactive, deregistered, or with a deactivation reason such as LOSI (Loss of Signal Indication) or Dying Gasp. This breaks the subscriber’s service entirely.

Common Causes of BDCOM ONU Offline

Before running a single command, it helps to know why ONUs go offline. In our experience, most BDCOM GPON ONU offline events fall into one of these categories:

#CauseDeactive Reason ShownLikely Fix
1Fiber cut or breakageLOSISplice / replace fiber
2ONU power failureDying GaspRestore ONU power supply
3High fiber attenuationLOSICheck dBm, clean connectors
4Authentication mismatch (SN/password)Auth FailRe-register ONU with correct SN
5ONU deregistered (manual/auto)DeregisteredRe-bind ONU on OLT interface
6PON port issue / SFP module faultLOSIReseat SFP, check PON port
7Dirty or damaged fiber connectorLOSIClean connector, replace patch cord
8Splitter port failureLOSITest each splitter port individually
9Wrong VLAN or service profile configConfig ErrorVerify ONU profile & VLAN binding
10OLT firmware bugIntermittentUpgrade OLT firmware
⚡ Pro Tip Always check the Deactive Reason first using show gpon interface gpON 0/X:Y onu basic-info. LOSI = physical fiber problem. Dying Gasp = power-side problem. This single distinction saves you 30 minutes of wrong-path troubleshooting every time.

How to Check ONU Offline Status — BDCOM CLI Commands

These are the essential BDCOM OLT commands for diagnosing any BDCOM ONU offline troubleshooting scenario. Run them in order for a complete picture.

1. View All ONU Status (Active + Inactive)

# Show all registered ONUs and their status on a PON port Switch# show gpon onu-information interface gpON 0/1# Output example: GPON0/1:1 SN: BDCM12345678 Status: Active Auth: OK GPON0/1:2 SN: BDCM87654321 Status: Inactive Auth: OK GPON0/1:3 SN: BDCM11223344 Status: Offline Auth: FAIL

The Status column immediately tells you which ONUs are down. Auth: FAIL points to a serial number or password mismatch.

2. Check a Specific ONU’s Deactivation Reason

# Replace 0/1:2 with your actual PON port:ONU ID Switch# show gpon interface gpON 0/1:2 onu basic-info# Sample output for offline ONU: ONU index : GPON0/1:2 ONU SN : BDCM87654321 ONU state : inactive Deactive reason : losi # ← LOSI = Fiber cut/signal lost Last up time : 2026-05-20 14:32:11 Last down time : 2026-05-21 08:15:44

Key deactivation reasons and their meanings:

Deactive ReasonMeaningAction Required
losiNo optical signal received — fiber cutInspect fiber path, splitter, connectors
dying-gaspONU sent power-off notification — ONU lost powerCheck ONU power supply
deregisteredONU was manually or automatically removedRe-register ONU on OLT
auth-failSerial number / password doesn’t matchCorrect ONU SN in OLT config
lost-omciOMCI management channel lostReboot ONU, check firmware

3. Check Optical Power Levels

# Check ONU optical power (ONU → OLT direction) — GPON Switch# show gpon optical-transceiver-diagnosis interface gPON 0/1:2# Check all ONU power levels on a PON port Switch# show gpon onu-optical-transceiver-diagnosis interface gpON 0/1# Check PON port TX/RX (OLT side) Switch# show gpon optical-transceiver-diagnosis interface gPON 0/1# Sample output: Interface : GPON0/1:2 Rx Power : -26.4 dBm # Approaching threshold (-27 dBm limit) Tx Power : 2.3 dBm Temp : 42 C Voltage : 3.28 V

4. Check PON Port Interface Status

Switch# show interface gpON 0/1# Shows PON port up/down state, error counters, optical SFP status GigabitEthernet 0/1 is up, line protocol is up Hardware is GPON, address is 00:1a:2b:3c:4d:5e MTU 1500 bytes, BW 2488320 Kbit Input errors: 0, CRC: 0, Frame: 0

5. Check Active Alarms

Switch# show alarm# Or check interface-specific alarms: Switch# show gpon alarm-info interface gpON 0/1

6. Find ONU by MAC Address

# Find ONU using last 4 digits of MAC Switch# show mac address-table | include 0AF9# Show MAC table on a specific ONU Switch# show mac address-table interface gpON 0/1:2

7. Check Full OLT Running Config

Switch# show running-config# Or view a specific interface config: Switch# show running-config interface gpON 0/1

Step-by-Step BDCOM OLT ONU Offline Fix

Follow these steps in order. Each step builds on the last — don’t skip ahead. This is how experienced ISP engineers fix BDCOM GPON ONU offline issues systematically.

1

Check ONU Power Supply

The simplest cause is often a power failure at the ONU. Check if the ONU has power (LEDs lit), the adapter is working, and the power outlet is functional. If Dying Gasp is shown in the deactivation reason, this is your answer.

# Confirm Dying Gasp (power loss) on OLT Switch# show gpon interface gpON 0/1:2 onu basic-infoDeactive reason : dying-gasp # ✓ ONU lost power — fiber is fine
⚡ Pro Tip Dying Gasp means the fiber link is intact. The ONU sent a “goodbye” signal before powering down. Don’t touch the fiber — go check the ONU’s power adapter and electrical outlet first.
2

Check LOS / PON LED on ONU

A solid or blinking red LOS (Loss of Signal) LED on the ONU means it’s not receiving an optical signal from the OLT. This points to a physical fiber problem — not a configuration issue. Proceed to Step 3.

ONU LED StateMeaningNext Action
LOS = Red (solid)No optical signalCheck fiber path, splitter
PON = Blinking greenTrying to registerCheck auth/SN config
PON = Solid greenRegistered successfullyCheck VLAN/service config
All LEDs offNo powerCheck power supply
3

Inspect the Fiber Cable Path

Physically trace the fiber route from the ONU to the OLT. Look for sharp bends (minimum bend radius is 30mm for standard single-mode fiber), crushed or pinched sections, rodent damage, and loose connections at patch panels and splice boxes.

⚠️ Fiber Safety Warning Never look directly into a fiber connector or cable end — even if you think it’s inactive. The 1490nm/1310nm wavelengths used in GPON are invisible to the human eye but can cause permanent eye damage. Always use a fiber optic power meter or visual fault locator (VFL) with proper eye protection. Use a fiber inspection scope or camera to check connectors.
4

Clean Fiber Connectors

Dirty connectors are responsible for more than 30% of optical link problems in the field. Even microscopic dust on an SC/APC or SC/UPC connector can cause 1–3 dB of signal loss, pushing you past the -27 dBm threshold.

Connector cleaning procedure:

  1. Use a fiber inspection microscope or endface camera to view the connector face
  2. If dirty, use a one-click cleaner (Fujikura, Cletop, or equivalent) for SC connectors
  3. For patch panel adapters, use a cassette cleaner stick
  4. Re-inspect after cleaning before reconnecting
  5. Reconnect firmly — SC connectors should click into place
⚡ Pro Tip Always clean both ends of a connector — the plug AND the adapter/port. Cleaning only one side and mating it with a dirty surface defeats the purpose completely.
5

Verify ONU Authentication (Serial Number)

If the fiber is physically fine but the ONU still won’t come online, check authentication. The ONU serial number (SN) registered on the OLT must exactly match the physical ONU’s SN label.

# Step 1: Find unregistered ONUs (auto-detected but not yet bound) Switch# show gpon onu-information interface gpON 0/1# Step 2: Check what SN is currently configured on an interface Switch# show gpon interface gpON 0/1:2 onu basic-infoONU SN : BDCM12345678 Auth status : auth-fail # SN mismatch!# Step 3: Check what SN the physical ONU is broadcasting # (Look for auto-discovered SNs in the unregistered list) Switch# show gpon onu-information interface gpON 0/1
6

Re-register the ONU

If the ONU was deregistered or the SN doesn’t match, you need to re-bind the ONU on the correct GPON interface. This is the most common fix ONU offline BDCOM OLT procedure for authentication-related issues.

# Enter global config mode Switch# config# Navigate to the specific GPON interface:ONU-ID Switch_config# interface gpON 0/1:2# Register ONU by serial number (replace SN with actual ONU SN) Switch_config_gpon0/1:2# gpon onu sn BDCM87654321# Optionally assign VLAN profile Switch_config_gpon0/1:2# gpon onu uni 1 vlan-profile 200# Exit and save Switch_config_gpon0/1:2# exit Switch_config# exit Switch# wr all# Verify ONU came online: Switch# show gpon interface gpON 0/1:2 onu basic-infoONU state : active # ✅ Online!
7

Restart the ONU Remotely

Sometimes the ONU needs a remote reboot to clear a stuck state, recover from a firmware hang, or re-negotiate the GPON handshake. BDCOM OLT allows you to reboot individual ONUs without a physical site visit.

# Reboot a single ONU remotely (GPON) Switch# config Switch_config# interface gpON 0/1:2 Switch_config_gpon0/1:2# gpon onu reboot# For EPON models: Switch_config_epon0/1# epon onu reboot onu-id 4# Wait 60–90 seconds, then verify: Switch# show gpon interface gpON 0/1:2 onu basic-info
⚡ Pro Tip After a remote reboot, wait at least 60–90 seconds before running the verification command. GPON registration (PLOAM handshake) takes time, especially on long-distance fiber runs up to 20km.
8

Check Optical Power Levels (dBm)

If the ONU keeps dropping offline intermittently, weak optical signal is the likely culprit. Use these commands to check the exact RX power levels and compare against acceptable thresholds.

# Check specific ONU optical power (ONU TX → OLT RX) Switch# show gpon optical-transceiver-diagnosis interface gPON 0/1:2Interface : GPON0/1:2 Rx Power : -25.8 dBm # ⚠️ Getting close to -27 dBm limit Tx Power : 2.1 dBm Temperature : 44°C Voltage : 3.30V# Check ALL ONUs on a PON port at once Switch# show gpon onu-optical-transceiver-diagnosis interface gpON 0/1# Check OLT PON port optical module (OLT TX power) Switch# show gpon optical-transceiver-diagnosis interface gPON 0/1
Power LevelRangeStatusAction
ONU RX (acceptable)-8 to -27 dBmNormalNo action needed
ONU RX (marginal)-25 to -27 dBmWarningClean connectors, check splitter
ONU RX (critical)Below -27 dBmCriticalONU will go offline — fix fiber path
OLT TX power+1.5 to +5 dBmNormalNo action needed
OLT TX power (low)Below +1.5 dBmSFP issueReplace OLT SFP module
9

Check Splitter Faults

A faulty splitter port is one of the trickiest problems to diagnose because it affects only specific ONUs while others on the same PON port remain online. If only a subset of ONUs on one PON port are offline, suspect the splitter first.

# Check which ONUs are offline on PON 0/1 Switch# show gpon onu-information interface gpON 0/1# If ONUs 3, 7, 11 are offline but 1,2,4,5,6 are fine: # → Suspect a specific splitter output port fault # → Check the fiber from splitter output to each ONU # → Use an OTDR to pinpoint break location# If ALL ONUs on PON 0/1 are offline: # → Check OLT PON port, feeder fiber, or first-stage splitter Switch# show interface gpON 0/1

Splitter troubleshooting logic:

  • 1 ONU offline, rest OK → Check that ONU’s drop fiber and connector
  • Group of ONUs offline → Check the 2nd-stage splitter serving that group
  • All ONUs on a PON port offline → Check feeder fiber or 1st-stage splitter
  • All PON ports affected → Check OLT uplink, power, or chassis issue
10

Upgrade OLT Firmware (If Intermittent/Unexplained)

If ONUs keep dropping offline without any clear physical or configuration cause — especially after a recent change — a firmware bug on the OLT may be responsible. BDCOM regularly releases firmware updates that fix ONU management and stability issues.

# Check current OLT firmware version Switch# show version# Sample output: BDCOM OS Software, Version 10.3.0D Build 65417 Copyright (c) 2004-2026 by BDCOM# Upload new firmware via TFTP Switch# copy tftp://192.168.1.100/bdcom-firmware-v10.3.1.bin flash:# Set boot image and reload (schedule during maintenance window!) Switch_config# boot system flash bdcom-firmware-v10.3.1.bin Switch# reload
⚠️ Important Always perform firmware upgrades during a scheduled maintenance window. A failed firmware upgrade can render the OLT unresponsive. Keep a console cable connected during upgrades and always have a rollback plan with the previous firmware version saved to flash.

ONU Offline vs Dying Gasp — Key Differences Explained

This is one of the most misunderstood distinctions in BDCOM GPON troubleshooting. Getting this right saves enormous time.

FeatureDying GaspLOSI (ONU Offline)
BDCOM Deactive Reasondying-gasplosi
What happenedONU sent a power-off notification before going offlineOLT received no signal at all — abrupt disconnection
Fiber StatusFiber is intact ✓Fiber likely cut or signal lost ✗
ONU StatusONU powered off (intentional or power failure)ONU may be powered on but receiving no signal
Root CausePower outage, adapter failure, ONU shutdownFiber cut, dirty connector, weak signal, splitter fault
First ActionCheck ONU power supply and adapterCheck fiber path, measure optical power
Standard definedITU-T G.984 (GPON standard)ITU-T G.984 LOSi alarm
Quick Memory Rule:
Dying Gasp = “ONU said goodbye” → Power problem → Check electrical supply
LOSI = “ONU disappeared silently” → Fiber/signal problem → Check physical path

Preventing Future BDCOM ONU Offline Issues

A proactive approach to network maintenance dramatically reduces BDCOM ONU offline incidents. Here’s what field engineers recommend:

Network Monitoring & Documentation

  • Enable SNMP traps on your BDCOM OLT to get instant alerts when an ONU goes offline — don’t wait for customer complaints
  • Document every ONU’s installed location, SN, and PON port ID in a spreadsheet or NMS system
  • Set optical power baseline readings when ONUs are first installed — this gives you a reference for future comparisons
  • Use a Network Management System (NMS) to track ONU uptime history and identify repeat offenders

Physical Infrastructure Best Practices

  • Schedule connector cleaning every 6–12 months, especially in dusty or industrial environments
  • Use SC/APC connectors (green) for GPON — they outperform SC/UPC in back-reflection performance
  • Protect outdoor fiber with proper weatherproof enclosures and figure-8 messenger wire
  • Maintain a minimum bend radius of 30mm — never kink or loop fiber tightly
  • Keep spare patch cords, splitter modules, and ONU units on-site for fast replacement

OLT Configuration Best Practices

# Always save configuration after any change Switch# wr all# Set up syslog for event tracking Switch_config# logging host 192.168.1.50 Switch_config# logging trap informational# Enable dying gasp logging Switch_config# gpon dying-gasp enable# Verify ONU authentication mode Switch# show gpon onu-authen-method interface gpON 0/1
⚡ Pro Tip Install a cheap UPS (Uninterruptible Power Supply) at OLT and critical aggregation points. Power micro-cuts lasting less than a second can cause mass ONU deregistration events that take minutes to recover, even though the fiber is perfectly fine.

Frequently Asked Questions — BDCOM ONU Offline Troubleshooting

❓ Why does my BDCOM ONU go offline repeatedly?
Repeated BDCOM ONU offline events are almost always caused by one of these: (1) marginal optical power levels hovering near the -27 dBm threshold — small temperature changes push it over, (2) a dirty or intermittently connected fiber connector, (3) a failing splitter port, (4) an ONU with a failing optical transceiver, or (5) an OLT firmware bug. Run show gpon optical-transceiver-diagnosis interface gPON 0/1:X and compare power levels across multiple times of day. If they fluctuate, you have a physical problem.
❓ How do I re-register an ONU in BDCOM OLT?
To re-register an ONU: Enter config mode → navigate to the correct GPON interface → use gpon onu sn [SERIAL_NUMBER] to bind it → assign the appropriate VLAN profile → save with wr all. See Step 6 above for the complete command sequence with examples.
❓ What is the normal optical power level for BDCOM GPON ONU?
The acceptable ONU RX optical power range for BDCOM GPON is -8 dBm to -27 dBm. Readings between -8 and -20 dBm are excellent. Between -20 and -25 dBm is acceptable but worth monitoring. Below -27 dBm, the ONU will go offline. OLT TX power should be between +1.5 and +5 dBm. Use show gpon optical-transceiver-diagnosis interface gPON 0/1:X to check.
❓ How do I check an ONU serial number in BDCOM OLT?
Use: Switch# show gpon interface gpON 0/1:2 onu basic-info — this shows the ONU SN registered on the OLT. To find newly discovered but unregistered ONUs (auto-detected by the OLT), use: Switch# show gpon onu-information interface gpON 0/1 and look for entries with “unauthorized” or no binding. You can also find the SN on a sticker on the physical ONU device.
❓ What does “Deactive Reason: LOSI” mean in BDCOM?
LOSI stands for Loss of Signal Indication. It means the OLT is not receiving any optical signal from the ONU on that PON port slot. This is a physical-layer problem — fiber cut, broken connector, dirty connector causing excessive loss, or a completely failed ONU laser module. Always inspect the fiber path when you see LOSI.
❓ Can I reboot an ONU remotely from BDCOM OLT without visiting the site?
Yes. Use: Switch_config_gpon0/1:2# gpon onu reboot from within the specific GPON interface in config mode. For EPON models, the command is epon onu reboot onu-id [X]. Wait 60–90 seconds after the reboot command before checking ONU status. This only works if the ONU still has power and a valid fiber connection — it won’t work if LOSI is active.
❓ How many ONUs can one BDCOM GPON PON port support?
BDCOM GPON OLT PON ports support up to 128 ONUs per PON port, though the recommended operational maximum for quality service is typically 64 ONUs at 1:64 splitting ratio. EPON ports support up to 64 ONUs. Exceeding these limits doesn’t cause offline issues per se, but degrades bandwidth per subscriber significantly.

BDCOM ONU Offline — Quick Reference Command Cheat Sheet

TaskBDCOM CLI Command
View all ONUs on a PON portshow gpon onu-information interface gpON 0/1
Check specific ONU state & deactive reasonshow gpon interface gpON 0/1:2 onu basic-info
Check ONU optical RX/TX powershow gpon optical-transceiver-diagnosis interface gPON 0/1:2
Check all ONU power on a PONshow gpon onu-optical-transceiver-diagnosis interface gpON 0/1
Check PON port optical module (OLT side)show gpon optical-transceiver-diagnosis interface gPON 0/1
Find ONU by MAC addressshow mac address-table | include [LAST4MAC]
Reboot ONU remotelygpon onu reboot (in interface config mode)
Register ONU by serial numbergpon onu sn BDCMXXXXXXXX (in interface config mode)
Check active alarmsshow alarm
Check OLT firmware versionshow version
Save configurationwr all
View running configshow running-config
Check PON port interface statusshow interface gpON 0/1
Check ONU image/firmware infoshow gpon onu-image-information interface GPON0/1:2

Conclusion

Fixing a BDCOM OLT ONU offline issue doesn’t have to be a mystery. With a systematic approach — checking the deactivation reason first, then working from power → fiber → optics → authentication → configuration — you can diagnose and resolve 95% of ONU offline issues without escalating to vendor support.

The two most important commands in your arsenal are show gpon interface gpON 0/X:Y onu basic-info to identify the root cause, and show gpon optical-transceiver-diagnosis to assess the physical link quality. Everything else flows from those two diagnostics.

Bookmark this guide and share it with your team. If you found it helpful or have additional troubleshooting scenarios to add, drop a comment below — real field experience from ISP engineers is what makes guides like this genuinely useful.