Hi @renedis, allereerst van harte welkom op onze community en ook alvast een warm welkom bij Odido!  Het is zeker mogelijk om de Zaram SFP+ module te gebruiken. Zodra de verbinding actief is, kan je mij of een andere moderator een PB sturen, dan zorgen we ervoor dat het serienummer geregistreerd wordt op de verbinding. Verder kan je meer informatie vinden in dit topic over het gebruik van een eigen modem/ONT en de instellingen hiervan: Eigen modem: wat zijn de vereisten? | Odido community. 

Hi @Demi van Odido , can I send you a PB, to test my XGSPON? 

That’s unfortunate to hear I was hoping this was an issue with the UDM-Pro, but it seems it’s an issue with SFP+ and Odido in general for some reason. I am still using the Huawei ONT as long as I’m not upgrading to a higher speed. Let me know if you find a permanent solution to this issue, and thank you for testing.

Thanks, ga ik doen!

@Demi van Odido, would it be possible to just clear the settings on the port of the OLT so that it doesn’t send the huawei specific commands to my ONU? 

I made longer writeup about this and testing here

But, long story short, Huawei is also suffering from it. While they certainly have SQM, which allows to reach maximal throughput, it still suffers heavily from crazy latency values. And simply limiting port speed for Zaram to value not higher than 5.2G results in nearly perfect upstream.  And SCM can be used on router itself in case of Zaram (I tried with OpenWRT and VyOS), and you can achieve similar similar results (depending on choice of SMT).

But downstream is bad for both of them. In fact, on Huawei even worse :)

So, it is general problem, not problem between Zaram and Odido. It a wider issue. It can be masked to certain extent and with different results, and Huawei is masking it so much as it can. But, to be honest, I prefer what I get with hard limit of 5.2G and Zaram. Upload become perfect, latency variation is minimal, no crazy spiking etc. 

And Download is tad better than with Huawei in terms of latency variation.

@TheMixpower so, outcome is : neither of them is really god, they just bad in different ways )))

But it looks to me, that on Zaram I never had such crazy values for latency as I see sometimes on Huawei.

So, I think I’ll stick to Zaram, limit TX to 5.2G and see what can I do about RX. (it sucks that on *BSD routers standard mechanisms can’t be used to address this issue at such speeds, and I am not ready to pull trigger on switching from pfSense).

By the way, back to ONTs registration.

Today I also made experiment with cloning REG ID  of my Huawei ONT. I cloned it on Zaram, Zaram was able in fact, to pass through authentication (or at least reported that), but it still didn’t work, as then it would stuck in barely responsive state. And, according to the logs, it would keep doing reconnects, as almost immediately after auth it’ll get disconnected. Tried to debug, tried to replace also sn_vsid and sn_vssn (effectively serial number) - same effect.

I’d probably debug more, but debugging something, which responds to commands once every few minutes is a pain :)

And one more update. I recheck. Limiting download bandwidth with fc-codel puts download latency also under control. Also around 5Gbps.

Thus, outcome is simple: stable service is up to 5Gbps. Above that you exchange quality/stability for bandwidth.

Are you on the 8Gbps package? I am having a similar issue as you with the auth, where I get to O5 and then I get reset. If you can access the omci commands, you might be getting the same issue I am. It seems the Huawei OLT’s send some vendor specific command and then alarms due to it. 

@ChaosMonkey 

Yes, exactly same story, reset after O5, when I am trying to mimic Huawei, and proper work when I use Zaram’s ID.

Do you also have telnet becoming PAINFULLY slow at this moment, or it is something local for me?

Oh no mine is fine, but if I try to up the debug level or dumb the omci output to console I loose my telnet and the admin ip becomes unavailable. But I have a MaxLinear chip, from E.C.I. Networks. I am getting 3540 and 373 managed entities commands, from the Huawei OLT. Which my device does not support, then my device gets kicked. 

OLT, depending on detection of ONT, might use different vendor profiles. So, no surprise here. It detects us as huawei

I suspect something similar in my case. I just didn’t have enough of patience to debug around non-responsive and regularly lost telnet.. Although it is confusing to me. According to stats, microcontroller pin ONT is used only for 6%. Then I am lost why it becomes sooo slow and, eventually, freeze.

In addition to your bufferbloat, do you see route flipflopping? 

Ive seen your another thread, yes and I think bad routing might be behind bufferbloat also.

traffic looping might heavily increase chance of it

I will check

Is het ook al mogelijk om op het Delta netwerk een eigen ONT te laten registeren? Heb ondertussen een XGS-PON module binnen voor mijn Fritzbox 5590 en zou deze graag willen laten registeren.

Hi @Akiranon, dit ga ik regelen! Stuur je mij een privébericht met het serienummer van je ONT? Ik kom er dan zo snel mogelijk op terug!

@Cheyenne van Odido : Super! Ik heb je een PB gestuurd.

Inmiddels online met de standaard ONT. De Gideon monteur heeft geprobeerd (samen met back-office) om mijn Zaram online te krijgen, maar dat is helaas niet gelukt. Ik stuur je dus even een PB.

@renedis Super dat je online bent! Ik heb de Zaram module voor je geregistreerd.

Helaas komt de Zaram niet online. Ik krijg geen DHCP adres. Ik heb je een PB gestuurd.

Ik ben nu online met de Zaram.

FYI voor nieuwe klanten die van KPN/Delta/xProviderx overstappen naar Odido en al eerder XGSPON met eigen ONT gebruikte dient er een “clear” uitgevoerd te worden. Anders blijft de ONT op de oude provider staan in de OLT.

Is er iemand beschikbaar om mijn XGS-PON SN te testen? Ik zou moeten testen met een nieuw serienummer en, als het niet werkt, terugvallen op het originele.

Hey @ChaosMonkey, door de drukte in mijn privé inbox is je bericht helemaal naar beneden verdwenen. Ik pak hem meteen op!