OVNM 5.3 - Operations Agent for NonStop Troubleshooting Guide

Troubleshooting HP Operations Manager 117
Once the Elink.cfg has been modified, run Elinktrace to start tracing.
>elinktrace -on.
Generate a Test message using the Test Message button in the OVNM Host Management Client while Elink is
being traced.
If no message is traced, check the NonStop EMS Log $0. If Test message are in the EMS Log, then the problem is
with the OVNM components on the NonStop Server.
If message are seen in the Elink trace, but are still not seen on the HP Operations Manager Console, try tracing
the OVNM Smart Plug-in process.
6-2-3 OSPI Tracing (OVNM Smart Plug In)
If problems still exist and there were no noticeable errors in the Elink log, you can verify whether the Events
messages are being received by the OVNM SPI (OSPI) process.
Stop the OSPI process on the HP Operations Manager Windows Management Server and change to the HP
OpenView Bin Directory.
>net stop OVNM_SPI
>cd <drv>:\Program Files\HP OpenView\bin
Option 1: Trace OSPI Messages to a Debug Display Window
Launch OVNMWin32 SPI agent to view message flow on the HP Operations Manager Management Server. Use
the following command to launch the OVNM SPI in the debug mode.
>OvnmSpiWin32 –debug –node
This will start a OVNM SPI Debug display window.
Option 2: Trace OSPI Messages to Log File
Locate the OVNM’s configuration file ovnmconf.cfg in the HP OpeView bin directory and change the TRACE
parameter to ON.
A part of the ovnmconf file has been provided for your reference:
#********************************************************************
# Here are sample options. Modify these options as per your needs.
#********************************************************************
TRACE ON
LOGFILE ovnmlog.log
LOGFILELEN 5000000
Restart OSPI process
#******
>net start OVNM_SPI
Generate a Test message using the Test Message button in the OVNM Host Management Client while OVNM
SPI is being traced.
If no message is traced, check the NonStop EMS Log $0. If Test message are in the EMS Log, then the problem is
with the OVNM components on the NonStop Server.
If messages are received in trace, but not in the HP Operations Manager console, check to see if Policies “SPI For
Nonstop Server” are installed and deployed on the Windows HP Operations Manager Server.
Troubleshooting HP Operations Manager