Hi Alex,
My understanding of this approach is alarm is there to grab your attention. To alert you about problem with something.
And in order to dig into problem you have to look further into logs and outputs.
On 23-Feb-16 18:42, Alex K. wrote:
Hello Timur, Thank you. Unfortunately, we ran those test to no avail. Since all the MX says is "major alarms at fpc x", it is seems that document intended for those specific errors it covers. I really wish Juniper will correct that message and put a proper documentation in place. Owning such powerful box, usually at important junctions of your network, with such amateur messages as troubleshooting triggers, sometimes seems to me as owning a Porsche with controls taken from Ford model T. Definitely not good starting point when the time comes for deciding on new boxes for your network. בתאריך 17 בפבר' 2016 17:12, "Timur Maryin" <timamar...@mail.ru <mailto:timamar...@mail.ru>> כתב: Hi Alex, Maybe this http://kb.juniper.net/KB23173 ? On 16-Feb-16 10:31, Alex K. wrote: As for the documentation, let begin with some knowledge base article outlining initial steps for alarms troubleshooting steps for MX. I'd like to read that one, to begin with.
_______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
