HP Operations Manager for Windows

ovrc


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
Displays all available options for the ovrc command.

-start [<target> ... ]
Starts the selected components. The <target> option specifies a component or category. If you do not use <target> , all components are started.

-stop [<target> ... ]
Stops the selected components. The <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> ... ]
Stops components before they are restarted. If you do not use <target> , all components are stopped and restarted.

-notify <event> [<target> ... ] [-value <value>]
Sends notification of an event with the value of <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>]
Reports the status of a component or category specified by <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
Status of registered components monitored by HPOM.

Level 1
Status of registered components, whether they are monitored by HPOM or not.

Level 2
Status of registered components and a dump of their registration information.

Level 3
ID of core processes. Zero (0) 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.

AUTHOR

ovrc 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:

SEE ALSO

ovc(1), ovcreg(1).