Community discussions

MikroTik App
 
Screemi
just joined
Topic Author
Posts: 2
Joined: Tue May 31, 2022 1:52 pm

CRS125-24G-1S (routerOS 6.48.3) Network stalls till it locks up

Tue May 31, 2022 2:24 pm

Hi

We have a CRS125-24G-1S with routerOS 6.48.3 and since about a year the network stalls down till it completely locks up and we have to manually reboot it. As soon as it stalls the webinterface and console is very unreliable and as soon as it locks up web/winbox and console are unusable. The only way to reboot is to use the touchscreen or simply pull the plug. We have to do the later because sometimes a reboot does not solve the issue.

When we updated to 6.48.3 our interface list got a little bit messed up and we didn't have the time/knowledge to fix it. Our IT provider went into retirement about a year ago and is not available anymore. There are no other MikroTik affine IT guys in our area. We had several companies for support and everyone just said we should switch HW provider to Cisco Business, Ubiquiti or some other brand. Actually have been pretty happy with our MT HW for several years and don't want to switch. That's why i am going to try to fix our issues my self now.

Here is an example of the stalling till lockup and after reboot:
C:\Users\USERXYZ>ping 192.168.48.9

Ping wird ausgeführt für 192.168.48.9 mit 32 Bytes Daten:
Antwort von 192.168.48.9: Bytes=32 Zeit=1248ms TTL=128
Antwort von 192.168.48.9: Bytes=32 Zeit=39ms TTL=128
Antwort von 192.168.48.9: Bytes=32 Zeit=1877ms TTL=128
Antwort von 192.168.48.9: Bytes=32 Zeit=241ms TTL=128

Ping-Statistik für 192.168.48.9:
    Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0
    (0% Verlust),
Ca. Zeitangaben in Millisek.:
    Minimum = 39ms, Maximum = 1877ms, Mittelwert = 851ms

C:\Users\USERXYZ>ping 192.168.48.9

Ping wird ausgeführt für 192.168.48.9 mit 32 Bytes Daten:
Antwort von 192.168.48.9: Bytes=32 Zeit=534ms TTL=128
Antwort von 192.168.48.9: Bytes=32 Zeit=108ms TTL=128
Antwort von 192.168.48.9: Bytes=32 Zeit=109ms TTL=128
Antwort von 192.168.48.9: Bytes=32 Zeit=960ms TTL=128

Ping-Statistik für 192.168.48.9:
    Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0
    (0% Verlust),
Ca. Zeitangaben in Millisek.:
    Minimum = 108ms, Maximum = 960ms, Mittelwert = 427ms

C:\Users\USERXYZ>ping 192.168.48.9

Ping wird ausgeführt für 192.168.48.9 mit 32 Bytes Daten:
Zeitüberschreitung der Anforderung.
Zeitüberschreitung der Anforderung.
Zeitüberschreitung der Anforderung.
Zeitüberschreitung der Anforderung.

C:\Users\USERXYZ>ping 192.168.48.9

Ping wird ausgeführt für 192.168.48.9 mit 32 Bytes Daten:
Antwort von 192.168.48.9: Bytes=32 Zeit=1ms TTL=128
Antwort von 192.168.48.9: Bytes=32 Zeit=15ms TTL=128
Antwort von 192.168.48.9: Bytes=32 Zeit=2ms TTL=128
Antwort von 192.168.48.9: Bytes=32 Zeit=2ms TTL=128

Ping-Statistik für 192.168.48.9:
    Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0
    (0% Verlust),
Ca. Zeitangaben in Millisek.:
    Minimum = 1ms, Maximum = 15ms, Mittelwert = 5ms

C:\Users\USERXYZ>ping 192.168.48.9

Ping wird ausgeführt für 192.168.48.9 mit 32 Bytes Daten:
Antwort von 192.168.48.9: Bytes=32 Zeit=1ms TTL=128
Antwort von 192.168.48.9: Bytes=32 Zeit=23ms TTL=128
Antwort von 192.168.48.9: Bytes=32 Zeit=2ms TTL=128
Antwort von 192.168.48.9: Bytes=32 Zeit=1ms TTL=128

i attached the supout.rif and maybe someone can take a look at it.

TY for your time!
You do not have the required permissions to view the files attached to this post.

Who is online

Users browsing this forum: devnull0, holvoetn and 33 guests