2.2.1 When you are using JP1/IM - Agent as agent

Organization of this subsection

(1) Tasks necessary what you need to do immediately after you change the host name of the manager.
(2) Tasks when you change the manager hostname
(3) Tasks when agent hostname is changed

(1) Tasks necessary what you need to do immediately after you change the host name of the manager.

Description about the tasks necessary what you need to do immediately after you change the host name of the manager.

(a) Tasks necessary in JP1/Base

In JP1/Base of the manager who changed the host name, change the host name of the authentication server. For details such as procedures, see the description of the effects and follow-up tasks when changing the host names in the chapter on modifying settings during JP1/Base operation of the JP1/Base User's Guide.

After that, you must exit JP1/Base of the manager whose hostname has been changed, and then restart.

(b) Necessary tasks related to the IM database

When a manager's host name is changed, see 1.2.3(7) Procedure for rebuilding the IM database and rebuild the IM database.

To Page Top

(2) Tasks when you change the manager hostname

(a) Host name that was set in the filtering condition

If the registered host name defined in the Severe Event Definitions window, the Settings for View Filter window, or the Detailed Settings for Event Receiver Filter window needs to be changed, you must change the registered host name settings in each setting window.

(b) Host name that was set in the Action Parameter Definitions window or in the automated action definition file

If the executing host name that was defined in the Action Parameter Definitions window or in the automated action definition file needs to be changed, you must change the executing host name settings in the Action Parameter Definitions window or in the automated action definition file.

After setting the host name, perform either of the following tasks:

When starting JP1/IM - Manager, in the Action Parameter Definitions window of JP1/IM - View, click the Apply button to enable the definition.
Reload the definition by executing the jcachange command.

(c) Host name that was set using a status change condition for the monitored object

If a host name that was set in the Status Change Condition Settings window or in the Common Condition Detailed Settings window needs to be changed, you must change the host name settings in each setting window.

After setting the host name, re-distribute the system configuration. For details, see 2.2.2(3) Procedure for re-distributing the system configuration when the host name of a manager or JP1/Base is changed.

(d) Host name that was set in the correlation event generation definition file

If a host name defined as a condition for generating a correlation event in the correlation event generation definition file needs to be changed, you must change the host name settings in the correlation event generation definition file.

After setting the host name in the correlation event generation definition file, enable the correlation event generation definition by executing the jcoegschange command.

(e) Host name that was set in the severity changing definition file

If a host name defined as a severity changing condition in the severity changing definition file needs to be changed, you must change the host name settings in the severity changing definition file.

If the severity changing function is enabled for an event, enable the host name change by performing one of the following tasks:

Execute the jco_spmd_reload command.
Start JP1/IM - Manager.
In the Add Severity Change Definition Settings window, click the OK button.
In the View Severity Change Definitions window, click the Apply button.

(f) Host name that is set in the display message change definition file

If a host name defined as a display message change condition in the display message change definition file needs to be changed, you must change the host name that is set in the display message change definition file.

If the display message change function is enabled for an event, enable the host name change by performing one of the following tasks:

Execute the jco_spmd_reload command.
Start JP1/IM - Manager.
In the Add Display Message Change Definitions window, click the OK button.
In the Display Message Change Definitions window, click the Apply button.

(g) Host name described in CN and SAN of a server certificate

If the communication encryption function is enabled and the host name described in CN and SAN of a server certificate needs to be changed, you need to re-create the server certificate.

For details about how to re-create a server certificate, see 9.4.2 Changing configured certificates in the JP1/Integrated Management 3 - Manager Configuration Guide.

(h) Hostname of the host that Intelligent Integrated Management Base runs on

After you change the host name of the host on which the Intelligent Integrated Management Base runs, you will need to restart JP1/IM - Manager. For details about how to start JP1/IM - Manager, see 3.1 Starting JP1/IM - Manager.

In addition, if the communication encryption function is enabled and the host name described in CN and SAN of a server certificate needs to be changed, you need to re-create the server certificate. For details about how to re-create a server certificate, see 9.4.2 Changing configured certificates in the JP1/Integrated Management 3 - Manager Configuration Guide.

If the host name of the host serving as the IM management node needs to be changed, you need to recollect the IM management node. For details about how to recollect an IM management node, see 3.5.6 Changes in IM management nodes in the JP1/Integrated Management 3 - Manager Overview and System Design Guide.

(i) Hostname given in the server certificate used in JP1/IM - Agent

■ Changing the hostname of the Integration Manager Host

Shut down JP1/IM - Manager.
Update with a server certificate that reflects the host name change.

For details on updating certificates, see Setup the certificate in 1.19.3(1)(b) Change settings of JP1/IM - Agent management base (for Windows) of JP1/Integrated Management 3 - Manager Configuration Guide.

Note that this step is not necessary if the certificate does not contain the host name before the change.
Start JP1/IM - Manager.

■ Changing the hostname of the Integration Manager host in a cluster system

Shut down JP1/IM agent management base.
Update with a server certificate that reflects changes in the logical host name.

For details on updating the certificate, see Setup the certificate in 7.3.3(9)(a) Setup changes for JP1/IM agent management base and 8.3.3(9)(a) Setting changes for JP1/IM agent management base of JP1/Integrated Management 3 - Manager Configuration Guide.

Note that this step is not necessary if the certificate does not contain the host name before the change.
Start JP1/IM agent management base.

To Page Top

(3) Tasks when agent hostname is changed

(a) Hostname of agent

Log in to agent host.
Shut down JP1/IM - Agent servicing.
For all JP1/IM - Agent definition files, change the location where the old host name is listed to the new host name.

For details about JP1/IM - Agent definition file, see Chapter 2. Definition Files in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.
Start JP1/IM - Agent servicing.
Reflects IM management node tree.

See 1.21.2(16) Creation and import of IM management node tree data for Windows (mandatory) and 2.19.2(17) Creating and importing IM management node tree data for Linux (mandatory) in the JP1/Integrated Management 3 - Manager Configuration Guide.

Important

The following notes apply to modifying definition files:

If you start a JP1/IM - Agent service without editing some of the definition files, or if you change the hostname to a previously used hostname (that is, a hostname with trend data left in Trend data Management Database), several configuration SID are mapped to a single tree SID. In such cases, IM management node tree file output by jddcreatetree command must be edited. For details about editing IM management node tree file, see 1.19.3(2)(c) Creation and import of IM management node tree data (for Windows) (mandatory) in the JP1/Integrated Management 3 - Manager Configuration Guide.

If you reflect the tree information without editing IM management node tree file, the display of the trend data may fail in the [Trends] tab of integrated operation viewer.

(b) Hostname to monitor for Blackbox exporter

Change the monitoring target of Blackbox exporter.

See 1.21.2(6)(c) Add, change, or Delete the monitoring target (for Windows) (mandatory) and 2.19.2(7)(c) Add, Modify, or Delete a monitoring target (for Linux) (mandatory) in the JP1/Integrated Management 3 - Manager Configuration Guide.

(c) Hostname of the host that Intelligent Integrated Management Base runs on

(d) Logical host name of the cluster system

■ For Windows

Shut down JP1/IM - Agent for a logical host.

Stop the service from the cluster software
Remove the logical-host service from Windows.

For the service used by the logical host, release the service for the logical host from Windows on both the running server and the standby server.

Run the following command to remove the logical host service:
```
Agent-path\tools\jpc_service -off service-key -h logical-host-name
```
The following shows a sample procedure for deactivating Alertmanager servicing.
```
Agent-path\tools\jpc_service -off jpc_alertmanager -h logical-host-name
```
Update the logical host name described in the definition file.

For files located in the shared-folder\jp1ima\conf and Agent-path\bin, search for the old logical host name and change all applicable locations to the new logical host name.

Agent-path\bin is executed on both the running server and the standby server because they exist on both servers.
Update the logical host name contained in the file name.

Change to the new logical host name because the file that exists in Agent-path\bin contains the logical host name.

Agent-path\bin is executed on both the running server and the standby server because they exist on both servers.
Registers a logical-host service with Windows.

For the service used by the logical host, register the service for the logical host in Windows on both the running server and the standby server.

Run the following command to register services on the logical host:
```
Agent-path\tools\jpc_service -on service-key -h logical-host-name
```
The following shows an example of registering a Alertmanager service.
```
Agent-path\tools\jpc_service -on jpc_alertmanager -h logical-host-name
```
Start all JP1/IM - Agent services for the logical host.

Start the service from the cluster software.
Reflects IM management node tree.

For details, see 1.21.2(16) Creation and import of IM management node tree data (for Windows) (mandatory) and 2.19.2(17) Creating and importing IM management node tree data (for Linux) (mandatory) in the JP1/Integrated Management 3 - Manager Configuration Guide.

■ For Linux

Shut down JP1/IM - Agent for a logical host.

Stop the service from the cluster software.
Remove the logical-host service from systemd.

For a service used by a logical host, the service for the logical host is released from systemd on both the running system and the standby system.

Run the following command to remove the logical host service:
```
/opt/jp1ima/tools/jpc_service-off service-key -h logical-host-name
```
The following shows a sample procedure for deactivating Alertmanager servicing.
```
/opt/jp1ima/tools/jpc_service -off jpc_alertmanager -h logical-host-name
```
Update the logical host name described in the definition file.

For files that exist in the shared-directory/jp1ima/conf and /usr/lib/systemd/system, search for the old logical host name and change all applicable locations to the new logical host name.

Because /usr/lib/systemd/system exists on both the running server and the standby server, it is executed on both servers.
Update the logical host name contained in the file name.

Change to the new logical host name because the file that exists in /usr/lib/systemd/system contains the logical host name.

Because /usr/lib/systemd/system exists on both the running server and the standby server, it is executed on both servers.
Registers a logical-host service with systemd.

For a service used by a logical host, the service for the logical host is registered in systemd on both the running system and the standby system.

Run the following command to register services on the logical host:
```
/opt/jp1ima/tools/jpc_service -on service- key -h logical-host-name
```
The following shows an example of registering a Alertmanager service.
```
/opt/jp1ima/tools/jpc_service -on jpc_alertmanager -h logical-host-name
```
Start all JP1/IM - Agent services for the logical host.

Start the service from the cluster software.
Reflects IM management node tree.

For details, see 1.21.2(16) Creation and import of IM management node tree data (for Windows) (mandatory) and 2.19.2(17) Creating and importing IM management node tree data (for Linux) (mandatory) in the JP1/Integrated Management 3 - Manager Configuration Guide.

(e) Host name of the container

You cannot change the hostname of a container. Therefore, create a new container and delete any containers that you no longer need.

For details on how to create a container, see 2.20.1(3) How to Create Docker and Podman Containers and 2.20.1(4) How to delete Docker and Podman Containers in the JP1/Integrated Management 3 - Manager Configuration Guide.

To Page Top