I have a 133 with 3 r52s that died suddenly and in an odd fashion.
I was working on the ospf configuration because one interface was not populating (remotely 30 miles away) adjacent routes. I decided to reboot because there was nothing wrong with the config. Dead on reboot. Drive 30 miles. Downstairs… no ping, no neighbor view, but NIC is lit on laptop. Climb up 80ft. Power cycle, hear first 2 beeps no third beep, reset with jumper/button, same result, no neighbor view, repeat.
Now I decide I am going to need to reconfigure with serial console. I pull the board, my only spare 133 is not available till tomorrow afternoon, so I bring it back to my office, plug it in without any r52s and .. I hear the third beep, before I even plug in the serial cable. OK good, maybe I can fix it. Its mac pops up in winbox (cleared ip/config though but I have the settings).
I start setting everything back up. After a few items.. (password/ip of ether1 etc) I remember I need to put back in the r52s, and I also notice that the ROS is 2.9.41. I upload the new OS, power down pop in the cards and power on. Never hear the first 2 beep.ARGH, worse than befor. I check the serial console, nothing. I try pulling the cards one a t a time, followed by a power cycle. No beep. I do notice that about every minute, the ether1 indicator lights both go out for a second.
Any chance of recovery? Ideas as to where to start?
One note, this is not my normal serial cable, I cannot find it, so the dead console, may not be an indicator.
