D.3 Limits when using IM Configuration Management
The tables below describe the limits that apply to JP1/IM - Manager and IM Configuration Management - View when using IM Configuration Management.
- Organization of this subsection
(1) JP1/IM - Manager limits
The following table describes the limits that apply to JP1/IM - Manager.
Item |
Limit |
---|---|
Number of instances of JP1/IM - IM Configuration Management - View that can connect to one JP1/IM - Manager |
64#1 |
Number of hosts one JP1/IM - Manager can manage (total number of JP1/Base hosts and remotely monitored hosts that can be placed directly below JP1/IM - Manager, regardless of IPv4 hosts, IPv6 hosts, or IPv4/IPv6 hosts) |
1,024 |
Number of hosts that can be monitored from one instance of IM Configuration Management (regardless of IPv4 hosts, IPv6 hosts, or IPv4/IPv6 hosts) |
10,000 1,024 agents can be configured directly under IM Configuration Management |
Number of tiers in the system hierarchy (IM configuration) that can be monitored by one IM Configuration Management instance |
3 levels (assuming the integrated manager as being in the first level) |
Maximum number of files that can be remotely monitored#2 |
1,024 |
Maximum number of log file trap processes that can be managed by one host |
100#3 |
Number of standby hosts that can be set up on one logical host |
4 |
Number of IP addresses that can be displayed for one host |
8 |
Number of alias host names that can be displayed for one host |
4 |
Total number of business groups and monitoring groups |
100 |
Maximum number of hosts that can be set for one business group or one monitoring group |
1,024 |
Number of tiers for business groups |
1 level |
Number of tiers for monitoring groups |
9 levels |
(2) JP1/IM - View limits
The following table describes the limits that apply to JP1/IM - View.
Item |
Limit |
---|---|
Number of concurrent logins from one instance of JP1/IM - View |
3# |