No Flows Seen - Collector Incorrectly Configured as a Physical Proxy.

Products

• VCF Operations for Networks

Issue/Introduction

• No virtual network flow data (vCenter/VDS/NSX) is being displayed in the VCF Operations for Networks UI.
• Security Planning and micro-segmentation flow diagrams are empty or missing recent data.
• The vCenter/NSX data sources show as connected, but flows are not processing.
• In the /var/log/arkin/collector/flow-processor.log, the following snippets are seen:

<timestamp> INFO flow-processor 39829 [netw@4413 class="vnera.ipfix.IpfixProcessor_1" thread="NFCAPD_vds" method="load" line="73"] Proxy type physical: true

<timestamp> INFO flow-processor 39829 [netw@4413 class="v2.helpers.IpfixRawFlowValidator" thread="five_tuple_task-0" method="printAndResetRejectionStats" line="472"] Raw Ipfix Record Rejection Stats [file=/var/flows/vds/nfcapd/nfcapd.202604012224]: DENY_FLOWS:0 WRONG_REPORTING_POINT:0 DATA_SOURCE_DISABLED:0 SESSION_NOT_ESTABLISHED:19400 NO_METRIC_DATA_4:0 NO_METRIC_DATA_6:0 ADDSTATE_WRONG_FLOW_TYPE:2110329

Environment

VCF Operations for Networks

Cause

The Collector processing the flows is configured exclusively as a Physical Flow collector, rather than a Normal (virtual) collector.
Since the vSphere Distributed Switch (VDS) is sending virtual IPFIX flows to this Collector, the Collector's physical proxy rejects them. It expects physical device telemetry (e.g., standard NetFlow or sFlow from physical switches/routers) and actively drops the virtual IPFIX records, resulting in the high ADDSTATE_WRONG_FLOW_TYPE drop count.

Resolution

To resolve this issue, the Collector must be converted from a Physical Flow Collector back to a Normal Collector.

Open a Support Case: Open a support ticket with Broadcom Support via the Broadcom Support Portal to perform the conversion.