for some reason when a routerboard running ospf and ibgp shutdown or reboot, some routers on network crashed the routing process ( the cpu goes 100%) and only goes back with a reboot. everything related to routing goes down.
up to version 5rc01 the same ocurred with x86 versions. since 5rc02 up to the lastast rc5 when the crash trigger happens , the routing proccess restart (which is better then a total crash ) so we lost all our 26 bgp peering sessions that couses a total colapse on our network for about 2 minutes..
we have 2 border/core routers ( octa core HP ML350) and about 30 rb450 to 1100 as PoP routers. that problem was reported to support and i allways update them with new info. our maximum bgp session uptime was 8 days. i’m really worried because we put a lot of trust in mikrotik / routeros and that routing problem with ospf/bgp put our SLA down to the ground.
its a really weird problem , i think is caused by ospf election or something like that when a peer goes down. most happens with a peer with more than one ospf path goes down. i’m trying to fix setting all our ospf routers with priority 0 only leaving our border routers with a bigger priority so with that no ospf election will occour when a ospf peer goes down.
I updated a lot of our pop routers to 4.13 and some of them still crashes ( 100% cpu and no routing at all) and our 5Rc05 differs from the 4.13 because they just resets the routing proccess as i said before.
we run version 5 because its the one that works with our HP ML 350 CORE Router (servers) . and thank god we run version 5 because for sure i would been fired if our router core just crash the routing proccess and stay crashed like the version 4.
Hello we have RouterBoard 133.
I have tried several times to update my ROS 3.30(License key already updated) to 4.15 then 4.16 but i haven’t success.
I tried install both 4.15 and 4.16 combined packages and also all_packages of two versions but system every time
give me error and said: (Following message getting from after 4.16 all package installation)
“broken package system-4.16-mipsle.npk”
“verified package security-4.16-mipsle.npk”
“verified package routerboard-4.16-mipsle.npk”
So whats the problem both 4.15 and 4.16 system packages are broken?
Major bug to report, when upgrading RB/493 to 4.16, all Ethernet ports disabled. A site visit required to manually reboot Mikrotik then everything is fine. This happened on (2) RB/493’s I just upgraded. Good thing I had a power reboot device at the site 2 hours away…
First I upgraded from v4.11 to v4.16, rebooted, router came back without a problem.
After 2-3 minutes I upgraded firmware from 2.28 to 2.29 using “system routerboard upgrade”, then “system reboot”. Router did not come back… I had to drive there and manually unplug/replug to get it back. After this it seems to work ok, did some "system reboot"s, it booted successfully.
I had lost the license of a 433 upgrading from 3.30 to 4.15 ( before 4.16 lounching ) , after lounching of 4.16 i use netinstall to install 4.16 and after installation the RB reports no license, i click in update license button and my license comes back..
First thing is my VPN (PPTP) stopped working properly, and the static routes I had set up to go through the tunnel for some private IP’s failed working but I got that going.
But now I can’t FTP into sites out on the internet. I don’t have any major rules on this one router. Static routes mainly through the tunnel. I am natting some private 10.x.x.x ip’s.
I have a public so I basically only go through one filter chain which is “forward accept” .
No mangling or anything going on right now.
The odd issue is that I rebooted the router, and as SOON as it started to ping I tried to FTP and it worked. But then after the router was up for about 30 seconds it stopped working again.
Same problem with 493ah here, I updated from 4.14 to 4.16 after reboot the PPP menu was missing and all settings lost, even with another flash to 4.16 and new reboot. I downgraded back to 4.14 and restore my backup puhhhhh… With 4.14 I have a problem with the reboot signal from winbox , I must unplug the power to bring the router back online.
wispwest, which version was installed on your RB493?
Do you have any specific on the configuration?
As one thing I could think about is MAC-address, that was changed during upgrade/reboot and caused downtime on your router (when you have dynamic MAC-address settings in bridge).