KEMBAR78
A10 Axdebug | PDF | System Software | Computing
Scribd
Upload
565 views4 pages

A10 Axdebug

The document describes advanced debugging tools for AX including axdebug and debug monitor. Axdebug captures packet details in pcap format that can be analyzed in Wireshark. Debug monitor provides formatted text output for quick issue analysis. Both tools provide session-based packet dumps that capture all packets matching a filter within a session between a client, AX device, and server. The document also provides instructions for starting axdebug captures, applying filters, exporting pcap files, and checking the axdebug status.

Uploaded by

Tuấn Anh Nguyễn
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
565 views4 pages

A10 Axdebug

The document describes advanced debugging tools for AX including axdebug and debug monitor. Axdebug captures packet details in pcap format that can be analyzed in Wireshark. Debug monitor provides formatted text output for quick issue analysis. Both tools provide session-based packet dumps that capture all packets matching a filter within a session between a client, AX device, and server. The document also provides instructions for starting axdebug captures, applying filters, exporting pcap files, and checking the axdebug status.

Uploaded by

Tuấn Anh Nguyễn
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

Advanced Debugging Tools

 axdebug
 Captured files in pcap format
 Can be easily opened with Wireshark / tcpdump
 Able to see every detail of the packets the AX receives & sends

 debug packet / debug monitor


 Provides a quick look at the issue on AX side
 Formatted text output

1
Advanced Debugging Tools

 Axdebug and debug are session based


 If one pkt matches filter, dump all the following pkts in the same session

Client AX – VIP Server


40.40.40.40 30.30.30.90 10.10.10.30

packet1 packet2

Src 40.40.40.40 Src 30.30.30.123 (nat pool)


Src port 35525 Src port 35525
Dst 30.30.30.90 Dst 10.10.10.30
Dst port 80 Dst port 80

2
Advanced Debugging Tools - axdebug

 Prepare the capture


 Capture file name
 Filters
 If multiple filters are used, traffic that matches any of the filters is captured.
Note: Refer to the CLI Reference for more options
AX# axdebug
AX(axdebug)# filter 1
AX(axdebug-filter:1)# ip 1.2.3.4 /32
AX(axdebug)# capture save file_name

 Stop the axdebug trace


AX# no axdebug
 Export the axdebug trace
AX# export axdebug file_name ?
use-mgmt-port Use management port as source port
tftp: Remote file path of tftp: file system(Format: tftp://host/file)
ftp: Remote file path of ftp: file system(Format: ftp://[user@]host[:port]/file)
scp: Remote file path of scp: file system(Format: scp://[user@]host/file)
rcp: Remote file path of rcp: file system(Format: rcp://[user@]host/file)
3
Advanced Debugging Tools - axdebug

 show axdebug status


# sh axdebug status
axdebug is disabled cpu#9 captured 0 packets.
300 seconds left cpu#10 captured 0 packets.
debug incoming interface disabled cpu#11 captured 0 packets.
debug outgoing interface disabled cpu#12 captured 0 packets.
maximum 3000 packets cpu#13 captured 0 packets.
Captured packet length 1518 cpu#14 captured 0 packets.
cpu#1 captured 0 packets. cpu#15 captured 0 packets.
cpu#2 captured 0 packets. cpu#16 captured 0 packets.
cpu#3 captured 0 packets.
cpu#4 captured 0 packets.
cpu#5 captured 0 packets.
cpu#6 captured 0 packets.
cpu#7 captured 0 packets.
cpu#8 captured 0 packets.

You might also like