I liked to use R52N card, so needed to upgrade to 4beta3 version. I run it on an rb600 and two rb433ah. Works without problems, but suddenly hangs up, and doesn’t do anything. Sometimes on the serial terminal works when I can’t ping the board, but sometimes doesn’t. And after 20-60 seconds comes back. The board doesn’t restart,
what could cause it?
64 bytes from 192.168.199.220: icmp_seq=116 ttl=64 time=0.197 ms
64 bytes from 192.168.199.220: icmp_seq=117 ttl=64 time=0.345 ms
64 bytes from 192.168.199.220: icmp_seq=150 ttl=64 time=4.19 ms
64 bytes from 192.168.199.220: icmp_seq=151 ttl=64 time=0.163 ms
…
64 bytes from 192.168.199.220: icmp_seq=418 ttl=64 time=0.209 ms
64 bytes from 192.168.199.220: icmp_seq=419 ttl=64 time=0.291 ms
64 bytes from 192.168.199.220: icmp_seq=432 ttl=64 time=0.186 ms
64 bytes from 192.168.199.220: icmp_seq=433 ttl=64 time=0.306 ms
There are too many factors, which can cause ping timeouts.
Firstly, you need to make sure that router is running the latest firmware. Upgrade it by the commands,
/system routerboard upgrade
/system reboot
Get local access to the router by null modem cable and check the output. Console should show all the information, what kind of problems are on the RouterBOARD.
I always trying through nullmodem-cable, and ethernet. It only occurs, if I connect the rb to a switch, and try to ping it. (but there is an RB433AH, and this 600A ) There is no any additional info about it.
You can do it by connecting Null Modem cable to the other RotuerBOARD,
on the other RouterBOARD you need to make the following,
/system console disable 0
/system serial-terminal serial0
Do not close connection and wait until the router will freeze again (that will give you information about the fact, what happen during the freeze).