6.2.1 Hierarchical configurations managed by IM Configuration Management
Using IM Configuration Management, you can define the host relationships and manage the JP1/IM system configuration as a hierarchy.
Defining the system hierarchy in IM Configuration Management allows you to perform the following operations in JP1/IM:
-
Forward JP1 events to a higher-level host
-
Execute commands from JP1/IM - View
-
Execute automated actions from JP1/IM
-
Collect and distribute definition information
For the hosts added to the system hierarchy, you are also allowed to manage the JP1/Base profiles and the profiles of the remotely monitored hosts from IM Configuration Management.
The figure below shows an example of defining a system hierarchy using IM Configuration Management.
|
Two types of 3-tier system configurations can be defined in IM Configuration Management:
-
A configuration where the agents are centrally managed by an integrated manager
-
A configuration where the agents are managed by base managers in separate domains
For remotely monitored hosts, a hierarchical configuration cannot be defined. When you centrally manage agents, use the integrated manager to operate on the agents and add agents under the integrated manager. When you manage agents by base managers, operate on each base manager and add the agents for the domain to under each base manager.
- Organization of this subsection
(1) Centralized management by an integrated manager
In a configuration where the agents in the JP1/IM system are centrally managed by an integrated manager, agent information is collected by relay managers placed in the middle tier.
The relay managers do not provide the IM Configuration Management functionality.
|
The table below describes the operations that can be performed from the integrated manager on the hosts in the above configuration example.
Target host |
Operation |
||||
---|---|---|---|---|---|
View the system configuration |
Change the system configuration |
View host information |
View and change profile information |
||
Integrated manager (jp1-sv1) |
Y |
Y |
Y |
Y |
|
Relay manager (jp1-sv2 and jp1-sv3) |
Y |
Y |
Y |
Y |
|
Agent |
Under the integrated manager (jp1-bs1 and jp1-bs2) |
Y |
Y |
Y |
Y |
Under relay managers (jp1-bs3, jp1-bs4, and jp1-bs5) |
Y |
Y |
Y |
Y |
- Legend:
-
Y: Can be performed.
(2) Agent management in separate domains
In a configuration where the agents are managed by base managers in separate domains, base managers are placed in the middle tier.
The base managers provide the IM Configuration Management functionality.
|
The table below describes the operations that can be performed from the integrated manager on the hosts in the above configuration example.
Target host |
Operation |
||||
---|---|---|---|---|---|
View the system configuration |
Change the system configuration |
View host information |
View and change profile information |
||
Integrated manager (jp1-sv1) |
Y |
Y |
Y |
Y |
|
Base manager (jp1-sv2 and jp1-sv3) |
Y |
Y |
Y |
Y |
|
Agent |
Under the integrated manager (jp1-bs1 and jp1-bs2) |
Y |
Y |
Y |
Y |
Under base managers (jp1-bs3, jp1-bs4, and jp1-bs5) |
Y |
N |
N |
N |
- Legend:
-
Y: Can be performed.
N: Cannot be performed.
The table below describes the operations that can be performed from a base manager on the hosts in the configuration example shown in Figure 6-8 System hierarchy example (agent management in separate domains).
Target host |
Operation |
||||
---|---|---|---|---|---|
View the system configuration |
Change the system configuration |
View host information |
View and change profile information |
||
Integrated manager (JP1-sv1) |
Y# |
N |
N |
N |
|
Base manager (local host) |
Y |
Y |
Y |
Y |
|
Base manager (remote host) |
N |
N |
N |
N |
|
Agent |
Under the integrated manager (jp1-bs1 and jp1-bs2) |
N |
N |
N |
N |
Under base managers (local host) |
Y |
Y |
Y |
Y |
|
Under base managers (remote host) |
N |
N |
N |
N |
- Legend:
-
Y: Can be performed.
N: Cannot be performed.
- #
-
Viewable only when the integrated manager is a level above the base managers.
(3) Management of remotely monitored hosts by an integrated manager
In a configuration where the remotely monitored hosts are centrally managed by an integrated manager, the remotely monitored hosts are placed directly under the integrated manager.
The table below describes the operations that can be performed from the integrated manager on the hosts in the configuration example shown in Figure 6-7 System hierarchy example (centralized management by an integrated manager).
Target host |
Operation |
||||
---|---|---|---|---|---|
View the system configuration |
Change the system configuration |
View host information |
View and change profile information |
||
Remotely monitored hosts |
Under the integrated manager (jp1-rm1) |
Y |
Y |
Y |
Y |
Under base managers |
N |
N |
N |
N |
|
Under relay managers (jp1-rm2) |
N |
N |
N |
N |
- Legend:
-
Y: Can be performed.
N: Cannot be performed.
(4) Management of remotely monitored hosts in separate domains
In a configuration where the remotely monitored hosts are managed by base managers, the remotely monitored hosts in each domain are placed directly under each base manager.
The following table describes the operations that can be performed from a base manager on the hosts in the configuration example shown in Figure 6-8 System hierarchy example (agent management in separate domains).
Target host |
Operation |
||||
---|---|---|---|---|---|
View the system configuration |
Change the system configuration |
View host information |
View and change profile information |
||
Remotely monitored hosts |
Under the integrated manager (jp1-rm1) |
N |
N |
N |
N |
Under the base manager (local host) (jp1-rm2) |
Y |
Y |
Y |
Y |
|
Under the base manager (remote host) |
N |
N |
N |
N |
|
Under relay managers |
N |
N |
N |
N |
- Legend:
-
Y: Can be performed.
N: Cannot be performed.