Disable CI Class

[big-m0dem]

What is the best way to disable a specific CI class from being discovered outside of the Configuration Console, like network adapters, config files, next hop routing rules, etc...?

We would like to stop certain classes from being discovered, and then delete them from the cmdb. We don't want them to show up on any upstream or downstream relationships.

[DaveHertel · Accepted solution]

Hi -- You can do a few things to stop discovery of certain types:

1. Deactive the probe/pattern that you don't want and/or

2. On the Classifiers, remove the probe/pattern you don't want launched from the related list "Triggers Probe".   This way, when X object is discovered (example: a windows server is running SQL processes...), and you don't want MS SQL probes launched... removing items from the trigger probe list will of course not send the probe/pattern

3. Deactivate the Classifier

On side note, I'd think very carefully about deleting a class in the CMDB... thats NOT a best practice and could set you up for future headaches.   A few reasons: 1) You can't predict the future impacts when SN comes out with new releases 2) Its possible someone/some business entity/mgr will change their mind later 3) There are probably other ways to accomplish the same goal, such as removing access permissions to use/read/write/whatever to the CI classes in question.    Removing access/roles/whatever is much easier to re-instate later when someone changes there mind....   my 2.5 cents!

Hope this helps?

[big-m0dem]

Thanks for the detailed response Dave. Would deactivating an Identification Rule be of any use?

[DaveHertel]

Hi, for what your use case us, no disabling ci identifiers will not help. Unless you have a specific need, I don't recommend disabling CI identifiers... It won't prevent discovery if CI classes but it could lead to duplicate if not planned well...

[feroz_shaik]

CI Identifier is used to restrict duplication of CIs which also be used at many places to identify ci like event management and Service Mapping. Best Practice is to restrict at schedule where you map schedule to class less. If it's to restrict specific port you can also create discovery behaviour finally above mentioned doesn't meet your requirements then disabling ci classification. **********Please feel free to mark it correct & helpful, which will be helpful to others.********