Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

G-010S-A with VLan #6

Open
galvesribeiro opened this issue Apr 19, 2021 · 20 comments
Open

G-010S-A with VLan #6

galvesribeiro opened this issue Apr 19, 2021 · 20 comments

Comments

@galvesribeiro
Copy link

Hello!

My ISP sends with the fiber link 3 VLans: 10 - internet, 20 - VoIP, 30 - IPTV. The only service I signed up is internet on VLan10.

I'm trying to get this SFP module to work with my ISP and UDM-Pro but for whatever reason, it seems that VLans are not passed by the SFP to the UDM-Pro so I'm unable to connect using the PPPoE.

With other GPON devices I was always able to either set the VLan10 on the GPON itself and keeping it as bridge, so the PPPoE connection on my UDM-Pro doesn't require me set the VLan Id. Other GPON devices uses what they call "Transparent mode" where we basically set nothing on the GPON and the UDM-Pro at the PPPoE settings set the VLan to 10. Both ways it work.

So, I've just updated to the latest firmware 3FE47111BFHB32, have the SLID set and I have the link on status O5, meaning that the link is up and authenticated and all I need todo is to make the proper PPPoE connection using the correct VLan 10.

Can you guys tell me what do I need todo on this GPON SFP module to either set the VLan "on it" or allow something like the "Transparent mode" so I can set the VLan on UDM-Pro?

Thank you! I really appreciate any help.

Best regards...

@hwti
Copy link
Owner

hwti commented Apr 19, 2021

AFAIK there is no specific VLAN setting on the SFP, it follows what the OLT asks using OMCI.

From what we saw with Orange France, there could be several issues :

  • Sometimes getting the O5 status isn't enough to get the VLAN, you might need the HardwareVersion (ritool set HardwareVersion XXXXXXXXXXXX) to match your official ONT (and maybe other things, it depends how your ISP configures the OLT).
  • With HWTC (Huawei) OLTs, there is a bug and the VLANs are not forwarded, or only in the down direction.

@galvesribeiro
Copy link
Author

@hwti thanks for the reply. But that sounds weird to me.

Today I replaced the ISP's ONT with UF-Loco from Ubiquiti. The only thing I had to change, is the PLOAM/SLID password to match the one on the original ISP modem then it would sync and get O5, and the PPPoE would work.

The thing is that I tried that with UF-Loco and the other TP-Link ONTs. Both worked. It looks like my ISP is using FiberHome since on the UF-Loco, I have to have the "Profile" set to 3 (https://help.ui.com/hc/en-us/articles/115009335068-UFiber-GPON-Supported-Third-Party-OLTs) in order to make it work.

The TP-Link ONT has a configuration like this:

  1. Transparent Mode: It doesn't tag the VLan and the router (in my case UDM-Pro) is responsible of tagging the VLan10 on the PPPoE connection settings;
  2. Tagged Vlan: In this case, I set the VLan Id to 10 on the ONT itself, and don't set it on the router.

An interesting thing is that the onu CLI on the module has several options with "vlan" on its name:

ONTUSER@SFP:~# onu | grep vlan
gpeet        gpe_extvlan_translate
gpevea       gpe_vlan_entry_add
gpever       gpe_vlan_entry_remove
gpevfa       gpe_vlan_fid_add
gpevfd       gpe_vlan_fid_delete
gpevfg       gpe_vlan_fid_get
gpevmd       gpe_vlan_meter_disable
gpevme       gpe_vlan_meter_enable
gpevmg       gpe_vlan_mode_get
gpevms       gpe_vlan_mode_set
gpevsc       gpe_vlan_segment_create
gpevsd       gpe_vlan_segment_delete
gpevsmg      gpe_vlan_segment_map_get
gpevsms      gpe_vlan_segment_map_set
gpevtfc      gpe_vlan_tagging_filter_create
gpevtfd      gpe_vlan_tagging_filter_delete
gpevtfg      gpe_vlan_tagging_filter_get
gpevtfs      gpe_vlan_tagging_filter_set
lanplvcg     lan_port_lct_vlan_cfg_get
lanplvcs     lan_port_lct_vlan_cfg_set

The problem is that I have no idea what each of those options means and I wasn't able to find any documentation related to it. It looks to me that some of those are related to what I'm mentioning :/

Any ideas where I can find any docs for those commands?

Thanks!

@hwti
Copy link
Owner

hwti commented Apr 20, 2021

I don't know what the different profiles change on the UF-Loco. It might be MIB files, but unlike G-010S-A / MA5671A and others we can't change them on G-010S-A (at least now with the current OMCI daemon).

The OMCI daemon is supposed to configure the rules to map GEM ports on the GPON side to the VLANs.
You can look at /tmp/omci.log, but it's usually long and complex to understand.
Perhaps :

  • There is an bug like what we see with Huawei OLTs.
  • The OLT checks something from from the ONT (which might be in the UF-Loco profile), and if it doesn't match it won't send any OMCI command to configure the VLANs.
  • The OLT never sends anything, and expects a static configuration (which might be what the TP-Link ONT uses, at least in the Tagged Vlan configuration) : the G-010S-A doesn't seem to support this kind of configuration out of the box.

The onu command allows to get/set low level runtime configuration (there is also gtop which can display a lot of information, for example the e menu lists traffic on the different GEM ports).
Outside of debug tests, the command is only used by boot scripts to set configuration from values read from ritool and bootloader configuration.
I don't know any documentation about it (and there are many commands about VLAN and GEM ports), running onu command shows the parameters at least. As this is runtime configuration only, you can try commands without worrying about bricking the ONT.

@galvesribeiro
Copy link
Author

log.txt

Here is the omci.log. I have no clue what is going on, perhaps you may see something on it. If you look from the last messages, there are a lot of "NOT VALID" on a lot of fields perhaps you may have a clue on what is going on...

@hwti
Copy link
Owner

hwti commented Apr 20, 2021

NOT VALID only means a field is not requested or not sent, so usually it isn't an issue.

oltinfo: vendor:HWTC,olt type:1,relInfo:31300000
So it's a Huawei OLT.

In the OMCI log, there are different threads which are mixed, so the order can be difficult to understand.
Sometimes we can see which OLT command does what, sometimes it's a mess...
I see flow rules being created and destroyed several times, but I don't know why (it's the same thing as what we see with Orange France).
For example, for VLAN 10 I see :

>>>>configFlowUpstream(145/145/145/145/145/145/145/145)(port=101,flow=512,act=1,ethtype=0:(FOP:15,FOV:4096,FIP:8,FIV:10->TOP:15,TOV:0,TIP:8,TIV:10))@35m:8s 65ms
>>>>configFlowDownstream(145/145/145/145/145/145/145/145)(port=101,flow=512,act=1,ethtype=0:(FOP:15,FOV:0,FIP:8,FIV:10->TOP:15,TOV:4096,TIP:8,TIV:10))@35m:8s 66ms

>>>>configFlowUpstream(145/145/145/145/145/145/145/145)(port=e01,flow=513,act=1,ethtype=0:(FOP:15,FOV:4096,FIP:8,FIV:10->TOP:15,TOV:0,TIP:8,TIV:10))@35m:8s 74ms
>>>>configFlowDownstream(145/145/145/145/145/145/145/145)(port=e01,flow=513,act=1,ethtype=0:(FOP:15,FOV:0,FIP:8,FIV:10->TOP:15,TOV:4096,TIP:8,TIV:10))@35m:8s 75ms

>>>>configFlowUpstream(145/145/145/145/145/145/145/145)(port=101,flow=2,act=1,ethtype=0:(FOP:15,FOV:4096,FIP:8,FIV:10->TOP:15,TOV:0,TIP:8,TIV:10))@35m:8s 384ms
>>>>configFlowDownstream(145/145/145/145/145/145/145/145)(port=101,flow=2,act=1,ethtype=0:(FOP:15,FOV:0,FIP:8,FIV:10->TOP:15,TOV:4096,TIP:8,TIV:10))@35m:8s 410ms

>>>>configFlowUpstream(145/145/145/145/145/145/145/145)(port=101,flow=2,act=1,ethtype=0:(FOP:15,FOV:4096,FIP:8,FIV:10->TOP:15,TOV:0,TIP:8,TIV:10))@35m:9s 670ms
>>>>configFlowDownstream(145/145/145/145/145/145/145/145)(port=101,flow=2,act=1,ethtype=0:(FOP:15,FOV:0,FIP:8,FIV:10->TOP:15,TOV:4096,TIP:8,TIV:10))@35m:9s 701ms

But there are also deletions, but they seem sometimes more asynchronous (or there isn't a equivalent trace which would be easy to match).

@galvesribeiro
Copy link
Author

The cable was removed and plugged at some point on those logs, and when you start to see more "interesting" messages are probably when it was plugged and synced up to O5.

So it's a Huawei OLT.

That is funny. On UF-Loco it was set as profile 3, which is FiberHome, but now that you said that, I've changed to Profile2, which is Huawei and it also worked! There is also a setting to change the SN prefix but that didn't matter as it worked both ways:

image

I have no idea why the G-010S-A doesn't work :/

@galvesribeiro
Copy link
Author

galvesribeiro commented Apr 20, 2021

image

That is basically what I have to configure to get the UF-Loco to work... :/

The only thing considered by the OLT is the PLOAM... The rest is the default which is set if left empty...

@J2Kbr
Copy link

J2Kbr commented Sep 22, 2021

Hello Galves.

As my setup would be same as yours, I've been following your attempts to get the G-010S-A to work with Vivo Fibra and UDM Pro for long time now, here as well as on some forums (e.g. MikroTik).

Today I finally got the chance to put in practice everything I learned from the past months and test this setup:

Vivo Fibra -> G-010S-A -> UDM Pro [WAN2/SFP+]

It is working!! The UDM Pro got public IP (from PPPoE).

Here is what I did:

G-010S-A

  • Updated to the latest firmware (3FE47111BFHB32);
  • Changed the SLID via web interface:
    SLID = 1234567890
  • Changed the serial number via SSH:
    ritool set MfrID MSTC
    ritool set G984Serial XXXXXX (replace XXXXXXXX with the modem's SN)

UDM PRO

  • Updated to latest firmware and UniFi Network application;
  • Changed WAN2/SFP+ port to use WAN profile (primary WAN);
  • Changed WAN1 port to use WAN2 profile (failover WAN);
  • WAN configurations:
    • Enabled VLAN and configured to 600;
    • Cloned the MAC address from the Vivo's modem;
    • Configured PPPoE (cliente@cliente, cliente);

That's all, it is working for me.

I live in Curitiba, here the VLan ID is 600 and the OLT is Alcatel (ALCL).

The G-010S-A will automatically enter in bridge mode after the omci initialization (O5), the UDM Pro must tag the correct Vlan for PPPoE connection.

Hope this helps you.

@galvesribeiro
Copy link
Author

Holy crap @J2Kbr! Thanks a lot for getting back!

I wasn't able to make it work until now, so I ended up paying the CarlitoxxPro expensive pricing to get it to work. I'll try what you did later this week.

Thank you very much for reporting back!

FYI, I'm on Vivo São Paulo, so the VLan ID is 10. I noticed that you used the MAC clone on the UDM. Was that necessary? I didn't needed to do that on the CarlitoxxPro.

Again, thanks for getting back! I have 2 of those SFP modules here that were completely useless :)

Thank yoU!

@J2Kbr
Copy link

J2Kbr commented Sep 22, 2021

To be honest, I'm not sure if cloning the modem's MAC is needed. I did that just for good measure, as I noticed the Vivo's technician took note of the MAC just before turn the modem on for the first time.

@hwti
Copy link
Owner

hwti commented Jan 30, 2022

There is now the 3FE46398BGCB22 firmware, which should fix the issues with Huawei OLTs (at least it does for me).

@chomba
Copy link

chomba commented Mar 3, 2022

@hwti Can you please let me know how you upgraded to image version 3FE46398BGCB22? I'm currently using 3FE47111BFHB32 (image 0) and have 3FE46398BGCB22 loaded on image 1

image

I'm using update_env_flag 1 to switch to image1 but it keeps on loading image 0 after the module reboots. Is there any other command that needs to be used to commit the changes and make the module load image 1?

@hwti
Copy link
Owner

hwti commented Mar 3, 2022

@chomba update_env_flag 1 should set next_active=1 and commit=1, so something is strange.
Can you check the values (with upgradestatus for example) just after the command, to check if the values are correctly written (I would expect errors if they aren't, but who knows...) ?
If they are correctly set, and the ONT is still on image0 after a reboot, then something happens at the bootloader level, maybe we would need to check the scripts with fw_printenv.

@chomba
Copy link

chomba commented Mar 3, 2022

Both next_active and commit are set to 1 after running update_env_flag 1 I've tried this multiple times but I can't get it to boot image1 it always boots image0 after a reboot, here's the output of the fw_printenv command:

ONTUSER@SFP:~# fw_printenv
a0_image=3FE46542AAAA_a0.bin
a2_iaddr=0xFE0000
a2_image=3FE46542AAAA_a2.bin
act_img_addr=0xBF20003C
addip=setenv bootargs ${bootargs} ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}:${netdev}:off
addmisc=setenv bootargs ${bootargs} ethaddr=${ethaddr} machtype=${machtype}  vpe1_load_addr=0x83f00000 vpe1_mem=1M mem=63M ${mtdparts} quiet
addmtdparts0=setenv mtdparts mtdparts=sflash:256k(uboot)ro,512k(uboot_env),6144k(linux),6144k(image1),1024k(configfs),2112k(logfs),64k(ri),64k(sfp),64k(ribackup)
addmtdparts1=setenv mtdparts mtdparts=sflash:256k(uboot)ro,512k(uboot_env),6144k(image0),6144k(linux),1024k(configfs),2112k(logfs),64k(ri),64k(sfp),64k(ribackup)
asc0=3
baudrate=115200
boot_image=run boot_image${c_img};
boot_image0=run kernel0_from_sf flashargs addip addmtdparts0 addmisc && bootm ${ram_addr}
boot_image1=run kernel1_from_sf flashargs addip addmtdparts1 addmisc && bootm ${ram_addr}
boot_image_err=setenv kernel_offs ${kernel0_offs};httpd && setenv image0_is_valid 1
bootargs=rootfstype=squashfs,jffs2 ip=192.168.1.10:192.168.1.100:192.168.2.1::::off ethaddr=ac:9a:96:00:00:00 machtype=SFP vpe1_load_addr=0x83f00000 vpe1_mem=1M mem=63M mtdparts=sflash:256k(uboot)ro,512k(uboot_env),6144k(linux),6144k(image1),1024k(configfs),2112k(logfs),64k(ri),64k(sfp),64k(ribackup) quiet
bootcmd=run flash_flash
bootdelay=5
c_img=0
commit=0
config_iaddr=0xCC0000
env_offs=0x40000
env_offs_redund=0x80000
ethact=SERDES
ethaddr=ac:9a:96:00:00:00
ethprime=SERDES
flash_flash=run select_image boot_image
flashargs=setenv bootargs rootfstype=squashfs,jffs2
gatewayip=192.168.2.1
goi_calibrated=1
goi_config=begin-base64 644 goi_config@H4sIAFMBAAACA+1YS4/bNhD2tf4VLHLwKVoO36rQwza7CRbdNou16xwWgUDL@si3UMg1Jm6T/vkM/urIsp0XTGs1Wc9F4ZshvONRHjpxWyYVbV1lyMXdZXNnJ@Mo2XtkyLuEhn8QS1ICk/9L5IKIoSYvNEaT4pKP2HLhjvUdBMyh6hvTPIY1nZ@gpDe259Hvwyv70/GFc5VvecnL8iVIytXkWRhV/OUVIuUjH5bpySbpqsqm2Vp@8W0URX1v+/72EisU31+/9pYXZJTma/Lw4/uI3FQL8vB4idrwGpV3F7nXLc73@UL7vc4BIBSrkUWgCCTKi/V4n/w1JP8f/L6f+3+S/Yop3/P/K+J93/H8e/P9g@19N4Mv2H2P8X+F/ThVLIf6mBdfw/D/+nB/z3PN+xfXx5dxX/cLVnekTGeCWQ@h7EntIhEGISGdUR+VvzHE/tfwPC81tjQn+I/ngA9YFpqCoxKf/9z4B3/zyK0@o8D/nv+JW82y+eYA2Krn5T8Tunb/a+35r/GToOP/GaS/3XGCm08G86Wb2OWg@/42/EdyKvLLLbFJYr4+yPMVKYcM/YBTClxRecjqi/DspI1ImRbauyFgHKhAR@efvq8tb/kAFE5PW7rcoH/QOswrcbZcNYYZ+RIuBjkW570fIpmU07UiZ2ufln@auk+kgENAE4FLLL5YhMhGhjTZJrE2OE2oTGhMs+qKi1OeOK1++ide7w7iCkZ@cG50zUa9DTRtzJG7VVa52uCfMNdaeeO7Wz/X5/xw4B9l9o3NdnZos9MTdvYn@OOhnT/4rrCeWk+4SpMwc+WDv47x1nE+cQvu4jY/q1nGYCDDQreM2Pq1qvqck@GdBD+y5B4EIeLPxTtXMEIWfAhKDC1JZ+k7upf5O2q2OBksIYKkDwY1i/CYwf@w6JdK3GMinYWsFAyasBIGbah+jlNgGUNhZBAzTGq3yotjlF9dYRsWSw6TACh@5BAqxkG0wWJMGNDQGBAQInDzTU5tifTM01VVe7v2tPOMk9i8GRMCfunXNu9+@OLyJQYR0aotf96F44GOcZJoLrmVLcH1e/DZkSiptGIBqiV3bwk7cMkv2A8Bo@DFaChbq5Cpc/NiwTV9qGaZaU2RPOm/EQJ/00U9IfZV3n0EknnXzt8juW2c08@ABwAAA==@====@
image0_addr=0xB00C0000
image0_is_valid=1
image1_addr=0xB0800000
image1_is_valid=1
image_name=g010sa
import_uboot_env=env import -t ${ram_addr} ${filesize}
ipaddr=192.168.1.10
kernel0_from_sf=sf probe 0;sf read ${ram_addr} ${kernel0_offs} ${max_kernel_size}
kernel0_offs=0xC0000
kernel1_from_sf=sf probe 0;sf read ${ram_addr} ${kernel1_offs} ${max_kernel_size}
kernel1_offs=0x6C0000
load_kernel=tftpboot ${ram_addr} ${tftppath}${image_name}-uImage
load_uboot=tftpboot ${ram_addr} ${tftppath}u-boot.img
load_uboot_env=tftp ${ram_addr} ${tftppath}u-boot.env
load_uboot_env_y=loady ${ram_addr}
log_iaddr=0xDC0000
machtype=SFP
magic_addr=0xBF200038
magic_val=0xDEADBEEF
max_kernel_size=180000
mtdparts=mtdparts=sflash:256k(uboot)ro,512k(uboot_env),6144k(linux),6144k(image1),1024k(configfs),2112k(logfs),64k(ri),64k(sfp),64k(ribackup)
net_nfs=run load_kernel nfsargs addip addmtdparts0 addmisc;bootm ${ram_addr}
netconsole=set stderr nulldev;set stdin nc,serial;set stdout nc,serial
next_active=0
nfsargs=setenv bootargs root=/dev/nfs rw nfsroot=${serverip}:${rootpath},${nfsoptions}
nfsoptions=rsize=1024,wsize=1024
preboot=gpio clear 100
ram_addr=80F00000
reset_uboot_env=env default -f -a; saveenv
ri_hiaddr=0xFD0000
ri_image=3FE46542AAAA_ri.bin
ri_siaddr=0xFF0000
save_uboot=sf probe 0;sf erase 0 40000;sf write ${ram_addr} 0 ${filesize}
select_image=if test -n $commit  ; then else setenv commit  _err;saveenv;fi;if test -n $image0_is_valid ; then else setenv image0_is_valid 1;saveenv;fi;if test -n $image1_is_valid ; then else setenv image1_is_valid 0;saveenv;fi;if itest *${magic_addr} == ${magic_val} ; then if itest *${act_img_addr} == 0 ; then setenv next_active 0;fi;if itest *${act_img_addr} == 1 ; then setenv next_active 1;fi;mw ${magic_addr} 0x0;mw ${act_img_addr} 0x0;fi;if test $next_active = -1 ; then setenv c_img $commit;else setenv c_img $next_active;if test $next_active != $commit ;then if test $next_active = 0 ;then setenv next_active 1;setenv commit 1;else setenv next_active 0;setenv commit 0;fi;saveenv;fi;fi;exit 0
serverip=192.168.1.100
start_netconsole=if test -n ${ncip}; then echo 'check for netconsole'; if ping ${ncip}; then run netconsole; echo 'netconsole enabled'; fi; fi
stderr=serial
stdin=serial
stdout=serial
update_A0=gpio clear 102;tftpboot ${ram_addr} ${tftppath}${a0_image};eeprom write 50 ${ram_addr} 0 ${filesize}
update_A2=tftpboot ${ram_addr} ${tftppath}${a2_image};sf probe 0;sf erase ${a2_iaddr} +${filesize};sf write ${ram_addr} ${a2_iaddr} ${filesize}
update_configfs=tftpboot ${ram_addr} ${tftppath}configfs.image;sf probe 0;sf erase ${config_iaddr} +${filesize};sf write ${ram_addr} ${config_iaddr} ${filesize}
update_image0=tftpboot ${ram_addr} ${tftppath}${image_name}-squashfs.image;sf probe 0;sf erase ${kernel0_offs} +${filesize};sf write ${ram_addr} ${kernel0_offs} ${filesize}
update_image1=tftpboot ${ram_addr} ${tftppath}${image_name}-squashfs.image;sf probe 0;sf erase ${kernel1_offs} +${filesize};sf write ${ram_addr} ${kernel1_offs} ${filesize}
update_logfs=tftpboot ${ram_addr} ${tftppath}logfs.image;sf probe 0;sf erase ${log_iaddr} +${filesize};sf write ${ram_addr} ${log_iaddr} ${filesize}
update_openwrt=run update_system
update_ri=tftpboot ${ram_addr} ${tftppath}${ri_image};sf probe 0;sf erase ${ri_hiaddr} +${filesize};sf write ${ram_addr} ${ri_hiaddr} ${filesize};sf erase ${ri_siaddr} +${filesize};sf write ${ram_addr} ${ri_siaddr} ${filesize}
update_system=run update_image0 && setenv commit 0 && setenv image0_is_valid 1 && saveenv
update_uboot=run load_uboot && run save_uboot
update_uboot_env=run load_uboot_env && run import_uboot_env && saveenv
update_uboot_env_y=run load_uboot_env_y && run import_uboot_env && saveenv
update_uboot_y=loady ${ram_addr} && run save_uboot
ver=U-Boot 2015.04-lantiq-gpon-1.3.6.1 (Feb 07 2018 - 17:12:06)
boot_fail=0

Any idea why this is happening?

@hwti
Copy link
Owner

hwti commented Mar 6, 2022

Any idea why this is happening?

Everything seems normal, so unless something is interfering (writing to the magic_addr/act_img_addr locations, the bootloader should switch to image1.
Do you do everything with the fiber disconnected ?
Maybe there is an issue when booting, and something resets to image0, but you would need to check with the UART to find out.

@hmmferreira
Copy link

J2Kbr

Thanks for your explanation. Did you manage to get any speeds above 1Gbps? I am asking because I know UDM-Pro has some limitations, and it will only negotiate to 1Gbps or 10Gbps, but I found somewhere people saying that even though UDM-pro didn't recognise it at 2.5Gbps, they managed to make it work.

Thx in advance for your help!

@Delitants
Copy link

Can someone help me? I can't get internet access (original box seems acts like bridge and I get IP over DHCP, vlan seems get stripped after it). Can't get any VLAN map at all from G-010S-A (I don't even know if provider use any, but they do have internet and IPTV services). They use Nokia G-010G-A as an original box, which has absolutely no known web gui or ssh/telnet access. SLID was obtained directly from tech and entered in web gui of the G-010S-A, rest like serial etc, was taken from the sticker of the box. State O5 and no traffic.

ONTUSER@SFP:~# ritool dump
the Format:01
the MfrID:ALCL
the Factorycode:08
the HardwareVersion:3FE46541AACA
the ICS:01
the YPSerialNum: F9502F49
the CleiCode:BVL3A8JNAA
the Mnemonic:G-010S-A
the ProgDate:181229
the MACAddress:ec:84:b4:88:e1:ae
the DeviceIDPref:0000
the SWImage:3030
the OnuMode:0001
the G984Serial:f9502f49
the HWConfiguration:0000000000000000
the PartNumber:3FE46542AACA
the OperatorID:XXXX
the SLID:30303030303030303030303030303030
the CountryID:01
the GroupID:30303030

GPE VLAN rule

Name: ONU_GPE_VLAN_RULE_TABLE
ID: 42
;;;enable;;;ethertype filter;;;;;outer;;;;;;;inner;;;;;;
no;end;def;two;one;zero;5;4;3;2;1;de enable;de filter;input tpid enable;vid enable;vid filter;priority enable;priority filter;de enable;de filter;input tpid enable;vid enable;vid filter;priority e
nable;priority filter
0; ;1; ; ;1; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ;
1; ;1; ;1; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ;
2;1;1;1; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ;
1016; ;1; ; ;1; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ;
1017; ;1; ;1; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ;
1018;1;1;1; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ;
1020; ;1; ; ;1; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ;
1021; ;1; ;1; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ;
1022;1;1;1; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ;

onu gpevtfg 0
errorcode=-3011 index=2150712848 vlan_count=2200298620 vlan="2164811068 0 65 9375 2150712848 0 2164811068 0 24 125000000 2151200136 4294167296 0 4294967295 2150714156 0 1 0 2150714152 0 1 0 2 131290 33554431 196610 0 2147646304 131290 0 0 0 1 65 2150712848 2 2150694912 2149540784 2150712848 4000000 2437 136000000 2187551128 0 2187207568 2187321144 0 0 65 9372 2150712848 196610 2164811052 0 8 2187207568 2005323776 2201654592 4120621056 4294967295 2150714156 0 1 0 2150714152 0 0 0 0 722 33554431 0 38 2147646304 131794 0 0 2187207568 0 65 2150712848 0 3221241856 0 2150712848 2201478656 2188017152 34 210 12288 1 3221225472 3 2187680920 2150714152 722 210 0 2206588320 0 38 2148898848 2150714152 722 210 2188029824 2206588320 3 2188017152 2147821680 0 2151200620 40 20 4294758400 210 2209991632 0 2200640116 2209995240 2206588320 2197822160 0 2206588320 0 2200040424 0 2148560516 3 2164811064 3255373824 2200580392 0 2200042372 0 2209991632 1 0 2187976708 3255373824 2200567808 2200218268 40 0 2201654652 2199252864 2200579776 2206588320 2197822160 2200218356 3 4294967295 2187976708 2199252864 2199252864 2148071416 2187681192 2202142312 2187681312 0 2206268528 4456448 2206588320 2197822160 2 2206588328 2148071152 2148257148 2 2 0 2187681400 2187681536 2149899564 2187681536 2 2187681400 2187681536 2 2148284400 0 2200447948 3255373840 10600 3255373832 2200001208 2197822160 78 0 2202142312 0 3255373840 " vlan_mask=3255373832 pass_on_match_enable=10600 tagged_drop_enable=3255373824 tagged_pass_enable=2200025780

l2-table get entry address valid

LUT address: 0x000c (1K LUT)
L2 Unicast table:
MACAddress Spa Fid Age Vid State Ext Hash
00:00:00:01:00:02 3 0 1 0 Static 0 SVL
CtagIf Auth DaBlock SaBlock Arp
Dis Dis Dis Dis Dis

LUT address: 0x0228 (1K LUT)
L2 Unicast table:
MACAddress Spa Fid Age Vid State Ext Hash
C4:48:FA:16:1E:F4 3 0 1 0 Static 0 SVL
CtagIf Auth DaBlock SaBlock Arp
Dis Dis Dis Dis Dis

LUT address: 0x03b4 (1K LUT)
L2 Unicast table:
MACAddress Spa Fid Age Vid State Ext Hash
00:5F:67:C1:59:4D 0 0 7 0 Auto 0 SVL
CtagIf Auth DaBlock SaBlock Arp
Dis Dis Dis Dis Dis

@FomosUA
Copy link

FomosUA commented Aug 2, 2023

There is now the 3FE46398BGCB22 firmware, which should fix the issues with Huawei OLTs (at least it does for me).

not work in transparent mod for huawei olt. OLT----100.20 qinq----ONT-----vlan 20 tag----Switch-----vlan 20 aceess----client

conf OLT:
ont-srvprofile gpon profile-id 1 profile-name "1"
ont-port pots adaptive eth adaptive
transparent enable
port vlan eth 1 transparent

ont-lineprofile gpon profile-id 1 profile-name "1"
mapping-mode port
tcont 1 dba-profile-id 12
gem add 1 eth tcont 1
gem mapping 1 1 eth 1

ont add 11 5 sn-auth "414C434C******" omci ont-lineprofile-id 1 ont-srvprofile-id 1 desc "test_SFP_ONU"
service-port vlan 100 gpon 0/4/11 ont 5 gemport 1 multi-service user-vlan 20 tag-transform translate-and-add inner-vlan 20 inner-priority 0

But, Nokia ONT G-010G-Q works with this config

@imbeee
Copy link

imbeee commented Jan 27, 2024

There is now the 3FE46398BGCB22 firmware, which should fix the issues with Huawei OLTs (at least it does for me).

This version works for me. It fix the vlan issues with Huawei OLT. Thanks

@Delitants
Copy link

There is now the 3FE46398BGCB22 firmware, which should fix the issues with Huawei OLTs (at least it does for me).

This version works for me. It fix the vlan issues with Huawei OLT. Thanks

Doesn’t fix anything for Nokia OLT.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants