Still multiple rb 411’s and 433ah’s that reboot due to watchdog failure when running any 5.x software. Firmware always updated to most recet.. Roll back to 3.30 and its smooth sailing. Thius happens on all kinds of setups. Rb’s connected to other RB with same verion ROS or different, auto on or off, full not full, auto on one side and full no auto on other.. Any and all combinations of the ethernet settings… There is always on side when its v5 to v5 that reports incorrect ethernet or duplex information.. Even when there set to the same like auto-auto with full-full or vice versa, one RB shows different information than other… Have had less reboots with one side auto and the other side no-auto.. Continued port flapping intermittent. You have to ping the attached rb and play with the ethernet settings to finally find a random combination that doesnt get packet loss.. Have some that one side is set to no auto half and other auto and full and is stable in terms of packet loss. Also highest actual throughput. I just dont understand why MT cant figure out this HUGE problem. I have changed boards, cables, power supplies etc no difference..
5.10 and 5.11
RB435g’s are now getting multiple times a day reboot due to kernal failure.!!! ALso updated to most recent firmware.. I almost give u[. Have lost sooooo many customers since trying to put some links on 5.xx for tdma wireless robustness… Last lost customers was 30 mins ago…
Heading out the door to purchase 4 IB798 via eden 1ghz boards to test out.. My entire business rests o if ros 5.xx runs stable on these things as I made the mistake in upgrading two primary links to 2x2 N… I dont want this issue going away… MT must have a wisp of there own.. I wonder of they use there own products loll
Im starting to replace some RB boards with 5.25 SBC’s