Re: [j-nsp] Only user login class super-user can execute reboot on Junos 8.5R3.4

Could I answer the next time, if you not objection...because there are other case which have to focused. let me to explain again.. I have implemented 6 routers most of them get problem the issue is the routing engine iniating reboot it self without any alarms. while the cfeb can't forward, If I re

Re: [j-nsp] Best practice to manage log information

--- [EMAIL PROTECTED] wrote: Here's how I do it in Solaris: /var/log/router.log -C 100 -c -p 1d -t /var/log/old-router-logs/router.log.%m-%d-%Y -z 1 /var/log/router.log -- BTW, the command is in my /etc/logadm.conf file and is one line. scott

Re: [j-nsp] Best practice to manage log information

- [EMAIL PROTECTED] wrote: - From: "Beny D Setyawan" <[EMAIL PROTECTED]> 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 any

Re: [j-nsp] default TTE for entries in the ARP table/cache

On Jun 20, 2008, at 5:55 PM, Judd, Michael (Michael) wrote: What is Juniper's default TTE for entries in the ARP table/cache ? RTFM? --Daniel __

Re: [j-nsp] Best practice to manage log information

On Fri, Jun 20, 2008 at 06:30:15PM +0700, Beny D Setyawan wrote: > 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. This one is start

[j-nsp] default TTE for entries in the ARP table/cache

Hello, What is Juniper's default TTE for entries in the ARP table/cache ? I see on the router that the arp aging-timer can be set and the range is 20-240 minutes. M40e-2-re1# set system arp aging-timer ? Possible completions: Change the ARP aging time value (20..240 minutes) Than

Re: [j-nsp] Best practice to manage log information

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

Re: [j-nsp] Only user login class super-user can execute reboot on Junos 8.5R3.4

Hi Amin, I'm not sure I follow you .. If I understand you correctly: a- upgrade from xxx ---> 8.4R3.4 ---> 8.5R3.4 : class with permissions all can't do 'request system reboot' and to solve this you need to reboot the box once more. b- upgrade from xxx directly to 8.5R3.4 (with no-validate): e

Re: [j-nsp] Best practice to manage log information

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

[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 t