What is the setting for your initial Event Stream node, Block or Pass? it
should be Block. If not, all events will be forwarded.
Is this the ruleset you are using for TEC in your /usr/OV/conf/tecinit.conf
file? It must be if that is what you want to determine what goes to TEC.
I don't know what to make of your 25 minute delay, except to say that this is
usually the result of poor name resolution. Every trap contains IP addresses
which must be resolved into hostnames at several points along the way in this
process and if your reverse name resolution is not set up properly this is
exactly what can happen. Also, you can have other system related effects, such
as a very busy ovwdb (it takes a call to ovwdb to resolve the smartset
membership) or a very busy nvcorrd because many other rulesets are running at
the same time. I would start to pursue this by turning on the nvcorrd trace
(issue nvcdebug -d all from the command lien) and looking at the
nvcorrd.alog/blog to see if you can determine where the problem might lie. I
would call Support if you think you need help.
James Shanks
Team Leader, Level 3 Support
Tivoli NetView for UNIX and NT
Aizprua Jerry <JAizprua@pacifico.fin.ec> on 06/29/2000 04:12:01 PM
Please respond to IBM NetView Discussion <nv-l@tkg.com>
To: NV-L@UCSBVM.ucsb.edu
cc: (bcc: James Shanks/Tivoli Systems)
Subject: [NV-L] Rule Set not working as expected
Operating System: AIX 4.3 Product Group: NetView for UNIX Fileset or
Version: Netview 6.0 .
Environment: Netview server has 512 Mb RAM, 1.2 Gb of Swap Space, Fast
Ethernet NIC, 2 x 166 Mhx risc processors TEC Server has 512 Mb RAM, 1.2 Gb
of Swap Space, 2 x 166 Mhx risc processors .
Hi :
We want to manage events from servers, routers and switchs. We have created
a smart set that includes the nodes mentioned before.
Then we created a rule that does the following :
1 Event Stream
2 Trap Settings - Here we specify that we only are intrested in the
entreprise netview6000 and the specific events 58916864 (Node Up) ,58916865
(Node Up), 58916866 (Interface Up),58916867 (Interface Down).
3 Query Smartset - Here we specify the smart set that only has the machines
that we want to monitor.
4
4.1 Forward - (Thist will display the events and forward them to tec)
4.2 Action -Here we have a small script that logs all the results in a file.
a ) Now the problems are that when we generata an event, we can find it in
the file trapd.log but it takes a long time until (25 min) until the trap is
displayed in the file mentioned in section 4.1 and also in the TEC Console.
b ) As you could see, we are trying to filter the events to those coming
only from the nodes in the smart set but for some reason we are also
receiving events coming from other nodes that are not part of the smart set.
We are also receving events that we don't want to manage. To be sure that
the rule is woking we use the file that we created in section 4.2 and we
only see the events filtered by the nodes in the ruleset but still the
events coming from other nodes are displayed in the event window from the
dynamic work space and also are sent to TEC.
Pls, Any help is apreciated.
Jerry
_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l
|