1. Knowledge Base
  2. CloudFS Maintenance

Diagnostic Tools

This article details the diagnostic tools Panzura provides, where to find them and how to use them.

Panzura provides the following tools to assist with troubleshooting CloudFS:

  • Packet capture tools: Capture packets on the Ethernet ports. You can select to capture all packets or restrict the capture to TCP or UDP packets. The captured packets are saved into a file that you can download and send to Technical Support.
  • Diagnostic tools: Execute network, filer‐specific, and cloud diagnostic commands.
  • Performance test tools: Execute Iperf commands to test network performance.

To use the filer's troubleshooting tools, navigate to the following page:

Maintenance > Diagnostics

The following table describes the filer's diagnostic tools sections Packet Capture and Diagnostic Tools.

Packet Capture Option Description
Packet Capture Tools
Capture type 1

Capture selected headers and packets.

  • pkt-capture β€“ Capture TCP and UDP headers and packet.
  • pkt-capture-tcp β€“ Capture TCP headers and packet.
  • pkt-capture-udp β€“ Capture UDP headers and packet.
  • pkt-capture-header-only β€“ Capture TCP and UDP headers.
  • pkt-capture-tcp-header-only β€“ Capture TCP headers.
  • pkt-capture-udp-header-only β€“ Capture UDP headers.
LAN or WAN Select whether to collect LAN or WAN packets.
Start/Stop Starts or stops the capture.
Download

Downloads a file with the capture results.

Diagnostic Tools
Command Type

Select a command. Click Run to see a description of parameters for the command. If there are no required parameters, clicking Run executes the command. The results are displayed on the screen.

A list of commands is contained in the following table.

 

Output Examples for Performance Test Tools

This example shows output from client filer vmcc92.

Diagnostics[57529]: Firewall is temporarily disabled to allow diagnostics operation and shall be enabled when operation is completed automatically.

------------------------------------------------------------

Client connecting to vmcc94, TCP port 5001

TCP window size: 65.0 KByte (default)

------------------------------------------------------------

[ 4] local 10.199.10.92 port 45867 connected with 10.199.10.94 port 5001

[ ID] Interval Transfer Bandwidth

[ 4] 0.0- 5.0 sec 436 MBytes 731 Mbits/sec

[ ID] Interval Transfer Bandwidth

[ 4] 5.0-10.0 sec 416 MBytes 698 Mbits/sec

[ ID] Interval Transfer Bandwidth

[ 4] 10.0-15.0 sec 369 MBytes 619 Mbits/sec

[ ID] Interval Transfer Bandwidth

[ 4] 15.0-20.0 sec 312 MBytes 524 Mbits/sec

[ ID] Interval Transfer Bandwidth

[ 4] 20.0-25.0 sec 401 MBytes 673 Mbits/sec

[ ID] Interval Transfer Bandwidth

[ 4] 25.0-30.0 sec 359 MBytes 603 Mbits/sec

[ ID] Interval Transfer Bandwidth

[ 4] 30.0-35.0 sec 433 MBytes 727 Mbits/sec

 

This example shows output in a case where the vmcc94 filer is acting as the server.

Diagnostics[46450]: Firewall is temporarily disabled to allow diagnostics operation and shall be enabled when operation is completed automatically.

------------------------------------------------------------

Server listening on TCP port 5001

TCP window size: 64.0 KByte (default)

------------------------------------------------------------

[ 5] local 10.199.10.94 port 5001 connected with 10.199.10.92 port 33313

[ ID] Interval Transfer Bandwidth

[ 5] 0.0-120.2 sec 9.09 GBytes 650 Mbits/sec

[ 6] local 10.199.10.94 port 5001 connected with 10.199.10.92 port 45867

[ ID] Interval Transfer Bandwidth

[ 6] 0.0-120.0 sec 9.46 GBytes 677 Mbits/sec