I am facing a strange issue with ITOM Discovery where specific devices are not being discovered during our automated schedules, but they discover perfectly via Quick Discovery.
The Setup:
- Subnet Block: x.x.x.x/20
- Example Target IP: x.x.x.x
- MID Server: Using the exact same MID server for both the schedule and the Quick Discovery test.
The Problem:
- When I run a Scheduled Discovery containing the block x.x.x.x/20, it finishes running but completely misses the target IP (x.x.x.x). The device is not updated or created.
- Even when I broke down the /20 block into smaller, sequential /24 IP Range Sets (like x.x.x.x/24) inside the schedule, the schedule still skipped the device.
- However, if I use Quick Discovery from the target IP or add this exact single IP directly to the Quick Discovery range, the device is found instantly and creates/updates the CI in the CMDB perfectly.
