Discovery Issues: best practice or methodology to help to solve issues, do exists something like this?

jleon
Giga Contributor

Hello

We just set up Discovery Schedules and all of needed to work like, IP Ranges, Credentials, MID Servers, etc

We are watching that some devices are not recognized in different networks with different issues. In other words, we have a lot of different errors that are not allowing some devices to be updated in the CMDB.

What is the best way to address and troubleshoot the Discovery issues, I mean, do you recommend a kind of project for this or a best practice?

Do I need to follow a kind of roadmap to solve all the Discovery issues?

Thanks!

Jesus

1 ACCEPTED SOLUTION

bernyalvarado
Mega Sage

Hola Jesus!  



I believe we met at K17 (or at K16 ). I hope you're doing great



It depends on what type of issues you're having. If there are a lot and there's some key foundations issues, then calling out a project may be the best idea. Discovery and CMDB is an ongoing journey. Having said that you can also apply a KANBAN methodology to address what's the most critical and important for the organization first.



Thanks,


Berny


View solution in original post

6 REPLIES 6

vkambham
Tera Expert

Hi Jesus,


I recently did the same exercise for a client. We dealt with it as a discovery tuning project. And the approach we took was to categorize the CI's with discovery issues into categories:


- unreachable hosts


- credential issues


- classification issues


- identification issues


- update issues


-   new probes/sensor


and then further group them by class and/or model if necessary



Then we addressed each issue category by creating a story to further investigate/troubleshoot it and determine a fix. We were able to break the problem into smaller chunks and were able to fix the CI discovery in batches.



Hope this helps.


bernyalvarado
Mega Sage

Hola Jesus!  



I believe we met at K17 (or at K16 ). I hope you're doing great



It depends on what type of issues you're having. If there are a lot and there's some key foundations issues, then calling out a project may be the best idea. Discovery and CMDB is an ongoing journey. Having said that you can also apply a KANBAN methodology to address what's the most critical and important for the organization first.



Thanks,


Berny


Venkatash describes a great way to categorise the issues so they become more manageable and Berny correctly suggests on prioritising these. For example, classification/identification issues will have higher priority because it could mean CIs not being created in the CMDB but a single command failing in the exploration phase might mean only one attribute is missing.



Even though the videos in this link are from a few years ago, I think they are still worth watching for some of the more common issues:



5-part series on Troubleshooting a failed Discovery



The identification is the area that has most changed due to a new identification engine so you might not see the exact errors shown in the second half of that video. And of course, in more recent releases more and more discovery patterns have been added. But I think all the other information is still useful.



Also, Doug Schulze adds some great extra information to the discussion in the link above which will probably help with troubleshooting. It also includes a video about adding SNMP classifiers which is something you are likely to come across.



Regards,



Dave


Berny


Yes, we met at the K17, I am fine. I am just working with a project with Discovery, trying to find out the best way to address the list of issues


Regards!


Jesus