Hitachi

JP1 Version 12 JP1/Performance Management - Remote Monitor for Platform Description, User's Guide and Reference

10.2.3 PFM - RM for Platform was started, but no performance data is being collected

If the Status field value in the PD record is ERROR, take appropriate action based on the Reason field value. If the cause of the error cannot be determined after you perform appropriate action, collect maintenance data and contact the system administrator.

The following describes the items to be checked for each Reason field value.

Organization of this subsection

(1) Connection failed: Connection to the monitored host failed.

When the monitored host is running Windows

  • Is the monitored host running?

  • Is the WMI service running on the monitored host?

  • Were the settings for the following specified correctly when the monitoring target was set up?#1

    • TargetHost

  • Can the name be resolved by the host name (TargetHost) that was specified when the monitoring target was set up?

  • Were the following WMI connection setup procedures performed correctly?

    • DCOM setting at the PFM - RM host

    • WMI namespace setting at the monitored host

    • Firewall setting at the monitored host

  • If there is a firewall between PFM - RM for Platform and the monitoring target, is the firewall passage port set appropriately?

When the monitored host is running UNIX

  • Is the monitored host running?

  • Is the SSH service running on the monitored host?

  • Were the following settings specified correctly when the monitored host was set up?#1

    • Target Host

    • UseCommonAccount#2

    • User#3

    • Private_Key_File#3

    •Port

  • Can the name be resolved by the host name (TargetHost) that was specified when the monitoring target was set up?

  • Were the settings for the following items specified correctly when the instance environment was set up?#4 (This applies only when the PFM - RM host is running Windows.)

    •SSH_Type

    •SSH_Client

    •Perl_Module

  • Was the SSH connection setup procedure performed correctly?

  • If there is a firewall between PFM - RM for Platform and the monitoring target, is the firewall passage port set appropriately?

#1

To check the items that have been set up, execute the jpcconf target setup command. If you are using common account information, execute the jpcconf acc display command to check the setting items. Alternatively, in PFM - Web Console, from the Remote Monitor Collector service of PFM - RM for Platform, view the Remote Monitor Configuration property to check the settings.

#2

This item is displayed when both the version of PFM - RM for Platform and the version of the prerequisite program (PFM - Manager or PFM - Base) in the same machine as PFM - RM for Platform are 10-50 or later.

#3

If you are using common account information, the values of User and Private_Key_File are the respective values that are specified in User and Private_Key_File in common account information (ssh).

#4

To check the items that have been set up, execute the jpcconf inst setup command. Alternatively, in PFM - Web Console, from the Remote Monitor Collector service of PFM - RM for Platform, view the Remote Monitor Configuration property to check the settings.

To Page Top

(2) Authorization failed: Authorization of the monitored host failed.

The items to be checked in Windows are described below. This error is not applicable to UNIX.

When the monitored host is running Windows

  • Were the following settings specified correctly when the monitoring target was set up?#1

    •UseCommonAccount#2

    • User#3

    • Password#3

    • Domain#3

  • Were the following WMI connection setup procedures performed correctly?

    • DCOM setting on the PFM - RM host

    • DCOM setting on the monitored host

#1

To check the settings, execute the jpcconf target setup command. If you are using common account information, execute the jpcconf acc display command to check the setting items. Alternatively, use PFM - Web Console to check the settings by displaying the Remote Monitor Configuration properties from the Remote Monitor Collector service of PFM - RM for Platform.

#2

This item is displayed when both the version of PFM - RM for Platform and the version of the prerequisite program (PFM - Manager or PFM - Base) in the same machine as PFM - RM for Platform are 10-50 or later.

#3

If you are using common account information, the values of User, Password, and Domain are the respective values that are specified in User, Password, and Domain in common account information (wmi).

To Page Top

(3) Collection timeout: Performance data collection did not end within the specified time

When the monitored host is running Windows

  • In the instance environment, is the collection interval of the collection process for the monitored host too short?

    The collection interval of the collection process means the Interval setting in the instance environment. If this interval is short, either reduce the number of monitoring targets in the instance environment or lengthen the collection interval of the collection process.

  • Has the monitored host been started?

  • Were settings specified correctly when the monitored host was set up?#1

  • Was the WMI connection setting procedure followed correctly?

  • Is the PFM - RM host or the monitored host under a heavy system load?

When the monitored host is running UNIX

  • In the instance environment, is the collection interval of the collection process for the monitored host too short?

    The collection interval of the collection process means the Interval setting in the instance environment. If this interval is short, either reduce the number of monitoring targets in the instance environment or lengthen the collection interval of the collection process.

  • Has the monitored host been started?

  • Were settings specified correctly when the monitored host was set up?#1

  • Was the SSH connection setting procedure followed correctly?

  • Is the PFM - RM host or the monitored host under a heavy system load?

  • Was no set for UseDNS#3 in the /etc/ssh/sshd_config#2 file on the SSH server of the monitored host?

    If the environment takes time to resolve the PFM - RM for Platform host name on the SSH server of the monitored host, a timeout might occur when collecting performance data from PFM - RM for Platform. In this case, this issue might be solved by setting no for UseDNS#3 in the /etc/ssh/sshd_config#2 file on the SSH server of the monitored host.

#1

To check the items that have been set up, execute the jpcconf target setup command. Alternatively, in PFM - Web Console, from the Remote Monitor Collector service of PFM - RM for Platform, view the Remote Monitor Configuration property to check the settings.

#2

This will be /opt/ssh/etc/sshd_config when using HP-UX.

#3

This will be LookupClientHostname when using Solaris.

To Page Top

(4) Invalid environment (SSH_Client): The file specified in SSH_Client when the instance environment was set up does not exist (when the PFM - RM host is running Windows and the monitored host is running UNIX)

The item to be checked when the PFM - RM host is running Windows and the monitored host is running UNIX is shown below. This error is not applicable when the monitored host is running Windows or when the PFM - RM host is running UNIX.

#

To check the item that has been set up, execute the jpcconf inst setup command. Alternatively, in PFM - Web Console, from the Remote Monitor Collector service of PFM - RM for Platform, view the Remote Monitor Configuration property to check the setting.

To Page Top

(5) Invalid environment (Perl_Module): The file specified in Perl_Module when the instance environment was set up does not exist (when the PFM - RM host is running Windows and the monitored host is running UNIX)

The item to be checked when the PFM - RM host is running Windows and the monitored host is running UNIX is shown below. This error is not applicable when the monitored host is running Windows or when the PFM - RM host is running UNIX.

#

To check the item that has been set up, execute the jpcconf inst setup command. Alternatively, in PFM - Web Console, from the Remote Monitor Collector service of PFM - RM for Platform, view the Remote Monitor Configuration property to check the setting.

To Page Top

(6) Invalid environment (Private_Key_File): The file specified in Private_Key_File when the monitored host was set up does not exist

The environment where the message The file specified in Private_Key_File when the monitored host was set up does not exist is output differs according to the version of PFM - RM for Platform, as follows:

The items below are checked when the monitored host is running UNIX. This error is not applicable when the monitored host is running Windows.

#1

To check the item that has been set up, execute the jpcconf target setup command. If you are using common account information, execute the jpcconf acc display command to check the setting items.

Alternatively, in PFM - Web Console, from the Remote Monitor Collector service of PFM - RM for Platform, view the Remote Monitor Configuration property to check the setting.

#2

This item is displayed when both the version of PFM - RM for Platform and the version of the prerequisite program (PFM - Manager or PFM - Base) in the same machine as PFM - RM for Platform are 10-50 or later.

#3

If you are using common account information, the value of Private_Key_File is the value that is specified in Private_Key_File in common account information (ssh).

To Page Top

(7) Values other than those described above

To Page Top

Copyright (C) 2019, 2020, Hitachi, Ltd.

Copyright (C) 2019, 2020, Hitachi Solutions, Ltd.