H.5 Connectivity with previous versions of JP1/Base
- Organization of this subsection
(1) Restrictions on event searches in JP1/Base 09-00 to 12-10 from JP1/IM - View 12-00
There are no restrictions on event searches from JP1/IM - View 12-00 to JP1/Base 09-00 or 12-10.
(2) Restrictions on managing JP1/Base 09-00 to 12-10 from JP1/IM - Manager 12-50 (when using IM Configuration Management)
|
JP1/Base version#1 |
Restrictions#2 |
|||
|---|---|---|---|---|
|
1 |
2 |
3 to 6 |
7 |
|
|
09-00 |
Y |
Y |
Y |
Y |
|
09-10 to 10-50 |
-- |
Y |
Y |
Y |
|
11-00 to 11-10 |
-- |
-- |
Y |
Y |
|
11-50 |
-- |
-- |
Y |
Y |
|
12-00 |
-- |
-- |
-- |
Y |
|
12-10 |
-- |
-- |
-- |
-- |
- Legend:
-
Y: Applicable
--: Not applicable
#1: Refers to the version of JP1/Base on the search target host.
#2: The restriction numbers correspond to the numbers in the following table.
|
No. |
Details |
|---|---|
|
1 |
You cannot perform the following operations for log file traps on the monitored hosts:
|
|
2 |
Event IDs and log file trap names cannot be set in the event log trap action definitions on monitored hosts. |
|
3 |
When a managed host is a site manager, IM configuration cannot be applied to the agents under the site manager by using the differing-components application method. |
|
4 |
No notification that agent settings for log file trap information might have been changed is sent while the Display/Edit Profiles window is being used. |
|
5 |
The enable/disable setting for starting processes automatically when the log file trap service is started cannot be changed in the Display/Edit Profiles window. |
|
6 |
Log file trap information for non-cluster operation cannot be applied by file transmission in the Display/Edit Profiles window. |
|
7 |
An attempt to execute a command fails due to suggestion activation criteria and response actions specified in a suggestion definition file. |
(3) Restrictions when the manager host uses JP1/IM - Manager version 12-50 and JP1/Base version 11-00 to 12-10 (when using IM Configuration Management)
|
JP1/Base version |
Restrictions# |
|
|---|---|---|
|
1 to 3 |
4 |
|
|
11-00 |
Y |
Y |
|
11-10 |
-- |
Y |
|
11-50 |
-- |
Y |
|
12-00 to 12-10 |
-- |
-- |
Legend: Y: Applicable --: Not applicable
#: The restriction numbers correspond to the numbers in the following table.
|
No. |
Details |
|---|---|
|
1 |
In remote-monitoring event log traps, the retry count for event log collection cannot be adjusted. |
|
2 |
In remote-monitoring event log traps, the retry interval and the monitoring interval for event log collection cannot be adjusted individually. |
|
3 |
When Apply Agent Configuration is run in the Edit Agent Configuration window, the differing-components application method cannot be used. |
|
4 |
You cannot set more than 1,025 agent hosts directly under JP1/IM - Manager in the agent configuration. |
(4) Connectivity for monitoring JP1/Base on agent hosts from JP1/IM - Manager (with the Central Console functionality)
|
JP1/Base (agent) version#1 |
JP1/IM - Manager (JP1/IM - Console) version#1 |
|||||
|---|---|---|---|---|---|---|
|
06-00 to 06-71 |
07-00 to 07-51 |
08-00 to 08-50 |
09-00 to 09-50 |
10-00 to 10-50 |
11-00 to 12-50 |
|
|
06-00 to 06-71 |
Y |
Y |
Y |
E |
E |
E |
|
07-00 to 07-51 |
Y |
Y |
Y |
Y |
E |
E |
|
08-00 to 08-50 |
E#2 |
E#2 |
Y |
Y |
Y |
E |
|
09-00 to 09-50 |
E#2 |
E#2 |
Y |
Y |
Y |
Y |
|
10-00 to 10-50 |
E#2 |
E#2 |
Y |
Y |
Y |
Y |
|
11-00 to 12-50 |
E#2 |
E#2 |
E |
Y |
Y |
Y |
- Legend:
-
Y: Supported
E: Only event forwarding from JP1/Base to JP1/IM - Manager is supported.
- #1
-
Functions provided by both JP1/Base and JP1/IM - Manager are supported. For details about connectivity and compatibility between JP1/IM - Manager (JP1/IM - Console) and JP1/Base, see the documentation for the applicable product version.
- #2
-
JP1/IM - Manager and JP1/IM - Console cannot process normally JP1 events issued in a UTF-8 locale environment. A compatible encoding mode must be set on the event-forwarding source JP1/Base.