Is there a way to create a CI through a Discovery for Cisco IP phones with no credentials and no open ports. I can only ping the devices.

jeremyjameshans · ‎03-06-2018

My company has 600+ Cisco IP Phones. I have been instructed to add these to the CMDB. I would rather have an automated way to create the CI's.

My Mid server can ping every device; however, I am unable to create the CI's as the phones are completely locked down. During credentialess discovery I can view the Horizontial discovery log and see the information I would like to discover.

NMap pulls the exact information I need: osclass type="VoIP phone" vendor="Cisco" address addr="IP Address Redacted"

All I want is to create a generic name of each phone with it's unique IP address. I have read many threads on this and most people have access to credentials. Has anyone had success with creating CI's from an IP address (ping Only)?

Thanks,
Jeremy

doug_schulze · ‎03-09-2018

You should look to the call manager.. we have some stuff on share that still works today to pull in those phones. Honestly dont think you're going to be able to do the phones directly.

https://share.servicenow.com/app.do#/search-result?search_query=ip%20phones&startRow=NaN&sort_parameter=title

View solution in original post

Marcel H_ · ‎05-26-2020

Thanks for the suggestion, I'll give that a shot when I circle back to this soon. Do you have an example you can share on your pattern setup?

ggarcia1 · ‎05-27-2020

Yup, but I'm not an admin so I couldn't export the pattern as an update set, so I just copied the pattern text.

Older ILOs don't support redfish api, but do have xml data pages.

This is a very simple pattern I used as practice. I don't think this includes the pre/post sensors, but I used one to do the host name lookup.

I hope it helps and do let me know if you get your IP Phones talking to ServiceNow. Ours will load the xml page in a browser without login, but don't want to come up during pattern debug.

Erick18 · ‎11-05-2020

Were you ever able to get past the debug issue?

ggarcia1 · ‎11-17-2020

I believe it has something to do with SLL Certification Verification.

I'm new to dealing with that, but I did ask our admins to load a root cert to our instance so I could test.

I'v since learned that we have high security settings enabled so we cannot disable the verification; so it turned out that loading the cert was the only option anyway. Others on the community have had success with different discoveries by disabling cert verification.

I still haven't gotten it to work, but I don't know enough to even ask the right questions concerning the role the cert plays in this.

Erick18 · ‎11-17-2020

I was actually able to get past the debug error. I had to use the steps outlined in serverless discovery to create the pattern. I followed the steps from the ServiceNow doc here: https://docs.servicenow.com/bundle/paris-it-operations-management/page/product/discovery/task/create-pattern-for-serverless.html#create-pattern-for-serverless.