When importing resources from cloud providers, CD&V may encounter certain issues that prevent some networks from being imported into Integrity. When a network cannot be imported, it is marked as a Dropped resource.
Locating dropped resources
Discovery and Visibility tabs: Schedule and visibility managers
When viewing schedule managers on the Discovery tab, or visibility managers on the Visibility tab, the field Contains dropped resources indicates whether any jobs within the schedule/visibility manager encountered cloud networks that could not be imported. Select the row containing the manager in the table to view the list of jobs within the manager, and determine which specific job contains dropped resources.
Discovery and Visibility tabs: Discovery and visibility jobs
Once you have selected the row for a schedule/visibility manager and opened the list of jobs, the jobs table similarly contains a Contains dropped resources field to indicate which job encountered cloud networks that could not be imported. When you select a discovery or visibility job, the sidebar expands with specific information regarding the dropped resource(s).
- Dropped due to conflicts
- Dropped due to IPv6 subnet size limitations
Cloud networks tab
Selecting a network on the Cloud networks tab will expand the sidebar with details about cloud networks that could not be imported due to conflict with the selected network.
Dropped resource scenarios
-
Dropped due to conflicts
-
A conflict has occurred due to data in the cloud
-
A conflict has occurred due to data existing on Address Manager
Note: In both cloud and Address Manager conflicts, the dropped resources depends on the number of CIDRs in the same VPC/VNet: If there is only one CIDR, only that CIDR is dropped. If there are multiple CIDRs in the same VPC/VNet, dropping one CIDR can cause other CIDRs to be dropped as well. In both scenarios, the entire VPC/VNet is also dropped.
-
-
Dropped due to IPv6 subnet size limitations
-
The IPv6 prefix length is smaller than 64
-
-
Dropped due to CD&V configuration settings, including:
-
Exclusion filters (Tag, CIDR)
-
Ignored default VPCs (AWS)
-
Overlapping VPCs dropped due to the overlapping configuration option being disabled
-