Wrong Nmon Records Graph
Hi:
On our environment we use nmon record files (instead native agent).
Today we found one lpar that its "Paging 2" tab / graph , was not right. (ie: real paging is 15% , and graphs showing only 5%)
So, for test purposes , we started graphing with the agent script as well: Agent is working right, its shows the real paging space being used.
We ugpraded to Version 6.0 (around 2 weeks ago)
So far its the only lpar where we find this issue.
On our environment we use nmon record files (instead native agent).
Today we found one lpar that its "Paging 2" tab / graph , was not right. (ie: real paging is 15% , and graphs showing only 5%)
So, for test purposes , we started graphing with the agent script as well: Agent is working right, its shows the real paging space being used.
We ugpraded to Version 6.0 (around 2 weeks ago)
So far its the only lpar where we find this issue.
Comments
-
Hi,on the agent side:1. lsps -s
2. tail /var/tmp/lpar2rrd*txt # the one file doew not contain "ps"3. daily graph
-
Hi Pavel, for some unknown reason to me, last saturday at around 00:00hs , the graphs got fixed. It now shows the correct paging space being used (lsps , nmon, agent, etc, it all matches) , which is ~20%Now, I don't see any point in sending the info you requested, since its working fine.Anyway, I'll keep an eye on this lpar, if this "anomaly" re-surface in the future, I'll update this post or open a new one.Thank you very much for help though .
Howdy, Stranger!
Categories
- 1.6K All Categories
- 41 XORMON NG
- 25 XORMON
- 149 LPAR2RRD
- 13 VMware
- 16 IBM i
- 2 oVirt / RHV
- 4 MS Windows and Hyper-V
- Solaris / OracleVM
- XenServer / Citrix
- Nutanix
- 6 Database
- 2 Cloud
- 10 Kubernetes / OpenShift / Docker
- 122 STOR2RRD
- 19 SAN
- 7 LAN
- 17 IBM
- 3 EMC
- 12 Hitachi
- 5 NetApp
- 15 HPE
- Lenovo
- 1 Huawei
- 1 Dell
- Fujitsu
- 2 DataCore
- INFINIDAT
- 3 Pure Storage
- Oracle