Who says cost effective = unreliable?
Still running 2.9.26 without a glitch for almost a year now.

Who says cost effective = unreliable?
Still running 2.9.26 without a glitch for almost a year now.



the same people who said the latest version is best?
this was 2.8.26 btw
2.9.26 seems popular : )
[@br2] > /system resource print
uptime: 58w5d10h1m32s ← 411d
version: “2.9.26”
free-memory: 861212kB
total-memory: 905764kB
cpu: “Intel(R)”
cpu-frequency: 2992MHz
cpu-load: 3
free-hdd-space: 1885948kB
total-hdd-space: 1959016kB
write-sect-since-reboot: 49865424
write-sect-total: 55303064
Woh, great uptime.
Hai frens
congratulation for all, and why anyone else restart needed…?
i love your uptime. ![]()
Just don’t touch it.
It’ll work.

Needs to be some sort of dude tool to check this.. have to go over about 20 or so devices ![]()
here


I don’t know why but one of my routers has rolled over it’s uptime.
BGP sessions have been up longer than the uptime counter.
[@br2] routing bgp peer> print status
Flags: X - disabled
0 name=“l3” instance=ebgp-1 remote-address=x remote-as=3356
tcp-md5-key=“” multihop=no route-reflect=no hold-time=3m ttl=60
in-filter=level3-in out-filter=level3-out remote-id=x
uptime=8w1d23h28m42s prefix-count=11 remote-hold-time=3m
used-hold-time=3m used-keepalive-time=1m refresh-capability=yes
state=established
1 name=“br1” instance=ebgp-1 remote-address=x remote-as=x
tcp-md5-key=“” multihop=no route-reflect=no hold-time=3m ttl=1
in-filter=ibgp-in out-filter=ibgp-borders remote-id=x
uptime=17w6d23h8m33s prefix-count=733 remote-hold-time=3m
used-hold-time=3m used-keepalive-time=1m refresh-capability=yes
state=established
[@br2] routing bgp peer> /system resource print
uptime: 4d21h25m23s
version: “2.9.26”
free-memory: 860768kB
total-memory: 905764kB
cpu: “Intel(R)”
cpu-frequency: 2992MHz
cpu-load: 2
free-hdd-space: 1885632kB
total-hdd-space: 1959016kB
write-sect-since-reboot: 61887520
write-sect-total: 67325160
Somehow I went from 450+ days to rolling it over. I know the router didnt reboot. Weird.
Sam
yep, time rolled over at approximately 496 days. Sten, can you check to see if your 490 day box rolled its time over already ? Just curious if it was my box only or some limit on uptime days in RouterOS.
Sam
afaik uptime is measured in ticks which are 100th of a second.
2^32 = 4294967296
so 2^32 ticks = about 497.1 days.
Im guessing they only use 32 bits long counter for uptime. hence the rollover.
jm
thats exactly it! so I supposed the uptime challenge ends at 497 days. bummer. maybe MT can change that to a 64 bit counter so in 2 years from now we can look back and still be counting.
we’ll try to fix it, thanks ![]()
Not Bad! ![]()

Uptime bug in routeros 5.22 ppc?
My uptime should be slightly more than 500days now. But it only shows 4 days.
But my PPPoE connection is 477 days (as it should be).
Is there a bug in routeros that it doesn’t show uptime above 500 days correctly?

7 years later and still not fixed ![]()
This is what a BGP Router should do. Just run
). RB1000 was a great device and 5.25 is the version which runs. Hope to see 6.25 anytime soon
).
[admin@gw18] > system resource print
uptime: 56w3d10h23m34s
version: 5.25
free-memory: 1250708KiB
total-memory: 1555512KiB
cpu: e500v2
cpu-count: 1
cpu-frequency: 1333MHz
cpu-load: 16%
free-hdd-space: 25800KiB
total-hdd-space: 61440KiB
write-sect-since-reboot: 18704950
write-sect-total: 23133082
bad-blocks: 0%
architecture-name: powerpc
board-name: RB1000
platform: MikroTik
[admin@gw18] >
RB2011 w/OSPF, MPLS, QueueTree and Firewall rules running smoothly for almost a year!! Approx. 25 clients connected to site and a few PtP’s. No restart needed, great!
[cnc@Site 26 (Panorama)] > system resource print
uptime: 45w6d19h36m53s
version: 6.12
build-time: Apr/14/2014 09:27:45
free-memory: 33.3MiB
total-memory: 64.0MiB
cpu: MIPS 74Kc V4.12
cpu-count: 1
cpu-frequency: 600MHz
cpu-load: 12%
free-hdd-space: 48.5MiB
total-hdd-space: 64.0MiB
write-sect-since-reboot: 1388868
write-sect-total: 2096657
bad-blocks: 0%
architecture-name: mipsbe
board-name: RB2011L
platform: MikroTik
We have many RouterOS boxes where the uptime counter has overflowed many times, so some of the boxes have many years of uptime …