Hitachi

Job Management Partner 1 Version 10 Job Management Partner 1/Integrated Management - Manager Messages


KNAN22249-E

Application of the IM configuration failed. (Cause: "Detailed information")

Application of the IM configuration (system hierarchy) failed.

S:

Stops applying the IM configuration.

O:

Take one of the following actions depending on the detailed information.

  • A communication with JP1/Base failed.

    Make sure that JP1/Base is running.

  • JP1/Base is busy.

    Wait awhile, and then retry the operation.

  • A timeout occurred.

    Check the following items:

    [Figure] Has an error occurred on a lower-level host?

    [Figure] If allocation of the definition takes too much time, the jbsrt_distrib command will time out. Revise the system configuration.

  • Failed to read the IM configuration definition file.

    Check the following items:

    [Figure] Is the configuration definition file in the correct location?

    [Figure] Do you have write permission for the conf/route/ directory?

  • A communication error occurred with JP1/Base.

    Check the following items:

    [Figure] Revise the common definition jp1hosts.

    [Figure] Make sure that the JP1/Base configuration ended normally.

    If these actions do not resolve the problem, collect data, and then contact a system administrator.

  • The execution environment of JP1/Base is invalid.

    Check the following items:

    [Figure] Is the JP1/Base conf directory defined in the common definition?

    [Figure] Did the JP1/Base configuration end normally?

  • An internal error occurred in JP1/Base during processing.

    Check the following items:

    [Figure] Is there sufficient memory?

    [Figure] Has Configuration Management been started?

    [Figure] Was JP1/Base restarted after JP1/IM was installed?

    [Figure] Do you have write and read permission for the conf/route/ directory?

  • There is not the local host name in the IM configuration.

    Define a local host in the configuration definition file.

  • Trap running for the removed Agentless host in the IM configuration.

    Check whether the remote monitoring host for which a log file trap was started has been deleted from the IM configuration.

  • The IM configuration might have been changed.

    Update the information to the latest host information, and then retry the operation.