Ok this got bounced yesterday for size, here is a resend:

Well here are the results after editing the TECIO to this:

#

# MODULE = TECIO

#

TECIO  MINOR    /usr/ov/log/nvtecad.log

TECIO  MAJOR    /usr/ov/log/nvtecad.log

TECIO  FATAL    /usr/ov/log/nvtecad.log

TECIO  LOW      /usr/ov/log/nvtecad.log

TECIO  NORMAL   /usr/ov/log/nvtecad.log

TECIO  VERBOSE  /usr/ov/log/nvtecad.log

 

 

The tecad_nv6k process again jumped to 50% of use after the first TEC event was forwarded and never dropped back down (been 10 minutes) thus the closing event when the node came back up was never forwarded…

The nvtecad.log file after restarting tecad_nv6k svc:

 

 

Wed Dec 13 15:26:26 2006     LOW: TECIO  , err 00,       .\tec_io.c line 0110: Initializing T/EC interface ...

Wed Dec 13 15:26:26 2006     LOW: TECIO  , err 00,       .\tec_io.c line 0180: T/EC interface initialization complete

Wed Dec 13 15:27:31 2006     LOW: TECIO  , err 00,       .\tec_io.c line 0276: Sending event to T/EC ...

 

TEC_ITS_INTERFACE_STATUS;source=NV6K;sub_source=NET;origin=x.x.x.101;adapter_host=NetviewServer;hostname=TestServerNode;msg='Interface Intel down. CRITICAL';category=2;ifstatus=2;ifname=762;hostaddr=x.x.x.101;nvhostname=y.y.y.30;END

 

Wed Dec 13 15:27:31 2006     LOW: TECIO  , err 00,       .\tec_io.c line 0313: Event sent to T/EC

Wed Dec 13 15:27:31 2006     LOW: TECIO  , err 00,       .\tec_io.c line 0276: Sending event to T/EC ...

 

TEC_ITS_NODE_STATUS;source=NV6K;sub_source=NET;origin=x.x.x.101;adapter_host=NetviewServer;hostname=TestServerNode;msg='Node Down. ';category=2;nodestatus=2;nvhostname=y.y.y.30;END

 

Wed Dec 13 15:27:31 2006     LOW: TECIO  , err 00,       .\tec_io.c line 0313: Event sent to T/EC

Wed Dec 13 15:27:31 2006     LOW: TECIO  , err 00,       .\tec_io.c line 0276: Sending event to T/EC ...

 

TEC_ITS_SEGMENT_STATUS;source=NV6K;sub_source=NET;origin=y.y.y.30;adapter_host=NetviewServer;category=2;msg='Segment x.x.Segment1 Marginal.';segstatus=3;nvhostname=y.y.y.30;END

 

Wed Dec 13 15:27:31 2006     LOW: TECIO  , err 00,       .\tec_io.c line 0302: Event filtered by tec_put_event()

Wed Dec 13 15:27:31 2006     LOW: TECIO  , err 00,       .\tec_io.c line 0303: No event sent to T/EC

Wed Dec 13 15:27:31 2006     LOW: TECIO  , err 00,       .\tec_io.c line 0276: Sending event to T/EC ...

 

TEC_ITS_NETWORK_STATUS;source=NV6K;sub_source=NET;origin=y.y.y.30;adapter_host=NetviewServer;category=2;msg='Network x.x

 Marginal.';netstatus=3;nvhostname=y.y.y.30;END

 

Wed Dec 13 15:27:31 2006     LOW: TECIO  , err 00,       .\tec_io.c line 0313: Event sent to T/EC

 

Again, thanks for any help anyone can give I’m long since out of ideas…

 

Eric

 

-----Original Message-----
From: nv-l-bounces AT lists.ca.ibm DOT com [mailto:nv-l-bounces AT lists.ca.ibm DOT com] On Behalf Of James Shanks
Sent: Wednesday, December 13, 2006 1:24 PM
To: Tivoli NetView Discussions
Subject: RE: [NV-L] TEC Event Forwarding Intermittently Failing on 7.1.5

 

You can edit tecad_nv6k.err to get some tracing. The first thing to do is to route all messages for TECIO to the log file and see what you get after the thing restarts. If NetView isn't sending the event on to the TEC library code, you should notice that here. But if you see the event was sent, then the TEC library has it, and what happens after that is a TEC issue.

The TEC folks would have to give you a tec_diag_config file (or you can get one from the TEC SDK) and have you run their trace.


James Shanks
Level 3 Support for Tivoli NetView for UNIX and Windows
Network Availability Management
Network Management - Development
Tivoli Software, IBM Corp
"Cooprider, Eric" <ecooprider AT ycsd.york.va DOT us>