How to troubleshoot NNMi connector issue - Support and Troubleshooting

How to troubleshoot NNMi connector issue Summary Basic guide to troubleshoot NNMi connector issues:

1. Compare NNMi connector configurations with the Document. Take note if the NNMi connector Definition JS script "NNMIEvents_JS" has been modified.

https://docs.servicenow.com/csh?topicname=configure-nnmi-connector.html&version=latest

2. Test and make sure the NNMi connector can pass connection test

3. If there is issue related to events, change parameter "debug = true" in the NNMi connector instance and then go to associated MID server to take MID server agent log.

4. Analyze MID server agent log and look for the NNMi events fetching logs:

Sample successful event fetching logs:

========================================================================================================== 07/01/20 20:24:39 (156) Worker-Interactive:ConnectorProbe-2a9d5764dbb99c503aa9a62fd39619e0 Worker starting: ConnectorProbe source: NNMi Event collector 07/01/20 20:24:39 (156) Worker-Interactive:ConnectorProbe-2a9d5764dbb99c503aa9a62fd39619e0 TP_CON_DEBUG: probe called 07/01/20 20:24:39 (315) Worker-Interactive:ConnectorProbe-2a9d5764dbb99c503aa9a62fd39619e0 *** Script: ***** NNMi CONNECTOR EXECUTE GET EVENTS! ***** 07/01/20 20:24:39 (315) Worker-Interactive:ConnectorProbe-2a9d5764dbb99c503aa9a62fd39619e0 *** Script: NNMi: EventConnector: last_event was as expected. Starting the fetch from 1593606141690 07/01/20 20:24:39 (315) Worker-Interactive:ConnectorProbe-2a9d5764dbb99c503aa9a62fd39619e0 *** Script: NNMi: URL: http://xxx.xxx.xxx.xxx/IncidentBeanService/IncidentBean 07/01/20 20:24:39 (315) Worker-Interactive:ConnectorProbe-2a9d5764dbb99c503aa9a62fd39619e0 *** Script: NNMi Query is: &lt;soapenv:Envelope xmlns:soapenv=" http://schemas.xmlsoap.org/soap/envelope/ " ... ... 07/01/20 20:24:39 (503) Worker-Interactive:ConnectorProbe-2a9d5764dbb99c503aa9a62fd39619e0 *** Script: NNMi: EventCollector handle total of 8 events in 0.188 seconds (42.553 per second) 07/01/20 20:24:39 (519) Worker-Interactive:ConnectorProbe-2a9d5764dbb99c503aa9a62fd39619e0 *** Script: ***** NNMi CONNECTOR FINISH ***** ==========================================================================================================

The URL " http://xxx.xxx.xxx.xxx/IncidentBeanService/IncidentBean " is the NNMi server address where the MID server retrieves events from. If the NNMi connector was configured with HTTPS connection and port 443, the URL would be " https://xxx.xxx.xxx.xxx:443/IncidentBeanService/IncidentBean "

Compare the logs with above example to help determine the root cause. You may test the URL on MID server host for further troubleshooting.