What is the default IP address of BDCOM OLT?

BDCOM EPON OLT default IP is 172.16.0.1. BDCOM GPON OLT default IP is 192.168.1.1. Default login is admin/admin.

What are the console settings for BDCOM OLT?

Use PuTTY with Serial connection. Settings: Baud 9600, Data bits 8, Parity None, Stop bits 1, Flow control None. Login with admin/admin.

How to save config on BDCOM OLT?

Use 'write all' from privileged mode. Wait for 'successfully wrote' confirmation. Never just reboot without saving or all changes will be lost.

Why is my ONU not registering on BDCOM OLT?

Check: PON port is not shutdown, optical RX power is above -28 dBm, fiber connectors are clean, ONU authentication mode, and that the PON port VLAN is configured correctly.

How to check optical power on BDCOM OLT?

For EPON: show epon optical-transceiver-diagnosis interface epON 0/1. For GPON: show gpon onu-optical-transceiver-diagnosis interface gpON 0/1. Normal range is -8 to -28 dBm.

How many ONUs does BDCOM OLT support per port?

BDCOM EPON supports up to 64 ONUs per PON port. BDCOM GPON supports up to 128 ONUs per PON port. For quality service, practical deployment is 32-64 for EPON and 64-96 for GPON.

BDCOM OLT Complete Setup Guide

Contents

0.1 Reference

1 1. Initial Login & Console Access
2 2. Hostname, Password & Basic Security
3 3. VLAN Configuration
4 4. Uplink (GigaEthernet) Port Configuration
5 5. Management IP, SSH & HTTP
6 6. PON Port Configuration (EPON & GPON)
7 7. ONU / ONT Registration & Configuration
8 8. Optical Power Monitoring
9 9. Essential Show Commands Reference
10 10. Save Configuration & Backup
11 11. Troubleshooting Common Issues
12 Related BDCOM & ISP Guides
13 Frequently Asked Questions — BDCOM OLT Setup

Madan KC — ISP Network Engineer

Configuring BDCOM OLTs daily in active ISP environments since 2017

ISP Professional BDCOM Field Experience Updated 2026

⚡ Quick Setup Summary

BDCOM OLT setup order: 1) Connect console cable → login admin/admin → 2) Set hostname → 3) Create VLANs → 4) Configure uplink (trunk) → 5) Set management IP → 6) Bring up PON ports → 7) Enable ONU authentication → 8) Save with write all.

BDCOM OLTs are among the most widely deployed EPON and GPON devices in ISP and WISP networks across Asia and beyond. This complete setup guide covers everything from first boot to full subscriber deployment — written from real hands-on ISP field experience, not documentation copy-paste.

🖥️

1. Initial Login & Console Access

Required: Console cable (RS232 to RJ45) + PuTTY

Connect console cable from OLT console port to your PC serial/USB port
Open PuTTY → Select Serial
COM port: check Device Manager for correct COM number
Speed (Baud): 9600 | Data bits: 8 | Parity: None | Stop bits: 1 | Flow: None
Click Open → press Enter → login prompt appears

Default credentials: Username: admin | Password: admin

EPON default IP: 172.16.0.1 | GPON default IP: 192.168.1.1

Connect Ethernet cable from PC to any GigaEthernet port on OLT
Set your PC IP to same subnet (e.g. 172.16.0.2 / 255.255.255.0)
Open browser → navigate to http://172.16.0.1 (EPON) or http://192.168.1.1 (GPON)
Login: admin / admin

SSH must be enabled first (see Section 5). Once enabled:

Open PuTTY → enter OLT management IP → Port 22 → SSH
Login: admin / your configured password

ip ssh enable                    # Enable SSH service
ip ssh version 2                  # Use SSH v2
write all                          # Save

📡

ISP Field Note

Always use the console cable for initial setup — it works regardless of IP configuration. Once the management IP is set and SSH enabled, switch to SSH for all future access. Never rely solely on Telnet in production; it sends credentials in plaintext.

⚙️

2. Hostname, Password & Basic Security

After first login, immediately set a meaningful hostname and change the default password. This is essential for identifying the device in logs and securing access.

! ── Enter privileged mode ──
Switch>
Switch>enable
Switch#config

! ── Set hostname ──
Switch_config#hostname ISP-BDCOM-OLT-01

! ── Change admin password ──
ISP-BDCOM-OLT-01_config#username admin password YourStrongPassword

! ── Enable password encryption ──
ISP-BDCOM-OLT-01_config#service password-encryption

! ── Set AAA authentication ──
ISP-BDCOM-OLT-01_config#aaa authentication login default local
ISP-BDCOM-OLT-01_config#aaa authentication enable default none

! ── Save ──
ISP-BDCOM-OLT-01_config#exit
ISP-BDCOM-OLT-01#write all

⚠️ Change the default password immediately. All BDCOM OLTs ship with admin/admin. Any device on the same network can access your OLT with default credentials. Change it before doing anything else.

🔀

3. VLAN Configuration

VLANs separate traffic between subscribers and management. A typical ISP deployment uses one VLAN per PON port, plus a separate management VLAN. This example creates VLANs 100–104: VLAN 100 for management, VLANs 101–104 for 4 PON ports.

ISP-BDCOM-OLT-01#config

! ── Create VLANs 100 to 104 ──
ISP-BDCOM-OLT-01_config#vlan 100-104
! Response: Creating VLAN(s), please wait...
ISP-BDCOM-OLT-01_config#exit

! ── Verify VLANs created ──
ISP-BDCOM-OLT-01#show vlan

📌 VLAN Planning Tip: Reserve VLAN 100 (or any low number) for OLT management traffic. Assign sequential VLANs to PON ports (101, 102, 103, 104…). This makes troubleshooting and auditing much easier.

🔗

4. Uplink (GigaEthernet) Port Configuration

The uplink port connects your OLT to the upstream router or aggregation switch. It must be configured as a trunk port allowing all subscriber and management VLANs.

ISP-BDCOM-OLT-01#config

! ── Configure uplink port GE0/1 as trunk ──
ISP-BDCOM-OLT-01_config#interface gigaEthernet 0/1
ISP-BDCOM-OLT-01_config_g0/1#description UPLINK-TO-ROUTER
ISP-BDCOM-OLT-01_config_g0/1#switchport mode trunk
ISP-BDCOM-OLT-01_config_g0/1#switchport trunk vlan-allowed 100-104
ISP-BDCOM-OLT-01_config_g0/1#no shutdown
ISP-BDCOM-OLT-01_config_g0/1#exit

! ── Save and verify ──
ISP-BDCOM-OLT-01_config#exit
ISP-BDCOM-OLT-01#write all
ISP-BDCOM-OLT-01#show interface gigaEthernet 0/1

✅ Verify: After no shutdown, the log should show: GigaEthernet0/1 changed state to up. If you see “down/down”, check the physical cable connection to the upstream router.

🌐

5. Management IP, SSH & HTTP

Assign an IP address to the management VLAN so you can access the OLT remotely via SSH or browser. Set a default route pointing to your upstream router.

ISP-BDCOM-OLT-01#config

! ── Assign IP to management VLAN 100 ──
ISP-BDCOM-OLT-01_config#interface vlan 100
ISP-BDCOM-OLT-01_config_vlan100#ip address 192.168.1.200 255.255.255.0
ISP-BDCOM-OLT-01_config_vlan100#exit

! ── Set default gateway ──
ISP-BDCOM-OLT-01_config#ip route default 192.168.1.1

! ── Enable SSH (recommended) ──
ISP-BDCOM-OLT-01_config#ip ssh enable
ISP-BDCOM-OLT-01_config#ip ssh version 2

! ── Enable HTTP web GUI (optional) ──
ISP-BDCOM-OLT-01_config#ip http server
ISP-BDCOM-OLT-01_config#ip http port 2009

! ── Enable Telnet (use SSH instead in production) ──
! ISP-BDCOM-OLT-01_config#ip telnet server

ISP-BDCOM-OLT-01_config#exit
ISP-BDCOM-OLT-01#write all

! ── Test connectivity ──
ISP-BDCOM-OLT-01#ping 192.168.1.1

📌 HTTP Port Tip: Changing HTTP from default port 80 to a custom port (e.g. 2009) adds a small layer of obscurity. Access the web GUI at http://192.168.1.200:2009.

📡

6. PON Port Configuration (EPON & GPON)

PON ports connect to subscribers via fiber. Each PON port must be brought up and assigned a VLAN. Ports are shutdown by default on most BDCOM models.

Configure each EPON port individually with its subscriber VLAN:

! ── EPON Port 1 → VLAN 101 ──
ISP-BDCOM-OLT-01_config#interface epon 0/1
ISP-BDCOM-OLT-01_config_epon0/1#switchport mode access
ISP-BDCOM-OLT-01_config_epon0/1#switchport pvid 101
ISP-BDCOM-OLT-01_config_epon0/1#no shutdown
ISP-BDCOM-OLT-01_config_epon0/1#exit

! ── EPON Port 2 → VLAN 102 ──
ISP-BDCOM-OLT-01_config#interface epon 0/2
ISP-BDCOM-OLT-01_config_epon0/2#switchport mode access
ISP-BDCOM-OLT-01_config_epon0/2#switchport pvid 102
ISP-BDCOM-OLT-01_config_epon0/2#no shutdown
ISP-BDCOM-OLT-01_config_epon0/2#exit

! ── Repeat for 0/3 (103) and 0/4 (104) ──
ISP-BDCOM-OLT-01_config#exit
ISP-BDCOM-OLT-01#write all

GPON port configuration with trunk mode for tagged subscriber VLANs:

! ── GPON Port 1 → trunk with VLANs ──
ISP-BDCOM-OLT-01_config#interface gpon 0/1
ISP-BDCOM-OLT-01_config_gpon0/1#switchport mode trunk
ISP-BDCOM-OLT-01_config_gpon0/1#switchport trunk vlan-allowed 101-200
ISP-BDCOM-OLT-01_config_gpon0/1#no shutdown
ISP-BDCOM-OLT-01_config_gpon0/1#exit

ISP-BDCOM-OLT-01_config#exit
ISP-BDCOM-OLT-01#write all

Enable all PON ports at once using interface range (faster for initial deployment):

! ── Enable all 4 EPON ports at once ──
ISP-BDCOM-OLT-01_config#interface range epon 0/1-4
ISP-BDCOM-OLT-01_config_if_range#no shutdown
ISP-BDCOM-OLT-01_config_if_range#exit

! ── For 8-port OLT: ──
! interface range epon 0/1-8

! ── For GPON 8-port: ──
! interface range gpon 0/1-8

ISP-BDCOM-OLT-01_config#exit
ISP-BDCOM-OLT-01#write all

🔌

7. ONU / ONT Registration & Configuration

When an ONU is connected, it appears as unregistered on the OLT. You need to authenticate and configure it with the correct VLAN settings for subscriber traffic to pass.

Check for connected and unregistered ONUs:

! ── Show all active/registered ONUs ──
ISP-BDCOM-OLT-01#show epon active-onu

! ── Show all ONU info across all ports ──
ISP-BDCOM-OLT-01#show epon onu-information

! ── Show ONUs on specific port ──
ISP-BDCOM-OLT-01#show epon active-onu interface epON 0/1

! ── Show inactive/offline ONUs ──
ISP-BDCOM-OLT-01#show epon inactive-onu

! ── Find ONU by MAC address ──
ISP-BDCOM-OLT-01#show epon active-onu mac-address 84:79:73:fb:3f:9d

! ── For GPON ──
ISP-BDCOM-OLT-01#show gpon onu-information interface gpON 0/1

Configure an EPON ONU (port 0/1, ONU slot 1) with VLAN tagging for subscriber:

ISP-BDCOM-OLT-01_config#interface EPON 0/1:1

! ── Add description (customer name) ──
ISP-BDCOM-OLT-01_config_epon0/1:1#description Customer-Ram-Prasad-Flat-3

! ── Configure ONU LAN port with subscriber VLAN ──
ISP-BDCOM-OLT-01_config_epon0/1:1#epon onu port 1 ctc vlan mode tag 101 priority 0

! ── Verify ONU LAN port status ──
ISP-BDCOM-OLT-01_config_epon0/1:1#exit
ISP-BDCOM-OLT-01#show epon interface epON 0/1:1 onu port 1 state

ISP-BDCOM-OLT-01#write all

Configure a GPON ONU with service VLAN:

ISP-BDCOM-OLT-01_config#interface GPON 0/1:1

! ── Add ONU description ──
ISP-BDCOM-OLT-01_config_gpon0/1:1#description Customer-Sita-Devi-House-5

! ── Configure UNI port VLAN ──
ISP-BDCOM-OLT-01_config_gpon0/1:1#gpon onu uni 1 vlan mode tag 201

! ── Verify ONU LAN port ──
ISP-BDCOM-OLT-01_config_gpon0/1:1#exit
ISP-BDCOM-OLT-01#show gpon interface gpON 0/1:1 onu port 1 state

ISP-BDCOM-OLT-01#write all

Set bandwidth limits per ONU subscriber port (ingress = download, egress = upload from OLT perspective):

ISP-BDCOM-OLT-01_config#interface EPON 0/1:1

! ── Set 10 Mbps download limit (10240 = 10 x 1024) ──
ISP-BDCOM-OLT-01_config_epon0/1:1#epon onu port 1 ctc rate-limit 10240 ingress

! ── Set 5 Mbps upload limit ──
ISP-BDCOM-OLT-01_config_epon0/1:1#epon onu port 1 ctc rate-limit 5120 egress

! ── Common speed values: ──
!   1 Mbps  = 1024     | 5 Mbps  = 5120
!   10 Mbps = 10240    | 20 Mbps = 20480
!   50 Mbps = 51200    | 100 Mbps= 102400

ISP-BDCOM-OLT-01_config_epon0/1:1#exit
ISP-BDCOM-OLT-01#write all

💡

8. Optical Power Monitoring

Monitoring optical Rx/Tx power (dBm) is critical for diagnosing fiber issues. Low RX power at the OLT means a problem between the OLT and ONU — dirty connector, bad splice, or too much attenuation.

dBm Range	Status	What It Means
-8 to -20 dBm	✅ Excellent	Clean fiber, proper splices, good connection
-20 to -25 dBm	✅ Good	Normal working range for EPON/GPON
-25 to -28 dBm	⚠️ Acceptable	Check connectors, may need cleaning
-28 to -30 dBm	⚠️ Marginal	Investigate fiber path, bent cables, dirty connectors
Below -30 dBm	❌ Critical	Fiber break, bad splice, wrong splitter ratio, dirty SFP

! ── EPON: Show all ONU RX power on port 0/1 ──
ISP-BDCOM-OLT-01#show epon optical-transceiver-diagnosis interface epON 0/1

! ── EPON: Show specific ONU RX power (ONU #4 on port 0/1) ──
ISP-BDCOM-OLT-01#show epon optical-transceiver-diagnosis interface epON 0/1:4

! ── EPON: Show ONU TX/RX via CTC command ──
ISP-BDCOM-OLT-01#show epon interface ePON 0/1:5 onu ctc optical-transceiver-diagnosis

! ── GPON: Show all ONU TX/RX on port 0/1 ──
ISP-BDCOM-OLT-01#show gpon onu-optical-transceiver-diagnosis interface gpON 0/1

! ── GPON: Specific ONU optical status ──
ISP-BDCOM-OLT-01#show gpon interface gpON 0/1:1 onu optical-transceiver-diagnosis

! ── Show OLT SFP/uplink optical power ──
ISP-BDCOM-OLT-01#show interface range epON 0/1

💡

Field Experience

In my ISP work, the most common cause of poor optical power is dirty SFP connectors and uncleaned fiber connectors at the splitter. Before replacing fiber, always clean connectors with an IEC 61300-3-35 cleaner. A single dirty connector can cause 3–5 dBm of extra loss. Check this before assuming a fiber break.

🔍

9. Essential Show Commands Reference

Command	What It Shows
show running-config	Full current OLT configuration
show vlan	All VLANs configured on OLT
show interface brief	Status of all interfaces (up/down)
show epon active-onu	All currently registered/active ONUs
show epon inactive-onu	Offline/deregistered ONUs
show epon onu-information	Full ONU info on all PON ports
show epon active-onu interface epON 0/1	Active ONUs on specific PON port
show epon interface epON 0/1:1 onu ctc basic-info	ONU MAC address and basic info
show epon interface epON 0/1:1 onu port 1 state	ONU LAN port status (up/down)
show epon optical-transceiver-diagnosis interface epON 0/1	All ONU optical power on port
show mac address-table interface epON 0/1	MAC addresses learned on PON port
show mac address-table interface epON 0/1:1	MAC addresses on specific ONU
show arp	ARP table (IP to MAC mappings)
show ip route detail	Routing table
show cpu	CPU utilization
show local-users	Admin users configured on OLT
show running-config interface epON 0/1:1	Configuration of specific ONU
show gpon onu-information interface gpON 0/1	GPON: ONU count and info on port
show gpon interface gpON 0/1:1 onu basic-info	GPON: ONU details and serial number

💾

10. Save Configuration & Backup

⚠️ Critical: Always save after every configuration change. If the OLT reboots without saving, all unsaved changes are lost. Use write all — not write alone on BDCOM.

! ── Save current running config to NVRAM ──
ISP-BDCOM-OLT-01#write all
! Response: "successfully wrote" = saved OK

! ── View current running config ──
ISP-BDCOM-OLT-01#show running-config

! ── View startup config (what loads on boot) ──
ISP-BDCOM-OLT-01#show startup-config

! ── Reboot OLT (with confirmation) ──
ISP-BDCOM-OLT-01#reboot
! Type: y  to confirm

! ── Reboot a single ONU remotely ──
ISP-BDCOM-OLT-01_config#interface EPON 0/1:1
ISP-BDCOM-OLT-01_config_epon0/1:1#epon reboot onu

! ── Reboot all ONUs on a port ──
ISP-BDCOM-OLT-01_config#interface epon 0/1
ISP-BDCOM-OLT-01_config_epon0/1#epon reboot onu all

! ── GPON reboot ONU ──
ISP-BDCOM-OLT-01#gpon reboot onu interface gpON 0/1:1

✅ Backup Tip: After finalising your configuration, download the startup config file via the web GUI (System → Backup Configuration) and store it somewhere safe. Label it with the date and OLT hostname. This saves hours if the device ever needs to be replaced.

🔧

11. Troubleshooting Common Issues

ONU connected but not showing as registered:

Check physical fiber connection — clean connectors and verify SFP is seated
Verify PON port is up: show interface brief → PON port should show “up”
Check optical power: show interface range epON 0/1 → RX power should be above -28 dBm
Verify ONU authentication mode: show epon onu-authen-method interface epON 0/1
If auth is “manual” and ONU is new, you may need to add it manually: run show epon inactive-onu to see the ONU MAC, then bind it
Try rebooting the ONU power — unplug and replug

ONU is registered but subscriber has no internet:

Check ONU LAN port state: show epon interface epON 0/1:1 onu port 1 state → must be “up”
Verify VLAN on PON port matches VLAN on uplink trunk: show running-config interface epON 0/1
Check uplink trunk allows the subscriber VLAN: show running-config interface gigaEthernet 0/1
Verify MAC is being learned: show mac address-table interface epON 0/1:1
Check ONU VLAN tag mode configuration: show epon interface epON 0/1:1 onu port 1 ctc vlan

Low or no optical signal:

Clean OLT SFP connector with fiber cleaner pen
Clean ONU/ONT optical connector at the customer end
Check splitter connections — loose connector at splitter = 3–10 dBm loss
Verify correct splitter ratio (1:8 = ~9 dBm loss, 1:16 = ~12 dBm loss, 1:32 = ~15 dBm loss)
Calculate total path budget: SFP TX power – cable loss – connector loss – splitter loss = must be above ONU RX sensitivity (-27 to -30 dBm)
Use OTDR to locate exact break point if signal is completely absent

Cannot SSH or ping the OLT management IP:

Connect via console cable and verify management IP is configured: show running-config interface vlan 100
Verify the management VLAN is reachable via the uplink trunk
Check that SSH is enabled: show running-config | include ssh
Verify default route: show ip route detail — check default route points to correct gateway
Ping from OLT to gateway: ping 192.168.1.1 — if it fails, check uplink physical connection

Related BDCOM & ISP Guides

📡BDCOM Category HubAll BDCOM guides and tutorials ⚙️BDCOM P3310 Step-by-StepEPON P3310 specific config guide 🔶Huawei OLT GuideCompare BDCOM with Huawei OLT setup ⚙️MikroTik GuidesConnect BDCOM OLT to MikroTik router 🌐ISP Help HubFTTH, GPON & network management 📚Networking BasicsVLAN, PON, FTTH fundamentals

Frequently Asked Questions — BDCOM OLT Setup

BDCOM EPON OLT default IP is 172.16.0.1 (accessible via any GigaEthernet port). BDCOM GPON OLT default IP is 192.168.1.1. For both, the EPON management port specifically uses 192.168.0.1. Default login credentials are admin / admin. Always change these immediately after first login.

Connect using a serial console cable (RS232 to RJ45). In PuTTY, select Serial connection type. Settings: Baud rate 9600, Data bits: 8, Parity: None, Stop bits: 1, Flow control: None. Once connected, press Enter to get the login prompt. Use admin / admin to login.

Use write all (not just write) from privileged mode. Wait until you see the response “successfully wrote” before proceeding. If you reboot without saving, all unsaved changes are lost. Make it a habit to run write all after every configuration change.

The most common causes are: (1) Poor optical signal — check RX power with show interface range epON 0/x, it should be above -28 dBm; (2) PON port is shutdown — run no shutdown on the interface; (3) ONU authentication is set to manual and the ONU hasn’t been bound — check with show epon inactive-onu and bind the MAC address; (4) Dirty fiber connector — clean both OLT SFP and ONU optical connector.

EPON (Ethernet PON) uses Ethernet framing with downstream 1.25 Gbps and upstream 1.25 Gbps shared per PON port. GPON (Gigabit PON) uses ATM/GEM framing with downstream 2.488 Gbps and upstream 1.244 Gbps. GPON supports more ONUs per port (up to 128 vs 64 for EPON) and has better QoS. GPON commands use gpon prefix while EPON uses epon prefix in BDCOM CLI. For new deployments in 2026, GPON is recommended.

For EPON: show epon optical-transceiver-diagnosis interface epON 0/1 shows all ONU RX power on port 0/1. For a specific ONU: show epon interface ePON 0/1:5 onu ctc optical-transceiver-diagnosis. For GPON: show gpon onu-optical-transceiver-diagnosis interface gpON 0/1. Normal range is -8 to -28 dBm. Below -28 dBm indicates a problem.

Use the rate-limit command on the ONU interface. For example, 10 Mbps download: epon onu port 1 ctc rate-limit 10240 ingress. For upload: epon onu port 1 ctc rate-limit 5120 egress. The value is in Kbps (10240 = 10 Mbps, 51200 = 50 Mbps, 102400 = 100 Mbps). Always run write all after setting limits.

BDCOM EPON OLT supports up to 64 ONUs per PON port. BDCOM GPON OLT supports up to 128 ONUs per PON port. However, for quality internet service, ISPs typically deploy 32–64 subscribers per PON port for EPON and 64–96 for GPON, depending on bandwidth plans. Oversubscribing beyond these numbers causes poor performance during peak hours.