The processes that run on the management server and managed nodes indicate the health of the OpenView environment. If you experience any problems with the standard operation of the OpenView product, check to ensure that all the necessary processes are running. Below are three examples of checking the status of the OpenView processes. Refer to Chapter 18, "Oracle for OpenView," and Chapter 22, "Troubleshooting Tips and Techniques," for information about commands to check the Oracle and Operating System processes. Descriptions of the OVO processes appear later in this chapter.
The OV service processes must be running in order for the OpenView server to function properly. Refer to Chapter 4, "Out-of-the-box Network Node Manager," for more information about the NNM processes. Check the status of the NNM processes with the command
/opt/
Name PID State Last Message(s) OVsPMD 1422 RUNNING - ovsessionmgr 1424 RUNNING Initialization complete. ovwdb 1425 RUNNING Initialization complete. ovuispmd 1484 RUNNING Successful restart. 0 ovw clients registered. ovtrapd 1455 RUNNING Initialization complete. ovactiond 1456 RUNNING Initialization complete. syslogTrap - NOT_RUNNING - ovalarmsrv 1457 RUNNING Initialization complete. pmd 1427 RUNNING Initialization complete. genannosrvr 1458 RUNNING - httpd - unknown (Does not communicate with ovspmd.) ovtopmd 1453 RUNNING Connected to native database "openview". netmon 1485 RUNNING Initialization complete. snmpCollect 1486 RUNNING Initialization complete. ovas 1492 RUNNING Initialization complete. ovrequestd 1430 RUNNING Initialization complete. ovdbcheck 1459 RUNNING Connected to embedded database. ovctrl - unknown (Does not communicate with ovspmd.) ovoacomm 1490 RUNNING Open Agent Service Server Initialization Complete.
For details about Open Agent Service use 'opcsv'. opc 1772 RUNNING OVO Server Initialization Complete. For details about OVO Manager Processes use 'opcsv'. #
The processes are initialized during system startup or manually controlled with the commands
ovstart and
ovstop . Refer to Chapter 4 for the NNM process descriptions. The
ovstop command will stop NNM and all OVO server processes. This will not stop the agent processes running on the server. When the server processes are down no user logins are allowed, and agent processes will buffer messages until the server processes are restarted.
The operation of the management server depends upon the functions provided by the operating system, Oracle, NNM, and OVO. Descriptions of the OVO processes are provided later in this chapter. Check the status of the OVO server processes with the command
/opt/
# opcsv OVO Management Server status: Control Manager opcctlm (4807) is running Action Manager opcactm (4814) is running Message Manager opcmsgm (4815) is running TT & Notify Mgr opcttnsm (4816) is running Forward Manager opcforwm (4817) is running Service Engine opcsvcm (4822) is running Cert. Srv Adapter opccsad (4820) is running BBC config adapter opcbbcdist (4821) is running Display Manager opcdispm (4818) is running Distrib. Manager opcdistm (4819) is running Open Agent Management status: Request Sender ovoareqsdr (4801) is running Request Handler ovoareqhdlr (4804) is running Message Receiver (BBC) opcmsgrb (4805) is running Message Receiver opcmsgrd (4806) is running Ctrl-Core and Server Extensions status: Control Daemon ovcd (4314) is running BBC Communications Broker ovbbccb (1467) is running Config and Deploy ovconfd (4315) is running OV Certificate Server ovcs (4802) is running #
Server processes that do no appear in the output of the
opcsv -status command include the following processes that run to support the user sessions and DCE-RPC data transfers:
opcuiwww Java UI Manager (one instance per for each connected Java GUI)
opcuiop Operator UI (one instance for each operator session using the MOTIF GUI)
opcuiopadm Administrator's Operator UI
ovw OV platform GUI session (one for each MOTIF GUI - admin+oper)
opccmm Subprocess of Message Receiver for bulk transfers (only if needed temporarily)
There are two commands available to check the agent status:
/opt/
OV /bin/OpC/opcragt and
/opt/
OV /bin/OpC/ovc . Both commands report the status of the primary agents responsible for intercepting events, collecting performance data, filtering and forwarding messages. The following example lists the output from the
Execute the command:
/opt/
opcmsga OVO Message Agent AGENT,EA(5129) Running opcacta OVO Action Agent AGENT,EA(5130) Running opcmsgi OVO Message Interceptor AGENT,EA(5131) Running opcle OVO Logfile Encapsulator AGENT,EA(5133) Running opcmona OVO Monitor Agent AGENT,EA(5135) Running opctrapi OVO SNMP Trap Interceptor AGENT,EA(5137) Running opceca OVO Event Correlation AGENT,EA Stopped opcecaas ECS Annotate Server AGENT,EA Stopped coda HP OpenView Performance Core (3657) Running #
The command
ovc (-start, -stop, -kill) also controls the agent processes from the command line. Refer to the man pages for
ovc complete syntax. The command
/opt/
OV /bin/OpC/opcagt is now a wrapper for
ovc . The output from the
ovc command for HTTPS-based agents is listed here.
# ovc ovcd Control Daemon CORE (4314) Running ovbbccb HP OpenView BBC Communications Broker CORE (1467) Running ovconfd HP OpenView Config and Deploy CORE (4315) Running ovcs HP OpenView Certificate Server SERVER Aborted opcmsga OVO Message Agent AGENT,EA (4321) Running opcacta OVO Action Agent AGENT,EA (4322) Running opcmsgi OVO Message Interceptor AGENT,EA (4323) Running opcle OVO Logfile Encapsulator AGENT,EA (4325) Running opcmona OVO Monitor Agent AGENT,EA (4327) Running opctrapi OVO SNMP Trap Interceptor AGENT,EA (4329) Running opceca OVO Event Correlation AGENT,EA Stopped opcecaas ECS Annotate Server AGENT,EA Stopped coda HP OpenView Performance Core 4331) Running
The output shows the processes that are responsible for overall control
ovcd , HTTPS communications
ovbbccb , distribution and configuration changes
ovconfd , and security authentication
ovcs . The
ovc and
opcagt commands work locally,
opcragt executes on the management server (both for DCE and HTTPS agents). The