Re: [j-nsp] RE switch master to backup
Gents, has anybody seen a dual RE MX gear switch the routing engine master to backup due to a “possibly bad console cable” ? Jul 1 11:21:29.941 2015 MX480LON_0 init: getty repeating too quickly on port /dev/ttyd0, sleeping 30 secs Did you happen to find a resolution for this? That message seems the most telling as to why it would fail over. On Sun servers there used to be a way cool method to get them to reboot: Send a trillion BREAKs over the console. Same thing could happen if you rebooted your console device a few times, or, indeed, if the cable was bad. I'm not sure if JUNOS operates like this internally, but as they have common BSD roots it could be related. Cheers Ross ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] RE switch master to backup
Once upon a time, Ross Halliday ross.halli...@wtccommunications.ca said: On Sun servers there used to be a way cool method to get them to reboot: Send a trillion BREAKs over the console. Same thing could happen if you rebooted your console device a few times, or, indeed, if the cable was bad. I'm not sure if JUNOS operates like this internally, but as they have common BSD roots it could be related. That was related to OpenFirmware serial console behaivor, which would be unrelated to the Juniper BIOS (for x86 systems) or U-Boot (for the other) behavior. It didn't have anything to do with the OS that was running. Also, Solaris is System V, not BSD (/usr/ucb notwithstanding). On OpenFirmware, sending a BREAK would drop the system to the firmware prompt, which stopped the running OS (the firmware was essentially always loaded and running in the background). BIOS and U-Boot systems don't operate like that (well, there are things like SMM, but that's different). -- Chris Adams c...@cmadams.net ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
[j-nsp] RE switch master to backup
Gents, has anybody seen a dual RE MX gear switch the routing engine master to backup due to a “possibly bad console cable” ? Jul 1 11:21:29.786 2015 MX480LON_0 /kernel: sio0: 1 more excessive framing errors (total 1) Jul 1 11:21:29.941 2015 MX480LON_0 init: getty repeating too quickly on port /dev/ttyd0, sleeping 30 secs Jul 1 11:21:31.136 2015 MX480LON_0 /kernel: sio0: 1 more excessive framing errors (total 2) Jul 1 11:21:32.473 2015 MX480LON_0 chassisd[1694]: CHASSISD_RE_CONSOLE_FE_STORM: Console device encountering framing error storm on Routing Engine 0 (possibly a bad console cable) Jul 1 11:21:32.485 2015 MX480LON_0 alarmd[2729]: Alarm set: RE color=YELLOW, class=CHASSIS, reason=Excessive framing errors on console port Code is 13.3R6 I’m not able to find any PR or KB. Thanks for any input. Cheers James ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
