350-401 Question 621
Single answerAn enterprise network engineer is troubleshooting a NetFlow configuration issue on a Cisco router. The router is configured for Flexible NetFlow, but flow records are not being exported to the NetFlow collector. Upon reviewing the configuration, the engineer finds the following details:
- The flow exporter is configured with the correct IP address and port of the NetFlow collector.
- The flow record contains the correct match and collect fields.
- The flow monitor is applied to the correct interface in the inbound direction.
What is the MOST likely issue preventing the NetFlow data from being exported to the collector?
- A
The flow monitor is not associated with the flow exporter.
- B
The NetFlow version on the flow exporter is set to v5, but the collector only supports Flexible NetFlow.
- C
The flow record is missing the 'match ip protocol' field.
- D
The router does not have sufficient CPU resources to process NetFlow data.
Show answer and explanation
Correct answer: A
Explanation
In Flexible NetFlow, the flow monitor must be explicitly associated with the flow exporter for the NetFlow data to be sent to the collector. This is a common configuration oversight that leads to NetFlow data not being exported, even if all other components are correctly configured.
- A. Correct.
Flexible NetFlow requires the flow monitor to be explicitly associated with the flow exporter. If this step is missed, the data will not be sent to the collector.
- B. Incorrect.
The NetFlow version mismatch is not relevant in this case, as the flow exporter is part of the Flexible NetFlow configuration, which can function independently of the collector's NetFlow version.
- C. Incorrect.
The 'match ip protocol' field is optional in Flexible NetFlow configurations. Missing it will not prevent data export as long as other required fields are present.
- D. Incorrect.
While high CPU utilization can impact NetFlow performance, the scenario does not mention any resource issues on the router.