-
Notifications
You must be signed in to change notification settings - Fork 106
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
UFiber UF-Instant management interface appears to go down shortly after reaching O5 state #309
Comments
To diagnose this issue, you'll need to dump the OMCI log and identify which MIB is causing the problem. For instance, the D-Link DPN-FX3060V (RTL9607DQ) has an ISP-specific OMCI MIB 517 that impacts the
In this case, the OLT pushes MIB 517, causing the WebGUI to be killed. It's possible that your OLT is doing something similar. Alternatively, MIB 171 might be causing the SFP stick to be disabled. This can happen for two reasons:
Identifying the specific MIB being pushed will help in determining the root cause and finding a solution. |
Is it possible to have It doesn't seem like the OMCI logfile path is configurable (possibly hardcoded in I've also tried running |
I see, it's better buy other stick instead like ODI or V2801F, no more headache about proprietary OMCI |
Yeah, I have one of the ODIs on the way -- I was just trying to get it up and running in the meantime with one of my UF-Instants, since the shipping is gonna take a really long time :) So anyway, I spent a bit more time messing around with it, and here's what I found out:
So with all of these caveats in mind... I'd just recommend that you not use a UF-Instant, especially if you're planning on using it with an SFP+ port on a Mikrotik router (and even if you aren't). For now, I've managed to get it working though, so there's that. |
I've got a UF-Instant running:
It's installed in a SFP+ port on a CCR2004-1G-12S+2XS.
After configuring the UF-Instant to match my ISP's Huawei HG8240T5 ONR and rebooting, it seems like the management interface goes down and the UF-Instant stops responding to pings or telnet to
192.168.1.1
.Removing the fiber cable and rebooting allows the stick to be reachable again, while inserting the fiber cable causes it to become unreachable shortly after the ONU state reaches O5 (as seen with
while sleep 1; do diag gpon get onu-state; done
).This leads me to suspect that it's because of something being pushed from my ISP through OMCI, though the nature of the issue makes it quite difficult to debug.
Is there a way to... prevent this from happening, somehow? Thanks!
The text was updated successfully, but these errors were encountered: