17.2.11 Troubleshooting problems related to linking with other programs

Organization of this subsection

(1) A server request error occurs and no connection is established when linking with an ODBC-compliant program.

Possible causes and solutions:

PFM - Manager has not started.

Confirm whether PFM -Manager has started. If PFM - Manager has not started, start it.
There is an error in the setting of PFM - Manager for the connection destination.

If PFM - Manager set to the connection destination has an error, correct it.

Possible causes and solutions:

PFM - Manager has not started.

Confirm whether PFM -Manager has started. If PFM - Manager has not started, start it.
The Trap Generator service of PFM - Manager has not started.

If the Trap Generator service of PFM - Manager has not started, start it.
There is an error in the Trap Destination setting of the Trap Generator service of PFM - Manager.

Confirm whether the host on which the linked NNM is installed is set as the Trap Destination.
NNM linking is not set in PFM - Web Console.

Confirm whether NNM linking is set in PFM - Web Console.
There is an error in the path name specified in the NNM registration file.

In Windows, makes sure that the path name in the NNM registration file is correct.
The NNM ovtrapd service has not started.

Execute the ovstatus command and confirm whether the ovtrapd service is running.
There is an error in the SNMP setting of NNM.

Confirm whether the community is set to public and the SNMP port is blank or set to 162.

Possible causes and solutions:

No status change event occurred.

Confirm whether a status change event appears in the alarm browser.
The NNM JPCObjMgr service has not started.

Execute the ovstatus command and confirm whether the JPCObjMgr service is running.

Possible causes and solutions:

There is an error in the settings for enabling JP1 events to be issued.

Confirm whether the settings for issuing JP1 events are correct with PFM - Web Console.
There is an error in the alarm setting.

Confirm whether the alarm setting is correct with PFM - Web Console.
JP1/Base is not installed or set up.

Confirm whether JP1/Base is installed and set up.
There is an error in a command definition of an alarm definition.

Confirm whether JP1/Base is installed and set up.

When you set -r logical-host-name as an argument for issuing JP1 events in a command definition of an alarm definition, do not include unnecessary line feeds. If you do so, JP1 events will fail to be sent. The following is an example of definition with error:
```
[[Action Definition Command]]
Command Name=../../tools/jpcimevt
Action Handler=PH1hostA
[[[Message Text]]]
<omitted>""JPC_REPORTID=aaaaaaaaaa:7518b0c:128fd04b38c:-7a16" -r hostA

[Alarm Data]
 :
```
Legend:

: Unnecessary line feed

Possible causes and solutions:

The monitored PFM - Agent or PFM - RM has never been started.

If PFM - Agent or PFM - RM has never been started, it is not displayed in the monitoring tree. Start PFM - Agent or PFM - RM and then redisplay the monitoring tree.
PFM - Agent and PFM - Manager are not connected, or PFM - RM and PFM - Manager are not connected.

If PFM - Agent and PFM - Manager, or PFM - RM and PFM - Manager are not connected, establish a connection.
The monitored object linkage function of JP1/IM is not set up.

If the monitored object linkage function of JP1/IM is not set up, set it up.

Possible causes and solutions:

A JP1 event has not been issued.

Use the Event Monitor window to make sure that a JP1 event has been issued. If a JP1 event has not been issued, make sure that the alarm definition is correct.
There is an error in the JP1/Base settings.

Confirm that there are no errors in the JP1/Base settings. When the issuing of a JP1 event from the PFM - Agent or PFM - RM host is specified, confirm whether the transmission of a JP1 event from the PFM - Agent or PFM - RM host to the PFM - Manager host is set.