HPE 3PAR StoreServ Storage

Re: System Reporter for FPG (srstatfsfpg) field meanings

Occasional Contributor

System Reporter for FPG (srstatfsfpg) field meanings

Hi everyone,
I know I've posted this before, but this is to ask about different fields. So below is the output from an srstatfsfpg command from the 3PAR CLI, and I was creating a script to generate reports using this information from various srstat commands. Usually there's an IO/s split into read/write, a data rate in Kb/s split into read/write and other normal performance metrics when querying about disks or volumes.
When trying to do the same for FPGs, I had taken the Reads/ReadByte per minute/Writes/WriteByte per minute fields to mean IO/s, but it was brought to my attention that the fields were under the category "Packets", and there were fields "Creates, Removes, Errors" were under the metric type of "Operations".
My question is: what exactly are the fields under the "Operations" metric type, and are there any equivalency to IO/s of other components such as disks or volumes? If not, what would be a similar metric to compare them to?

Time: 2020-05-22 10:55:00 CDT (1590162900)
,,,--------------------------per minute--------------------------,,,,,,,--------average---------,


Re: System Reporter for FPG (srstatfsfpg) field meanings

Hi Mark

Thank you for coming on HPE community Forums

The latencies displayed is  average per minute (for the entire time frame). And they are in milli seconds.

I suggest you to kindly refer Page #644 to Page #647 from HPE 3PAR Command Line Interface Reference using the below mentioned link.


Hope this helps.!!


I work for HPE

Accept or Kudo

[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
Occasional Contributor

Re: System Reporter for FPG (srstatfsfpg) field meanings

Thanks for the reply Mahesh, you had actually replied on a similar post of mine a few months ago haha

I had already solved that issue, this post is asking about different fields (difference between packets and operations metrics)