Discovery - Broadcast Address Reporting
Example:
A range of 10.1.126.0/255.255.254.0 has been set for discovery.
This range of 512 addresses is actually operationally masked as 255.255.255.252.
When autodiscovery happens, it is reporting all the broadcast addresses as one of the devices within each /30 subnet.
How do you keep the discovery process from falsely reporting these broadcast addresses as a device? There are over 3,000 of these /30 subnets, so loading each subnet individually would be an impossible task AND they need to be grouped by the bigger mask [255.255.254.0] for managability. Is it possible to bypass the interface and load these manually via SQL to the database? Would the upload maintain them in the group of the bigger mask?
Thanks in advance!
A range of 10.1.126.0/255.255.254.0 has been set for discovery.
This range of 512 addresses is actually operationally masked as 255.255.255.252.
When autodiscovery happens, it is reporting all the broadcast addresses as one of the devices within each /30 subnet.
How do you keep the discovery process from falsely reporting these broadcast addresses as a device? There are over 3,000 of these /30 subnets, so loading each subnet individually would be an impossible task AND they need to be grouped by the bigger mask [255.255.254.0] for managability. Is it possible to bypass the interface and load these manually via SQL to the database? Would the upload maintain them in the group of the bigger mask?
Thanks in advance!