Understanding viostat -adapter vfchost output - Part Two.Further to my previous post on viostat, Dan Braden (from IBM ATS) provided me with one of his new presentations; Monitoring, Measuring Bandwidth And Tuning SAN Storage From AIX . In this document Dan presents several ways for monitoring virtual FC adapter usage statistics.
“Hi Chris,
I just saw your article in your blog on the subject. There are 3 ways to look at real FC adapter thruput that I'm aware of:
Slide 45 shows an example where I had only NPIV traffic flowing thru the adapters and I used the "^" and "a" commands in interactive nmon to show both reports. The FC adapter report (getting its statistics from the adapter driver) shows the real thruput, while the adapter report (getting its statistics from the hdisk driver) doesn't show any IO.”
Dan sent a follow up email stating:
“....there is now a new option for fcstat (the -n <WWPN> option) which will display the statistics for a virtual port on the adapter. “
In the most recent VIOS version (2.2.2.2) the fcstat command has been updated to support new options. The -n flag can display the statistics on a virtual port level specified by the WWPN of the virtual adapter, for example:
$ fcstat -n C050760547E90000 fcs0
The -client flag will display the statistics of the virtual adapter per client, for example:
$ fcstat -client
dev hostname inreqs outreqs ctrlreqs inbytes outbytes DMA_errs Elem_errs Commrrs fcs10 marsv1 74931 53991 420344 76503184 245192288 0 0 0 upt_marsp19 15623 1253293 44 467153915 5591830528 0 0 0 upt_marsp22 142 0 55 14494 0 0 0 0 upt_marsp13 15725 1237911 44 469603323 5544087552 0 0 0 upt_marsp12 142 0 55 14494 0 0 0 0
fcs12 marsv1 165859 70463 560963 162233849 352085524 0 0 0 upt_marsp19 0 0 0 0 0 0 0 0 upt_marsp22 118 1354 38 5514704 5545984 0 0 0
So far, I've not had any success with the -client option. The command dumps core. The VIOS support guys tell me this will be fixed in the next release.
More information on the fcstat command can be found here:
http |