Hello,
Background, I have done a number of discoveries over the years but generally they have been smaller or more targeted to migration planning and DD work. I am running a very large global discovery that has many private 172.16.0.0, 192.168.0.0 and 10.0.0.0 subnets. There are over 30k devices and ~7k (or more) expected targets for discovery.
- I have used many /16 summarized subnets (e.g. 10.1.0.0/16) to make it easier to coalesce in the RN150 interface and capture all currently undocumented subnets and targets.
- Outside of the obvious oversize/time issues, are there any Flexera based issues that I should be aware of or scanning gaps that the summarizing might cause? I have noticed some inconsistencies on what gets discovered in the same overall summarized network and the more directed /24 subnets.
- When /16 subnets are added to scope, does Flexera end up seeing the actual and smaller subnets (i.e. /24 etc) and add them to the scanned subnets group? I have seen inconsistencies and/or lack of clarity about this.
- Regarding subnets and locations, as anybody has done this for a large network knows, it is extremely painful and manual to move subnets/locations in the portal.
- There seems to be a feature called out whereas these locations can be auto-grouped via the SNMP mechanism to the network devices. I have the SNMP configuration for the network devices but this subnet to location definitions do not seem to work. Note, I am not referring to the subnet discovery option in the assessment Appliance settings. Is there something I should be aware of to get this properly configured?
- I have been running through various subnet entries and scans to confirm and validate issues we have run into, if a subnet is not currently selected for scanning, does that then automatically configure said subnet to be flagged as “Out-of-Scope”?
- I assume this is flagged when Build App Stacks is executed but I would have assumed that if the subnet is still within the RN150 subnets list (just not activated) it would not change the in or out of scope labelling.
- Similarly, there does not appear to be any rhyme-reason to systems that show in the “No Connectivity” group where there obviously is when there is an IP, hostname and Device Type listed.
- Any experienced tips/tricks on managing large and dispersed networks for ongoing Flexera Cloudscape/Foundation discoveries?
Thanks for your advice.
