So here's the answer:
Add a "ServerPort=<portnumber>" entry at the end of the
/usr/OV/conf/tecint.conf file.
I am curious why this would work without this entry on one NetView server
and not on the other. The only other difference I found is that the
originally successful NetView server is also a gateway (for fewer than 10
endpoints).
Regis Ebersole
SRA International, Inc.
regis_ebersole@sra.com
-----Original Message-----
From: Ebersole, Regis
To: 'nv-l@tkg.com'
Sent: 1/5/01 1:49 PM
Subject: Solaris 2.6 with NIS+, not forwarding events to TEC
I am experiencing a problem forwarding events from a NetView 6.0.1
managed node to a separate TEC managed node within the same TMR.
A snoop shows that:
* no traffic is reaching the TEC server,
* no traffic is hitting the firewall,
* the correct NIC is being used,
* portmapper is behaving differently than on a successful server.
A wtdumprl shows that no events are reaching the TEC server and failing
parsing or being dropped.
A wpostemsg from the NetView managed node reaches the TEC managed node
and a snoop shows communication between the two.
A postmesmg from the NetView managed node does not reach the TEC managed
node and a snoop shows the same results as for NetView events. The
postemsg fails with an error of "tec_put_event failed, errno=38".
A separate NetView server in the same TMR is successfully sending events
to TEC, and none of the problems above are seen. The tecint.conf files
appear identical.
The only difference seems to be that the successful server is not using
NIS+.
Any suggestions? Also, what are the know problems with NIS+ and NetView
6.0.1 on Solaris 2.6?
Regards,
Regis Ebersole
|