7.2.4 Verifying the system hierarchy
You can use IM Configuration Management to verify whether the configuration definition information held in JP1/Base on an agent in the JP1/IM system matches the configuration definition information held in the IM Configuration Management database. For a remotely monitored host, you can verify the remote connection by using the authentication information for remote setting.
Verify the system hierarchy on the IM Configuration page of the IM Configuration Management window.
The following table describes the range of hosts whose system configuration information you can verify from the integrated manager.
|
Host type |
Verify |
|
|---|---|---|
|
Local host |
Y |
|
|
Relay manager |
Y |
|
|
Base manager |
Y |
|
|
Agent |
Directly under the local host |
Y |
|
Under a relay manager |
Y |
|
|
Under a base manager |
N# |
|
|
Remotely monitored host |
Under the local host |
Y |
|
Under a base manager |
N# |
|
- Legend:
-
Y: The information can be verified.
N: The information cannot be verified.
- #
-
Verify the system hierarchy on the base manager because a firewall might prevent the integrated manager from connecting to the agent or remotely monitored host under a base manager.
The following table describes the range of hosts whose system configuration information you can verify from a base manager.
|
Host type |
Verify |
|
|---|---|---|
|
Local host |
Y |
|
|
Parent host |
N |
|
|
Relay manager |
Y#1 |
|
|
Base manager |
Y#1 |
|
|
Agent |
Directly under the local host |
Y#1 |
|
Under a relay manager |
Y#1 |
|
|
Under a lower-level base manager |
N#2 |
|
|
Remotely monitored host |
Under the local host |
Y |
|
Under a lower-level base manager |
N#2 |
|
- Legend:
-
Y: The information can be verified.
N: The information cannot be verified.
- #1
-
Not recommended because the system configuration, including the integrated manager, would be more than three tiers.
- #2
-
Verify the system hierarchy on the lower-level base manager because a firewall might prevent the integrated manager from connecting to the agent or remotely monitored host under the lower-level base manager.
Verify the system hierarchy while connection can be established with the monitored host. If connection cannot be established, the verification process might require a considerable amount of time.
You can check the verification results in the following windows:
-
Host List page or IM Configuration page of the IM Configuration Management window
-
Execution Results window
If the information held by JP1/Base on the manager running IM Configuration Management differs from the information in the IM Configuration Management database, the affected hosts are represented by error-status icons in the tree display area of the IM Configuration page.
If verification fails, an error-status icon is displayed for the affected host in the tree display area of the IM Configuration page.
Configuration definition information cannot be verified on hosts running a version of JP1/Base earlier than version 9. In this case, the affected hosts are represented by error-status icons in the tree display area of the IM Configuration page.
If the configuration definition information on the manager does not exist or if the information held by JP1/Base and the information in the IM Configuration Management database do not match, verification on the manager fails, the processing is terminated, and the system hierarchy appears grayed in the tree display area on the IM Configuration page.
If the system hierarchy appears grayed in the tree display area on the IM Configuration page, check and, if necessary, revise the configuration definition information (agent configuration), and reapply the agent configuration.
For a base manager, first execute Synchronize IM Configuration on the integrated manager, and then check, on the base manager, whether Collect IM Configuration was executed.
For details, see 3.2.4(3) Applying a system hierarchy to a system managed by IM Configuration Management in the JP1/Integrated Management 2 - Manager Configuration Guide.