MID server Capabilities

[Anupam Thomas]

Hi,
Receiving below error after running discovery
mid server is not a suitable mid because it does not have the following capabilities capability:Nmap value:Null
Please help me resolve this issue.

[Onkar Pandav]

Hi,

Open the Mid server record and check the "Capabilities" related list.

What are the capabilities in that list? You can select "ALL" or "Namp".

MID Server capabilities define the specific functions of a MID Server within an IP address range. The Nmap capability is only assigned to MID Servers for which the Network Mapper (Nmap) scanner has been installed for credential-less Discovery. This capability cannot be added to or removed from any MID Server manually.

Also check below links for information.

https://docs.servicenow.com/bundle/paris-servicenow-platform/page/product/mid-server/reference/mid-s...

https://docs.servicenow.com/bundle/paris-servicenow-platform/page/product/mid-server/task/install-nm...

[Rahul Priyadars]

NMAP is used for Credential Less discovery and for that you need to Install NMAP on Mid Server.

(1) Make Sure MID Server Capability is Set All

(2) I assume you have configured  Credentials for discovery (WMI/SSH etc).

(3) Is Quick Discovery for 1 IP is working?

(4) In Your case if Connectivity and Credentials are OK then make sure you have correct IP Range given.

In IP range make sure ITs IP of devices not the IP of Subnet.

Regards

RP 

[doug_schulze · Accepted solution]

If you have enabled Credential-less discovery then yes, you would need the NMAP capability. If you have not then you want to change this sys_property. It might be set to true when it should be false..

[ADavis]

Where is this property located? We currently do not have credentialless discovery enabled or installed on our MidServers, but the Nmap error continues to generate during ServiceMapping and Discovery jobs.