D.4 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.

Table D‒6: Limits for JP1/IM - Manager
Item	Limit
Number of instances of JP1/IM - IM Configuration Management - View that can connect to one JP1/IM - Manager	64
Number of hosts one JP1/IM - Manager can manage (total number of the JP1/IM - Manager hosts, the JP1/Base instances that can be placed directly below JP1/IM - Manager, and the remotely monitored hosts in the system configuration, regardless of IPv4 hosts, IPv6 hosts, or IPv4/IPv6 hosts)	2,500
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 2,499 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 monitored remotely^#1	1,024
Maximum number of log file trap processes that can be managed by one host	100^#2
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
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	2,500
Number of tiers for business groups	1 level
Number of tiers for monitoring groups	9 levels

#1: This is the total of the number of log files monitored by remote log file traps and the number of servers monitored by remote event log traps.

#2: If 101 or more log trap files are active, the message KNAN22411-W is output and the first 100 are collected.

The following table describes the limits that apply to JP1/IM - View.

Table D‒7: Limits for JP1/IM - View
Item	Limit
Number of instances of JP1/IM - View that can be started within a single session (per process^#1)	3^#2
Number of definitions that can be specified for a manager host in the non-encryption communication host configuration file for encrypted communication	1,024 definitions
Maximum length (in characters) of a manager host name in the non-encryption communication host configuration file for encrypted communication	255 characters

#1: The following viewers and windows are started for each process:

#2: The larger the number of active instances of JP1/IM - View, the greater the memory and disk space requirements.