Troubleshooting
This troubleshooting section includes the following topics:
- Report Is Not Displayed Correctly
- Incorrect TCP Performance Statistics
- Memory/Cache Warning
- More Than 32 Matches per Class
- More Than Five Monitors per Class
Report Is Not Displayed Correctly
The following may be helpful for troubleshooting a report that is not displayed correctly:
- Verify that your flow exporter is configured with the correct destination IP.
- If you are using a VRF, ensure that it is added at the destination.
- Review the running-config and verify that nothing is missing or misconfigured. The problem can be caused by even a single access-list missing.
- Cisco IOS XE Platforms : Verify that account-on-resolution (AOR) is active.
– If AOR is active, handles will have a non-zero value, as shown in the following example:
– If AOR is inactive, handles will have the value of zero, as shown in the following example:
Incorrect TCP Performance Statistics
The following may be helpful for troubleshooting incorrect TCP performance statistics:
- Verify that the monitor that includes TCP performance metrics is applied to only one interface.
- For that interface, service-policy must be attached in both directions.
- Check for asymmetric routing.
- Verify that routes/route-maps are configured correctly.
- If filtering applications, ensure that the appropriate class-map has hits.
- Verify that account-on-resolution (AOR) is active. For details about verifying AOR, see Report Is Not Displayed Correctly.
- Enable IP NBAR Protocol Discovery on the interface to determine whether the protocol of interest is identified.
Memory/Cache Warning
An error message typically occurs if the total memory consumed by all monitors exceeds 25% of the total available memory. If the memory required for all enabled features exceeds the memory available, the following may be helpful for troubleshooting:
- Review the configuration. If there are mismatches, remove the configuration and reapply it.
- Reduce the FNF monitor cache size.
Also see Cache Size Recommendation.
Cache Warning on Cisco IOS Platforms
On Cisco IOS platforms, the following type of MMA warning can occur:
Memory Warning on Cisco IOS XE Platforms
On Cisco IOS XE platforms, the following type of FNF warning can occur:
This warning message indicates that a large amount of memory is allocated to Flexible NetFlow (FNF) monitors. Allocating this amount of memory to FNF monitors is acceptable, but the total memory required by all other enabled features must not exceed the available memory.
More Than 32 Matches per Class
The following may be helpful for troubleshooting the following type of error message regarding configuring more than 32 matching statements:
More Than Five Monitors per Class
The following may be helpful if you receive the following type of error message regarding the limit of five (5) monitors per policy per class: