8.2.2 Acquiring the system hierarchy
Using IM Configuration Management, you can acquire from the manager on which IM Configuration Management is running, the definition information of the system hierarchy (configuration definition information) held in JP1/Base on manager hosts. You can then save that information as the configuration definition information in the IM Configuration Management database on the manager on which IM Configuration Management is running. Note that you cannot collect the system hierarchy information from remotely monitored hosts.
Acquire the system hierarchy on the configuration definition information on the IM Configuration page of the IM Configuration Management window.
When the system hierarchy is applied, the content of system hierarchy displayed by the IM configuration management viewer is applied. If the system hierarchy has not been acquired, a system hierarchy different from the currently configured hierarchy might be applied. To avoid this problem, you must be sure to acquire the system hierarchy.
Acquire the system hierarchy as follows:
-
When the system hierarchy has been changed without using IM Configuration Management as in the following cases, acquire the system hierarchy on the integrated manager:
-
When IM Configuration Management is deployed in an existing JP1/IM system
-
When the system hierarchy is altered by executing the jbsrt_distrib command on the manager running IM Configuration Management
-
-
After the system hierarchies are synchronized between the integrated manager and the base managers, acquire the system hierarchy on each base manager.
The configuration definition information held in the IM Configuration Management database is updated when the system hierarchy is acquired. If you want to save the existing information before it is updated, you must export it in advance on the manager running IM Configuration Management.
After the acquisition, the system hierarchy is displayed as follows in IM Configuration Management:
-
Any unregistered hosts included in the acquired information are automatically registered in the IM Configuration Management database. No host information is acquired for these hosts, however. Instead, you must collect the information manually on the Host List page or IM Configuration page of the IM Configuration Management window.
If duplicated host names exist in the acquired information, an error message appears and the acquired information is not applied in the configuration definition information held in the IM Configuration Management database.
Make sure no hosts with the same host name exist in the configuration definition information.
-
Acquired information containing duplicated host names is discarded and the IM configuration tree appears grayed on the IM Configuration page.
-
If the acquired information differs from the information in the IM Configuration Management database, the affected host is represented by an error-status icon in the tree display area of the IM Configuration page.
-
If the configuration definition information held by JP1/Base on the manager running IM Configuration Management has been deleted, the following message appears: IM configuration does not exist. Do you want to reflect to the IM configuration maintained in server?
Click the Yes button to erase the deleted information from the IM Configuration Management database. Click the No button to keep the deleted information. This will make the system hierarchy appear grayed on the IM Configuration page.
-
In an agent configuration, if the system hierarchy appears grayed in the tree display area of the IM Configuration page, check and, if necessary, revise the configuration definition information (agent configuration), and then apply the agent configuration. For details about how to apply the agent configuration, see 3.2.4(3) Applying a system hierarchy to a system managed by IM Configuration Management in the JP1/Integrated Management 3 - Manager Configuration Guide.
When IM Configuration Management starts, configuration definition information is acquired automatically so that the information held by JP1/Base on the manager running IM Configuration Management can be checked for consistency with the definitions in the IM Configuration Management database.