Steve,
If what you say about the tecint.conf file being overwritten is true (and
thus you have a "chicken or the egg" type situation), please open a pmr
with the Tivoli Distributed NetView group so we can test/debug and fix
where appropriate.
thanks,
Gareth Holl
Software Engineer
gholl@tivoli.com
Tivoli Systems / IBM Corporation
Research Triangle Park, North Carolina. 1-800-TIVOLI-8
-----------------------------------------------------------------------------------------------------------
No matter what happens, somebody will find a way to take it too seriously
"Steve Damron" <swdamron@us.ibm.com>@tkg.com on 06/01/2001 10:17:55 AM
Please respond to IBM NetView Discussion <nv-l@tkg.com>
Sent by: owner-nv-l@tkg.com
To: nv-l@tkg.com
cc:
Subject: [NV-L] How to Forward to TEC without portmapper?
Problem-
Is it possible to forward to TEC without the NetView -> TEC handshake
having to use a portmapper call? This is a security violation for us and
this portmapper call will not be allowed. The problem - when forwarding to
TEC is initially turned on and the portmapper call fails NetView will not
forward to TEC.
Already tried-
I have read the readbook "Extending NetWork Management Through Firewalls"
section 4.5.
Forwarding to TEC with SNMP to the SNMP adapter on TEC will not work as
this is a very high maintenance solution for the TEC folks to maintain.
Have tried to put ServerPort=<my port> in /usr/OV/conf/tecint.conf but
turning on forwarding to TEC nukes this file and therefore the port
designation is not effective. You have to add the ServerPort entry to the
file after forwarding is turned on then it is to late to help with the
portmapper issue (plus it gets written over every time a change is made and
forwarding has to be refreshed/restarted).
Any help ideas would be appreciated, as this issue is currently holding up
a monitoring project.
Steve Damron
swdamron@us.ibm.com
_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l
|