Troubleshooting Tips
The following tips are for IOS platform. For troubleshooting information on IOS XE platform, see Cisco Application Visibility and Control User Guide.
- Whenever there is an issue, turn on the relative debugs and search for keywords such as Error or Fail. Such a search will usually provide useful information about further debugging.
- Use the show policy-map type mace interface command if you want to know the number of Layer 4 flows that match the MACE policy. This is commonly used to check the basic statistics because MACE is a flow-based feature.
- Occasionally the user may observe zero values in the metrics. These are as expected if the flow is still active. Check whether the flow is terminated or not.
- Some of the metrics are only available after certain protocol stages. For example, the HTTP Host and URI metrics are only available after the flow is terminated.
- Some of the metrics support only IPFIX export protocol. These include the HTTP and URI metrics. Be sure to choose the right export protocol under the flow exporter configuration.
- Use the show flow export template command to get the properties of the exported flow data.
- Use MACE show commands to view the current export data on the router. These commands are very useful for basic debugging.
- If you encounter issues on the collector, the user can get the hex dump of the packets on the collector side and manually check if there is anything that does not conform to the NetFlow v9 or IPFIX protocol.
Debug and Show Commands
Table 4-1 lists the debug and show commands supported on PA.
Table 4-1 Debug and Show Commands Supported on PA