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.

Tuning and Troubleshooting OVO<br />

Solving OVO Installation Problems with Multi-homed Hosts<br />

Solution<br />

To use a specific subnet in this environment, follow these steps:<br />

1. Select the IP address of the managed node manually from the GUI.<br />

In the above example, the communication should be bound to subnet<br />

15.136.120. You can select an IP address from the Add Node or<br />

Modify Node window of the OVO administrator. The name service of<br />

the management server must contain both IP addresses for the node<br />

jacko.deu.hp.com.<br />

2. Set the path that the managed node uses for communication with the<br />

management server.<br />

Specify the parameter as follows:<br />

On HTTPS-based managed nodes<br />

Use the ovoconfchg command-line tool as follows:<br />

ovconfchg -ns eaagt -set OPC_RESOLVE_IP <br />

For more details about the ovconfchg command-line tool, refer<br />

to OVO HTTPS Agent Concepts and Configuration Guide. See<br />

also the ovconfchg man page for more information.<br />

On DCE-based managed nodes<br />

Add the string<br />

OPC_RESOLVE_IP to the opcinfo file.<br />

For details about the opcinfo file, see Table 11-1 on page 404.<br />

NOTE The changes in opcinfo are lost when the OVO agent software is<br />

reinstalled.<br />

3. Restart the agents of the managed node:<br />

/opt/OV/bin/OpC/opcagt -start<br />

Chapter 11 473

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

Saved successfully!

Ooh no, something went wrong!