Alive, Not classified

nk_dubey1
Kilo Contributor

‎11-23-2014 03:37 PM

Hi,

 

While Discovery bunch of my IP returning this error. I checked the log and it indicates that IP is not Active but it's Alive. I can see refusal on many ports. I have below questions in the discovery:

 

(1) What is the difference between Active and Alive. Does

(2) What Discovery use for fetching information TCP or UDP? Also in which order.

(3) Alive, Not classified (Does this means Discovery was able to ping IP, but it received negative response from port?)

 

Any easy way to solve these kind of issue.

Labels:
0 Helpfuls
  • 6,062 Views
10 REPLIES 10

tim_broberg
ServiceNow Employee
ServiceNow Employee

‎11-23-2014 04:54 PM

1 - Alive indicates we got a response. Active means we were able to probe the port.


2 - Depends on the port probe. You can look at Discovery Definition / port probes to see which probes do what.


3 - Correct.



Generally, you're looking at a firewall / policy issue when you see alive, not classified. The server doesn't want to talk to us on that port.



Some debugging steps:


  1. Ping the server. Presumably, this works.
  2. Telnet to the port. Presumably this does not. (telnet server port)
  3. Check server access logs
  4. Temporarily disable the firewall
  5. Check that the relevant service is running on the server


Hope this helps,


    - Tim.


0 Helpfuls

nk_dubey1
Kilo Contributor
In response to tim_broberg

‎11-23-2014 05:01 PM

Hi Tim,



Thanks for answering.



I had same understanding as you explained. I got confused as few IPs were giving me this error, but customer says this device shouldn't be alive as these devices were decommissioned a while ago.



Any thought, why Discovery was able to ping the IP, but client says it's is not alive?


0 Helpfuls

amit_dhuleshia
ServiceNow Employee
ServiceNow Employee
In response to nk_dubey1

‎11-23-2014 08:19 PM

Are you able to reach/ping the IP without using Discovery? From the machine where the MID Server is installed?


0 Helpfuls

nk_dubey1
Kilo Contributor
In response to amit_dhuleshia

‎11-23-2014 08:29 PM

Hi Amit,



I am working remotely and don't have access to the MID Server. I have already asked engineer at client site to try and ping the IP from MID Server. Is there is any way to ping the IP from the Service-Now instance?



Also as per my information IP which are not reachable will not show up in Discovery log? Also let me know when SN log error "Alive, Not classified". Does SN through this error even if IP is not reachable/ping?


0 Helpfuls