Discrepancy in 3par CLI for ShowPD and StatPD leading to incorrect Data going to Stor2RRD.
Getting Physical disk information with StatPD in the 3Par CLI shows that my SSDs are listed twice, one entry showing the expected IOPS and one showing next to nothing for activity, It seems the SSDs are served by 2 Backplane Ports within the 3Par. My FC disks are not affected by this.
This is causing StorSSD to collect the IOPs data for the SSDs incorrectly. Stor2RRD lists the Disks by "Cage Position" listed in ShowPD, but seems to collect the IOPS by ID in StatPD. Given that StatPD can have multiple entries for the same ID, Stor2RRD does not recognise this, and can pull the the wrong info.
Stor2RRD should add the data for lines with the same Disk ID in StatPD in order to be accurate.
An example below of StatPD with multiple lines of data for the same Disk ID.
This is causing StorSSD to collect the IOPs data for the SSDs incorrectly. Stor2RRD lists the Disks by "Cage Position" listed in ShowPD, but seems to collect the IOPS by ID in StatPD. Given that StatPD can have multiple entries for the same ID, Stor2RRD does not recognise this, and can pull the the wrong info.
Stor2RRD should add the data for lines with the same Disk ID in StatPD in order to be accurate.
An example below of StatPD with multiple lines of data for the same Disk ID.
08:43:52 05/28/2019 r/w I/O per second KBytes per sec Svt ms IOSz KB Idle % ID Port Cur Avg Max Cur Avg Max Cur Avg Cur Avg Qlen Cur Avg 55 0:0:2 t 1324 922 1324 29258 15522 29258 1.87 0.92 22.1 16.8 1 87 91The Above Disks are listed as below in ShowPD.
55 1:0:2 t 45 56 109 546 756 1742 0.26 0.27 12.2 13.6 0 99 99
56 0:0:1 t 1244 908 1244 26239 15064 26239 0.78 0.48 21.1 16.6 0 91 94
56 1:0:1 t 33 48 112 421 673 1835 0.13 0.14 12.8 14.2 0 100 99
Id CagePos Type RPM State Total Free A B Capacity(GB)
55 3:13:0 SSD 100 normal 456704 0 1:0:2* 0:0:2* 480 56 2:13:0 SSD 100 normal 456704 1024 1:0:1* 0:0:1* 480
Comments
-
Hi,ok, I see it, it is something we see for the first time, we will have to adopt our code.We will let you know as soon as it is done, thanks for notifying us.
-
Hi,here are hot fixes, let us know if the problem is resolved.-rwxrwxr-x 1 stor2rrd stor2rrd 21113 Jun 4 08:09 bin/hp3parperf.plGunzip it and copy to /home/stor2rrd/stor2rrd/bin (755, stor2rrd owner)If your web browser gunzips it automatically then just rename it: mv hp3parperf.pl.gz hp3parperf.plAssure that file size is the same as on above example-rwxrwxr-x 1 stor2rrd stor2rrd 113143 Jun 4 08:09 bin/HP3PAR.pmGunzip it and copy to /home/stor2rrd/stor2rrd/bin (755, stor2rrd owner)If your web browser gunzips it automatically then just rename it: mv HP3PAR.pm.gz HP3PAR.pmAssure that file size is the same as on above example
-
Hi Pavel - that looks to have done the trick. Thank you. It now seems to be collecting the Data for duplicate StatPD IDs correctly. Quite a difference in the Drive IO charts now.
Howdy, Stranger!
Categories
- 1.6K All Categories
- 48 XORMON NG
- 25 XORMON
- 153 LPAR2RRD
- 13 VMware
- 16 IBM i
- 2 oVirt / RHV
- 4 MS Windows and Hyper-V
- Solaris / OracleVM
- XenServer / Citrix
- Nutanix
- 7 Database
- 2 Cloud
- 10 Kubernetes / OpenShift / Docker
- 124 STOR2RRD
- 19 SAN
- 7 LAN
- 17 IBM
- 3 EMC
- 12 Hitachi
- 5 NetApp
- 15 HPE
- Lenovo
- 1 Huawei
- 2 Dell
- Fujitsu
- 2 DataCore
- INFINIDAT
- 3 Pure Storage
- Oracle