Service Mapping Error

[Ashutosh30]

I am getting the below two errors while performing discovery for mapping:

I am facing this error after the recent upgrade of instance to Kingston

1.Nmap is not installed on MID Server. Verify all MIDs configured to handle selected IP Address have Nmap Capability. Nmap root directory path does not exist: C:\ServiceNow\DCAM*******3-Amsterdam\mid.geneva-08-25-2015__patch5-03-09-2016_03-23-2016_1452.windows.x86-64\agent\nmap

2.Failed to identify CI due to the host 10.***.**.*** lacking an application running on port 80. Make sure that the application is running and run quick discovery on the host.

[Ashutosh30]

Thanks Jeff,

Actually I read that Nmap is required in case of credential less discovery,but we never chose for credential less discovery earlier but the discovery was working fine.

This error has encountered now after the upgrade.

Are there any consequences in case if I go for credential less discovery now.

[johnnyjava]

1)Nmap is attempted as part of Credentialess Discovery. I haven't found it all that helpful yet, but your milage my vary. If you plan on having Credentials to access all systems within your networks, then you really don't need to install nmap on all your MID Servers. You can instead remove nmap from the capabilities related lists on your MID Servers. I think you can also disable it using the system property 'mid.discovery.credentialless.enable' described here - https://docs.servicenow.com/bundle/london-it-operations-management/page/product/discovery/concept/nmap-credential-less-discovery.html

2)This could a few different things. If you are performing Service Mapping in an environment where Discovery Schedules are not keeping your CMDB up to date, it could be that the Running Process has been marked as absent. Performing a Quick Discovery against that IP will update the records. You can then re-run Discovery on the Service Map to see if that resolves this.

It could also be that no process is running on that port. Possible causes include Network Address Translation that is forwarding the port, such as described here - https://community.servicenow.com/community?id=community_question&sys_id=a0b0f9a4db99eb805129a851ca9619e9&view_source=searchResult

I have also seen F5 Pools where the old Pool Members are still present but marked down by the F5 admin. Service Mapping still trys to connect these pool members, thinking that since they exist within the Pool config, they are or could be valid at any time. Your F5 admin should remove any pool members from the Pool config that aren't going to actually be present.

[Ashutosh30]

Thanks everyone, I went to system properties table and changed the value of mid.discovery.credentialless.enable to false as after the upgrade it went to true but I did not wanted this to happen, The credential less error is resolved now.