Yes, we only forward to TEC using postemsg in our scripts - we have turned
off native forwarding to TEC. I'm not sure what the CPU usage is on nvcorrd
(something we'll check out) ...otherwise, it sounds very similar to your
situation. Thanks, Ray.
Mark
-----Original Message-----
From: Ray Schafer [SMTP:schafer@tkg.com]
Sent: Wednesday, June 07, 2000 8:44 AM
To: IBM NetView Discussion
Subject: Re: [NV-L] Question concerning Netview Event History
Window???
"Lemire, Mark" wrote:
> I am a co-worker of David Tremblay. Dave hurt his back (unrelated
to
> Netview :) and is out today so I'll reply to the posts.
>
> You are correct that we mean the standard Events Window.
>
Do you *only* forward to TEC using scripts? You don't have any
rulesets that
are used to forward events to TEC using the standard NetView Method?
I had
this problem before (about 2 years ago). The symptoms were nvcorrd
waiting
(zero CPU time), and nvserverd looping using much CPU time. It was
a problem
related to TEC forwarding. We had a PMR opened, but I don't recall
if we
recievced a fix or if the problem went away with an upgrade, but it
is gone
now. It may not be the same as yours, escpecially if you don't
forward
directly to TEC.
|