17.2 Troubleshooting

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

• The specified Performance Management user name is not recognized during logon.

• Cannot establish a connection from PFM - Web Console to the View Server service.

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

• No agent is displayed in the Agents window of PFM - Web Console.

• The operating status of the server or agent is Unconfirmed or Not Supported.

17.2.6

Report definition

• There is a time period not indicated on the history report.

• A memory shortage can occur with the View Server service when a large number of reports are displayed simultaneously.

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

• The KAVJS6570-I message is output to the Monitoring Suspension Settings window.

• The KAVE06189-W message is output during command execution.

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

• When the jpctool config mgrimport command is executed, an error is output.

17.3.1

• The host name is not distributed to agents when the jpcconf primmgr notify command is executed.

17.3.2

• The host name is not distributed to the primary Manager when the jpcconf primmgr notify command is executed.

17.3.3

• A connection from PFM - Web Console to PFM - Manager cannot be established.

17.3.4

• No agent is displayed on the secondary Manager.

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

• A connection from NNM's Performance Management Report to PFM - Web Console cannot be established.

17.3.7

• A connection from the time the JP1/IM's Event Console starts monitoring to PFM - Web Console cannot be established.

17.3.8

• PFM-related settings cannot be specified from JP1/ITSLM.

17.3.9