5.3.10 Changing the physical host name of PFM - Agent or PFM - RM

You must perform operations on the following hosts when changing the PFM - Agent or PFM - RM host name:

PFM - Manager host
PFM - Agent or PFM - RM host
Monitoring console

The following figure shows the process flow.

If Performance Management is linked with JP1/SLM, before you start the procedure described below, see the section in the JP1/Performance Management User's Guide that describes the general procedure for changing host names after Performance Management has been linked with JP1/SLM.

Figure 5‒8: Process flow for changing the physical host name of the PFM - Agent or PFM - RM host

Use the following procedure to set the display conditions (Each step corresponds to the step number in the figure above):

Suspend monitoring for the PFM - Agent or PFM - RM host whose host name is to be changed.

If you do not want health check events to occur while changing the host name, suspend monitoring for the host whose name is to be changed. You can do so by using the jpctool monitor suspend command of the PFM - Manager host or from the monitoring console.

In a multiple-monitoring configuration, perform this step on the primary manager.

For details about suspending monitoring, see the chapter that describes suspending and resuming of monitoring in the JP1/Performance Management User's Guide.
Suspend monitoring with the new host name specified.

If you suspended monitoring in step 1, you also need to suspend monitoring with the new host name specified.

In this case, use the -force option of the jpctool monitor suspend command of the PFM - Manager host.

In a multiple-monitoring configuration, perform this step on the primary manager.
Delete the settings for PFM - Agent or PFM - RM.

Use your PFM - Web Console to delete the agent definitions from the PFM - Agent or PFM - RM host whose host name is to be changed (by deleting the definitions from the management folder in the Agents tree).

In a multiple-monitoring configuration, perform this step on the primary manager.

For details about the procedure for changing the agent definition, see the chapter that describes monitoring agents in the JP1/Performance Management User's Guide.
Stop the services on the PFM - Agent or PFM - RM host.

Stop all Performance Management programs and services on the PFM - Agent or PFM - RM host for which you intend to change the host name. To stop services, use the jpcspm stop command.
Change the monitoring host name of the PFM - Agent or PFM - RM host.

Execute the jpcconf host hostname command to change the monitoring host name.

To change a physical host name to hostB:
```
jpcconf host hostname -newhost hostB -d /var/tmp/backup -dbconvert convert
```
Note:

After you execute the above command, do not execute other Performance Management commands until you change the physical host name in the next step.

For details about the jpcconf host hostname command, see the chapters that describe commands in the manual JP1/Performance Management Reference.

Note

As a guideline, the directory specified for the -d option in the jpcconf host hostname command must have empty disk space that is equal to or greater than the sum of the total size of the PFM - Agent and PFM - RM Store databases on the specified host and the total size of the databases in the import directories. If the Store database storage directory and the import directory have been changed, determine the required disk space based on the sizes of the databases in the new directories.

For example, if PFM - Agent for Platform and PFM - Agent for Oracle are on the specified host, empty disk space equal to or greater than the sum of the total size of the Store databases of those agents and the total size of the databases in the import directories is required. However, you do not need to include the size of Store database for the PFM - Manager Master Store service in the total size.
Change the physical host name of the PFM - Agent or PFM - RM host.

Change the physical host name of the PFM - Agent or PFM - RM host.
Change the settings in the jpchosts file, in the hosts file, or on the DNS server as necessary so that the new host names in the Performance Management system can be resolved to IP addresses.

If the machines need to be restarted, change the settings of the Performance Management programs and services so that they will not start automatically when the machines restart. After the PFM - Manager host operation has finished, return the settings so that the Performance Management programs and services start automatically.

Perform the PFM - Agent-specific procedure, if necessary.

Table 5‒17: Necessity of the PFM - Agent-specific procedure
Configuration		Necessity and reference
The version of PFM - Agent on which the monitoring host name is changed is 09-00 or later.		Whether the PFM - Agent-specific procedure is necessary depends on PFM - Agent. For details about the PFM - Agent-specific procedure, see the chapters describing the installation and setup in the PFM - Agent manuals.
The version of PFM - Agent on which the monitoring host name is changed is earlier than 09-00.	The following PFM - Agent: PFM - Agent for Cosminexus PFM - Agent for Domino PFM - Agent for Enterprise Applications	The PFM - Agent-specific procedure is necessary. For details about the PFM - Agent-specific procedure, see 5.3.13 Optional PFM - Agent-specific procedure to be performed when the monitoring host name is changed.
	For all other cases	The PFM - Agent-specific procedure is not necessary.

If the PFM - Agent-specific procedure is necessary, perform the procedure indicated in the table above, and then proceed to the following steps.

Delete service information on the PFM - Manager host.

Even though the PFM - Agent or PFM - RM host name is changed, the service information of the Performance Management programs with the previous host name remains the same. Therefore, you need to delete unnecessary information from the PFM - Manager host. In a multiple-monitoring configuration, perform this step on both the primary and secondary managers.

The types of service information that you need to delete and the method of checking the service information are described as follows:

Service information on the host with the previous host name

All the items that are displayed by executing the following command must be deleted:
```
jpctool service list -id "*" -host previous-host-name
```
Service information whose service ID contains the previous host name

Items whose Service ID column contains the previous host name of the items that are displayed by executing the following command must be deleted:
```
jpctool service list -id "*"
```
Service information can be deleted by using the jpctool service delete command.

Delete service information on the host with the previous host name by using the following command:
```
jpctool service delete -id "*" -host previous-host-name
```
Additionally, delete service information whose service ID contains the previous host name by using the following command:
```
jpctool service delete -id "???previous-host-name" -host new-host-name
```
If the KAVE05233-W message is issued during command execution because of a service information deletion error, re-execute the command as follows:
```
jpctool service delete -id "*" -host previous-host-name -force
jpctool service delete -id "???previous-host-name" -host new-host-name -force
```
Note

Even though you execute the jpctool service list command, old service information that contains the previous host name might not be displayed. Because such service information also needs to be deleted from the database, you must execute the jpctool service delete command shown above.

For details about the commands, see the chapter that describes commands in the manual JP1/Performance Management Reference.
Apply PFM - Manager's service information.

To apply the deletion of service information to PFM - Web Console, synchronize the service information between PFM - Manager and PFM - Web Console. Use the jpctool service sync command to synchronize service information.

In a multiple-monitoring configuration, perform this step on both the primary and secondary managers.

The time when the service information, which is synchronized by using the jpctool service sync command, is applied to PFM - Web Console differs depending on the version of PFM - Web Console. For details about the jpctool service sync command, see the chapter that describes commands in the manual JP1/Performance Management Reference.
Start the services on the PFM - Agent or PFM - RM host.

Start the Performance Management programs and services on the PFM - Agent or PFM - RM host for which you have changed the host name. To start the services, use the jpcspm start command.
Change the configuration of the business groups, if necessary.

If a PFM - Agent or PFM - RM host whose host name has been changed has been assigned to business groups, you need to change the configuration of the business groups.

In a multiple-monitoring configuration, perform this step on the primary manager.

For details about the procedure, see the chapter that describes management of user accounts and business groups in the JP1/Performance Management User's Guide.
Reconfigure the definition in step 3 as necessary.

Reconfigure the definition (that was deleted in step 3) of PFM - Agent or PFM - RM for which the host name was changed.

In a multiple-monitoring configuration, perform this step on the primary manager.
Update the alarm settings.

In the following cases, you must update the alarm settings by using the jpctool alarm command of the PFM - Manager host or the monitoring console.

In a multiple-monitoring configuration, perform this step on the primary manager.
- The action handler of the PFM - Agent or PFM - RM host is specified for the action handler that executes actions.
  
  Edit the alarm to set PH1<new-pfm-agent-or-pfm-rm-host-name> for the action handler that executes actions.
For details about how to edit alarms, see the chapter that describes the operation monitoring with alarms in the JP1/Performance Management User's Guide.
Update the JP1 system event settings.

If one of the following conditions is met, you need to update the JP1 system event settings by using the PFM - Web Console:

In a multiple-monitoring configuration, perform this step on the primary manager.
- The previous host name has been specified as the name of the event server to which JP1/Base connects.
- The previous host name has been specified as the host name of the monitoring console for JP1 system events.
For details on JP1 system events, see the chapter that explains operation monitoring linked with the integrated management program (JP1/IM) in the JP1/Performance Management User's Guide.
Resume monitoring with the previous host name specified.

If you suspended monitoring in step 1, you need to resume monitoring with the previous host name specified to delete the settings information of monitoring suspension for the previous host name.

In this case, use the -force option of the jpctool monitor resume command of the PFM - Manager host.

In a multiple-monitoring configuration, perform this step on the primary manager.
Resume monitoring for the PFM - Agent or PFM - RM host whose host name was changed.

If you suspended monitoring in step 2, use the jpctool monitor resume command of the PFM - Manager host or use the monitoring console to resume monitoring for the PFM - Agent or PFM - RM host.

In a multiple-monitoring configuration, perform this step on the primary manager.
Match the definitions on the primary manager and the secondary manager (in a multiple-monitoring configuration).

Export the definitions for the multiple-monitoring configuration from the primary manager and import them to the secondary manager so that the primary manager and the secondary manager have the same definitions.

For details about how to match definitions on the primary and secondary managers, see the description regarding duplication of definitions in the JP1/Performance Management User's Guide.
Check whether the JP1 system event settings have been properly updated.

Check the following items the settings are changed:
- Collection of performance data
  
  Make sure that performance data can be collected for a period at least twice as long as the time period specified as the collection interval (Collection Interval).
- Execution of the jpcrpt command
  
  Make sure that there is no problem in outputting the collected performance data.
- Check of the report definition and alarm definition
  
  Make sure that there is no problem with the report definition and alarm definition created in the Web browser.
- Check of the actions
  
  Make sure that there is no problem in executing the created alarm actions.

To Page Top