HP NonStop G-Series - Manual (Page 62)

Troubleshooting OVNM 62
7-2-1 Messages not Getting Populated on HPOM Event Browser
7-2-1-1 Linux
The following steps are intended to assist in diagnosing why NonStop messages are not flowing to the HPOM
Message Browser.
Check Connectivity between HPOM and NonStop Server
To check the connectivity between the HPOM Management server and the NonStop server, run the
ovnm_status.sh script.
# /opt/OV/ovnm/bin/ovnm_status.sh
root502500018:33:42?0:01elink
root609500018:33:42?0:03ovnm_spi
Status of OVNM NonStop Servers
SN Node(Ipaddress:Port) State.
1 \NODE(111.111.111.111:5030) Connecting
If connection is “Connecting/Not Connected”, verify the OVNM NonStop Server Components are running
by obtaining status of OVNM components on the NonStop Server.
This can be accomplished by starting a Telnet session and logging on to the NonStop Server having the
problems.
>VOLUME $InstVol>.OVNM
>RUN STATOVNM
This will display the current status of the OVNM Agent running on the NonStop Server. Review the status output
for errors. If an error has occurred and more information is needed, check the NonStop Server EMS event log for
additional messages. HP OVNM EMS errors events are generated with “TANDEM.OVNM” SYSID.
If OVNM components are not running on the NonStop Server then Stop and Start Agents using the following
commands.
>RUN STOPVONM
>RUN STRTOVNM
Now check the status on the UNIX Management server again.
# /opt/OV/ovnm/bin/ovnm_status.sh
If connection is still not connected, check the Elink log files on the UNIX Management Server for errors.
Elink Service Tracing (Communication Interface)
If problems still exist, you can view the Elink log file.
By default Elink Service logs ERROR to /opt/OV/ovnm/bin/elink.log.
Here is an example error message in the Elinks log.
ERROR: Connection failed to host \nskit01.atc-hp.com:5030(getsockopt
error=239)”
error 239: Indicates that a socket error occurred when attempting to access \NSKIT01. This error occurred
because the OVNM NonStop Agent was not running on node \NSKIT01 or possible Firewall on Port 5030.
If required, the Elink tracing levels can be changed to view event messages without having to stop the Elink
Service. Changing the Tracing level can be accomplished by running the Elinktrace utility.
The elinktrace program is located in /opt/OV/ovnm/bin/Elink.
The following steps will change the tracing level from ERROR, which is the default value (Logging all ERROR
messages) to PROGRESS, (Trace all messages).
• Turn the tracing off using the following command.
#cd /opt/OV/ovnm/bin
#./elinktrace –off -cfg /opt/OV/ovnm/bin/elink.cfg
Tr
ou
bl
es
hoot
ing
O
VN
M