Some background:
My organization uses 2 sets of class A networks internally, one legacy and one the new standard. For this post I will call the Legacy 20.0.0.0/8 and the new 10.0.0.0. We have remote sites grouped in the 20.1.0.0 - 20.128.255.255 range with and equivalent on the 10.0.0.0 side along with a few class B subnets for datacenters and the like.. Not all device have the new 10.0.0.0 network yet so what I do for one I have to do for the other.
The Issue:
There has never been a good way of tracking network equipment implemented and I am trying to correct that but it seems ever few weeks someone is telling me about something that wasn't on any list or was previously down for so long that it never made it into a SolarWinds import. I would like to schedule discoveries to try to correct this. They would be primarily SNMP discoveries with testing for NCM. No WMI, vmware, or any of that fun. I would like to have some suggestions as to how I should carve up this massive IP space into something manageable by a discovery process. I am open to any suggestions (except doing it by each class C because I think the shear volume of discoveries would be a problem then, not to mention going through them all).