1.8.5 Executing actions
-
Actions cannot be executed correctly if the PFM - Manager for the connection destination or Action Handler services stop. Start the PFM - Manager for the connection destination and Action Handler services when executing actions.
-
You can configure an action that is set on an alarm so that the action is executed only when the alarm event is caused by Performance Management while the action is not executed when the alarm event is caused by a user operation. This function is called the function for suppressing the execution of remote actions when an alarm is returned to normal by user operation.
In a new installation of PFM - Manager, the function for suppressing the execution of remote actions when an alarm is returned to normal by user operation is enabled. In an upgraded installation, the function for suppressing the execution of remote actions when an alarm is returned to normal by user operation is disabled. To enable or disable the function for suppressing the execution of remote actions when an alarm is returned to normal by user operation, edit the Suppress Action Execution label in the startup information file (jpccomm.ini).
The executability of actions depends on whether the alarm event is caused by Performance Management operation or user operation and whether the function for suppressing the execution of remote actions when an alarm is returned to normal by user operation is enabled or disabled.
- If the function for suppressing the execution of remote actions when an alarm is returned to normal by user operation is enabled:
Actions are executed when Performance Management operation causes the alarm event. No actions are executed when user operation causes the alarm event. The following table describes the executability of actions for each cause of the alarm event. There is no difference between local actions and remote actions in terms of whether or not an action is executed.
Table 1‒7: The executability of actions for each cause of the alarm event (if the function for suppressing the execution of remote actions when an alarm is returned to normal by user operation is enabled) Cause of the alarm event
Executability of actions set on the alarm
Message text
Local actions
Remote actions
Performance Management operation
An alarm condition is evaluated. #
To be executed
To be executed
User-defined statement
The current time does not fall in the alarm evaluation time window.
"Alarm expired"
User operation
Stop the service of the agent.
Not to be executed
Not to be executed
"Alarm cleared"
Unbind an alarm table in the Agents tree.
Import alarms to overwrite alarm definitions in the Alarms tree.
Run the jpctool config sync or jpctool config alarmsync command, or apply alarm information.
Unset up monitoring for alarms bound with PFM - RM.
Clear the Activate check box for a bound alarm in the Alarms tree.
"Alarm deactivated"
Edit a bound alarm in the Alarms tree.
Delete some alarms from an alarm table in the Alarms tree.
"Alarm updated/deleted"
- #
-
For details about when alarm conditions are evaluated, see 6.3.5(2) Examples of alarm settings and generated alarms.
- Note:
-
If the function for suppressing the execution of remote actions when an alarm is returned to normal by user operation is enabled, do not set the following statements as alarm message text in alarm definitions. If you do not observe this, no action is executed upon successful recovery from the alarm state.
- "Alarm deactivated"
- "Alarm cleared"
- "Alarm updated/deleted"
- If the function for suppressing the execution of remote actions when an alarm is returned to normal by user operation is disabled:
Actions (local actions and remote actions) are executed when Performance Management operation causes the alarm event. On the other hand, when user operation causes the alarm event, local actions are not executed while remote actions are executed or not depending on the cause of the alarm event. The following table describes the executability of actions for each cause of the alarm event.
Table 1‒8: The executability of actions for each cause of the alarm event (if the function for suppressing the execution of remote actions when an alarm is returned to normal by user operation is disabled) Cause of the alarm event
Executability of actions set on the alarm
Message text
Local actions
Remote actions
Performance Management operation
An alarm condition is evaluated. #
To be executed
To be executed
User-defined statement
The current time does not fall in the alarm evaluation time window.
"Alarm expired"
User operation
Stop the service of the agent.
To be executed
To be executed
"Alarm cleared"
Unbind an alarm table in the Agents tree.
To be executed
Import alarms to overwrite alarm definitions in the Alarms tree.
-
When the Collector service is busy:
Actions after the import might be executed.
-
When the Collector service is not busy:
Not to be executed
Run the jpctool config sync or jpctool config alarmsync command, or apply alarm information.
To be executed
Unset up monitoring for alarms bound with PFM - RM.
To be executed
Clear the Activate check box for a bound alarm in the Alarms tree.
To be executed
"Alarm deactivated"
Edit a bound alarm in the Alarms tree.
-
When the Collector service is busy:
Actions after the edit might be executed.
-
When the Collector service is not busy:
Not to be executed
Delete some alarms from an alarm table in the Alarms tree.
To be executed
"Alarm updated/deleted"
- #
-
For details about when alarm conditions are evaluated, see 6.3.5(2) Examples of alarm settings and generated alarms.