Theoretically it is possible but I wouldn't recommend it.
The NetView box will be busy using SNMP a lot and it makes little sense to
have the TEC SNMP adapter involved there.
I would install it on another box and have trapd forward traps there.
If you have to install them on the same box then you will have to have
trapd own 162 and set the SNMP_TRAP port in the adapter's config file to
some unused port on you system and have trapd forward the traps to his own
box at that port.
See the man page on trapd for information on how to configure trapd to
Note that the SNMP TEC adapter cannot forward, that is why he has to get
everything from trapd or you have to have your network devices send to him
also on an alternate box.
Team Leader, Level 3 Support
Tivoli NetView for UNIX and NT
Pieter_Van_Cauwenberghe AT csi DOT [email protected] on 07/12/2001 01:19:31 PM
Please respond to IBM NetView Discussion <nv-l AT tkg DOT com>
Sent by: owner-nv-l AT tkg DOT com
To: nv-l AT tkg DOT com, tme10 AT list.ephibian DOT com
Subject: [NV-L][TEC] SNMP port 162
Some advice please,
Envir: NetView 6.0.1 and TEC 3.7 on solaris 2.6, SUN3500
I would like to monitor network devices with NetView but correlate SNMP
traps sent by these and other devices with the TEC through its SNMP
But... NetView and TEC (and the SNMP Adapter) are running on the same
So, If this TEC SNMP Adapter is listening on port 162, NetView's trapd
cannot receive SNMP traps from SNMP Agents.
(and vice versa)
All other NetView features i want to use seem to perform ok.
As long as the TEC SNMP Adapter is started before NetView's trapd daemon,
this design seems to work fine.
Has anyone else done this?
Are there any drawbacks?
(both from the NetView and the TEC point of view)
Should or shouldn't i be doing this?
NV-L List information and Archives: http://www.tkg.com/nv-l