ZIOMON_MGR(8)

📦 version 2.44.1, in opensuse-leap 16.0

💅 ZIOMON_MGR(8) — the ziorep_traffic glow-up

okay so bestie, welcome to the System Manager's Manual page for ziorep_traffic, and no cap, it's giving "I/O traffic report for FCP adapters" realness. It lives in the s390-tools family, and we're gonna walk through the whole thing together. grab a strawberry drink 🍓 and let's go.

✨ NAME ✨

ziorep_traffic — I/O traffic report for FCP adapters. literally that's the whole vibe. 🦋

🌸 SYNOPSIS 🌸

ziorep_traffic [-V] [-v] [-h] [-b <begin>] [-e <end>] [-i <time>] [-s]
[-c <chpid>] [-u <id>] [-t <num>] [-p <port>] [-l <lun>] [-d <fdev> ]
[-m <mdev> ] [-x] [-D] [-C a|u|p|m|A] <filename>

like, you hand it a <filename> and some flags and it does its thing. iconic behavior honestly. 👑

🎀 DESCRIPTION 🎀

ziorep_traffic prints a report from the specified data. that's it, that's the tweet. simple, effective, main character energy. 💖

💅 OPTIONS 💅

  • -h or --help — print help information, then exit. your little "what do i do" safety net 🫶
  • -v or --version — print version information, then exit. so you know exactly which era of this tool you're living in ⭐
  • -V or --verbose — be verbose. yes bestie, use your words 💬
  • -b or --begin — limit the timeframe to consider to data beginning with the specified date. dates must be specified in the following format: YYYY-MM-DD HH:MM[:SS]. e.g. 2008-03-21 09:08 is 9:08 on March 21, 2008. so specific, we love a format 💜
  • -e or --end — limit the timeframe to consider to data ending with the specified date. dates must be specified in the following format: YYYY-MM-DD HH:MM[:SS]. e.g. 2008-03-21 09:08 is 9:08 on March 21, 2008. bookend that data, periodt 🎀
  • -i or --interval — specify an aggregation interval. the interval is given in seconds, and must be a multiple of the interval as found in the source data. like, math is math, respect it 🔢
  • -s or --summary — print a summary of the data, then exit. the TL;DR of the TL;DR ✨
  • -c or --chpid — consider the specified physical adapter. adapters must be specified in hex. if multiple adapters should be specified, specify each one separately. e.g. '-c 7a' 🧚
  • -u or --bus-id — consider the specified bus-IDs. bus-IDs must be specified in hex. if multiple bus-IDs should be specified, specify each one separately. e.g. '-u 0.0.4c78' 🌈
  • -p or --port — consider the specified target port. target ports must be specified in hex. if multiple ports should be specified, specify each one separately. e.g. '-p 0x500507630040710b' 🔥
  • -l or --lun — consider the specified lun. luns must be specified in hex. if multiple luns should be specified, specify each one separately. e.g. '-l 0x4021402d00000000' 💀
  • -d or --device — consider the specified device. if multiple devices should be specified, specify each one separately. e.g. '-d sda' 🙈
  • -m or --mdev — consider the specified multipath device. if multiple devices should be specified, specify each one separately. e.g. '-m 36005076303ffc1040002120' 🍓
  • -x or --export-csv — write data to file(s) in CSV format. output filenames will be based on the data filename. spreadsheet girlies rise 💖
  • -t or --topline — repeat topline after specified number of frames. 0 for no repeat (default). so if you want the headers again, you just gotta ask nicely 🎀
  • -D or --detailed — print histograms. pretty little bars, we stan a visual 📊
  • -C or --collapse — collapse the data by the specified criterion:
    • a — collapse by physical adapter.
    • u — collapse by bus-ID.
    • p — collapse by target port.
    • m — collapse by multipath device.
    • A — collapse all data into a single dataset.

🦋 OUTPUT 🦋

here is a list of the columns and their descriptions. timestamps of the frames printed depict the ending of the respective timeframe. (iykyk — it's the end of the window, not the start, don't get caught out 💅)

  • I/O rt MB/s — I/O rate of the respective device in megabytes per second, considering individual requests and their total processing time, including channel latency, etc. min and max give the minimum and maximum respectively. ⚡
  • thrp in MB/s — throughput of the respective device in megabytes per second, considering times of activity only. avg and stdev give the average utilization as well as its standard deviation respectively. 🌀
  • I/O requests — statistics on the numbers and kinds of I/O requests seen. #reqs is the total number of requests, rd is the number of read requests, wrt is the number of write requests and bidi is the number of bi-directional requests. all the deets, no gatekeeping 🫶
  • I/O subs. lat. in us — latency of the I/O subsystem in microseconds. this is the time needed to execute a request, from the I/O stack down to the hardware and back up again. it excludes channel and fabric latencies. min, max, avg and stdev give the minimum, maximum and average latency as well as its standard deviation respectively. ⏱️
  • channel lat. in us — channel latency in microseconds. this is the time needed to execute a request on the FCP adapter. it excludes I/O subsystem and fabric latencies. min, max, avg and stdev give the minimum, maximum and average latency as well as its standard deviation respectively. 🔌
  • fabric lat. in us — fabric latency in microseconds. this is the time needed for the requests within the fabric, from the FCP adapter to the target device and back again. it excludes I/O subsystem and channel latencies. min, max, avg and stdev give the minimum, maximum and average latency as well as its standard deviation respectively. 🌐

🌟 EXAMPLES 🌟

Example

Print a traffic report for all devices. only data after 8:57 April 5, 2008 should be considered. data should be aggregated to 60 second intervals.

ziorep_traffic -i 60 -b "2008-04-05 08:57" sample.log

Example

Print a detailed traffic report for all devices connected to target port 0x500507630313c562. data should be aggregated over the whole data range.

ziorep_traffic -i 0 -p 0x500507630313c562 sample.log

Example

Print a detailed traffic report for all devices that are either connected to target port 0x500507630313c562 or part of multipath device 36005076303ffc5620000000000001314. the result should be collapsed on the bus-ID level.

ziorep_traffic -C u -p 0x500507630313c562 -m
36005076303ffc5620000000000001314 sample.log

👑 SEE ALSO 👑

ziorep_config(8), ziorep_utilization(8) — go read those too bestie, they're the supporting cast and they ate 💜

and that's a wrap!! this page came from s390-tools, dated Jul 2008 — yeah she's vintage, but she's still that girl 🌸✨ mwah, love u, bye!! 🎀

📦 where this page comes from