Unknown Path when the flow traverses an NSX Edge cluster.VCF Operations for Networks 9.0.x
This behavior occurs due to two architectural and product limitations:
System-Managed Exclusion: NSX automatically places system-deployed components—including NSX Managers, Malware Prevention VMs, Service Insertion SVMs, and NSX Edge appliances deployed via an active Compute Manager—into a read-only, system-excluded DFW group. Broadcom mandates this exclusion to prevent critical performance degradation and security loop risks.
Feature Support Limitation: Edge IPFIX capability is not supported in the current architecture of VCF Operations for Networks 9.0.x.
For the DFW Exclusion List Requirement: Do not attempt to bypass or force-remove system virtual machines from the exclusion list, as filtering their traffic through DFW policies is unsupported. For any additional custom or unsupported virtual machines that require exclusion to maintain performance and safety baselines, manually add them to user-excluded groups within the DFW configurations. For detailed guidance on management workflows, review the official documentation: Manage a Firewall Exclusion List.
For the Edge IPFIX Functionality Requirement: Edge IPFIX is an unsupported feature in VCF Operations for Networks 9.0.x. This capability requires a product enhancement. Status tracking and requirements management for this roadmap item are managed within the internal engineering tracking systems.
Subscribe to this knowledge article to get updates on this issue.