Setting up and starting service
|
-
A Performance Management program service does not start.
-
A service takes a long time to start once startup is requested.
-
Immediately after a Performance Management program service is stopped, another program starts service and communication is
not performed properly.
-
After the message The disk capacity is insufficient is output, the Master Store service, Agent Store service, or Remote Monitor Store service stops.
-
The Correlator service takes a long time to start after PFM - Manager restarts.
-
The Agent Collector service or Remote Monitor Collector service does not start.
-
Multiple agents that start simultaneously take a long time to recover from stand-alone mode.
|
17.2.1
|
Connecting to agents
|
An error message, such as Cannot connect to an agent is output to PFM - Web Console.
|
17.2.3
|
Logging on to PFM - Web Console
|
|
17.2.4
|
Executing commands
|
-
When the jpctool service list command is executed, the names of services not operating are output.
-
When the jpctool db dump command is executed, the output data does not match the data in the specified Store database.
-
Deleted agents are displayed.
|
17.2.5
|
Agent management
|
|
17.2.6
|
Report definition
|
|
17.2.7
|
Alarm definition
|
-
The program defined to be executed by an action does not work properly.
-
No alarm event is displayed.
-
Although the threshold value for an alarm is exceeded, the color of the alarm icon that is displayed in the Display Alarm
Status window in the Agents tree remains green.
-
Many alarms are generated when an alarm table is deleted.
|
17.2.8
|
Collecting and managing performance data
|
-
Even if the data storage time is set for a shorter period, the size of the Store database for the Agent Store service and
the Remote Monitor Store service does not become smaller.
-
The KAVE00128-E message (Illegal data was detected in the Store database) or KAVE00163-E message (The database type is illegal) is output to the common message log and startup of the Store service fails.
-
Collection of performance data is skipped and the KAVE00213-W message is output.
|
17.2.9
|
Monitoring suspension function
|
|
17.2.10
|
Linking with other programs
|
-
A server request error occurs and no connection is established when linking with an ODBC-compliant program.
-
A status change event is not displayed in the event browser when linking with NNM.
-
No symbol appears in ovw when linking with NNM.
-
JP1 events are not reported when linking with JP1/IM.
-
Monitored PFM - Agent or PFM - RM is not displayed in the monitoring tree window when linking with a monitored object function
of JP1/IM.
-
The display color of the monitored object does not change when linking with a monitored object function of JP1/IM.
|
17.2.11
|
Multiple monitoring
|
|
17.3.1
|
|
17.3.2
|
|
17.3.3
|
|
17.3.4
|
|
17.3.5
|
-
Multiple actions are executed in one event.
-
No events are sent to the secondary Manager.
-
Events are sent to the secondary Manager but actions are not executed.
-
Events are sent to both the primary Manager and the secondary Manager but actions are executed only on the primary Manager.
-
When the primary Manager is down, no action is executed in response to an event notification.
|
17.3.6
|
|
17.3.7
|
|
17.3.8
|
|
17.3.9
|