Discovery completed activities explanation

[Eitan_B]

Can someone please explain what these Discovery activities Mean:

Empty

Active

Active, couldn't classify , no WMI

Active, couldn't classify

Active, Windows Cluster VIP

Alive, not active, not classified

Classified

Classified, couldn't identify

Created CI

Identified CI

Identified, ignored extra IP

Updated CI

[sachin_namjoshi · Accepted solution]

The Devices related list in the Discovery Status form provides a summary list of all the devices scanned.

Empty

--> Your Discovery Logs indicate that it matched on primary keys e.g serial number, so your there isn't a problem with the Identification rules. Either you have a CI in the CMDB class table that doesn't have a name (hence empty) or you have something deleting your CI during the Discovery run.

Active

--> This means There were classification ports open during discovery.

Active, couldn't classify , no WMI

--> This means  port was open but when discovery tried to talk WMI no response was given.

Active, couldn't classify

--> This means  classification ports are open but when discovery tried to authenticate it failed

Active, Windows Cluster VIP

--> This message comes as part of the Windows cluster discovery  which means that discovery classifies the device correctly but CI is not created.

Alive, not active, not classified

--> This means Classification ports are open but discovery got some level of response such as refused . 

Classified

--> When Discovery scans for IP addresses only (without credentials or identifiers), no updates are made to the CMDB. All IP addresses discovered appear on this list, including multiple IPs on the same device. The results of IP address scans include slightly different information than the results of a CI scan. Since there is no CMDB activity associated with the IP address scan, the Completed activity column displays only the classification status.

Possible statuses are:

• Classified
• Unclassified
• Alive, not classified

Classified, couldn't identify

--> You need to configure a CI Identity probe that is triggered by your classifier.

Created CI

--> This means discovery run was successful and it created CI in CMDB.

Identified CI

--> This means discovery run identified CI as per your identifier configuration.The CI Identification phase is where Discovery attempts to determine whether the target device that is being discovered already has a record in the CMDB. If the answer is yes, then Discovery continues by launching the exploration probes. If there answer is no, then Discovery creates a record for it in the CMDB before launching the exploration probes. 

Identified, ignored extra IP

--> This means While discovering, discovery is scanning the same machine again which should not happen. This can be minimized if you enable an identifier that looks for just the name and give it the highest priority.

Updated CI

--> This means discovery run was successful and it updated existing CI in CMDB.

Regards,

Sachin

[Vicky8]

Hello Satchin,

How about Classified but Disabled? Can you help me to understand what's the meaning of it? And also how to fix it??

Any help from you is greatly appreciated.

Regards,

Victoria

[sachin_namjoshi]

Below article should be helpful to resolve classification issues

https://hi.service-now.com/kb_view.do?sysparm_article=KB0535236

Regards,

Sachin

[VinayChavhan24]

Hi Sachin,

Is there any documentation available with the possible solution for above issues?

Regards,

Vinay