Credentialless Discovery Network Device

[masayuki sanpei]

Hello, I have confirmed the operation of "credential less discovery"
"Pattern Launcher: Credentialless Discovery Network Device"
In "7. Terminate If sys_class_name is undefined (null or eos)"
It will be an error.

I am investigating the above cause, but I do not know the cause.
Please let me know if you know what to check.

By the way, the result of "Nmap Scan Report" is as follows.

Ports
the 43 ports scanned but not shown below are in state:filtered
　・ 43 ports replied with: no-responses

Remote Operating System Detection
Unable to identify operating system.

Is it possible that the above is the cause?

[sethivarun · Accepted solution]

Hello, 

the credential-less discovery utilizes the SetCredentialLessDeviceClassName mid server script includes to finalize the class name. 

Please have a look at that to see if the nmap can identify the OS for it. 

By default the OS that the credential less is looking at the os mentioned in this script includes.

[masayuki sanpei]

Thanks,

An error occurred because the OS could not be identified because the port, port status, and OS family were not acquired.

We will investigate the cause that can not be acquired by nmap.

[shaunwarnock]

This is because the NMAP commands from the MID Server to the target are failing and none of the ports that are scanned are coming up as OPEN which is used for classification.

Ensure that ports to the target device are open for the NMAP to scan the IP and fetch the information.

Refer to the following documentation:

https://docs.servicenow.com/bundle/paris-it-operations-management/page/product/discovery/reference/data-collected-nmap.html
https://docs.servicenow.com/bundle/paris-it-operations-management/page/product/discovery/concept/nmap-credential-less-discovery.html