10.1 Main Router new RB1100 watchdoged to ip of fiber switch - No problems with watchdog to that address no reboots
10.2 Second router RB433AH (replaced with RB433 as thought previous board was defective) in the line up as important takes data from outside to inside.
10.2 keeps rebooting due to ping timeout to 10.1..!! was every few hours now every 20-40 mins.. I changed everything I can think of…
changed the board itself, changed the outdoor rj45 to inside, changed power supply changed the rb110 ports from 12 and 13 to 1 and 2 so now nothing on 11-12
when the 10.2 dies, the rb1100 still seems to be working normally as im still logged into it and see the ethernet plug of 10.2 go down and reboot.
All in production stuff and about to loose my business…!!!
could it be this damn rb1100 even though to me it looks to be working okay? It was running 5.0then upgraded to 5.1still same crap… rb1100 was installed a few days ago and it seems these issues started slowly from there… 10.2 was rebooting like once maybe twice a day down to now every 10-30 mins
If X.X.10.2 can’t ping X.X.10.1 and is rebooting because of it (the watchdog timer) why not simply turn it off temporarily (the watchdog timer) and try to work out where the issue is that’s causing it not to be able to ping 10.1?
I have done that. I have also changed ports on the 433.
Problem seems to have been resolved by taking the RB1100 and throwing it off the 5 floor into the parking lot.
Put back in service older 386 core router ROS machne and all seems back to normal..
MOST LIKELY CAUSE of me loosing a once perfect reputation and probably will loose some very important customers tomorrow when the dust settles…,
F’'ing piece of crap RB1100 that doesnt seem to be able to deliver data over a distance of 130 ft.. Again, badely tested hardware that they were just eager to get out the door and sell to us suckers..!!
DO NOT USE A RB1100 FOR MEDIUM TO LONG DISTANCE CABLE RUNS!!! YOU WILL LOOSE YOUR BUSINESS
overreacting like that to a configuration issue most likely introduced by yourself, will not get you very far, and will eventually get somebody mad there at the parking lot …
sorry for reacting quite heavily, but I have had this setup working for the past two years with the x386 as main router going to the rest of my 433’s.. Since ROS 5.xx all hell has broken loose.. I just clearly dont see what the hell the point is of calling a release STABLE when its pretty much one of the worst one I have ever seen..
I use MT products ONLY for the past 7 years since pre 2.9.5
ROS 5.xx has HUGE issues with port links going up and down.. Sometimes its stable with auto nego off, sometimes on, sometimes good for a couple days with half Dup.. Its horrible. I have had some issues lately with 802.11 and tdms has saved my ass, my the fact that ROS 5.xx is causing etehrnet link issues, my routers are rebooting from watchdog time outs.. This is causing havoc on my clients especially that most of them us VoIP.!!
I cant turn watchdog off cause everything locks up…
PLEASE PLEASE PLEASE hurry and workout the etehrnet link issues with 5.xx