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.

Maintaining OVO<br />

Changing Hostnames and IP Addresses<br />

a. Perform the following steps only on those nodes that contain<br />

the modified OVO management server:<br />

1. Shut down the OVO agents by entering:<br />

For DCE nodes:<br />

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

For HTTPS nodes:<br />

/opt/OV/bin/ovc -kill<br />

2. On RPC-based managed nodes, update the agent<br />

opcinfo file with a new hostname for the management<br />

server. For the location of the opcinfo file on the<br />

RPC-based managed nodes, see Table 11-1 on page 404.<br />

On HTTPS-based managed nodes, use a command-line<br />

tool ovconfchg to update it with a new management<br />

server hostname. Use the following namespaces:<br />

[sec.core.auth]<br />

MANAGER<br />

MANAGER ID<br />

and<br />

[sec.cm.client]<br />

CERTIFICATE_SERVER<br />

MANAGER and CERTIFICATE_SERVER are usually the same.<br />

For more details on how to use the ovconfchg, refer to<br />

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

See also ovconfget and ovconfchg man pages for more<br />

information.<br />

3. Restart the OVO agent processes by entering:<br />

For DCE agents:<br />

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

For HTTPS agents:<br />

/opt/OV/bin/ovc -start<br />

Chapter 13 557

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

Saved successfully!

Ooh no, something went wrong!