Various issues arise as users work with the probe. Troubleshooting information is provided to help you diagnose and resolve such issues.

Probe is missing some events and how to resolve it?

Part of the value set for the JmsFilter property includes the value set for the PersistentJmsId property. So, the probe will not work properly if the JmsFilter property is not updated after changing the value of the PersistentJmsId property. When the probe encounters this issue, the following debug message appears in the logfile:

Debug: NFM-P: Sleeping until receiving the NFM-P server's data?

To resolve this problem, set the JMS filter and the JMS ID to the same IP address or host name, and not to a combination of local host and IP or host name.

Missing SystemInfoEvent message upon initial JMS connection

The NFM-P server is not currently sending the expected SystemInfoEvent message when the probe makes a JMS connection. If you have enabled inactivity processing (that is, set the Inactivity property in the probe properties file to a value greater than 0), the probe will shut down when it does not receive the SystemInfoEvent message within the number of seconds defined in the Inactivity property during the check subscription process.

The workaround for this issue is to disable inactivity processing by setting the Inactivity property in the nokia_nfmp.props file to 0.

JmsMissedEvent messages are not being sent when events have been lost

The NFM-P server is not currently sending the expected JmsMissedEvents messages when events have been lost. This means that the probe is not able to force a resynchronization in order to recover the missed events.

There is no workaround for this issue because since the JmsMissedEvents message is not sent by the NFM-P server, the probe has no way of knowing to send a resynchronization request. If you notice that there is event loss, you should request a resynchronization manually through the command port or HTTP interface to recover the lost events.