D.3 Limits when using the Central Scope
The following tables describe the limits that apply to JP1/IM - Manager and JP1/IM - View when using the Central Scope.
- 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 - View that can connect to one JP1/IM - Manager |
64 |
Number of hosts that can be monitored by one instance of the Central Scope |
5,000 This value includes all hosts being monitored from the Central Scope, such as JP1/AJS - Agent hosts and hosts being monitored using the SNMP trap converter of JP1/Base, in addition to hosts configured under JP1/IM - Manager. |
Number of Monitoring Tree windows that can be managed by JP1/IM - Manager |
1 |
Longest monitoring node name that can be set in a configuration file for a monitoring tree |
255 bytes#1 |
Longest basic information for a monitoring node that can be set in a configuration file for a monitoring tree |
Attribute value: 1,023 bytes#1, #2 |
Longest status change condition name that can be set in a configuration file for a monitoring tree |
63 bytes |
Longest value specifiable for individual conditions in a configuration file for a monitoring tree |
Attribute value: 1,023 bytes#1, #2 |
File size of a guide information file |
1 MB |
File size of a guide-message file |
1 MB |
(2) JP1/IM - View limits
The following table describes the limits that apply to 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 monitoring nodes that can be monitored in a Monitoring Tree window |
50,000 |
Length of a monitoring node name |
255 bytes#3 |
Number of basic information items that can be set for one monitoring node |
5 |
Number of characters that can be entered in a basic information field |
Attribute name: 32 bytes#3 Attribute value: 1,023 bytes#3, #4 |
Number of status change conditions that can be set for one monitoring node |
8 |
Length of a status change condition name |
63 bytes |
Number of individual conditions that can be set in one status change condition for monitoring objects |
5 |
Percentage value that can be set as a comparison condition in one status change condition for monitoring groups |
100 |
Maximum count that can be set as a comparison condition in one status change condition for monitoring groups |
50,000 |
Number of characters that can be entered in an individual condition field |
Attribute name: 32 bytes#3 Attribute value: 1,023 bytes#3, #4 |
Number of JP1 events that can be issued by one monitoring node |
7 |
Number of status change event logs that can be kept by each monitoring node |
100 |
File name length of a background image that can be set in a monitoring group |
260 bytes#3 |
File name length of an image file used as an icon for a monitoring node (for the normal and expanded status, and Visual Icon) |
260 bytes#3 |
Number of common conditions that can be added by the user |
191 |
Length of the common condition name set in the Common Condition Detailed Settings window |
63 bytes#3 |
Number of characters that can be entered in a Common condition details field (other than the Extended attribute area) of the Common Condition Detailed Settings window |
1,023 bytes#3 |
Number of characters that can be entered in a Common condition details field (Extended attribute area) of the Common Condition Detailed Settings window |
Attribute name: 32 bytes#3 Attribute value: 1,023 bytes#3, #4 |
Length of the file name of the background image in a Visual Monitoring window |
260 bytes#3 |
Number of monitoring nodes that can be placed in one Visual Monitoring window |
128 |
Number of Visual Monitoring windows that users can create |
64 |
Length of the name set for a Visual Monitoring window |
63 bytes#3 |
Length of a comment about a Visual Monitoring window |
80 bytes#3 |
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 |