Larry,
I'd surmise that you are correct but I don't have any better idea what
this message means than you do. That's an issue for the sender. There may
be comments in the MIB which will tell you some more, or else you will have
to consult the vendor, either in his manuals or through a support channel,
unless you can find another user who knows. There is no standard for what
one puts in a trap. The vendor, whose agent sends it, decides.
But you can make the message say whatever you want it to say using xnmtrap.
You don't have to display all the variables ($*) in the log message.
mib2trap does that because he doesn't know what else to do. That's his
default. But you can customize this trap to display just the text you want
, or a combination of variables and text, such as "Disk space low in
partition $2 ". That would make this trap msg be simply "Disk space low in
partition /dev/w0f" when you see it again. The addtrap scripts mib2trap
creates are just starting points.
James Shanks
Level 3 Support for Tivoli NetView for UNIX and Windows
Tivoli Software / IBM Software Group
Larry Fagan
<larrytechie@yaho
o.com> To
Sent by: nv-l@lists.us.ibm.com
owner-nv-l@lists. cc
us.ibm.com
Subject
Re: [nv-l] Traps not formatting
04/01/2005 01:55 right!
PM
Please respond to
nv-l
James,
I just made a copy of trapd.conf and added another
enterprise OID as NOKIA-SYS with OID as
1.3.6.1.4.1.94.1.21.1(without 0). Now when the traps
came , they are formatted right as below.
" systemTrapLowDiskSpace - NOKIA-SYS 6 4 4 args: [1]
hrPartitionEntry.hrPartitionIndex.3.1 (Integer): 1
[2] hrPartitionEntry.hrPartitionLabel.3.1
(OctetString): /dev/wd0f [3]
hrPartitionEntry.hrPartitionSize.3.1 (Integer): 396952
[4]
host.hrDevice.hrFSTable.hrFSEntry.hrFSMountPoint.1
(OctetString): / "
This trap's event name is systemtrapLowDisSpace. So
what am i supposed to understand from this trap
message. That there is low disk space on /dev/wdof? am
i right? Is there a way to trim this message more
meanfull? b'cos the message never said that there low
disk space.
Thanks again..
Larry
--- James Shanks <jshanks@us.ibm.com> wrote:
>
>
>
>
> Ooops. Sorry. Spoke too soon.
> Actually, come to think of it, that will be harder
> to do because xnmtrap
> only lets you add and delete enterprise ids, not
> modify them.
> You could make a backup copy of trapd.conf and edit
> the running one, but
> that's a lot of work, since you have to correct the
> enterprise entry and
> all the individual entries too.
>
> Still got your addtrap script from mib2trap? Fix it
> there. You can delete
> all the old entries using xnmtrap, or just add the
> new ones with the
> addtrap script.
>
> James Shanks
> Level 3 Support for Tivoli NetView for UNIX and
> Windows
> Tivoli Software / IBM Software Group
>
>
>
>
> James
>
> Shanks/Raleigh/IB
>
> M@IBMUS
> To
> Sent by:
> nv-l@lists.us.ibm.com
> owner-nv-l@lists.
> cc
> us.ibm.com
>
>
> Subject
> Re: [nv-l]
> Traps not formatting
> 04/01/2005 01:15 right!
>
> PM
>
>
>
>
>
> Please respond to
>
> nv-l
>
>
>
>
>
>
>
>
>
>
>
>
>
> So you are saying that what you have is an agent
> which is sending one
> thing, while its MIB says it will send another.
> That's not all that
> uncommon.
>
> If that's the case, then use xnmtrap to correct the
> OID to what is actually
> sent.
>
>
> James Shanks
> Level 3 Support for Tivoli NetView for UNIX and
> Windows
> Tivoli Software / IBM Software Group
>
>
>
> Larry Fagan
> <larrytechie@yaho
> o.com>
> To
> Sent by:
> nv-l@lists.us.ibm.com
> owner-nv-l@lists.
> cc
> us.ibm.com
>
> Subject
> [nv-l] Traps
> not formatting right!
> 04/01/2005 01:10
> PM
>
>
> Please respond to
> nv-l
>
>
>
>
>
>
> Hi,
> Back again.. I have sucessfully loaded Nokia System
> trap definitions into netview using mib2trap
> command.
> They are defined under 1.3.6.1.4.1.94.1.21.1.0. in
> xnmtrap. Now when we receive traps from nokia
> device,
> the TEC shows as below:
>
> Trap found with no known format in trapd.conf(4)
> Enterprise ENTERPRISES (1.3.6.1.4.1.94.1.21.1)
> community test generic trap:6 specific trap:4
> Timestamp:315688386 Agentaddr:testnokia.us.com
> args(4): [1] hrPartitionEntry.hrPartitionIndex.3.1
> (Integer): 1 [2]
> hrPartitionEntry.hrPartitionLabel.3.1 (OctetString):
> /dev/wd0f [3] hrPartitionEntry.hrPartitionSize.3.1
> (Integer): 396952 [4]
> host.hrDevice.hrFSTable.hrFSEntry.hrFSMountPoint.1
> (OctetString): / "
>
> Take a look at the OID in the event. It is without
> last digit "0" from xnmtrap. Now my question is,why
> is
> the diffence in OID? how do i decode this
> unformatted
> trap. What am i supposed to understand from this
> unformatted trap?
> Many thanks as usual to all..
> Larry
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam
> protection around
> http://mail.yahoo.com
>
>
>
>
>
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
|