Discovery Targets linked to Subnet Category
Typically when doing a discovery the targets are list /24s or specific addresses / URLs.
I have a couple of customers down here in APAC who are looking to define a Subnet Category and then add specific subnets to that category,
It would then be very useful to be able to use a Subnet Category as part of the discovery target.
Potentially what would also be good is if we choose a Subent Category we then get the option to use all or some of the subnets within that category.
Would make larger environments easier to map out with subnets and discoveries.
I am one of Dom's customers and we have discussed how this would be very beneficial to my organisation (the Australian Broadcasting Corporation), as it would make it much easier to identify the target of discovery jobs, when these are being defined at scale, which will lower the effort and errors associated with maintaining discovery jobs. As an example, we have created a Windows discovery job for a single site (knowing that it won't exceed 65,536 IP addresses) and have to list the 232 subnets currently associated with this site, however when we can only view an IP address, it makes understanding and maintaining what is targetted very challenging. At the same time, we have created subnet records and subnet categories within Device42, so that we can see what has been discovered per subnet and what may still need to be discovered. If these records could be referenced and used within the discovery job, it would make our lifes much easier and also ensure Device42 is being used most effectively.1
Please sign in to leave a comment.