NAME
ovrc
- perform actions on remote components.
SYNOPSIS
ovrc -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
DESCRIPTION
The ovrc
command 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 Operations Manager (HPOM), HP Operations agents (for example, the Performance 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(1)) providing HP Software 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 you do not
specify the hostname or IP addressd, 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
The ovrc
command recognizes the following
options:
-h|-help
ovrc
command.
-start
[<target> ...
]<target>
option specifies a component or
category. If you do not use <target>
,
all components are started.
-stop [
<target> ...
]
<target>
option specifies a component or
category. If you do not use <target>
, all
components are stopped except components which are CORE processes.
-restart [<
target
>
... ]
<target>
, all components are stopped and
restarted.
-notify <
event
>
[<
target
> ... ] [-value
<
value
>]
<value>
to the component or category
specified by <target>
. If you do not use
<target>
, the event notification is sent
to all components. If you do not use
<value>
, only the event notification is
sent.
-status [
<target> ...
] [-level
<level>
]
<target>
. The status report contains the
component's label, description, category, process ID, and STATE.
Components can be in one of the following states: Stopped (0 in
numeric format), Starting (1), Initializing (2), Running (3),
Stopping (4), N/A (5), or Aborted (6). If you do not use
<target>
, the status of all
components is returned.
The <level>
option specifies the type
and quantity of information to display, as follows:
Level 0
Level 1
Level 2
Level 3
Level 4
Level 5
Level 6
Level 7
-version
ovrc
.AUTHOR
ovrc
was developed by Hewlett-Packard Company.
EXIT STATUS
The following exit values are returned:
0
1
2
64
65
67
69
70
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:
mach.hp.com
:
ovrc -host mach.hp.com -status SERVER
opcle
on a
local host:
ovrc -stop opcle
Before opcle
itself stops, components that depend
on opcle
are stopped.
SEE ALSO