Dollars to donuts, that is your problem. The presence of tecint.conf is how
nvserverd knows to forward to TEC. So yours is spending a lot of worthless time
trying to do just that, even if there is no TEC on the box he is sending to.
I'll bet you have a nice big /etc/Tivoli/tec/cache file too. These files should
be deleted. As for recycling the daemon, that is the sure way to make sure no
attempts at TEC forwarding are going on. There is the nvtecia -stop command,
but I don't know for certain how well it works at your level, since I just fixed
a major bug in it for 5.1.3. You could try it and see if your problem goes
away. But you must delete or rename those tecint.conf files so this does not
re-occur.
You said you said turned off TEC forwarding. How did you do that?
James Shanks
Tivoli (NetView for UNIX and NT) L3 Support
"Lemire, Mark" <mlemire@JHANCOCK.COM> on 06/07/2000 09:58:01 AM
Please respond to IBM NetView Discussion <nv-l@tkg.com>
To: "'IBM NetView Discussion'" <nv-l@tkg.com>
cc: (bcc: James Shanks/Tivoli Systems)
Subject: RE: [NV-L] Question concerning Netview Event History Window???
There IS a tecint.conf on both Netview's - interesting. The only difference
is ServerLocation. We can certainly remove this -- just a matter of
deleting it? Do we need to recycle daemons?
Thanks,
Mark
-----Original Message-----
From: James_Shanks@TIVOLI.COM [SMTP:James_Shanks@TIVOLI.COM]
Sent: Wednesday, June 07, 2000 9:57 AM
To: IBM NetView Discussion
Subject: RE: [NV-L] Question concerning Netview Event History
Window???
No possibility that you have an old /usr/OV/conf/tecint.conf file
around?
I'd also try "nvcdebug -d all" which tells nvcorrd to trace, and
that will
show what he is forwarding to nvserverd, plus any ruleset issues
might well show
up there, in the nvcorrd.alog/blog.
James Shanks
Tivoli (NetView for UNIX and NT) L3 Support
"Lemire, Mark" <mlemire@JHANCOCK.COM> on 06/07/2000 09:47:59 AM
Please respond to IBM NetView Discussion <nv-l@tkg.com>
To: "'IBM NetView Discussion'" <nv-l@tkg.com>
cc: (bcc: James Shanks/Tivoli Systems)
Subject: RE: [NV-L] Question concerning Netview Event History
Window???
The scripts are being kicked off via automatic action from traps.
We don't
use any rulesets defined in ESE.automation, but do use a ruleset
defined in
our Control Desk workspace (And you're correct -- we've gone through
these
questions with support). They're reviewing the ruleset. The same
ruleset
is being used on both Netview's. There is, of course, *something*
different
between the two environments, so fingers crossed, we'll find it
soon.
Thanks!
Mark
-----Original Message-----
From: James_Shanks@TIVOLI.COM
[SMTP:James_Shanks@TIVOLI.COM]
Sent: Wednesday, June 07, 2000 8:27 AM
To: IBM NetView Discussion
Subject: RE: [NV-L] Question concerning Netview Event History
Window???
Ok, but how are the wpostemeg scripts being kicked off?
Rulesets?
Automatic
actions from traps? If rulesets, are they listed in
ESE.automation?
If you've
got a problem open to Support as David said, then they will be
asking you all
the same questions if they haven't already.
In all the years I have done this, I have never had a problem
with
nvserverd
that didn't start somewhere else.
James Shanks
Tivoli (NetView for UNIX and NT) L3 Support
"Lemire, Mark" <mlemire@JHANCOCK.COM> on 06/07/2000 08:01:33 AM
Please respond to IBM NetView Discussion <nv-l@tkg.com>
Archives: http://www.tkg.com/nv-l
_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l
_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l
_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l
|