[j-nsp] Templates for logging from EX series

[Scott T. Cameron]

I'd recommend you not rely on Juniper to do this but instead do it yourself.
 If you output the entire contents of syslog to a syslog-ng server, you can
do all of the intelligent filtering you need on the server end.

Personally, I'd rather Juniper focus on fixing bugs for my SRX. :)

Scott

On Wed, Jun 23, 2010 at 1:12 PM, <sthaug at nethelp.no> wrote:

> > 2) I disagree with a huge number of the default prioties for a lot of
> > events. For example, an IGP DOWN event is a priority 5 / notice, while
> > an IGP UP is a priority 6 / info. If you actually want to match up your
> > igp flaps and know if a circuit has come back up you'll need to monitor
> > all the info stuff, in which case be prepared for a flood of useless
> > crap messages.
>
> Agreed, having IGP UP be an info event is awful. I'm afraid it may be
> too late in the game to change the default, however.
>
> But Juniper - pretty please: We *really* need a simple method to be
> able to match UP and DOWN events and not drown in useless trash.
>
> Steinar Haug, Nethelp consulting, sthaug at nethelp.no
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>