Hitachi

JP1 Version 12 JP1/IT Desktop Management 2 Overview and System Design Guide


2.18.7 Managing devices in a multi-server configuration

In a multi-server configuration, you can manage the device information reported from management relay servers under the local server, in addition to the device information directly under the local server.

Tip

Devices managed on the local server are subject to device maintenance. This means that, in a multi-server configuration, devices managed by management relay servers under the local server are not subject to device maintenance on a higher management server. When you use a multiple-server configuration, perform device maintenance separately on the management server and on the management relay server under the local server.

Related Topics:

Organization of this subsection

(1) Automatic device information reporting to the higher management server

In a multi-server configuration, a management relay server automatically reports the device information to the higher management server. The higher management server can collectively manage device information for device directly under the server and device information reported by the management relay server under the server.

The following figure shows the device information reporting flow in a multi-server configuration.

[Figure]

The conditions that trigger a lower management relay server to report the device information to the higher management server are as follows:

Report to the higher management server includes device information of agent-installed computers and agentless computers.

The device information of offline-managed computers must be reported from an administrator's computer managed by the same server. The device information of offline-managed computers are also reported to the higher management server when the collected information is reported to the management server that manages the computers.

If you change a device type on a management relay server managing the device, and when the new device type item does not exist in the higher management server, the device type is added to the higher management server.

(2) Manual device information reporting to the higher management server

In a multi-server configuration, the device information collected by a management relay server can be manually reported to the higher management server. By manually reporting the device information, you can restore the device information inconsistency between the management servers.

If the device information becomes inconsistent between a management relay server and the higher management server due to one of the following reasons, manually report the device information.

Manually reported device information is only reflected to the connection target of the management server on which reporting is made. The information is not reflected to management servers at a level higher than the connection target management server.

(3) Editing the device information managed by a management relay server under the local server

You can use any management server to edit the device information reported by management relay servers under the management server. The device information that can be edited for devices directly under the local server and for other devices is the same.

The edited device information value is only applied to the higher management server. If you want to apply the change to the management relay servers under the server, you need to edit values in the management relay server under the server.

(4) Mechanism of changing the managing device in a multi-server configuration

If a managed computer is moved to under another management relay server, the information of the device is added to the new management relay server, and the device information is removed from the original management relay server. The following figure shows the device information flow when the managed computer is moved.

[Figure]

1. Collecting the device information

If a computer managed by M03 moves to under M04, the device information is collected by M04.

2. Reporting the device information (from M04 to M02)

M04 adds the device information, and then reports the device information to M02.

3. Reporting the device information (from M02 to M01)

M02 detects the device route change, and then update the device information. It also reports the device information to M01.

4. Reporting the device information (from M02 to M03)

M02 notifies M03 of deleting the device information. M03 deletes the device information.

Trigger of the notification of deleting the device information

If a device is moved between different management servers, the device route change is reflected to the configuration information held by the management servers. This triggers the notification of deleting the device information to the original management relay server.

Important

You must change the connection target in the agent configuration of the original management relay server before moving the device. For details, see the description on how to change the management server to which the agent connects in the JP1/IT Desktop Management 2 Configuration Guide.

Related Topics:

(5) Applying software search conditions on a management relay server under the local server

In a multi-server configuration, you can apply the software search conditions created in the local server to the management relay servers under the local server. If you apply the search conditions, the applied conditions are added to all the management relay servers. Because a management relay server can have original search conditions in addition to the applied search conditions, a management relay server can use individual search conditions.

The software search conditions applied by the higher management server cannot be changed on the applied computer. However, the search condition can be deleted. For example, if the higher management server is replaced without applying the deletion of a search condition, delete the unnecessary search condition on the applied computer.

Related Topics:

(6) Collecting revision history of the devices managed by management relay servers under the local server

In a multi-server configuration, the device revision history collection target can be narrowed down to only the devices directly under the local server. If you want to distribute loads on the management server due to revision history collection, configure so that the revision history of devices other than those directly under the local server is not collected. By default, the revision history of devices other than those directly under the local server is collected.

The following shows an example multi-server configuration where the revision history of the devices other than the devices directly under the local server is not collected.

[Figure]

In this example, each management server only collects the revision history of the computers directly under itself. If there is no administrator for management relay server 2, the administrator of the primary management server starts the operation window of management relay server 2 to check the revision history.

Related Topics:

(7) Deleting device information in a multi-server configuration

If you want to delete a device that no longer needs to be managed, delete the device information on the management relay server that manages the device. If a device is deleted in the management relay server, the deletion is reported to the higher management server, and the device information is deleted from the higher management server.

Conditions that trigger deletion of device information are as follows:

Trigger for device information deletion

Operation after deletion

The device information is deleted in the operation window of the management relay server that manages the device.

The device information is deleted from the higher management server.

JP1/IT Desktop Management 2 - Agent is uninstalled.

The device information is deleted from the higher management server.

This operation is based on the State_AfterAgentUninstalling value in the configuration file specified for the management relay server. Depending on the settings in the configuration file, the device information is not deleted and the management type is changed to agentless.

The Asset Status of a hardware asset is changed to Disposed.

The device information related to the disposed asset information is deleted from the higher management server and management relay servers under the local server.

Asset information is deleted in JP1/IT Desktop Management 2 - Asset Console.

The connection target management relay server of the device is changed.

The device information is deleted from the original management relay server.

Tip

If the device information reporting fails and device information becomes inconsistent between the higher management server and the management relay server that manges the device, manually delete the device information on the higher management server to restore consistency. At this time, deletion of the device information is not reported. The device information is deleted only from the higher management server.

Related Topics: