Prerequisites:
Ensure the architecture satisfies the following criteria prior to executing discovery:
- Licensing: VMware VCF Operations for Networks Enterprise edition or VCF entitlement.
- Compute Sizing: The platform node must be deployed using the Extra Large (XL) brick size.
- Data Baseline: The system must have discovered a minimum of 10 VMs and logged at least 100 VM-to-VM network flows.
- Load Balancer Integration (Recommended): Integrating Load Balancers as data sources, which increases tier grouping accuracy via configuration metadata analysis.
Configuration Workflow
- Access Discovery Engine: Navigate to Applications > Discover in the left navigation pane and select the Flows tab.
- Define Scope and Naming:
- Click Edit Discovery to isolate the scope (e.g., specific clusters, vCenter instances, or duration of analyzed flows).
- Define the Application and Tier Naming hierarchy (e.g., Security Tags > VM Names). The system defaults to VM nomenclature if tags are omitted.
- Use Regular Expressions (Regex) in the VM Names configuration to match standard enterprise naming conventions (e.g., APP-.*).
- Set Clustering Granularity: Adjust granularity to control the clustering algorithm's aggression:
- Coarse: Generates applications with a higher density of VMs and tiers.
- Medium: Balances tier isolation.
- Fine: Generates highly segmented applications with fewer VMs per tier.
- Execute and Validate:
- Click Submit to initiate the analysis.
- Review the tabular output, focusing on the Confidence column. High confidence denotes strong flow correlation, requiring minimal manual override.
- Click Save Application to commit the mapped topologies for Day 2 Network Assurance and Micro-segmentation planning.