What you are doing is not officially supported. But other folks have
gotten this to work.
Try adding /usr/OV/lib to your LIBPATH: export
LIBPATH=/usr/OV/lib:/$LIBPATH and see if that helps.
However, once you get passed that "can't load" message you will find that
you get security errors, since their will not be an nvsecd running on the
non-NetView box. You would have to copy over the unsecured versions of
the snmp commands in
/usr/OV/security/cmds.
Good luck
James Shanks
Tivoli (NetView for UNIX) L3 Support
"Youngmann, Patricia L." <YoungPL1@CENTRAL.SSD.JHUAPL.EDU> on 03/19/99
10:42:09 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: running snmptrap command from server other than NV server
Hello,
I am having problems running the /usr/OV/bin/snmptrap command from a server
other than my NetView server. I'll call the non-NV server serverX. I
copied the snmptrap command to /usr/OV/bin on serverX. When attempting to
run it, the error message I received was," Could not load program snmptrap.
Could not load library libov.a[libov.osh]. Error was: no such file or
directory."
I then copied all the /usr/OV/lib files from the NV server to serverX and
put the OV directories in my path (OV_BIN, OV_LIB, OV_CONF.) I also copied
the trapd.conf file to serverX. I still get the same message. There is a
libov.a file in serverX's /usr/OV/lib directory. I even copied the
snmptrap
command to the /usr/OV/lib directory and tried running it from there.
Still
no success.
ServerX is running AIX 4.2.1, Framework 3.6 and Distributed Monitoring 3.6
-
it's a managed node. My NV server is version 5.1. I am not using TEC
(it's
just too expensive) and want to send my DM events to the NV Events window
using snmptrap commands in shell scripts. Currently I can only run the
snmptrap command from my NV server. If I need to perform corrective
actions, such as restarting a daemon on serverX, I need to use 3 different
scripts: one script running on the NV server to send the daemon down event
,
one script running on serverX to restart the daemon and another one running
on the NV server to send the daemon up event - if the daemon was brought up
successfully. Plus I need to time the execution of the scripts just right.
It would greatly simplify things if I could run one script from serverX
that
performed all 3 actions.
Any knowledge or suggestions would be greatly appreciated.
-Pat Youngmann
Network Engineer
Johns Hopkins University
Applied Physics Laboratory
patricia.youngmann@jhuapl.edu
|