ITEM: AT8160
NetView - Verify ems_log_agent and nameserver" error
Question:
Try running /usr/OV/service/reset_ci.
If that doesn't work, try the longer set of steps below.
***********************************************************************
Follow these steps if you have events problems, or if you see the error
"Verify ems_log_agent and nameserver".
1) Bring down the user interface and stop all daemons with ovstop
2) /usr/OV/bin/nettl -stop
3) Using the "ps" command, search for any NetView for AIX processes
that are still running. Good choices for processes to look for
include:
trapgend, trapd, ipmap, nvela, nvhelp, ovhelp, nvevents
Kill any remaining NetView for AIX processes with
"kill -9 \"
4) cd /usr/OV/log
5) rm ovevent.log.BAK ovevent.log
6) cd /usr/OV/sockets
7) rm *
8) cd /etc
9) view the "hosts" file, and verify that the loopback IP address
and your hostname are correct. You may wish to try statements
like:
host loopback
host localhost
to verify these IP addresses.
10) run
ovorsutil -d
Verify that the entry that corresponds to "ems_log_agent" matches
your hostname.
11) cd /usr/OV/conf
12) Verify that all hostnames in the /usr/OV/conf/ovsnmp.conf file are
resolvable by whatever nameserver you are using.
13) Verify that your nameserver times out quickly for any names that
cannot be resolved. If your nameserver doesn't timeout quickly,
you may wish to add the following two lines to your
/etc/environment file:
export RES_RETRY=1
export RES_TIMEOUT=1
14) nettl -start
15) ovstart
16) Use the "ovstatus" command to verify that the daemons are running
17) Run
/usr/OV/service/reset_ci
If the reset_ci script does not seem to be running correctly,
you can run the following commands individually:
ovstop OVORS_M
rm /usr/OV/conf/ovors
ovstart OVORS_M
ovaddobj /usr/OV/lrf/ovesmd.lrf
ovaddobj /usr/OV/lrf/ovelmd.lrf
ovstart
18) Bring up the user interface with the command
/usr/OV/bin/ovw &
Support Line: NetView - Verify ems_log_agent and nameserver" error ITEM: AT8160
Dated: January 1996 Category: N/A
This HTML file was generated 99/06/24~13:30:25
Comments or suggestions?
Contact us