13.12.2012 Views

HP OpenView Operations Administrator's Reference - filibeto.org

HP OpenView Operations Administrator's Reference - filibeto.org

HP OpenView Operations Administrator's Reference - filibeto.org

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Installing OVO Agents on the Managed Nodes<br />

Managing OVO Agent Software<br />

68<br />

Administering Managed Nodes Depending on<br />

subagent id Values<br />

opcragt in OVO/UNIX can accept subagent id values as numbers or<br />

names. The behavior is dependent upon communication type being used:<br />

HTTPS or DCE.<br />

HTTPS Communication Type<br />

When the subagent id argument is a name, the selected node is<br />

administrated directly. When the subagent id is number, a mapping<br />

to subagent id name must exist in the subagt_aliases file.<br />

DCE Communication Type<br />

When the subagent id is a number, status or start/stop<br />

command is called directly. When the subagent id is a name, then<br />

mapping from name to number must exist in the subagt_aliases<br />

file.<br />

By default three mappings are defined in subagent_aliases file:<br />

(0 -> AGENT)<br />

(1 -> EA)<br />

(12 -> CODA)<br />

The location of the subagt_aliases file is:<br />

/etc/opt/OV/share/conf/OpC/mgmt_sv/subagt_aliases<br />

When mapping between number and name is required but does not exist,<br />

the following error message is displayed:<br />

DCE Nodes<br />

Can't find information for subagent id '< sugagent_id >'<br />

searching in<br />

/etc/opt/OV/share/conf/OpC/mgmt_sv/subagt_aliases.<br />

(OpC40-340)<br />

If desired, a new mapping can be added by manually editing the<br />

subagent_aliases file.<br />

HTTPS Nodes<br />

Subagent XXX:<br />

Subagent not registered.<br />

Chapter 1

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!