3.15.8 Polling monitoring of JP1/IM agent control base
JP1/IM agent management base detects connections and disconnections from JP1/IM agent control base and issues JP1 events.
- Organization of this subsection
(1) Function Overview
JP1/IM agent control base's polling monitoring detects that JP1/IM agent control base is connected to and disconnected from JP1/IM agent management base and issues a JP1 event. JP1/IM agent control base starts and connects to JP1/IM agent management base on a regular basis. Therefore, JP1/IM agent management base determines that it has been disconnected for a period of time if there is no connection from JP1/IM agent control base. You can view published JP1 events by viewing the list of integrated operation viewer events by selecting JP1/IM agent control base SID's IM management node.
JP1/IM agent management base and JP1/IM agent control base processes are composed of the following processes. For this feature, JP1/IM agent management base refers to imbase process, and JP1/IM agent control base refers to imagent process. For details about the roles of individual processes, see 3.15.7(1) Common capabilities.
- JP1/IM agent management base
-
imbase
-
imbaseproxy
- JP1/IM agent control base
-
imagent
-
imagentproxy
-
imagentaction
(2) Polling monitoring for JP1/IM agent control base
JP1/IM agent control base starts and connects to JP1/IM agent management base periodically. JP1/IM agent management base detects that a JP1/IM agent control base has been disconnected and issues a JP1 event-if it has not been connected to it for a period of time. When JP1/IM agent control base is started, or when JP1/IM agent control base connects to JP1/IM agent management base after disconnection, it detects the connection and issues a JP1 event. If JP1/IM agent control base is stopped normally, it is disconnected from JP1/IM agent management base, so it issues a JP1 event.
The following table shows JP1 events that are issued by polling monitoring in JP1/IM agent control base and the timing at which they are issued. For details about JP1 events, see 3.2.3 Lists of JP1 events output by JP1/IM - Agent in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference. A JP1 event is issued only when the connected/disconnected status is changed.
|
Event ID |
Severity |
Message |
|---|---|---|
|
00007620 |
Error |
KNBC20043-E |
|
00007621 |
Information |
KNBC20044-I |
|
00007622 |
Information |
KNBC20045-I |
The following is a use case for checking JP1 events that are issued by polling monitoring in JP1/IM agent control base.
|
Use case |
Event ID |
|---|---|
|
Checking when JP1/IM agent control base error is detected # |
00007620 |
|
Checking when JP1/IM agent control base is starting up after a successful shutdown and connecting to JP1/IM agent management base for the first time |
00007621 |
|
Checking when JP1/IM agent management base connects to JP1/IM agent control base for the first time after error is detected# in JP1/IM agent management base |
|
|
Checking when JP1/IM agent management base connects to JP1/IM agent control base for the first time after restarting your JP1/IM agent management base |
|
|
Checking when JP1/IM agent control base connects to JP1/IM agent management base for the first time after obtaining licensing information after JP1/IM - Agent install/setup |
|
|
Checking when JP1/IM agent control base is stopped normally |
00007622 |
#: If JP1/IM agent control base is not connected to JP1/IM agent management base for 60 seconds (can be specified on polling_monitoring_interval in imbase configuration file) or more in the following cases, an error is detected.
-
No networking between JP1/IM agent management base and JP1/IM agent control base
-
JP1/IM agent control base hang-up or abnormal shutdown
The following is a use case in which JP1 events issued by polling monitoring of JP1/IM agent control base cannot be checked.
|
Item number |
Use case |
|---|---|
|
1 |
After JP1/IM agent control base has stopped abnormally, JP1/IM agent control base starts and connects to JP1/IM agent management base prior to JP1/IM agent management base error detection# |
|
2 |
JP1/IM agent control base error detection# while JP1/IM agent management base is stopped |
|
3 |
Successful shutdown of JP1/IM agent control base while JP1/IM agent management base is down |
#: If JP1/IM agent control base is not connected to JP1/IM agent management base for 60 seconds (can be specified on polling_monitoring_interval in imbase configuration file) or more in the following cases, an error is detected.
-
No networking between JP1/IM agent management base and JP1/IM agent control base
-
JP1/IM agent control base hang-up or abnormal shutdown
Even if the JP1/IM agent control base and the JP1/IM agent management base cannot connect due to a temporary network error, if the JP1/IM agent control base reconnects before the JP1/IM agent management base detects the disconnection, the JP1/IM agent management base will not detect the disconnection.
The JP1/IM agent control base and the JP1/IM agent management base perform the following processes periodically:
-
The JP1/IM agent control base connects to the JP1/IM agent management base once every 10 seconds#1.
-
The JP1/IM agent management base checks whether there has been no connection from the JP1/IM agent control base for 60 seconds#2 or more, at intervals of 60 seconds#2.
In the process where the JP1/IM agent management base checks for the absence of JP1/IM agent control base that has not been updated for the value set in the imbase configuration file's polling_monitoring_interval (unit: seconds), the system behaves as follows when an anomaly occurs:
-
If the issuance of a JP1 event fails during the check process, it outputs the message "KNBC20038-E" and retries the check at the next interval.
-
If the check process does not complete within (value of polling_monitoring_interval - 5) seconds, it interrupts the process, logs the message "KNBC20048-E", and treats it as a disconnection.
-
- #1
-
10 seconds is the default value. It is configured in the imbase configuration file under agent_polling_interval.
- #2
-
60 seconds is the default value. It is configured in the imbase configuration file under polling_monitoring_interval.
The following describes the retries for communication between JP1/IM agent management base and JP1/IM agent control base.
-
JP1/IM agent control base does not retry because it periodically connects to JP1/IM agent management base. If the connection fails, connect again at the next regular connection.
-
The activation notification does not retry. If notification fails, notification is notified when connection is made at the next regular connection.
-
A stop notification does not retry.
- Important
-
-
If JP1/IM agent management base goes down, the connected JP1/IM agent control base is disconnected but not detected. After JP1/IM agent management base starts, JP1/IM agent control base connects and issues a JP1 event with an event ID of 00007621.
-
If JP1/IM agent control base stops abnormally and starts JP1/IM agent control base prior to JP1/IM agent management base detection, no JP1 event with an event ID of 00007620 is issued. If you want to detect such a case (a case that starts up quickly after JP1/IM agent control base has stopped abnormally), please see the description of Setup of integrated agent process alive monitoring in the JP1/Integrated Management 3 - Manager Configuration Guide to monitor imagent process. This setting notifies the integrated manager through JP1/IM agent control base, so you are not notified when JP1/IM agent control base has stopped abnormally, but you are notified when JP1/IM agent control base has started.
-
JP1/IM agent control base's polling monitoring is started after you get the licensing information. (polling monitoring is not enforced while using initial secret.) For licensing details, see 3.15.7(1)(b) Authentication with initial secret.
-
Depending on the number of JP1/IM - Agents monitored by JP1/IM - Manager, it may be necessary to modify the settings of polling_monitoring_interval and agent_polling_interval in the imbase configuration file.
For details, see the description of polling_monitoring_interval and agent_polling_interval in imbase configuration file (jpc_imbase.json) in Chapter 2. Definition Files in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.
-
(3) Health check function
Polling monitoring with the health check function is supported only for imagent processing of JP1/IM agent control base.
For processes other than imagent process of JP1/IM agent control base, use the alive monitoring of the process by the user's operation.
For details on how to monitor the alive of a process in the user's operation, see the description of Setup of integrated agent process alive monitoring in the JP1/Integrated Management 3 - Manager Configuration Guide.
- Important
-
If JP1/IM agent base process-down occurs, JP1/IM - Agent cannot communicate with JP1/IM - Manager, so no JP1 event is issued for integrated agent host. By starting JP1/IM agent base process, communication will be retried while it is stopped. However, log trapper may discard JP1 events if JP1/IM agent base process has been stopped for a long time#.
For details, see 3.15.3(9)(c) Buffer function for log data to be sent (buffer).
- #
-
How long Fluentd defaults settings to register about 270000 JP1 events