Joe are you setting up the trapd daemon to archive traps?
It sounds like you didn't run the canned script that does this, under
the following...
I use the TIVOLI Netview desktop under Configure > Set options for
daemons > Set option for event and trap processing daemons > Set option
for trapd daemon.. Once you get here read HELP to explain how to archive
traps.
You should never lose any traps unless you specify the file space limit
in the above setup. Also the specific traps you want to log, must have
"logging enabled" under Event Configuration.
I am running on Solaris but would assume you could do the same.
Hope this helps.
Jeff Fitzwater
CIT Systems & Networking
Princeton University
James Shanks wrote:
>
> I hear what you are saying Joe, and lots of people use a similar the
> mechanism
> you describe in order to better manage keeping copies of old trapd.logs by
> renaming them. But I don't understand your claim that
> if either the file size is too small and/or the network has lots of
> traps for that day, (and/or if you rotate logs every 24 hrs) then it is
> possible that you could lose some logging information if that happens.
>
> trapd keeps a count of every trap he writes and he adds the size in bytes to
> what he has already written. So as long as he handles the switching of
> trapd.log to trapd.log.old, there is no way you can lose traps, because he
> won't
> write the new one to the file until the old log has been switched. But
> some
> people have tried to force a switch on a 24-hour boundary and that can cause
> a
> problem if you are working with the actual trapd.log. I recommend that
> people
> let trapd switch the logs himself, and only mess with the trapd.log.old.
>
> James Shanks
> Tivoli (NetView for UNIX) L3 Support
>
> Joe Stover <jstover@state.pa.us> on 11/18/99 02:20:21 PM
>
> Please respond to jstover@state.pa.us
>
> To: NV-L@UCSBVM.UCSB.EDU
> cc: (bcc: James Shanks/Tivoli Systems)
> Subject: Re: Event logs limitation
>
> James:
> It is my understanding that the trapd.log size can be increased via
> smit,
> but if this file exceeds the size limit, then netview seems to copy
> trapd.log to trapd.log.old and then continue logging again on trapd.log.
> however if either the file size is too small and/or the network has lots of
> traps for that day, (and/or if you rotate logs every 24 hrs) then it is
> possible that you could lose some logging information if that happens. In
> smit options "set options for daemons", "Full Name of Trapd log maintenance
> script:" we have defined a script that Appends to a file if the size of
> trapd.log is over the specified. This is in parallel with our cron script
> that attaches the julian date for that particular day's log.
>
> Joseph E. Stover
> Network Technician
> Pennsylvania State Police
> 1800 Elmerton Avenue
> Harrisburg, PA 17110
>
> jstover@state.pa.us
>
> -----Original Message-----
> From: James Shanks [mailto:James_Shanks@TIVOLI.COM]
> Sent: Thursday, November 18, 1999 1:41 PM
> To: NV-L@UCSBVM.ucsb.edu
> Subject: Re: Event logs limitation
>
> Bert -
>
> I am not certain what you are asking for. A limitation on the size of
> trapd.log? A limitation on the size of ovevent.log?
> Both of these can be set by configuring those daemons, trapd and ovelmd,
> using
> the Framework menu for that or SMIT.
> But they do have built-in maximums you cannot override.
>
> James Shanks
> Tivoli (NetView for UNIX) L3 Support
>
> Bertram Chang <bertram.chang@BMO.COM> on 11/18/99 10:51:21 AM
>
> Please respond to Discussion of IBM NetView and POLYCENTER Manager on
> NetView
> <NV-L@UCSBVM.UCSB.EDU>
>
> To: NV-L@UCSBVM.UCSB.EDU
> cc: (bcc: James Shanks/Tivoli Systems)
> Subject: Event logs limitation
>
> Hi,
>
> Does any body knows that is there a limitation of event logs? If it does,
> where
> I can set the parameters?
>
> Bert
|