Table of Contents
Advertisement
Tuning, Troubleshooting, Security, and Maintenance
Changing Hostnames/IP Addresses
If you are not operating in a multi-management server environment
(see opcmom(4)), perform the following steps on all managed nodes
that are configured in the Node Bank and which are running an ITO
agent:
a. Shut down the ITO agents:
/opt/OV/bin/OpC/opcagt -kill
b. Update the agent's opcinfo file with the ITO management
server's new hostname. See Table 10-3 on page 399 for the location
of the opcinfo file on the managed nodes.
c. Restart the ITO agent processes:
/opt/OV/bin/OpC/opcagt -start
If you are running your system in a multi-management-server
environment (using flexible-management features), carry out the
following steps:
a. Perform steps a through c above only on those nodes that contain
the modified ITO management server in their opcinfo file.
b. If the modified ITO management server is configured as a primary
manager for some managed nodes, update those managed nodes
by running the following command from the modified ITO
management server:
/opt/OV/bin/OpC/opcragt -primmgr [ -all | \
[ -nodegrp <group>...] <node>...]
c. Make sure that your hostname/IP-address changes are reflected in
all appropriate configurations and templates across the entire
flexible-management environment. Refer to opcmom(4) for how to
setup, modify or distribute the templates in a
flexible-management environment.
16. If you have setup manager-to-manager message forwarding, you will
need to modify the hostname and IP-address manually on all
management servers that have the changed system in their node
bank. In addition, check message-forwarding or escalation templates
on the management servers concerned for occurrences of the old
hostname/IP address and modify accordingly. The following file needs
to be checked:
/etc/opc/OV/share/conf/OpC/respmgrs/msgforw/escmgr
430
Chapter 10
Advertisement
Table of Contents
Troubleshooting
