OVRC(1)OVRC(1)NAMEovrc - perform actions on remote components
SYNOPSISovrc -h|-help
ovrc-host <name_or_ip> [-tid <ids>] -start [<target> ... ]
ovrc-host <name_or_ip> [-tid <ids>] -stop [<target> ... ]
ovrc-host <name_or_ip> [-tid <ids>] -restart [<target> ... ]
ovrc-host <name_or_ip> [-tid <ids>] -status [<target> ... ] [-level
<level>]
ovrc-host <name_or_ip> [-tid <ids>] -notify <event> [<target> ...]
[-value <value>]
ovrc-version
DESCRIPTIONovrc controls the starting, stopping, event notification, and status
reporting of all components on remote hosts.
A component can be a server process belonging to any of the products
such as HP OpenView Operations (OVO), OVO agents (for example, the Per‐
formance Agent or the Discovery Agent), an event interceptor, or an
application delivered by an integrator. Each component must have an
associated registration file (see ovcreg) providing HP OpenView with
configuration and process information about the component.
In the -host option, you can specify the fully qualified hostname or IP
address of the remote node. If the hostname or IP address is not speci‐
fied, the requested operation is performed on the local node, where the
command is run.
To perform an action, a target can be either a component or a group of
components, defined as a category. The ovrc command first tries to run
the requested operation on the category specified in target. If the
category called target is not found, ovrc tries to start the individual
component target. A category name must not match any component name.
You can also use the -tid option to specify a target ID (CORE ID) of
the remote host specified in the -host option. The CORE ID is a unique
identification for a node. You can use the CORE ID with the -tid option
to make sure that the remote host that receives the request is correct.
Parameters
ovrc recognizes the following options:
-h|-help
Displays all available options for the ovrc command.
-start [<target> ... ]
Starts the selected components. <target> specifies a component
or category. If <target> is not used, all components are
started.
-stop [<target> ... ]
Stops the selected components. <target> specifies a component or
category. If <target> is not used, all components are stopped
except components which are CORE processes.
-restart [<target> ... ]
Stops components before they are restarted. Used in conjunction
with -start <target>. If <target> is not used, all components
are stopped.
-notify <event> [<target> ... ] [-value <value>]
Sends notification of an event with the value of <value> to the
component or category specified by <target>. If <target> is not
used, the event notification is sent to all components. If
<value> is not used, only the event notification is sent.
-status [<target> ... ] [-level <level>]
Reports the status of a component or category specified by <tar‐
get>. The status report contains the component's label, descrip‐
tion, category, process ID, and STATE. Components can be in one
of the following state: Stopped (0 in numeric format), Starting
, Initializing , Running , Stopping , N/A or Aborted . If <tar‐
get> is not specified, the status of all components is returned.
<level> specifies the type and quantity of information to dis‐
play, as follows:
Level 0
Status of registered components monitored by HP OpenView.
Level 1
Status of registered components whether they are monitored
by HP OpenView or not.
Level 2
Status of registered components and a dump of their regis‐
tration information.
Level 3
ID of core processes. 0 (zero) indicates root, non-zero
indicates non-root ownership.
Level 4
Similar to level 0, but the STATE is reported in numeric
format.
Level 5
Similar to level 1, but the STATE is reported in numeric
format.
Level 6
Similar to level 0, but the output is not formatted
Level 7
Similar to level 1, but the output is not formatted
-version
Prints the version of ovrc.
AUTHORovrc was developed by Hewlett-Packard Company.
EXIT STATUS
The following exit values are returned:
0
Success
1
Not defined
2
Ignored
64
Generic error
65
Invalid target
67
Operation aborted
69
Missing prerequisite
70
Authorization error
71
Operation on prerequisite failed
73
Invalid event
EXAMPLES
The following examples show how to use the ovrc command and some of its
options to control and display important information about registered
components.
· To display the status of category SERVER on a remote system with the
hostname; mach.hp.com:
ovrc-host mach.hp.com -status SERVER
· To stop the component registered as opcle on a local host:
ovrc-stop opcle
Before opcle itself stops, components that depend on opcle are
stopped.
SEE ALSO
ovc, ovcreg
OVRC(1)
