-
Notifications
You must be signed in to change notification settings - Fork 95
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
O5 but no ONU ID and no connection #282
Comments
@Anime4000 Don't you have any comment? I can not debug omci too /tmp/omcidebug.par is empty. |
The Xicom SFP is the same hardware as ODI you can use any ODI firmware on it, show the output of mib 84 and 171 by telnet commands: omcicli mib get 171 |
the outpus is
|
The above index 0 changes VLAN 35 to 1600, try VLAN 1600, mib171 is not followed by Realtek chipset SFPs like ODI, Lantiq will follow mib171 correctly and you can use VLAN 35 like original ONU Like FS SFP. |
how can i change the vlan 1600? from ODI or on mikrotik. sfp-sfpplus1 interface tagged to vlan35, and vlan35 selected by my pppoe_client interface on mikrotik. Is it correct? |
Yes, just use VLAN 1600 instead, so sfpplus1 tag make it VLAN 1600 |
Thank you very much :) Mikrotik gave me the error "we could not verify ourselves for peers" a few times, then it connected by itself |
Is the Upload and Download the same as Original? |
Hello again, Today my connection lost suddenly. My guess my ISP changed some configs. I saw the connection when I connected the ISP's OLT back from vlan35. Obviously SFP-OLT mib84 query is empty like
ZTE's mib result like this. It is different according to my older result.
|
Does it still have O5 status? |
yes O5 |
Try VLAN 771 on ODI |
ZTE's MIB84 query data previously showed hex(06 40) dec(1600). Currently it says hex(03 03) dec(771) in the same place. Accordingly, I tried to connect to Mikrotik with vlan 771, but it did not work. |
So, which VLAN should I assign to the sfp-plus1 interface in mikrotik? |
The most likely explanation is you have fake O5... |
Maybe try: |
did not change anything. I looked at the link you sent. I set all OMCI related things. But still MIB 84 and MIB 171 got empty. I can not understand my O5 state fact or fake. Do you have any suggestion? What can i do? This system worked a few weeks with same router same SFP and same ISS. |
Well you can try Lantiq based GPON SFPs like this one: |
flash set OMCI_OLT_MODE 21 |
it is already 21 right now. because when i change it, my software version changes itself then onu state changes between O3 and O5 |
on your ZTE ONU, can you get MIB 350 until 399 (Vendor Specific OMCI) |
There is no data between mib 350 and 399 |
Hello Everyone,
I'm from Turkey and I use turktelekom as ISS. they provide me GPON ONT which is ZTE ZXHN F601 and does not supply any information about changing their ONT. I have a Mikrotik RB4011 router and eth1 tagged the vlan35 and my pppoe client uses vlan35 as interface. My connection speed is 1000/100mbps
i am tring to use DFP-34X-2C2 as GPON ONT like everbody is here. But my SFP ONT brand is not ODI it is Xicom I bought it from aliexpress so I'm afraid of changing its firmware because all firmwares tested on ODI. My version is "V1.0-220923"
i have connection to ZTE ONT via http and telnet and I can quering to ME codes and it have "setmac" command for some configs. I collected all information from ZTE. they are below.
I have always got O5 state but no ONU ID and LOID status is Initial Status. I have no connection to internet. What is missing or how can I debug the auth state?
As I understand setmac commands defination below. But Im not sure
setmac 2 512 gives device serial number
setmac 2 768 gives OUI
setmac 2 2176 PON vendor ID (first 4 char of gpon serial)
setmac 2 2177 GPON serial number (last 8 char of gpon serial)
setmac 2 2178 PLOAM password.
Loid and loid password obviosly seems in ME 256 query
ZTE setmac commands
ZTE OMCI ME queries
i applied all information to DFP-34X-2C2 but there is no connection. They are below.
DFP-34X-2C2 config
The text was updated successfully, but these errors were encountered: