nv-l
[Top] [All Lists]

Re: nvserverd and TEC

To: nv-l@lists.tivoli.com
Subject: Re: nvserverd and TEC
From: James Shanks <James_Shanks@TIVOLI.COM>
Date: Tue, 8 Dec 1998 09:27:35 -0500
Reply-to: Discussion of IBM NetView and POLYCENTER Manager on NetView <NV-L@UCSBVM.UCSB.EDU>
Sender: Discussion of IBM NetView and POLYCENTER Manager on NetView <NV-L@UCSBVM.UCSB.EDU>
For the most part, yes.  But I cannot give you a list of those that are and
those that aren't.   The adapter code inside nvserverd links the EIF
libraries from TEC in order to forward the events to TEC.  So any
parameters which can be specified in the the tecad.xxx.conf  file which
alter that forwarding mechanism are supported as entries in tecint.conf.
Others, such as Testmode, which require the adapter to ignore some of his
parameters and write to file instead of sending to TEC, are not supported
at this time.

What parameters do you need?

James Shanks
Tivoli (NetView for UNIX) L3 Support



Terje Lindholm <teli@EEC.ERICSSON.SE> on 12/08/98 09:11:33 AM

Please respond to Discussion of IBM NetView and POLYCENTER Manager on
      NetView <NV-L@UCSBVM.UCSB.EDU>

To:   NV-L@UCSBVM.UCSB.EDU
cc:    (bcc: James Shanks)
Subject:  Re: nvserverd and TEC





Does this mean you support "normal" tecad_xxx.conf parameters ????

/Terje

>nvserverd uses his own tecint.conf file which you configure initially
>through the framework or SMIT.  The tecad file is shipped by TEC not
>NetView for their tecad adapters.  The only exception is NT, which ported
>the tecad adapter there because it does not have an nvserverd daemon.
>
>If your TEC setup requires additional entries in the tecint.conf file,
such
>as ServerPort, in order to work, then you can edit
/usr/OV/conf/tecint.conf
>after you build it initially and add them.
>
>James Shanks
>Tivoli (NetView for UNIX) L3 Support
>
>To:   NV-L@UCSBVM.UCSB.EDU
>cc:    (bcc: James Shanks)
<Subject:

<Prev in Thread] Current Thread [Next in Thread>

Archive operated by Skills 1st Ltd

See also: The NetView Web