How do I disable ServiceNow SNMP discovery from using DNS to determine the host name which is causing the snmp - classify step to match on the name on the hardware table?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-08-2022 11:09 AM
Currently we are trying to discover printers using SNMP. For many of our printers DNS is incorrect. It appears that ServiceNow as part of the Shazzam or Classify probes that it uses the FQDN from the DNS probe to provide a host name and then in turn use that to match on the name field on the hardware table. I would still like to have the dns probe enabled for Discovery as a whole but not to be used when classifying snmp printers. Is there a way to ignore the values coming from DNS?
Thanks,
Erick
- Labels:
-
Discovery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-10-2022 03:57 AM
Hi
Refer this KB0794203 which can solve your issue.
Please mark Helpful / Accept Solution so that it helps others with similar questions.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-10-2022 05:21 AM
Hi Sid,
I am actually looking for the exact opposite behavior. I am wanting the snmp name and in my scenario the snmp name is being used. However DNS is being used in the initial identification which is causing IRE to find an existing CI and perform an update based on the DNS name instead of matching using the snmp name.
Thanks,
Erick
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-16-2022 01:14 AM
Hi
Ok, you can add an extension section and override the DNS with empty value and you can avoid the issue.
You can disable this extension once proper DNS values are fixed in your env.
Please mark Helpful / Accept Solution so that it helps others with similar questions.