Hitachi

JP1 Version 12 JP1/Integrated Management 2 - Manager Messages


KNAN22255-E

IM Configuration synchronization is failed. (Cause: detailed-message)

Synchronization failed.

S:

Stops synchronization.

O:

If the following detailed information is displayed, take the indicated corrective action.

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

    Check the following items:

    • Is there sufficient memory?

    • Has Configuration Management been started?

    • Was JP1/Base restarted after JP1/IM was installed?

    • Do you have write and read permission for the conf/route/ directory?

  • A communication with JP1/Base failed.

    Make sure that JP1/Base is running.

  • JP1/Base is busy.

    Wait awhile, and then retry the operation.

  • The IM configuration does not exist.

    Execute the jbsrt_get command, and then make sure that the IM configuration (system hierarchy) exists on the host.

    If there is no IM configuration (system hierarchy), use the IM Configuration Management window to refresh it.

  • A timeout occurred.

    Check the network configuration and status with the acquired host.

    Also make sure that JP1/Base is running on the acquired host.

  • The execution environment of JP1/Base is invalid.

    Check the following items:

    • Is the JP1/Base conf directory defined in the common definition?

    • Did the JP1/Base configuration end normally?

  • The JP1/Base configuration file could not be accessed.

    Make sure that the access permission to the file has been set correctly. Also determine whether the file has been opened (locked) by another application.

  • A communication error occurred with JP1/Base.

    Check the following items:

    • Revise the common definition jp1hosts value.

    • 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.

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