Service Mapping Error: Failed to match endpoint of type cmdb_ci_endpoint_tcp, please check the identifier rules

waseem_asif
Tera Contributor

While adding an entry point in Service Mapping for type TCP, receiving the following error: "Failed to match endpoint of type cmdb_ci_endpoint_tcp, please check the identifier rules". I also updated the discovery properties to use CMDB identifiers, but still unable to add an entry point. From context perspective, we recently upgraded Eureka to Helsinki.

7 REPLIES 7

saadit
Kilo Expert

Hi Waseem,



Were you able to resolve this issue yet?



I havent encountered this error message yet so I'm going to try to offer some common troubleshooting steps you can try.



  • Validate the port on the entry point and make sure the same port is Listening the target CI (I'm sure you've already done this but still throwing it out there)
  • Delete the entry point from the BSM and try delete the same from cmdb_ci_entrypoint_tcp table as well if it's still there - re-run discovery
  • Whatever the target CI is, one thing I've seen work in the past is deleting the CI from the CMDB altogether and then re-running the discovery via Service Mapping.


Regards,



Saadi Tahmid


Cognizant Technology Solutions


Hi Saadi,



Yes, I was able to resolve the issue and Issue was   that I had few mandatory fields. Once the mandatory fields were excluded, all worked fine.



Thanks,


Waseem


can you please help me here , where you excluded the fields?

 

Dave Mau
ServiceNow Employee
ServiceNow Employee

Are there any fields that are mandatory on your CIs?   If so you might want to exclude that from being mandatory on cmdb_ci_endpoint, cmdb_ci_hardware, cmdb_ci_lb_service , and cmdb_ci_appl