Manualshelf

OVNM 5.3 - Operations Agent for NonStop Troubleshooting Guide

ManualsBrandsHP ManualsServerHP NonStop G-Series
111112113114115116117118119120
Troubleshooting HP Operations Manager 114
6-2 Messages not Getting Populated on HPOM Windows
The following steps are intended to assist in diagnosing why NonStop messages are not flowing to the HP
Operations Manager Windows Message Browser.
6-2-1 Check Connectivity between HPOM and NonStop Server
To check the connectivity between the HP Operations Manager server and the NonStop server, execute the
NonStop Nodes Status utility. Click on the Start\Programs\HP OVNM\NonStop Server Tools\NonStop Nodes
Status option.
Figure 6-2 NonStop Nodes Status Option
The NonStop Nodes Status window is displayed
Figure 6-3 NonStop Nodes Status Window
A green icon next to the node name in the window indicates that the connection is established with the remote
HP NonStop Elink. In case the remote HP NonStop Elink is not up, the icon will be seen in red.
• If connection is green, verify that the HP Operations Manager environment is running and that the HP
Operations Manager Console can receive messages other than Nonstop Server Events.
• From the command prompt, execute the following opcmsg command. This will test HP Operations
Manager without using the OVNM infrastructure.
C:\ opcmsg a=OVNM o=o msg_text=hello
If no messages appear in the HP Operations Manager Message Browser, then the problem is with the
HP Operations Manager environment.
• Make sure that the HP Operations Manager Agent is running on the Management Server. From the
command prompt execute the following opcagent command.
C:\opcagt –status
Verify that all reported HP Operations Manager agent components are running.
• Verify that OVNM Node name and policies are deployed on Management Server.
C:\ opcmsg a=OVNM o=o msg_text=hello -option SERVICEID=NSSAPP:OVNM
node=<Nodename> s=CRITICAL
Where, <Nodename> is the name of the HP NonStop node without “\”.
If no messages appear in the HP Operations Manager Message Browser, the problem is either with the
NonStop Node name or the OVNM Policies have not been deployed in HP Operations Manager.