How to add VLANs to active ONT on Huawei MA5683T

To add VLANs to an active ONT on a Huawei MA5683T, you don’t need to remove or re-register it. This guide reuses the ONT’s existing line profile to add new GEM ports and service ports for each new VLAN, so the ONT keeps running the whole time and never needs to restart. For hardware and firmware details, see Huawei’s official SmartAX MA5683T support page.

Written by Madan Kc

Quick answer

Create the new VLANs and assign them to the uplink port, open the ONT’s existing ont-lineprofile, add a new GEM port and VLAN mapping for each VLAN, then add a matching service-port for each one. Traffic starts passing right away — the ONT does not need to be restarted.

Before you start

The ONT is already registered and working on an existing line profile and service profile.
You know the ONT’s line profile ID, its GPON port/ONT ID, and the uplink port the VLANs need to reach.
You have spare GEM port numbers available in that line profile — check with display ont-lineprofile gpon profile-id <id> before adding new ones.

How to add VLANs to an active ONT on a Huawei OLT, step by step

Step 1 – Create the new VLANs
Create the VLANs you want to add. A range and a single VLAN are both shown here:
```
vlan 28 to 30 smart
vlan 40 smart
```

Step 2 – Assign the VLANs to the uplink port

port vlan 28 to 30 0/9 0
port vlan 40 0/9 0

Step 3 – Open the ONT’s existing line profile
Open the line profile the ONT already uses — do not create a new one:
```
ont-lineprofile gpon profile-id 8 profile-name "ixnfo"
```
Step 4 – Add a GEM port and VLAN mapping for each new VLAN
Each new VLAN needs its own GEM port bound to the same T-CONT, plus a mapping to that VLAN:
```
gem add 8 eth tcont 4
gem add 9 eth tcont 4
gem add 10 eth tcont 4
gem add 11 eth tcont 4
gem mapping 8 1 vlan 28
gem mapping 9 1 vlan 29
gem mapping 10 1 vlan 30
gem mapping 11 1 vlan 40
commit
quit
```
Tip: Use GEM port numbers that are not already used in this line profile. Run display ont-lineprofile gpon profile-id <id> first to check what’s already there.

Step 5 – Add a service-port for each new VLAN

Each service-port ties one VLAN to its matching GEM port on the ONT:

service-port 1319 vlan 28 gpon 0/0/9 ont 46 gemport 8 multi-service user-vlan 28 tag-transform translate
service-port 1320 vlan 29 gpon 0/0/9 ont 46 gemport 9 multi-service user-vlan 29 tag-transform translate
service-port 1322 vlan 30 gpon 0/0/9 ont 46 gemport 10 multi-service user-vlan 30 tag-transform translate
service-port 1323 vlan 40 gpon 0/0/9 ont 46 gemport 11 multi-service user-vlan 40 tag-transform translate

Done. Traffic passes on the new VLANs immediately — the ONT does not need to be restarted.

Command reference

Command	Purpose
`vlan <id> smart` / `vlan <start> to <end> smart`	Create one VLAN, or a range of VLANs
`port vlan <id> <frame/slot> <port>`	Assign a VLAN to the uplink port
`ont-lineprofile gpon profile-id <id> profile-name <name>`	Open an existing line profile for editing
`gem add <gem> eth tcont <id>`	Add a new GEM port bound to a T-CONT
`gem mapping <gem> <index> vlan <id>`	Map a GEM port’s traffic to a VLAN
`service-port <id> vlan <vlan> gpon <frame/slot/port> ont <id> gemport <gem> multi-service user-vlan <vlan> tag-transform translate`	Bind one VLAN to the ONT’s GEM port and bring it online

Frequently asked questions

Do I need to restart the ONT after adding new VLANs this way?

No. Once the service-ports are added, traffic passes on the new VLANs immediately.

Can I add VLANs to a line profile that other ONTs also use?

The example here edits one specific line profile. If that profile is shared by other ONTs, the new GEM ports and mappings apply to all of them, so confirm the profile is only used by the ONT you intend to change, or create a separate profile if it’s shared.

What does tag-transform translate do in the service-port command?

It tells the OLT to translate the VLAN tag between the ONT side and the network side for that service-port, which is the usual mode for adding a tagged customer VLAN this way.

Why do all the new GEM ports use the same tcont?

They share the T-CONT (tcont 4 in this example) that’s already bound to a DBA profile for that ONT, so the new VLANs’ traffic is covered by the same bandwidth allocation as the ONT’s existing services.