Re: nvevents problem
It may be that your problem is one of expectations.
How soon after starting the daemons are you opening the events window?
You will only get in the window events in nvcorrd's cache, which is empty
when it starts. The display window is NOT filled with old events from the
ovevents.log. It worked that way with Version 3 and earlier, but this
behavior was changed in V4 with the introduction of rulesets.
nvcorrd only processes new events so that old actions are not repeated.
Tivoli (NetView for UNIX) L3 Support
Bruce Jordan <jordan AT BERBEE DOT COM> on 01/31/99 12:02:12 AM
Please respond to Discussion of IBM NetView and POLYCENTER Manager on
NetView <NV-L AT UCSBVM.ucsb DOT edu>
To: NV-L AT UCSBVM.ucsb DOT edu
cc: (bcc: James Shanks)
Subject: nvevents problem
When I start netview my events window is blank until a new event
arises. I have confirmed that the app-defaults files
(/usr/OV/app-defaults/Nvela and Nvevents) have an entry for load events
selections (all set at 500). I even set the ovevents.log to 2048 via
the Tivoli interface and stopped and restarted the Daemons. Using the
event history pull down and doing query events gives me the same thing
even after selecting all devices.
My system is TME 10 5.1 on an AIX 4.3.1 with 512 memory managing about
350 nodes. It was upgrade from 5.0 which had the same problem.
Any thoughts would be greatly appreciated.
Bruce Jordan, CCIE #4215
Berbee Information Networks
jordan AT berbee DOT com