Discovery of multiple IPs is getting the error: "Alive, not active, not classified"

[aoop_pfeital]

Dear Community Members,

I configured a schedule on demand to discovery 10 IPs(via quick ranges), The schedule got the error: "Alive, not active, not classified" for all of IPs. However when I run the quick schedule for individual IP at time, all of them completed with no errors. 

It starts to happen after upgrade to San Diego's version. 

Does anyone have noticed this behavior as well?

Looking into the posts in community and support site I did not find anything similar reported.

Thanks in advance for your support.

Patricia
Aoop Cloud Solutions

[Jacob Nan]

I see this occasionally in my discovery schedules. It's tough to tell with such a small range of devices. Id ensure the following:

1. The devices are turned on and connected to the network
2. Proper credentials for accessing the devices have been stored in ServiceNow
3. Proper ports have been specified if not included with the OOB probes.
4. Check the payload xml to ensure an actual response is being received from the devices.

[SiD2]

Hi @aoop.pfeital,

One possibility is that the mid servers used in quick discovery and schedule might not be the same one, so verify that once.

It also could be that the servers were not available at some point of time and it must have been a coincidence.

I would suggest check if same mid used as explained above and if yes, try both quick and scheduled at same time and observe.

Please mark Helpful / Accept Solution so that it helps others with similar questions.

[aoop_pfeital]

Hello SID,

Thanks for your return.

Yes, it was done using the same mid servers.

The behavior is the same, running both quick and scheduled together. Quick works and scheduled does not.

It starts to happen after upgrade from Quebec to San Diego.

Regards,

Patricia

[SiD2]

Hi @aoop.pfeital,

It's strange, so this time you ran both types of discovery for a single IP, right?

Can you share the screenshot of the working vs failed scenario?