Someone please correct me if I am wrong (
I am also new to Netview)
Your best bet is to remove them at the
source. You only want traps coming into Netview that you wish to act upon.
Do you know what product/device is sending
Setting up a trap for them is only going
to change the formatting of the information; you will still process them
through trapd and still have the associated overhead.
firstname.lastname@example.org [mailto:email@example.com] On Behalf Of Amir, Mohammed - Corporate
Core - ICT Services
Sent: July 12, 2007 5:27 AM
Subject: [NV-L] Trapd Events
First question about netivew....I am new to Netview so
people I apologise in advance for any stupid questions.
I have a situation where I'm receiving loads of traps in
trapd.log and most of them are similar to the following:
? NO FMT IN TRAPD.CONF: Enterprise (22.214.171.124.126.96.36.199.5) generic:4
Now this is what I have done to try and get rid of this
I have started xnmtrap and added a new Enterprise Name
called Enterprise and an Enterprise ID
as 188.8.131.52.184.108.40.206.5 and then added an Event Name as Authentication_Error and
under generic trap I left that as Enterprise Specific with the specific
trap as 0. I reloaded the trapd.conf file with event -e
FMTCHG command and was hoping that this will get rid of the NO FMT
bit but I'm still getting then and this whole saga has left in
confusion hence my plea for help to you guys who have worked with this
product for a while now.
Also is there a way to acknowledge these trap events so that
they stop coming into the trapd.log file once you start to action on it or you
are aware of the issue ....this is to stop the log file going into some kind of
trap storm which inadvertently affects demand poll and quicktest.
Oxfordshire County Council - rated a four-star 'Excellent' council by the Audit
The information in this e-mail, together with any attachments, is confidential.
If you have received this message in error you must not print off, copy, use or
disclose the contents. The information may be covered by legal and/or
professional privilege. Please delete from your system and inform the sender of
the error. As an e-mail can be an informal method of communication, the views
expressed may be personal to the sender and should not be taken as necessarily
representing the views of the Oxfordshire County Council. As e-mails are
transmitted over a public network the Oxfordshire County Council cannot accept
any responsibility for the accuracy or completeness of this message. It is your
responsibility to carry out all necessary virus checks. You should be aware
that all emails received and sent by this Council are subject to the Freedom of
Information Act 2000 and therefore may be disclosed to other parties under that