I don't understand.
You say starting and stopping the daemon makes no difference but re-running
tecconfig.bat does? That doesn't make sense, I am sorry to say.
Furthermore, just because the serversetup panel says "running" for daemon
status, does not mean that everything is running fine, only that the
daemon's original process is still active in the machine. One or more
threads could have terminated and it would still say "running".
There are only two causes I know of for events to stop flowing in Windows
using the adapter. One is that an admin user logs out. That problem will
be corrected in FixPack 4, with a new TEC library. The other is that you
are not at the FixPack 3 level and have an earlier bad level of the TEC
library.
So if you are not at FixPack3, then get there, because there is nothing
else you can do.
Troubleshooting TEC forwarding is neither simple nor easy. The NetView
adapter code is linked with the TEC EEIF library, just like any other user
adapter might be. The NetView code receives the event, checks the OID and
CDS files for information on how to format it, and calls the TEC library
code to send it. What happens after that is solely the province of the TEC
library code and NetView is blind to it. One thing the library code will
do is cache events if it loses contact with the TEC server and it will try
on every subsequent event it send to make that contact again. When that
occurs, he will then send over all the cached events in a big bunch. So
you might look to see whether your cache file is growing.
In addition, you can edit the tecad_nv6k.err file and specify some location
for the entries under the TECIO section at the bottom of the file. They
will show you any errors that are occurring. By itself, the LOW level will
show whether the event is actually being "sent" -- that is, handed off to
the TEC library for sending or not. If that says it is, then you will
definitely have to open a problem to NetView Level 2 and enlist their aid
in debugging, because they in turn will have to get TEC Level 2 involved.
There is a special diag file which can be installed on your system (part of
the TEC SDK) which will trace the TEC library code, but only the TEC Level
2 guys can tell you how to read that trace.
James Shanks
Level 3 Support for Tivoli NetView for UNIX and Windows
Tivoli Software / IBM Software Group
"Senny M"
<senthil.mani@ust
ri.com> To
Sent by: <nv-l@lists.us.ibm.com>
owner-nv-l@lists. cc
us.ibm.com
Subject
RE: [nv-l] Problem with Event
12/08/2005 11:45 forwarding to TEC on Tivoli Netview
AM 7.1.4
Please respond to
nv-l
James,
Thanks for your support!
In my case the daemon tecad_nv6k is not at all having any problem. When I
see the status, it seems to be working normal. I even tired restarting the
service, but event forwarding doesn't seem to resuming.
Also the event forwarding is getting stalled automatically without doing
anything like logging out etc.
So will there be any reason for this issue?
Appreciate if could give me any resolution as our monitoring engineers are
more particular on events rather looking at Tivoli Netview console?
Thanks
-----Original Message-----
From: owner-nv-l@lists.us.ibm.com [mailto:owner-nv-l@lists.us.ibm.com] On
Behalf Of James Shanks
Sent: Thursday, December 08, 2005 10:05 PM
To: nv-l@lists.us.ibm.com
Subject: Re: [nv-l] Problem with Event forwarding to TEC on Tivoli Netview
7.1.4
Why cannot you just restart the daemon tecad_nv6k using serversetup?
Or simply "ovstart", or more specifically "ovstart tecad_nv6k", from the
command line?
Once tecconfig.bat has been run, the configuration file
\usr\ov\conf\tecad_nv6k.conbf has been altered to reflect what you selected
in the configurator, and the proper daemon executable has been established
in \usr\ov\bin, and registered in \usr\ov\conf\ovsuf. That's what it's job
is. Starting the daemon for you is the last step and one which is easily
accomplished in other ways.
As for the daemon stopping, are you logging out of the NetView server when
this happens or does it seems to just occur? The former is a known
problem and there is a temporary fix for it available from NetView Level 2.
In the latter case, you can set up logging and tracing for this daemon
using the \usr\ov\conf\tecad_nv6k.err file by entering a destination file
(for example "\usr\ov\log\tecad.log") for each level of tracing you want to
see.
And in any case, I'd recommend a call the NetView Level 2 by opening a
problem ticket with IBM to get some assistance on troubleshooting this.
James Shanks
Level 3 Support for Tivoli NetView for UNIX and Windows
Tivoli Software / IBM Software Group
"Senny M"
<senthil.mani@ust
ri.com> To
Sent by: "IBM Tivoli Netview"
owner-nv-l@lists. <nv-l@lists.tivoli.com>
us.ibm.com cc
Subject
12/08/2005 11:22 [nv-l] Problem with Event
AM forwarding to TEC on Tivoli Netview
7.1.4
Please respond to
nv-l
Hi there,
I am using IBM Tivoli Netview 7.1.4 in Windows 2003 platform. Also, I
enabled forwarding the Events to my TEC server using the batch file
provided by Tivoli Netview (tecconfig.bat). I observed an issue with event
forwarding to TEC Server from Netview server i.e. it is stopping the event
forwarding process at times. This forces me to start and run the batch
file entirely to resume the event forwarding. The frequency is at least
twice a day.
Did anyone come across with this issue? If so, could you please share how
this was resolved?
Also is there any other way that I can sort this issue using a simple batch
file running an executable instead of running the whole process of event
forwarding using the batch file provided by Netview (tecconfig.bat)?
---------------------------------------|
(Embedded image moved to| |
file: pic29989.jpg) | |
---------------------------------------|
Senthil Kumar M GNOC
senthil.mani@ustri.com 4N Bhavani
Technopark, Trivandrum
PSTN: ++91-471-2335777 Extn 8653
VOIP: ++1-949-716-8239 Extn 1118
|