- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-18-2017 05:25 AM
Please see the attached .XML. The name that is being populated in the CMDB is the sysname showing in the sysdesc portion of the xml. I need to parse out the name that is showing in the CIData portion towards the bottom. The short name being used is RHT1 while I need it to populate as RHT1WPC000101. I've made good progress, but this issue is holding me back. Any help would be greatly appreciated.
Plus, I have attached the xml I am trying to attach for assistance.
Solved! Go to Solution.
- Labels:
-
Discovery

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-18-2017 10:54 AM
If the below discovery property is not set then I guess it won't come. But test it with few IP address before running it on all IP address.
Regards,
Vivek
Based on the impact hit like, helpful or correct

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-18-2017 05:27 AM
Hi Terry,
I assume this is a Discovery related question. If so, you'll need to find the related Sensor that is processing the returned payload. You can usually doing that by tracing which probe was kicked off to request it. The probe asks the question from the target, the sensor processes the answer and puts it in the "right places" in ServiceNow.
http://wiki.servicenow.com/index.php?title=Discovery_Probes_and_Sensors
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-18-2017 08:20 AM
Chuck-
Thanks for the response. Assuming the probe is the SNMP - Identity probe what is going to be my approach to get the name parsed out of the CIData from the probe? Do I modify the SNMP - Identity sensor (I'm assuming not). Do I make a copy of that sensor and make it work for me? Or lastly, do I create a completely custom sensor to parse out the name for this specific device type? I apologize, but this is where I typically get stuck on non-standard discovery probes/sensors.
-Terry
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-21-2017 01:43 PM
The ServiceNow Wiki content is no longer supported. Updated information about this topic is located here: Discovery Probes and Sensors
Visit http://docs.servicenow.com for the latest product documentation

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-18-2017 08:45 AM
Hi Terry,
If you have enabled your trusted name source is SNMP in the discovery properties then uncheck it and make sure you selected DNS or Netbios is trusted source for hostname.
I hope this will fix your issue without creating the custom sensor.
Regards,
Vivek
Based on the impact hit like, helpful or correct