Re: [NV-L] Layer 3 Events missing in trapd.log
2007-05-28 06:41:47
James,
Is there any way, we can find that Netview is discovering and processing Layer 2&3 Events because i cannot see no events related to Layer 2&3 and no events related to port monitoring(servmon.conf) where i have defined ports to monitor which was working previously fine.
Thanks & Regards,
Sudhakar Gandhi
On 5/26/07, James Shanks <jshanks AT us.ibm DOT com> wrote:
2000 events per minute is a trap storm. You event windows will never keep up with that amount of data. You need to shut off events from devices which are flooding you. Use the log to see which ones those are, and either reconfigure them to be less verbose or shut them off entirely. If you have to you can install an MLM as a trap receiver and him filter out duplicates..
James Shanks Level 3 Support for Tivoli NetView for UNIX and Windows Network Availability Management Network Management - Development Tivoli Software, IBM Corp
"sudha g" <sudha.unix AT gmail DOT com>
Hi,
>From Netview, events are stopped and when i run "
nvevents" command, there is no events in the event browser (it is blank). but i can see events in trapd.log file
We are getting lot of events from a messaging Server (average of 2000 events per minute) and in trapd.log i cannot find my other Layer 3 devices like node up/down,interface up/down events._______________________________________________
NV-L mailing list NV-L AT lists.ca.ibm DOT com
Unsubscribe:NV-L-leave AT lists.ca.ibm DOT com http://lists.ca.ibm.com/mailman/listinfo/nv-l
(Browser access limited to internal IBM'ers only)
_______________________________________________ NV-L mailing list NV-L AT lists.ca.ibm DOT com
Unsubscribe:NV-L-leave AT lists.ca.ibm DOT com
http://lists.ca.ibm.com/mailman/listinfo/nv-l (Browser access limited to internal IBM'ers only)
_______________________________________________
NV-L mailing list
NV-L AT lists.ca.ibm DOT com
Unsubscribe:NV-L-leave AT lists.ca.ibm DOT com
http://lists.ca.ibm.com/mailman/listinfo/nv-l (Browser access limited to
internal IBM'ers only)
|
|
|