KNAN21407-E

Host information could not be collected. Because host information could not be collected from a remote host, all remote monitoring operations on the host were stopped.

S:

Does not collect host information and stops all remote monitoring operations on the host.

O:

Perform the corrective action that is described in the detailed information, and then re-execute the collection of host information.

After the collection of remote host information from the remote host finishes normally, restart the remote monitoring operations that were stopped.

If an error occurred during the collection of host information from a remote host and the following detailed information is displayed, perform the indicated corrective action.

• Remote communication settings have not been configured.

  Configure the remote communication settings of the host, and then retry the operation.

• An attempt to connect to the monitored host failed.

  If the OS of the monitored host displayed for host-name is UNIX, check the following items:

  • Is communication with the monitored host possible?

  • Is the remote communication type of the monitored host set correctly?

  • Is the SSH server running on the monitored host?

  If no error is found by checking the preceding items, make sure that the SSH connection is configured correctly.

  If the OS of the monitored host displayed for host-name is Windows, check the following items:

  • Is communication with the monitored host possible?

  • Has the password for the user who is trying to log in to the monitored host expired?

  • Is the remote communication type of the monitored host set correctly?

  • Is the WMI service running?

  If no error is found by checking the preceding items, make sure that the NetBIOS (NetBIOS over TCP/IP) connection and WMI connection are configured correctly.

• Authentication failed.

  If the OS of the monitored host displayed for host-name is UNIX, check the following item:

  zueng030.tif Is SSH authentication configured correctly?

  If no error is found by checking the preceding item, make sure that the SSH connection is configured correctly.

  If the OS of the monitored host displayed for host-name is Windows, check the following items:

  • Are the user name, password, and domain name specified correctly in the System Common Settings window or the Remote Monitoring Settings window?

  • Is DCOM configured correctly on the monitored host?

  • Is DCOM configured correctly on the JP1/IM - Manager host?

  If no error is found by checking the preceding items, make sure that the WMI connection is configured correctly.

• Acquisition of an SSH private key failed.

  On the SSH page in the system common settings, set a private key file path.

• Creation of the remote monitoring process failed.

  Check the IM host account specified in the system common settings.

If detailed information other than the above is output, use the data collection tool to collect data, and then contact a system administrator.

If an error occurs during the collection of host information from JP1/Base and the following detailed information is displayed, perform the indicated corrective action.

• Collection of host information failed because a connection could not be established with the host "host-name".

  • Make sure that the connection-destination host is running.

  • Make sure that a connection can be established with the host.

  • Make sure that JP1/Base is running.

  • Make sure that name resolution can be performed.

• Collection of host information failed because the version of JP1/Base on the host "host-name" is not supported.

  • Upgrade JP1/Base to version 09-00 or later.

• An attempt to collect host information for the host "host-name" failed because the actual host type is different from the registered host type. (registered host type = registered-host-type, actual host type = host-type)

  • Change the host attribute to correct the host type, and then retry the operation.

• Collection of host information from the host "host-name" failed. (Details: IM Configuration Management database access error)

  • Execute the jimdbstatus command to check whether the IM database service is running. If the service is not running, start it.

• Collection of host information from the host "host-name" failed. (Details: A connection could not be established with the host.)

  • Make sure that the connection-destination host is running.

  • Make sure that a connection can be established with the host.

  • Make sure that JP1/Base is running.

• Collection of host information from the host "host-name" failed. (Details: The data acquired during the connection to the host is invalid.)

  • Invalid data might have been sent from JP1/Base on the target host. Make sure that JP1/Base is running on the target host.

• Collection of host information from the host "host-name" failed. (Details: There are not enough resources.)

  • Make sure that OS resources such as disk space and memory are sufficient.

• Collection of host information from the host "host-name" failed. (Details: The connection-destination host is busy.)

  • Wait a while, and then retry the operation.

• Collection of host information from the host "host-name" failed. (Details: Failed to send data to the connection-destination host.)

• Collection of host information from the host "host-name" failed. (Details: Failed to receive data from the connection-destination host.)

  • Check the OS resources, memory status, and the condition and status of the network connection with the connection-destination host.

  • Make sure that the IM Configuration Management service is running on the connection-destination host.

• Collection of host information from the host "host-name" failed. (Details: A request was executed in an invalid operating environment.)

  • The IM configuration (system hierarchy) might have been deleted.

  • Click Operation and then Verify IM Configuration to check whether the current configuration is correct.

If detailed information other than the above is output, use the data collection tool to collect data, and then contact a system administrator.