Discovery Scanning Devices not included in Range Set

Donnie Thoeny
Tera Contributor

Hello,

 

Has anyone encountered a problem with Discovery scanning IP addresses that are not defined in a range set? We are currently experiencing a problem with Discovery scanning several NetApp servers at 11pm but these servers do not reside in the specified range set. 

 

We have a schedule that runs daily against one of our data centers at 11pm and while these NetApp servers reside in the same data center, the range set is configured with other addresses. There is a separate schedule to scan these NetApp servers at 2am and those scans are successful. 

Furthermore, there are no evidence of in the Discovery Status logs of scanning these devices yet our admins are receiving reports showing that several MID servers are attempting to authenticate against these NetApp servers using multiple credentials despite the MID server already having a credential affinity. 

 

Any advice on what to check or look for would be greatly appreciated. 

1 REPLY 1

Rahul Priyadars
Giga Sage
Giga Sage

Furthermore, there are no evidence of in the Discovery Status logs of scanning these devices yet our admins are receiving reports showing that several MID servers are attempting to authenticate against these NetApp servers---> Ask them for LOGS from their environment and the timings of these LOGS. Also see which MID Server those CRED Requests are coming?

 

Regards

RP

 

IP not in Discovery Schedule and Also Cred Affinity with These Netapp Servers - I doubt its possible.