Events History (or nvela from the command line) is the way to see what it
is in ovents.log. It should not be filling up any faster than trapd.log,
so I would be looking there for what is happening. There are no
"automatic" filters you can set for Events History, but there may be some
in your Events window. Look at Options --> Show Status to find out.
One other thing that could cause you problems on your display is a "bad"
ruleset in ESE.automation. If you have anything in there, you need to
check and make sure the initial node is set to "block" and not "pass",
which is the default.
James Shanks
Tivoli (NetView for UNIX) L3 Support
Bruce Jordan <jordan@BERBEE.COM> on 01/31/99 11:17:16 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)
Subject: Re: nvevents problem
First, I want to thank James and Mark for their responses.
Reading the responses I realized I am both flawed in my expectations and I
have a problem. When I initialy noticed the problem the daemons had been
running for about 1 week. I restarted the interface with the results of a
blank events window, new events would then appear as they happened. I
then
changed setting in app-defaults files and restarted the daemons and
restarted
the interface expecting (incorrectly) old events. I think Mark may be
close
to my problem but I do not think I have any filters running. But I am
seeing
the ovevents.log grow / rotate quickly (5-10 minutes) even at 2048K. Is
there
a way to see what is going in there and check for any filtering I may have
setup and forgot about. ( I initialy set the system up in September but it
was "unused" until 5.1).
Regards,
Bruce Jordan, CCIE #4215
Consulting Engineer
Berbee Information Networks
jordan@berbee.com
James Shanks wrote:
> 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.
>
> James Shanks
> Tivoli (NetView for UNIX) L3 Support
>
> Bruce Jordan <jordan@BERBEE.COM> on 01/31/99 12:02:12 AM
>
> 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)
> Subject: nvevents problem
>
> All,
>
> 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
> Consulting Engineer
> Berbee Information Networks
> jordan@berbee.com
|