[j-nsp] (no subject)

[C. Hagel]

What exactly are you looking for in the logs?  When this thread started
you were looking for "interface logs", which from your setup and example
output you are getting.  You also want to see Protocol logs, these are
going to be in a differect file.  This is usually set under the [ system
syslog ] section.  If you are looking for protocol logs and interface
up/down messages you will set it under [ system syslog ] with the
command:

root# set system syslog file messages any any

this will give you all messages and will catch interface up/down as well
as protocol transitions (along with a lot of other stuff). 



On Mon, 25 Apr 2005 19:08:06 +0300
S B <akdamar at gmail.com> wrote:

SB> Erdem,
SB> Thanks again.I tried it.
SB> 
SB> 
SB> 
SB> Below you can see my config.
SB> [edit interfaces]
SB> 
SB> M10i-re0# show 
SB> traceoptions {
SB>     file intf size 10m files 2;
SB> 
SB> e1-0/0/0:2 {
SB>         traceoptions {
SB>         flag all;
SB> 
SB> 
SB> 
SB>  After I run monitor start intf I see a few log like these.
SB> 
SB> Apr 25 18:46:32 Going idle, 11 sync writes, 9 sync reads, 0 ifstate
SB> msgs, 0 ifstate reads, 0 rtb msgs, 0 rtb reads, 2422 usec
SB> Apr 25 18:46:32 Received SIGCHLD, collecting zombies.
SB> Apr 25 18:46:32 Received SIGCHLD, collecting zombies.
SB> 
SB>  But I expect ospf logs or other packets logs at least.
SB> What do you think about?What is the problem?
SB> 
SB> 
SB> On 4/25/05, Erdem Sener <erdem.sener at borusantelekom.com> wrote:
SB> > 
SB> > 
SB> > Hi,
SB> > 
SB> > You don't have to enable any flags on [edit interfaces] section. What
SB> > you can do,
SB> > if I understood you correctly, is something like:
SB> > 
SB> > [edit interfaces]
SB> > set traceoptions file intf-msgs size 10m files 50
SB> > [edit interfaces ds-1/2/3:4]
SB> > set traceoptions xxx
SB> > 
SB> > where xxx could be "all", or "event" etc.
SB> > 
SB> > Now when you run "monitor start intf-msgs", you should only see
SB> > traceoption logs
SB> > for the specific interface(s).
SB> > 
SB> > Hope this helps,
SB> > Erdem
SB> > 
SB> > > -----Original Message-----
SB> > > From: S B [mailto:akdamar at gmail.com]
SB> > > Sent: Monday, April 25, 2005 6:07 PM
SB> > > To: Erdem Sener
SB> > > Cc: juniper-nsp at puck.nether.net
SB> > > Subject: Re: [j-nsp] (no subject)
SB> > >
SB> > > Hi Erdem,
SB> > > First of all thanks for your  reply.It seems OK but when I
SB> > > enable general flags on  edit interfaces I see all of
SB> > > interfaces traces.How can I only see only specific interfaces
SB> > > logs? Is it possibble?
SB> > >
SB> > > On 4/25/05, Erdem Sener <erdem.sener at borusantelekom.com> wrote:
SB> > > >
SB> > > >
SB> > > > Hi,
SB> > > >
SB> > > > You should specify the filename on [edit interfaces]
SB> > > section. You can
SB> > > > also enable general flags here, or insert
SB> > > additional/different flags
SB> > > > for individual interfaces.
SB> > > >
SB> > > > Cheers,
SB> > > > Erdem
SB> > > >
SB> > > > > -----Original Message-----
SB> > > > > From: juniper-nsp-bounces at puck.nether.net
SB> > > > > [mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of S B
SB> > > > > Sent: Monday, April 25, 2005 5:31 PM
SB> > > > > To: juniper-nsp at puck.nether.net
SB> > > > > Subject: [j-nsp] (no subject)
SB> > > > >
SB> > > > > Hi ,
SB> > > > >
SB> > > > > I have a problem with debugging in JUNOS .
SB> > > > >
SB> > > > > I set traceoptions flag all for an e1 interface in m10i
SB> > > > > router.Usually when I want to see traces online I set
SB> > > traceoptions
SB> > > > > file  then I operate monitor start file_name command.However
SB> > > > > traceoptions file file_name  command does not work for  the
SB> > > > > interface.How could I see the traceoptions log online  for e1
SB> > > > > interfaces .??
SB> > > > >
SB> > > > > cheers.
SB> > > > > SB
SB> > > > >
SB> > > > > _______________________________________________
SB> > > > > juniper-nsp mailing list juniper-nsp at puck.nether.net
SB> > > > > http://puck.nether.net/mailman/listinfo/juniper-nsp
SB> > > > >
SB> > > >
SB> > > > UYARI/NOTIFICATION:
SB> > > >
SB> > > **********************************************************************
SB> > > > ***** Bu e-posta ve ekleri sadece gonderilen adres
SB> > > sahiplerine aittir.
SB> > > > Bu mesajin yanlislikla tarafiniza ulasmis olmasi halinde,
SB> > > lutfen gondericiye derhal bilgi veriniz ve mesaji
SB> > > sisteminizden siliniz. BORUSAN TELEKOM bu mesajin icerigi ve
SB> > > ekleri ile ilgili olarak hukuksal hicbir sorumluluk kabul
SB> > > etmez.  Gonderen taraf hata veya unutmalardan sorumluluk kabul etmez.
SB> > > >
SB> > > > The information contained in this e-mail and any files
SB> > > transmitted with it are intended solely for the use of the
SB> > > individual or entity to whom they are addressed.If you
SB> > > received this message in error, please immediately notify the
SB> > > sender and delete it from your system.BORUSAN TELEKOM doesn't
SB> > > accept any legal responsibility for the contents and
SB> > > attachments of this message..The sender does not accept
SB> > > liability for any errors or omissions.
SB> > > >
SB> > > >
SB> > > **********************************************************************
SB> > > > *****
SB> > > >
SB> > >
SB> > 
SB> > UYARI/NOTIFICATION:
SB> > ***************************************************************************
SB> > Bu e-posta ve ekleri sadece gonderilen adres sahiplerine aittir. Bu mesajin yanlislikla tarafiniza ulasmis olmasi halinde, lutfen gondericiye derhal bilgi veriniz ve mesaji sisteminizden siliniz. BORUSAN TELEKOM bu mesajin icerigi ve ekleri ile ilgili olarak hukuksal hicbir sorumluluk kabul etmez.  Gonderen taraf hata veya unutmalardan sorumluluk kabul etmez.
SB> > 
SB> > The information contained in this e-mail and any files transmitted with it are intended solely for the use of the individual or entity to whom they are addressed.If you received this message in error, please immediately notify the sender and delete it from your system.BORUSAN TELEKOM doesn't accept any legal responsibility for the contents and attachments of this message.The sender does not accept liability for any errors or omissions.
SB> > 
SB> > ***************************************************************************
SB> >
SB> 
SB> _______________________________________________
SB> juniper-nsp mailing list juniper-nsp at puck.nether.net
SB> http://puck.nether.net/mailman/listinfo/juniper-nsp


-- 
C. Hagel           <nanog at lordkron.net>
JNCIP #103
--