nv-l
[Top] [All Lists]

Re: FW: Ruleset to forward Traps in NT

To: nv-l@lists.tivoli.com
Subject: Re: FW: Ruleset to forward Traps in NT
From: James Shanks <James_Shanks@TIVOLI.COM>
Date: Thu, 6 May 1999 17:49:05 -0400
Reply-to: Discussion of IBM NetView and POLYCENTER Manager on NetView <NV-L@UCSBVM.UCSB.EDU>
Sender: Discussion of IBM NetView and POLYCENTER Manager on NetView <NV-L@UCSBVM.UCSB.EDU>
Geoff -

In the future, please send you questions to the NV-L and not to me
personally.

As I said in my append, TEC forwarding is different than trap forwarding.

TEC forwarding in UNIX via the internal adapter (nvserverd) does use
rulesets and rulesets can check the Origin or imbedded hostname of the
trap.  The Event Attribute Node will do this for a single value.
You can use multiple Event Attribute Nodes in parallel to check for a small
number of hosts / IP addresses or you can write yourself a script and run
it in an Inline Action Node.  The script would grep a list of hostnames or
IP addresses that you have built just for this purpose.  You would pass
that script $NVA (for the origin of the trap) or $NVATTR_2 for the second
variable of the trap, which is where NetView always puts the hostname.   If
the grep succeeds, then you set one return code.  If it fails you set
another.  And you specify in the Inline Action which return code means
continue (and go on to the Forward) otherwise it will halt.

I am sure this is the kind of thing Xu He wanted to do for trap forwarding
but there is no simple way to do that with rulesets, unless you write
another script to re-issue the trap itself with snmptrap (or nvsnmptrap in
NT) add literally send a new trap to the required destination.  That hadn't
occurred to me before.

So  I guess trap forwarding MIGHT be done via rulesets using  two scripts.
So  this might be done on NT, but it would be tricky to write the ruleset
without the editor from UNIX.   The internal syntax of the ruleset editor
is not published and is not easy, since it was designed to be machine
readable and not human readable.   And since Actions Node will not execute
on NT in the current release, only Inline Actions could be used, even for
the nvsnmptrap command.  So the performance here would likely be poor.  But
given all that, it just might work.


I hope this makes sense to people.

James Shanks
Tivoli (NetView for UNIX) L3 Support



"Hawes, Geoff" <geoff.hawes@email.airborne.com> on 05/06/99 03:56:27 PM

To:   James Shanks/Tivoli Systems
cc:
Subject:  FW: Ruleset to forward Traps in NT





Hello James
I also have a need to send 'qualified' traps to a TEC. i.e. from specified
source IP addresses. This can be done using the TECAD adapter in UNIX.
I previously did this with an AIX 4.x Netview 4 box, but I now need to do
that
with the Solaris Netview 5.11.
Do I have to build custom traps and use that to qualify what the source is?
Is there no way to use a rule that checks the source IP is a list? If match
list=forward?
Put another way, how do I build a rule to forward node up/dwn events from
specific source IP's?

I would appreciate your comments
Thanks

Geoff Hawes
Airborne Express

-----Original Message-----
From: James Shanks [mailto:James_Shanks@TIVOLI.COM]
Sent: Thursday, May 06, 1999 12:10 PM
To: NV-L@UCSBVM.ucsb.edu
Subject: Re: Ruleset to forward Traps in NT


I assume you mean that what you want to do is to check to see if the source
of the trap, or the interface it is about, is in the address range
172.25.*.* and then forward it if it is, else not forward it.
Unfortunately this capability is not within NetView on any platform.

You are confused about what rulesets can and cannot do, and about how trap
forwarding works in NetView.

Rulesets cannot be used to affect trap forwarding on either NT or UNIX,
unless what you are doing is forwarding events to TEC, which is NOT the
same thing as forwarding a trap to another NetView.  A TEC event is
specially-formatted thing and can only be read by TEC, not another NetView.
In NT forwarding to TEC is not affected by rulesets and is done by
tecad_nv6k.exe.  In UNIX TEC forwarding is controlled by rulesets and the
slot map values set in trapd.conf.

Trap forwarding in NetView is handled by trapd daemon in UNIX and by the
trapfrwd daemon in NT.   Neither of these gives you the option to forward
traps by address range.   Instead, you select the enterprise id and
specific trap numbers to forward as well as the destination to forward to.
On NT, look in the /usr/ov/conf/trapfrwd.conf file for details.   Also,
even in 5.1.1 this is not working quite right, so if you try it and you
don't get exactly the ones you want after you configure the file, then call
Support and get the latest efix for trapfrwd.exe.

Hope this helps
James Shanks
Tivoli (NetView for UNIX) L3 Support



Xu He <xuhe@YAHOO.COM> on 05/06/99 02:42:38 PM

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:  Ruleset to forward Traps in NT





Good day everyone,

I have a newbie Ruleset question/dilemma.  I am running Netview for NT
V5.1.1 on two servers, only one of them is the recepient of the traps
for about 400 NT servers.  I want to forward these traps by address
range (172.25.*.*) to this other server.  My problem is I only have NT
Netview 5.1.1, and there isn't a .rs editor for NT.  Has any one have
any experience in this, or know where I can find the syntax for
generating the rulesets, or have some examples in doing this kind of
filtering?  I would much appreciate it!

Thanks
Xu He
Network Solutions, Inc.
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com

<Prev in Thread] Current Thread [Next in Thread>

Archive operated by Skills 1st Ltd

See also: The NetView Web