Netflow Troubleshooting Commands - Cisco Nexus 1000V Troubleshooting Manual

NetFlow Troubleshooting Commands

S e n d d o c u m e n t c o m m e n t s t o n e x u s 1 k - d o c f e e d b a c k @ c i s c o . c o m .
NetFlow Troubleshooting Commands
Use the commands listed in this section to troubleshoot NetFlow problems.
•
•
•
•
•
•
•
Use the following commands to collect information about NFM process run-time configuration errors:
•
•
Cisco Nexus 1000V Troubleshooting Guide, Release 4.2(1)SV2(2.1)
14-2
debug logfile filename—Use this command to redirect the output of the following debug commands
to a file stored in bootflash.
debug nfm all
–
debug sf_nf_srv all
–
vemdebug netflow dump policy— Use this command to verify if the correct policy is installed on
an interface on a VEM. The output of this command goes to the vemlog internal buffer. Make sure
the output shows the cache type as normal, and shows the correct cache size and cache timer values.
Apr 14 12:20:51.504410
monitors for dir INPUT traffic IPV4
Apr 14 12:20:51.504412
Apr 14 12:20:51.504413
fm1
Apr 14 12:20:51.504413
3
Apr 14 12:20:51.504413
Apr 14 12:20:51.504414
normal
Apr 14 12:20:51.504414
allocated
Apr 14 12:20:51.504415
256 entries
Apr 14 12:20:51.504415
Timeout: 15 secs
Apr 14 12:20:51.504416
Timeout: 1800 secs
vemdebug netflow dump pakstore—Use this command to dump pakstore usage for a policy on an
interface. The output goes to a vemlog internal buffer. Make sure the output shows the correct
monitor name and interface.
Apr 14 12:25:30. 29787
Client: fm1
Apr 14 12:25:30. 29793
Client: LTL49
vemlog debug sfnetflow_cache all
vemlog debug sfnetflow_config all
vemlog debug sfnetflow_flowapi all
Use these command to enable NetFlow debugging for policy installation on the VEM. Debug
messages are printed for every PDL session open, verify, and commit requests coming from the
DPA.
vemlog debug sfnetflow all
Use this command to enable packet path debugging for Netflow policies on the VEM. Debug
messages are printed for every packet that hits a NetFlow policy. Use this command with caution.
High traffic could result in lot of debug messages.
show flow internal event-history errors
show flow internal event-history msgs
19 2 2 16 Debug Port 49 has 1
20 2 2 16 Debug Flow Monitor fm1:
21 2 2 16 Debug
22 2 2 16 Debug
23 2 2 16 Debug
24 2 2 16 Debug
25 2 2 16 Debug
26 2 2 16 Debug
27 2 2 16 Debug
28 2 2 16 Debug
260 0 2 16 Debug Pak Store for
266 0 2 16 Debug Pak Store for
Chapter 14
Description:
Monitor ID:
Cache:
Type:
Status:
Size:
Inactive
Active
OL-28795-01
NetFlow