17.2.8 Troubleshooting problems related to alarm definition
- Organization of this subsection
(1) The program defined to be executed as an action does not work properly
Possible causes and solutions:
-
The machine's login environment does not match the execution environment for the program defined to be executed as an action.
If the login environment does not match the execution environment for the program defined to be executed as an action, execution of the program might be not be possible. Determine whether the defined program can be executed as a Performance Management action. The following table lists the execution environment for a program defined to be executed as a Performance Management action.
Table 17‒4: Execution environment when a program is executed as a Performance Management action Execution environment
Windows
UNIX
Account
System account
root user permission
Environment variables
System environment variables when a Performance Management program service starts
root user environment variables when Performance Management starts
Current directory
Folder of the Action Handler service
Directory of the Action Handler service
Shell at startup
(Not applicable)
Login shell with root user permission
-
You do not have permissions to execute the defined program.
When the following programs are defined as Performance Management actions, execution of the program might not be possible depending on the restrictions of the execution permissions:
-
Programs in an NFS mount directory
-
Programs for viewing or updating files in an NFS mount directory
Confirm whether the defined program can be executed as a Performance Management action. For details on the execution environment when a program is executed as a Performance Management action, see Table 17-4 Execution environment when a program is executed as a Performance Management action.
-
-
PFM - Manager or the Action Handler service of PFM - Agent or PFM - RM of the destination host for performing the action has not started.
If the PFM - Manager or the Action Handler service of PFM - Agent or PFM - RM of the destination host for performing the action is stopped, the action cannot be performed. To perform the action, start PFM - Manager and the Action Handler service of PFM - Agent or PFM - RM of the destination host for performing the action.
(2) No alarm event is displayed
Possible causes and solutions:
-
PFM - Manager has not started.
When PFM - Manager is stopped, alarm events from PFM - Agent or PFM - RM might not be issued correctly. To monitor alarm events, start PFM - Manager.
(3) Although the threshold value for an alarm is exceeded, the color of the alarm icon remains green in the Alarm Status window in the Agents tree
Possible causes and solutions:
-
An alarm table that uses multi-byte characters is bound in an environment where the character encodings of the LANG environment variable for the PFM - Manager host, PFM - Agent host, and PFM - RM host do not match.
In such cases, an alarm that uses multi-byte characters is not evaluated normally. Match the character encoding of the LANG environment variable for the PFM - Manager host, PFM - Agent host, and PFM - RM host before operation. For LANG environment variable settings, check the common message logs and check which character encoding is output for the most recent service activation message.
Note that when the PFM - Manager host is using an English environment and when the character encoding is changed while the current settings apply, the characters in the existing alarm definition are garbled and cannot be deleted. Therefore, perform the following:
-
If alarm tables that use multi-byte characters in the alarm definition are necessary, export all the alarm tables from PFM - Web Console.
Note that you cannot use the jpctool alarm export command to export alarm tables.
-
Delete all alarm tables that use multi-byte characters in the alarm definition.
-
Stop PFM - Manager.
-
Change the character encoding of the LANG environment variable for the PFM - Manager host.
-
Start PFM - Manager.
-
If you exported alarm tables in step 1, use PFM - Web Console or the jpctool alarm import command to import alarm tables.
-
For notes on environments that have several character encodings, see the chapter describing Performance Management functionality in the JP1/Performance Management Planning and Configuration Guide.
(4) Many alarms are generated when an alarm table is deleted
If you delete an alarm table that is bound to an agent, the alarm status always changes to normal. The following table describes the relationship between alarm status changes and whether alarm events are issued.
|
# |
Alarm status |
Whether an event is issued |
|
|---|---|---|---|
|
Before an alarm table is deleted |
After an alarm table is deleted |
||
|
1 |
Abnormal |
Normal |
An alarm event is issued. |
|
2 |
Warning |
Normal |
An alarm event is issued. |
|
3 |
Normal |
Normal |
An alarm event is not issued. |
When you delete an alarm table, if the status of any of the alarms contained in the alarm table is abnormal or warning, the alarm status of the agent changes from abnormal or warning to normal. When that occurs, an alarm event is issued.
If you delete an alarm table that is bound to multiple agents, many alarm events are generated, possibly exceeding the peak capability temporarily.
You can check whether the peak capability is exceeded by checking whether the following message is output to the common log.
KAVE00422-W The number of events waiting to be processed reached the limit.
If the KAVE00429-E or KAVE00345-E message is output to the common log in addition to the above message, the Action Handler service has failed to delete action definitions. However, in this case, the alarms that trigger actions are already deleted and any action that has failed to be deleted will not be executed. The action information held by the Action Handler service is restored when the Action Handler service restarts.
(5) After changing the port number of PFM - Manager during operation, no alarm events are displayed
With PFM - Manager version 11-50 or later, if, after you change the port number setting specified for the Master Manager or Correlator for which the port number has been fixed, you do not restart the PFM services running on the agent host on which PFM - Base version 11-50 or later is installed, alarm events are not displayed. In this case, you need to restart the PFM services on which PFM - Base version 11-50 or later is installed.
For details about how to change the port number setting, see the section describing how to change the port number setting in the JP1/Performance Management Planning and Configuration Guide.