ziomon - Collect FCP performance data

Use the ziomon tool to gather FCP performance data. The monitor tool ziomon collects information and details about:
  • The FCP configuration
  • The system I/O traffic through FCP adapters
  • The overall I/O latencies, adapter latencies, and fabric latencies
  • The usage of the FCP resources
Use the ziorep tools to analyze the reports created by ziomon. The process is illustrated in Figure 1.
Figure 1. The FCP performance tools

On the target system, use ziomon to gather data and ziorep to analyze the data.

Authorization

Root access is required on Linux™ operating systems.

ziomon syntax

See the ziomon man page for the complete syntax and all options.

1  ziomon ? -l<size limit of output file>? -i <interval> -d<duration> -o<output file> + <device node>

Parameters

-i <interval>
Specifies the elapsed time between writing data to disk in seconds. Defaults to 60 seconds.
-d <duration>
Specifies the monitoring duration in minutes. Must be a multiple of the interval length.
-l <size limit of output file>
Defines the upper limit of the output files. Must include one of the suffixes M (megabytes), G (gigabytes), or T (terabytes). This limit is only a tentative value that can be slightly exceeded.
-o <output file>
Specifies the prefix for the log file, configuration file, and aggregation file.
<device>
Denotes one or more device names that are separated by blanks.

Examples

To generate a diagnostic report for devices /dev/sda and /dev/sdb, issue the command:
[root@system]# ziomon -i 20 -d 5 -l 50M -o trace_data /dev/sda /dev/sdb

Output

The ziomon tool creates two output files in the directory where it was started:
  • <output file>.cfg holds various configuration data from the system
  • <output file>.log holds the raw data samples that are taken during the data collection phase in a binary format
  • <output file>.agg aggregates old sample data when the .log file grows larger than the allowed limit, thus freeing the log file for more recent data.

Usage notes

  • Needs vmalloc space for each device node and CPU.
  • The ziomon tool can be stopped with CTRL+C before the time period expires.