How to add ONT with new VLAN on Huawei OLT

How to Add ONT with a New VLAN on Huawei OLT

Written by Madan kc — 10+ years of ISP/GPON experience, DG Link Network

Last updated: September 2026

Applies to: Huawei SmartAX MA5600T, MA5608T, MA5683T, and MA5800 series OLTs.

TL;DR: To bring an ONT online on a VLAN that doesn’t exist on the OLT yet, first create the VLAN and bind it to the uplink port, then build a matching ont-srvprofile and ont-lineprofile around that VLAN, and finally register the ONT using those new profiles.

Scenario: Your MA5683T already has plenty of ONTs working, and a DBA profile is already in place — but you need to onboard an ONT on a brand-new VLAN, which means the VLAN, service profile, and line profile all need to be created first.

Values in red are examples — replace the VLAN ID, port numbers, profile names/IDs, and IP addresses with your own.

Quick Navigation

1. Enter Configuration Mode
2. Create the New VLAN
3. Configure DHCP Relay (Optional)
4. Create the ONT Service Profile
5. Create the ONT Line Profile
6. Register the ONT on the Port

Step 1 – Enter Configuration Mode

Connect to the OLT and go into setup mode:

enable
config

Step 2 – Create the New VLAN

Create the VLAN and point it to the uplink port so traffic on it can actually leave the OLT:

vlan 1169 smart
port vlan 1169 0/8 0

Step 3 – Configure DHCP Relay (Optional)

If this VLAN needs to reach a DHCP server (for example, one already configured under dhcp-server 0 ip x.x.x.x), point the new VLAN interface at it:

interface vlanif 1169
dhcp-server 0
exit

Skip this step if the VLAN doesn’t need DHCP relay — for example, if customers on it will use static IPs or PPPoE instead.

Step 4 – Create the ONT Service Profile

This defines the Ethernet port capability and the VLAN translation for the ONT:

ont-srvprofile gpon profile-name "madankc"
ont-port eth 1
port vlan eth 1 translation 1169 user-vlan 1169
commit

Step 5 – Create the ONT Line Profile

This assigns the T-CONT (bandwidth, via the existing DBA profile) and maps the GEM port to the new VLAN:

ont-lineprofile gpon profile-id 12 profile-name "Madankc"
tcont 4 dba-profile-id 11
gem add 1 eth tcont 4
gem mapping 1 0 vlan 1169
commit

Step 6 – Register the ONT on the Port

With the VLAN and both profiles in place, the last step is registering the ONT itself on the GPON port it’s physically connected to — using ont-lineprofile-id 12 and the service profile you just created.

Already covered step-by-step in a separate guide: Adding ONU to Huawei SmartAX MA5683T →

Command Reference

Command	Purpose
`vlan <id> smart`	Create a new VLAN on the OLT
`port vlan <id> <frame/slot> <port>`	Bind the VLAN to the uplink port
`interface vlanif <id>`	Enter the VLAN’s Layer 3 interface
`dhcp-server <id>`	Enable DHCP relay on the VLAN interface
`ont-srvprofile gpon profile-name <name>`	Create a new ONT service profile
`port vlan eth <port> translation <vlan> user-vlan <vlan>`	Map the ONT’s Ethernet port to the VLAN
`ont-lineprofile gpon profile-id <id> profile-name <name>`	Create a new ONT line profile
`tcont <id> dba-profile-id <id>`	Assign bandwidth via an existing DBA profile
`gem mapping <gem> <index> vlan <id>`	Map the GEM port’s traffic to the new VLAN

FAQ

Do I need a new DBA profile too, or can I reuse an existing one?
You can reuse an existing DBA profile, as in this example (dba-profile-id 11). DBA profiles control bandwidth allocation and aren’t tied to a specific VLAN, so the same one can be referenced by multiple line profiles.

Will creating a new VLAN affect ONTs already working on the OLT?
No. Adding a new VLAN and new profiles doesn’t touch existing VLANs, service ports, or ONT bindings — they’re independent configuration objects.

Do the service profile and line profile both need to reference the same VLAN?
Yes. The ont-srvprofile handles the ONT-side Ethernet-to-VLAN translation, while the ont-lineprofile handles the GEM-to-VLAN mapping on the OLT side. Both need to point at the same VLAN ID or traffic won’t pass correctly.

When can I skip the DHCP relay step?
Skip it if the new VLAN doesn’t need the OLT to relay DHCP requests — for example, if customers on that VLAN will use PPPoE authentication or static IP addressing instead.