
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-02-2020 08:19 AM
Hi Team,
We have few Cisco Appliance in our environment. We ran the Discovery using SNMP for these devices. Discovery is completed with few errors. I can also see entry in CMDB table for this device but its not a clean discovery.
Error-Not exploring device because record was not created for main CI type. Check that classification table matches your pattern type.
Failed Exploring CI Pattern, Pattern name: Network Router, To Check Pattern Log Press
When we analyzed we found that for the given Device OID entry is not present in OID Table.
I am looking for the best practice Steps for - It may be a common use case when OID is not Present in OID Table for a given N/W Device. Steps to cover this scenario please so we can do clean discovery of n/w device in next discovery Cycle.
Regards
RP
Solved! Go to Solution.
- Labels:
-
Discovery

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-26-2021 06:23 AM
error was coming because of a custom BR written on CMDB_CI table. It was an old BR which was written on DISPLAY way back but now it impacted our discovery.
Similar error we received for few more classes.
Added exclusion for Discovery user in given BR solved it.
Regards
RP

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-02-2020 09:57 AM
Hi,
As per my experience i would say you can add the OIDs in OID table and then if possible create a custom pattern for this or extend the router pattern. But i would not recommend you to change the existing pattern
Thanks,
Ashutosh

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-26-2021 06:23 AM
error was coming because of a custom BR written on CMDB_CI table. It was an old BR which was written on DISPLAY way back but now it impacted our discovery.
Similar error we received for few more classes.
Added exclusion for Discovery user in given BR solved it.
Regards
RP