Hi Beny,
Also a general approach would be that you don't shouldn't need active
traceoptions during normal
operation. I would say the traceoptions are more troubleshooting
assistance than logging tools.
That said, I would also suggest to have a syslog server and have most
of the information sent there. Locally,
the defaults as listed below and maybe one or two little tweaks should
serve you fine.
Cheers,
Erdem
P.S: You may also want to check PSN-2008-02-011
On Fri, Jun 20, 2008 at 2:36 PM, <[EMAIL PROTECTED]> wrote:
> Hi Beny
>
> I believe the best Start is the default syslog config of JUNOS:
>
> system {
> syslog {
> user * {
> any emergency;
> }
> file messages {
> any notice;
> authorization info;
> }
> file interactive-commands {
> interactive-commands any;
> }
> }
> }
>
> After that you can add, as new target, the syslog server and add some more
> traces but carefully.
>
> You must keep in mind that for local logs (on the hard disk) if you see your
> log files rotating too fast (I mean if your files with the default size and
> number do not cover more than One week of time) they will be useless.
>
> Regarding the trace-options you must be careful also with some "flag all"
> statements that are writing on the disk a hudge amount of data.
>
> We've had sometimes some M series hanged because of some heavy traces.
>
> First thing so is to have a quick look at your log files:
> "Show log ?"
> If you see some of them that are rotating too fast, start removing some
> traces leading that.
>
> Hope this help
>
> Alain
>
>
> -----Message d'origine-----
> De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] De la part de Beny D Setyawan
> Envoyé : vendredi 20 juin 2008 13:30
> À : [email protected]
> Objet : [j-nsp] Best practice to manage log information
>
> Hi List,
>
>
>
> Somehow my m-series hang and need to reboot. JTAC suspected that this is due
> to harddisk busy, since there were so many log that write-erase to the
> harddisk and suggested to reduce that process. Does anyone has information
> what is the best practice on how to manage syslog severity on the Juniper
> router? Which log should be send to syslog server and should be save also in
> the router itself.
>
> The goal is how to make the router healhty by reduce log of changing any
> information on the router from harddisk on the routing-engine perspective.
> But in the other hand we need the log information for the NMS.
>
>
>
> Thanks & Rgds,
>
> Beny D Setyawan
>
>
>
>
>
> _______________________________________________
> juniper-nsp mailing list [email protected]
> https://puck.nether.net/mailman/listinfo/juniper-nsp
> _______________________________________________
> juniper-nsp mailing list [email protected]
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>
_______________________________________________
juniper-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/juniper-nsp
