We have 12 MX80's and they've been running fine for a year so far. Had a couple with disk corruption after reboots/upgrades (which were easy enough to fix with rescue USB drives), although tbh we don't console that much - we have out-of-band set up to them but always login via ssh On Wed, Jun 6, 2012 at 2:12 PM, Ian Batterbee wrote:

Just a quick question to those using juniper MX series routers.. or perhaps any series - is there a known issue with the console port dying ? We've seen this happen on two different boxes - completely unresponsive after running for a few weeks, reboot doesn't fix it, and no output at all on it, even during the freebsd boot sequence.

So before I start second and third-guessing what I've been doing to it, is this a known issue that people have seen elsewhere ?

_______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

-- Sam Russell Network Operations Research & Education Advanced Network NZ Ltd ddi: +64 4 913 6365 mob: +64 21 750 819 fax: +64 4 916 0064 http://www.karen.net.nz

Thanks for the replies. To answer questions, this is a real db9 port on a linux laptop, no usb trickery involved, and besides, the same cable works fine when moved to another mx80, or indeed to the aux port of the mx80 with the problem. We RMA'd another one with identical symptoms at JTAC's request - this is the replacement, which worked fine for about 2 weeks, then was untouched for a few more weeks, and then today I found the console port dead - exact same symptoms as before, and it seems rather too odd to be a coincidence. Hence my question about whether this is a common thing. I'll follow up with JTAC. On 6 June 2012 14:12, Ian Batterbee wrote:

Just a quick question to those using juniper MX series routers.. or perhaps any series - is there a known issue with the console port dying ? We've seen this happen on two different boxes - completely unresponsive after running for a few weeks, reboot doesn't fix it, and no output at all on it, even during the freebsd boot sequence.

So before I start second and third-guessing what I've been doing to it, is this a known issue that people have seen elsewhere ?