8.1.2 Registering hosts

Using IM Configuration Management, you can register hosts in the network as hosts to be managed in the IM Configuration Management database. You can also list the registered hosts.

After registering hosts, you can add them to the system hierarchy or check the operating status of their services in IM Configuration Management.

You can register the following three types of hosts as management targets in IM Configuration Management:

• Agent host

• Remotely monitored host

• Host in virtualization configuration

An agent means a host managed by JP1/IM on which JP1/Base installed. A remotely monitored host means a host managed by JP1/IM on which JP1/Base is not installed.

For remotely monitored hosts, communication settings for remote connection are required. WMI/NetBIOS (NetBIOS over TCP/IP) is used for Windows, and SSH is used for UNIX.

For details when registering a host in FQDN format, see 15.3.10 System configuration for managing monitored hosts with host names in FQDN format.

The following describes the methods of registering the hosts to be managed in IM Configuration Management:

• Registering from the IM configuration management viewer

  In the Register Host window of the IM configuration management viewer, you can set and register information including the host name and host type.

• Automatically acquiring host information from definition information of the system hierarchy

  The host information contained in definition information of the system hierarchy (configuration definition information) can be registered into the IM Configuration Management database. Information about the host names, IP addresses, list of host names, host types, configuration types, and configuration application dates and times can be acquired. Host information can be acquired from the system hierarchy (IM configuration) by the following three methods:

  • Using the IM configuration management viewer to acquire the system hierarchy

    For details about how to acquire the system hierarchy, see 8.2.2 Acquiring the system hierarchy.

  • Using the IM configuration management viewer to load the system hierarchy from the configuration definition file

    For details about how to load the system hierarchy, see 8.2.5(6) Loading the system hierarchy.

  • Importing the system hierarchy on the server on which IM Configuration Management is running

    For details about how to import the system hierarchy, see 8.8.3 Importing IM Configuration Management information.

• Importing host information of remotely monitored hosts

  You can import host information of remotely monitored hosts, and then register the information in the IM Configuration Management database. Information about the host names, IP addresses, list of host names, and host types can be acquired.

  Host information of the remotely monitored hosts is acquired in the following ways:

  • In the Edit Remote Monitoring Configuration window of the IM configuration management viewer, the Open Remote Monitoring Configuration menu command is executed.

  • Remote monitoring configuration information is imported from a manager on which IM Configuration Management is running.

• Acquiring virtualization configuration information

  You can acquire virtualization environment information, and then register the information for host management. For details, see 8.3 Virtualization configuration management.

After registering hosts, host information is registered in the IM Configuration Management database, and the IP addresses set for the relevant hosts are automatically registered.

The figure below shows an example of the host information registered in the database at host registration.

Figure 8‒1: Example of host information registered in the IM Configuration Management database at host registration

Any unregistered hosts in the system hierarchy are automatically registered in the IM Configuration Management database when configuration definition information is collected from the hosts.

After IM Configuration Management is started, if no hosts are registered in the IM Configuration Management database, host information of the host (physical or logical host) on which IM Configuration Management is running is automatically registered in the IM Configuration Management database.

If the number of hosts loaded from the system hierarchy exceeds the maximum number of hosts that can be registered in the IM Configuration Management database, only the maximum number of hosts are registered in the IM Configuration Management database.

The following checks are performed on the acquired system hierarchy when the acquisition is performed by IM Configuration Management - View is used:

• Whether the local host name in the acquired system hierarchy matches the local host name registered in the IM Configuration Management database. If different, the following message is output and processing is canceled: Collection of the IM configuration failed because the local host name "host1" is different from the registered host name "host2".

• Whether two or more hosts with the same host name exist in the acquired system hierarchy. If so, a message reports that the host name is duplicated and processing is canceled.

After these checks, if there is no higher-level host in the acquired system hierarchy, the configuration type of the local host changes to Integrated manager. If there is a higher-level host in the acquired system hierarchy, the configuration type of the local host changes to Relay manager.

When you import the system hierarchy on the server running IM Configuration Management, the hosts' IP addresses are not registered in the IM Configuration Management database even if set in the export file (host_input_data.csv).

When you register the remotely monitored hosts, you can save and manage the communication settings of the OS as the system common settings in the System Common Settings window of the IM configuration management viewer.

The following table describes the system common settings information that can be managed.

Table 8‒2: System common settings information

Item	Description
WMI/NetBIOS#	Authentication information details required for a WMI/NetBIOS (NetBIOS over TCP/IP) connection are managed as common values. If you specify Common for Setting method in the communication settings for the OS, you can use the saved authentication information.
SSH	Manages authentication information using the public key authentication method.
IM host account#	Manages the account information required by a Windows manager host for remote monitoring, as the IM host account.

To Page Top