Users Guide

0026a8d0 <mi_switch+0x1b0>:
0026a00c <bpendtsleep>:
----------------STACK TRACE END----------------
--------------------FREE MEMORY---------------
uvmexp.free = 0x2312
Enabling TCP Dumps
A TCP dump captures CPU-bound control plane trac to improve troubleshooting and system manageability. When you enable TCP dump,
it captures all the packets on the local CPU, as specied in the CLI.
You can save the trac capture les to ash, FTP, SCP, or TFTP. The les saved on the ash are located in the ash://TCP_DUMP_DIR/
Tcpdump_<time_stamp_dir>/ directory and labeled tcpdump_*.pcap. There can be up to 20 Tcpdump_<time_stamp_dir> directories. The
21st le overwrites the oldest saved le. The maximum le size for a TCP dump capture is 1MB. When a le reaches 1MB, a new le is
created, up to the specied total number of les.
Maximize the number of packets recorded in a le by specifying the snap-length to capture the le headers only.
The tcpdump command has a nite run process. When you enable the tcpdump command, it runs until the capture-duration timer and/or
the packet-count counter threshold is met. If you do not set a threshold, the system uses a default of a 5 minute capture-duration and/or a
single 1k le as the stopping point for the dump.
You can use the capture-duration timer and the packet-count counter at the same time. The TCP dump stops when the rst of the
thresholds is met. That means that even if the duration timer is 9000 seconds, if the maximum le count parameter is met rst, the dumps
stop.
To enable a TCP dump, use the following command.
Enable a TCP dump for CPU bound trac.
CONFIGURATION mode
tcpdump cp [capture-duration time | filter expression | max-file-count value | packet-count
value | snap-length value | write-to path]
Debugging and Diagnostics
1213