philp

Email sent to the above address. Hopefully it explains the issue fully.

Another check shows that this seems to be across many lpars. Looking at the output of "iostat -Dsal" it appears that the vscsi output is split across 2 sections, not together and the client parsing is only picking up the last entry e.g.Vadapter: xfers read write queue --------------------…

From the client lpar2rrd-agent.txt <machine>:<vio_client_name>:5:1561557060:Wed Jun 26 15:51:00 2019 version…

On further investigation it appears that all the vscsi adapters from one VIO server are missing from every lpar. The last entry in the ".err" file was May 22nd. The following is the last line from the agent.txt as requested <machine>:<vio_name>:3:1561556460:Wed Jun 26 13:41:00 2019 version…

iostat -Dsal 10 1|grep vscsi vscsi7 0.1 82.3 78.9 3.4 3 78.9 0.5 0.2 2.4 3.4 0.6 0.3 1.1 0.0 0.0 0.0 0.0 0.0 0.0 vscsi6 0.6 618.5 131.6 486.9 2 131.6 0.5 0.1 4.6 486.9 0.3 0.2 5.9 0.0 0.0 0.0 0.0 0.0 0.0 vscsi5 0.9 908.4 626.5 281.9 3 626.5 0.4 0.1 4.1 281.9 0.3 0.2 3.0 0.0 0.0 0.0 0.0 0.0 0.0 vscsi4 0.3 338.4 324.6 13.8 2…

Hi Pavel, Thanks for this, it seems to have worked. So my next question is : is it possible to merge 2 LPAR2RRD instances into one ? Now both our instances are on 5.07, is there a procedure to easily move and combine instances ? The idea would be to have a new server host the new website, maybe on the new version (still in…

Thanks for the reply head lpar2rrd.cfg# # LPAR2RRD main configuration file # LPAR2RRD home : http://www.lpar2rrd.com # version=5.07 (client) rpm -qalpar2rrd-agent-5.05-8.ppc

Example of data that fails from client 8286-42A*782C51X:<host>:15:1543785540:Sun Dec 2 21:19:00 2018 version…