I have an application that is sending traps to my Netview 5.1 on NT.
How can I implement this on NT? I have tried to convert the script file
to a NT batch file. I can issue the batch file and it shows up in the
event viewer, but it doesn't change the status of the icons.
nvsnmptrap XU .1.3.6.1.4.1.2.6.3.1
NVTEST 6 58916871 ""
.1.3.6.1.4.1.2.6.3.1.1.2.0 Integer 14
.1.3.6.1.4.1.2.6.3.1.1.3.0 OctetString %COMPUTERNAME%
.1.3.6.1.4.1.2.6.3.1.1.4.0 OctetString "Object status is"
.1.3.6.1.4.1.2.6.3.1.1.5.0 OctetString %1
If anyone got this working on NT, I could really use you help.
Thanks
Xu He :)
--- BANDIERAMONTE Miguel TECSIS <TCSBTE@TECSIS.COM> wrote:
> Leslie,
> I opted to use the command line snmptrap and
> it works fine over real
> nodes, but I made manualy a new object and doesn4t
> work on it, here is the
> description:
> OBJECT: 63654
>
> FIELD ID FIELD NAME
> FIELD VALUE
> 10 Selection Name
> "sapserv4"
> 14 OVW Maps Exists
> 1
> 15 OVW Maps Managed
> 2
> 71 isNode
> TRUE
> 73 isComputer
> TRUE
> 81 isMini
> TRUE
> which is the parameter I have to change (and how)
> in orther to snmptrap
> script works fine?
> Thanks . . .
>
> > -----Original Message-----
> > From: PUB:Leslie Clark [SMTP:lclark@US.IBM.COM]
> > Sent: Monday, April 05, 1999 1:07 PM
> > To: NV-L@UCSBVM.ucsb.edu
> > Subject: Re: Changing status... The Word from
> Support
> >
> > Here's something I keep handy on this subject..
> Warning. long append.
> > File for future reference.
> >
> >
> ------------------------------------------------------------------
> >
> > One of the most common, and yet most complicated,
> things that NetView
> >
> > users ask about is how to alter the status
> (color) of an icon on the
> >
> > map using a trap, effectively overriding what
> netmon has done. This
> >
> > can be accomplished in one of three ways, (1)
> using a ruleset with the
> >
> > override node in it, (2) issuing the 58916871
> NetView trap, or (3) by
> >
> > configuring a non-NetView trap.
> >
> > This document is an attempt to explain how these
> processes work.
> >
> > Types of status
> >
> > There are three (3) sources of status for objects
> on a NetView map:
> >
> > 1. Object source -- status of a single object is
> kept in the
> >
> > database entry for that object
> >
> > 2. Compound Propagated source -- object has no
> status of its own, but
> >
> > it is derived from status of its
> constituent objects.
> >
> > Network symbols and collection objects
> have status source of
> >
> > 'Compound Propagated'
> >
> > 3. Symbol source -- an ipmap status not part of
> the object host nodes
> >
> > in the map have this status source
> >
> > You can determine the status source for any map
> object by selecting
> >
> > it with the rightmost mouse button and clicking
> on Edit ==> Modify /
> >
> > Describe ==> Symbol.
> >
> > General requirements
> >
> > 1. In order for an event, no matter how it is
> processed, to override
> >
> > status and change the color of an object on the
> map(s), the Event
> >
> > process (called nvevents) must be running in
> dynamic workspace in a
> >
> > control desk on the read-write map, and the
> control desk must have
> >
> > been started by ovw (the map process) initially.
> This is the default
> >
> > NetView End User Interface configuration.
> >
> > The reason for this is that the APIs for the
> status override function
> >
> > are in nvevents and ovw, and they can only be
> used effectively when
> >
> > both are connected to the same read-write map.
> >
> > 2. The API can easily override the status of
> objects which have a
> >
> > status source of 'Object' or 'Symbol', but a
> status source of
> >
> > 'Compound Propagated' is more difficult. Since
> this is a derived
> >
> > status it cannot be changed directly. What
> nvevents can do in this
> >
> > case, is to change the status source of the
> object to 'Symbol' first,
> >
> > and then override it. But as this means that
> from that time on, the
> >
> > map object will no longer reflect the combined
> status of the objects
> >
> > "below" it (unless you later change the status
> source back to
> >
> > 'Compound Propagated again via Edit with the
> right mouse button) you
> >
> > must set the application defaults for nvevents to
> permit this to
> >
> > happen. You must edit app-defaults/Nvevents to
> say
> >
> > nvevents.overrideCompoundStatus : True
> >
> > When your event requests a status override, the
> object's status source
> >
> > will be changed from compound to symbol, and then
> overridden. But now
> >
> > you must take responsibility to change the status
> again when the
> >
> > condition which caused you to change it in the
> first place has passed,
> >
> > as it will never again reflect the status derived
> from its components.
> >
> > Failure to have nvevents.overrideCompoundStatus
> : True set in your
> >
> > Nvevents file is the most common reason why users
> report that overrides
> >
> > do not work. Be aware that each user could have
> his or her own
> >
> > copy of Nvevents in his or her $HOME directory or
> could have
> >
> > incorporated the Nvevents entries into a
> .Xdefaults file. And be aware
> >
> > that X is not forgiving about user defaults. The
> value here must be
> >
> > "True" and not "True " with any extra spaces
> trailing the 'e'.
> >
> > Note that if a host node is in a Collection, it
> has status source of
> >
> > 'Compound Propagated', while on the IP Segment
> map it will have a
> >
> > status source of 'Symbol'. If you do not have
> >
>
=== message truncated ===
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
|