6.9.4 Notes about alarm application status
This subsection provides notes about alarm application status.
- Organization of this subsection
(1) If PFM - Manager version 11-00 or later was installed by overwriting a PFM - Manager version earlier than 11-00
The first time the monitoring manager service is started after the overwrite installation, all application statuses are shown as Successful regardless of whether alarm information has been applied.
(2) If the PFM - Manager services are stopped
If a PFM - Manager service is stopped, the previous application status in effect before the service was stopped is restored the next time the service is started. This is because when a service stops, the applied data is output to a recording file for the alarm application state. When the service is restarted, data is imported from that file.
Note that the previous application status is not restored in the cases listed below. In these cases, execute the jpctool config sync command to synchronize the monitoring manager and the monitoring agent to apply the correct alarm information.
-
Output of data to the recording file for the alarm application state failed.
The KAVE00545-W message is output to the common message log and the applied data is discarded.
-
Data import from the recording file for the alarm application state failed.
The KAVE00544-W message is output to the common message log and the application status is treated as being Successful.
-
The monitoring manager service terminated abnormally.
The application status is treated as being Successful regardless of whether alarm information has been applied.
(3) If the recording file for the alarm application state has been deleted when the monitoring manager service starts
If the recording file for the alarm application state has been deleted when the monitoring manager service starts, all service application statuses are shown as being Successful. In this case, the KAVE00544-W message is output to the common message log.
(4) Scenarios where application status becomes Uncertain
The application status becomes Uncertain in the following cases:
-
The environment does not allow the target monitoring agent or service to send responses.
If the application has not been completed, the KAVE00348-W or KAVE00169-E message is output to the common message log. If this occurs, take one of the following corrective actions:
-
Execute the jpctool config alarmsync -target uncertain command.
-
Apply alarm information from the Alarm Application Status window.
-
Restart the service.
-
Bind or unbind the alarm table.
If the KAVE00348-W or KAVE00169-E message has not been issued, no corrective action is needed because alarm information has been applied.
-
-
An attempt to access the monitoring manager's database failed.
The KAVE00531-E message is output to the common message log. Take the corrective action provided in that message.
-
All alarm tables were unbound from a remote agent or a group agent that does not send responses.
Take one of the following corrective actions:
-
Execute the jpctool config alarmsync -target uncertain command.
-
Restart the remote agent.
-
(5) If the service is running but the application status is Inactive
If the service is running but the application status is Inactive, check for one of the problems listed below. If either of these problems exists, eliminate the cause of the problem, and then restart the service.
-
The firewall pass-through settings are invalid.
-
The target service is busy.
(6) If alarm information has been applied to remote agents or group agents
-
If alarm information is applied to a remote agent or a group agent and the source PFM - RM service is stopped, the alarm application status of all remote agents and group agents under that PFM - RM becomes Inactive.
-
If alarm information is applied to a remote agent or a group agent, the application processing is performed on all remote agents and group agents under the same PFM - RM.
(7) If failover occurs in a cluster system
When failover occurs in a cluster system, the alarm application status is inherited from the primary system to the secondary system. However, if either of the following occurs during failover processing, the alarm application status is not inherited to the secondary system:
-
The Master Manager service terminates abnormally.
-
Failover processing is not successful.
In such a case, all services' application status is shown as Successful. Execute the jpctool config sync command in the primary system environment.
(8) If the primary and secondary systems were swapped in a multiple-monitoring environment
If the primary and secondary systems were swapped by the jpcconf primmgr notify or jpcconf mgrhost define -shift command, all services' application status is shown as Successful.