Why would you edit the ovsuf file? That's asking for trouble. You should
configure your daemons via SMIT or the Tivoli desktop and get the scripts
to do it for you. Under Configure --> Options for daemons --> event and
trap processing daemons, select ovactiond. Set max wait time to zero.
Then go back and select trapd. Change his connected applications queue
size to something larger than the default 500, say 1000 or 1500. That
should fix it.
James Shanks
Tivoli (NetView for UNIX) L3 Support
Douglas Staub <Douglas_Staub@KEYBANK.COM> on 09/09/98 08:07:26 AM
Please respond to Discussion of IBM NetView and POLYCENTER Manager on
NetView et alia <NV-L@UCSBVM.UCSB.EDU>
To: NV-L@UCSBVM.UCSB.EDU
cc: (bcc: James Shanks)
Subject: Re: ovactiond and trapd losing contact
Blaine,
This is the exact message I get - to configure ovactiond is my next hurdle;
I believe this is contained in the ovsuf file, but I will contact support
to take it from here. Thank you Vladimir and Blaine for your comments!
Sincerely,
Doug Staub
Key Services Corporation
Please respond to NV-L@UCSBVM.ucsb.edu
To: NV-L @ UCSBVM.ucsb.edu
cc: (bcc: Douglas Staub/GL/KSC/KeyCorp)
Subject: Re: ovactiond and trapd losing contact
Douglas, by any chance have you noticed events which read something like
"netmon-related application reached maximum number of outstanding
events, disconnecting from trapd"? If so, it may be that ovactiond is
simply not able to keep up with the volume of traps being received. It
might help to configure ovactiond to wait 0 seconds for command
completion or there may be some other configuration changes which would
help if this is the case.
Blaine Owens
bowens@eastman.com
> -----Original Message-----
> From: Douglas Staub [SMTP:Douglas_Staub@keybank.com]
> Sent: Tuesday, September 08, 1998 8:12 AM
> To: NV-L@UCSBVM.ucsb.edu
> Subject: ovactiond and trapd losing contact
>
> Hi all:
>
> I have been experiencing consistent problems with the ovactiond daemon
> losing contact with the trapd daemon. Has anyone experienced the same
> problem? We are using NetView 4.1 on AIX 4.2.1 and will be upgrading
> to
> 5.1 by end of year. We also rely on the rulesets for processing many
> events. Here is the output from doing an ovstatus for ovactiond:
>
> object manager name: ovactiond
> behavior: OVs_WELL_BEHAVED
> state: NOT_RUNNING
> PID: 541382
> last message: ovactiond lost contact with trapd.
> exit status: exit(1)
>
> /usr/OV/bin/ovstart fixes it, but not permanently. Any ideas??
>
> Any help would be greatly appreciated. Thanks in advance!
>
> Sincerely,
> Doug Staub
> Key Services Corporation
> (216) 689-0632
|