OVNM 5.3 - Operations Agent for NonStop Event Management Guide for UNIX

HP Operations Manager Message Templates 29
Whether action commands for HP NonStop Servers are executed as Automatic or Operator- initiated, the
commands are required to use the “nscmd” utility. The “nscmd” utility is supplied with OVNM and executes on
the HP Operations Manager Management Server. It then send the command defined in the –cmd option to the
NonStop Server identified with the –node option.
Since the “nscmd” command executes on the Management Server the Node field in the Command dialog box
MUST be set to <$OPC_MGMTSV>.
The following diagram explains the nscmd message flow.
Figure 3-5 NSCMD Message Flow
Nscmd Basic Parameters
-node Remote HP NonStop Node Name (without “\”)
-cmd Command String within “ “ (double quotation marks). Command can be either a Guardian or OSS
command or Utility.
Examples:
nscmd –node TEST –cmd “DSAP $SUBJECT”
nscmd – node TEST –cmd “osh ls -l”
Please note that neither –c nor –p options can be used with “osh”.
Optional Variables
The following optional message variables can be used with “nscmd”.
NODENAME Node name of the Nonstop Server message.
SUBJECT Object/Subject name, for example Disk name, CPU number, Process name, Pathway TCP name,
Pathway TERM, and Collector Name contained in the message received.
MANAGER Manager name contained in the message receive. For example, PATHMON name in case you want to
take an action on a TCP or TERM object and Spooler name in case you want to take an action on a
collector within the spooler.
Examples:
nscmd -node <$OPTION(NODENAME)> -cmd “DSAP <$OPTION(SUBJECT)>”
nscmd -node <$OPTION(NODENAME)> -cmd "SCF; STATUS LINE <$OPTION(SUBJECT)>,
DETAIL”
nscmd -node <$OPTION(NODENAME)> -cmd "spoolcom <$OPTION(MANAGER)>; COLLECT
<$OPTION(SUBJECT)>, status detail"
HP Operations Manager Message Templates