Loading...
Loading...
The same probe sends out to multiple MID servers on one of their discovery schedules, and the IP Range splitter can not detect duplicated IP Addresses in overlapping IP ranges leading to duplicated scans. The MID server load balancing cluster sometimes sends out the same probe to multiple MID servers. Example defining overlapping IP Range in their Discovery schedule: 10.15.64.0/21 10.15.64.0/23 When batching because the total of # of IP Addresses exceeded 5k, the ranges are divided into batches of 5k IP Addresses. The overlapped IP Address may be in different batches, therefore, IP Range splitter can not detect duplication leading to duplicated scans.
Create an on-demand discovery schedule. set for configuration. Create a discovery behaviour for windows and Unix functionality and have it go to two MID servers. Set two discovery ranges that overlap, e.g.: 10.15.64.0/21 10.15.64.0/23 Save the discovery and run it. Observe two Shazzam probes in ecc queue are generated with duplicated IPs in the batched range: "10.15.64.1-10.15.64.171" and "10.15.64.1-10.15.64.221".
This problem is under review and targeted to be fixed in a future release. To receive notifications when more information becomes available, subscribe to this Known Error article by clicking the Subscribe button at the top right of this form. As a workaround, search in the discovery schedule for IP ranges that may contain overlaps as in the steps to reproduce section. If possible, split the discovery schedule in order to isolate further the problem IP range, and remove unnecessary IP ranges that overlap.
PRB1382401
Click on a version to see all relevant bugs
ServiceNow Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.