Rulesets are generally portable. The ruleset itself is just an ASCII file.
They are always upward compatible. Downward is a bit riskier. For
example, the Query Smartset node was added in either Version 5.0 or 5.1, I
don't remember which. Obviously it could not work in earlier versions.
The real issue is the underlying code in nvcorrd. There has never been a
maintenance release when we did not fix something in nvcorrd -- a core due
to an unexpected condition, a memory leak, something -- so using a current
ruleset, one which works fine on 6.0.2 for example, may cause problems on
6.0 if that ruleset uses a function we fixed in a later release.
That said, I do not know of any problems with the Threshold Node.
There is a distinction to be made between the editor, nvrsEdit, which you
use to examine or construct a ruleset, and nvcorrd, the daemon which runs
it. The use the same load mechanism, so that nvcorrd cam always load
whatever you can build, but you must make sure that what you save is what
you intend. For example, once you start connecting nodes in the ruleset
with the editor, it will automatically connect the next node you add to the
last one. That convenience feature may not be what you intend to happen.
If your ruleset is large, or your GUI slow, the re-draw by the X-server may
not happen for several seconds and I have seen people miss the fact that a
connection was made that they did not explicitly draw. I always recommend
that you use the Edit --> Refresh Layout function in the editor before you
save the ruleset so you can be sure that what you are saving is what you
intend.
Hope this helps.
What symptoms are you seeing which makes you think that your trapd.conf is
(still) corrupted?
It might be but without some indication of what makes you think so, I
couldn't say what to do.
James Shanks
Level 3 Support
Tivoli NetView for UNIX and NT
Tivoli Software
IBM Software Group
Please note that my new id is jshanks@us.ibm.com
netview@toddh.net (Todd H.)@tkg.com on 09/21/2001 03:59:46 PM
Please respond to IBM NetView Discussion <nv-l@tkg.com>
Sent by: owner-nv-l@tkg.com
To: IBM NetView Discussion <nv-l@tkg.com>
cc:
Subject: Re: [NV-L] ruleset, trapd.conf corruption causes/fixes?
I must be getting better at this James. I'm starting to actually
understand your replies. :-) Thanks for the excellent tips.
Question: how portable are rulesets across NetView versions? Will a
6.02 rulset run on a back-level server? I've been told by coworkers
that it seems to work in many instances.
What's interesting now that trapd.conf is well again, is that I'm
seeing rulset corruption (still in NV6.0--finding a patched server as
we speak), yet trapd.conf is fine this time--no syntax errors
reported.
Are there known problems in 6.0 with rulsets containing a Threshold
node? All was well yesterday, with this ruleset (it has only Trap
Settings, Forward, and one Threshold in it), but when I went to edit
the ruleset today, one of my nodes moved on me and is now connected to
something else! At least nvcorrd doesn't seem to mind running it, but
it's very strange.
Off to a 6.02 server.....
Thanks again for your immensely helpful replies!
Todd
"James Shanks" <SHANKS@us.tivoli.com> writes:
> If trapd is running, and you issue "event -e FMTCHG", trapd will try to
> reload /usr/OV/conf/C/trapd.conf.
> If successful, trapd just starts using the new file and no messages are
> produced.
> If there are syntax errors in the file, you will see an error message
> about them in trapd.log.
[snip]
--
Todd H.
http://www.toddh.net/
_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l
|