Hi James,

Yes, I've used the debug but honestly cannot see where things are going
wrong (I can see where my rule is having action taken on it but nothing
appears wrong).  I am going to temp change ESE.automation to include
only this rule in hopes of finding more info.  I know I cannot post
trace info to this group - so I'll focus on things I need to still
confirm.  Since I am querying this MIB .1.3.6.1.2.1.1.3
(system.sysUpTime.0) I should use Origin - since #2 should only be used
for Netview MIBs, right?  Next, in the value to compare - should I use
the whole string "system.sysUpTime.0 = Timeticks: (9000)" or just the
number 9000 or something else (I feel this is the key)  Lastly, has
anyone concocted a alternative solution to this problem (validating a
Node Up trap is legitimate before taking action on it)?

As always, thanks very much,

Glen Warn
PEMCO Corporation Computer Services (PCCS)
glen.warn AT pemcocorp DOT com
206-628-5770

-----Original Message-----
From: owner-nv-l AT lists.us.ibm DOT com [mailto:owner-nv-l AT lists.us.ibm DOT 
com]
On Behalf Of James Shanks
Sent: Thursday, April 28, 2005 5:31 AM
To: nv-l AT lists.us.ibm DOT com
Subject: Re: [nv-l] Ruleset ? using Compare MIB Variable





Glen,

Have you been tracing nvcorrd's execution of your rulesets with
"nvcdebug -d all" as I suggested?
If you want to see why one case is working and the other not, that's the
way.

By definition, SNMP TimeTicks are in hundredths of a second, or at least
that's what they should be.  So you should get 600 to the minute, not
1000.

There is no good source for writing rulesets.  The only Redbook I know
of which discusses them is very old, SG24-4515-00, Examples Using
NetView for
AIX Version 4, which came out when rulesets were new (December 1995).
If
you search the nv-l archives you should also find a short document I
wrote giving some performance hints and tips.  We've already discussed
much of it
in your last few postings.   But running the trace is the way to answer
most questions.

If you are using NetView traps, then I would specify attribute 2, the
fully-qualified hostname, rather then the Origin as the source of your
MIB query.  Why?  You don't want to query the NetView box, but the host
the trap is about.  If you are using non-NetView traps then Origin is
required.

HTH

James Shanks
Level 3 Support  for Tivoli NetView for UNIX and Windows Tivoli Software
/ IBM Software Group