17.3.6 Troubleshooting related to events
- Organization of this subsection
(1) Multiple actions are executed in one event
A possible cause of the problem is that the remote action control function of the agent that reported the event is in all execution mode.
If the remote action control function is in all execution mode, remote actions will be executed twice. Change the execution mode to fit operational needs. For details about the remote action control function, see 11.3.5 Controlling remote actions.
(2) No events are sent to the secondary Manager
Possible causes and solutions:
-
The secondary Manager is not registered in the setting of PFM - Manager for the connection destination.
Make sure that the host name of the secondary Manager is set as PFM - Manager for the connection destination. If the host name has not been set, set it. For details about setting up the primary Manager and the secondary Manager, see 11.3 Setting up multiple monitoring.
-
There is an error in the setting of PFM - Manager for the connection destination.
Make sure that there are no spelling errors, host specification errors, or other errors in the host name set as PFM - Manager for the connection destination. For details about setting up the primary Manager and the secondary Manager, see 11.3 Setting up multiple monitoring.
(3) Events are sent to the secondary Manager but actions are not executed
A possible cause of the problem is that the remote action control function of the agent that reported the event is in one-side execution mode or primary execution mode.
If the remote action control function is in primary execution mode, only remote actions of events reported to the primary Manager are executed. If the remote action control function is in one-side execution mode, only remote actions of the event that is first reported successfully are executed. Change the execution mode according to the operation. For details about the remote action control function, see 11.3.5 Controlling remote actions.
(4) Events are sent to both the primary Manager and the secondary Manager but actions are executed only on the primary Manager
A possible cause of the problem is that the remote action control function of the agent that reported the event is in one-side execution mode or primary execution mode.
If the remote action control function is in primary execution mode, only remote actions of events reported to the primary Manager are executed. If the remote action control function is in one-side execution mode, only remote actions of the event that is first reported successfully are executed. Change the execution mode to fit operational needs. For details about the remote action control function, see 11.3.5 Controlling remote actions.
(5) When the primary Manager is down, no action is executed from event notification
Possible causes and solutions:
-
The remote action control function of the agent that reported the event is in primary execution mode.
If the remote action control function is in primary execution mode, only remote actions of events reported to the primary Manager are executed. Therefore, while the primary Manager is not running, no remote actions will be executed.
Change the execution mode of the remote action control function to all execution mode or one-side execution mode according to the operation, or switch the primary Manager and the secondary Manager.
For details about the remote action control function, see 11.3.5 Controlling remote actions.
For details about the procedure for switching the primary Manager and the secondary Manager, see 11.7 Switching the primary Manager and the secondary Manager.
-
There is an error which set alarm actions in the action handler.
If <host-name-of-primary-manager><Action Handler> is set as the action handler in which alarm actions are set, actions of events reported to the secondary Manager are also executed on the primary Manager. Therefore, while the primary Manager is not running, no remote actions will be executed.
When you set Manager for the action handler, actions are executed by the action handler of PFM - Manager receiving events.
You can set Manager for the action handler from PFM - Web Console or by executing the jpctool alarm import command.
For details, see 6.4 Setting alarms using the Web browser (Alarms tree) or the chapter that describes the jpctool alarm import command in the manual Job Management Partner 1/Performance Management Reference.