TMF 642 - Alarm Management Open API

[Gaurav Bhatia]

Hi All,

I need help in using TMF 642 plugin in ServiceNow. We basically want to register our ServiceNow instance with 3rd party network monitoring tool who is using TMF 642 APIs and sending alarms in TMF format.

As per the process to receive the alarms from monitoring tool to ServiceNow, we will have to register our API endpoint into the monitoring system. Once this is done then we should start receiving the alarms and that should process into events in ServiceNow.

To achieve this, I have installed a plugin 'Telecommunications Alarm Management Open API' in ServiceNow which uis giving 1 Scripted REST API 'Alarm Management Open API' and it has 3 rest resources as shown in below screenshot.

I have registered 1 endpoint (Create Alarm) to the 3rd party monitoring system so that whenever new alarm will generate in monitoring tool then it will come to ServiceNow and the Create Alarm API will process this alarm into event.

ServiceNow API Endpoint:

https://instance.service-now.com/api/sn_ind_tmf642/alarm_mgmt/alarm

After doing everything as mentioned above, when the alarms are coming into ServiceNow then I can see below error in the log table for every alarm coming into ServiceNow.

Can anyone please help me why this error is coming and how to fix this?

Do I need to create Connector definition OR SNMP Trap listeners OR MID WebService Event Listeners? If yes then do you know why anyone of these did not automatically come with the plugin installation

Regards,

Gaurav

[Tony Chatfield1]

Hi, I would start by requesting that the vendor\external party provide you with a copy of the sent message and that they validate their settings, as your example errors seems to show an endpoint of
/sn_ind_tmf642/alarm_mgmt/alarm/client/listener
yet your resources screenshot shows seems to show
/api/sn_ind_tmf642/alarm_mgmt/alarm/

[Shubham44]

hi Gaurav,

It looks like the url configured in the 3rd party is incorrect, kindly get it checked again. 

[Gaurav Bhatia · Accepted solution]

Hi,

I have raised a case with ServiceNow and I have also discussed with 3rd party and got to know that they have interpreted the TMF documentation wrongly. As per there interpretation of the document they have to append /client/listener in the ServiceNow end point. So, they agreed to remove the /client/listener from the ServiceNow end point.

Thanks Tony and Shubham for your responses.

Regards,

Gaurav