Pavel

This look like director of a WPAR. I would need to list directory of global wpar == LPAR. (ls -lR) Whole path pls (anonymize serial/hmc if necessary)

This ouptup: date cd /home/lpar2rrd/lpar2rrd ls -lR data/<server>/*/<lpar name / global wpar>/

ok, looks like in the past there was for a moment installed agent higher version on that lpar earlier than on the server. Anyway when ever you see this error in the server daemon log "not a simple unsigned integer" then remove affected file (all files of that type). rm…

1. Is that issue global (all HMCs) or only on that particular HMC? 2. is this cmd shows that correctly? lshwres -m <server> -r mem --level lpar -F lpar_name,curr_min_mem,curr_mem,curr_max_mem,run_mem We do not put "0" into that column when I look in the code, it must come from the HMC.

What is your lpar2rrd server version? (GUI --> menu panel --> next to the last item) Looks like you have installed higher version of the agent than server (actually or in the past) Based on version info I will let you know resolution.

is it working with installed glibc.i686? It is something what helped in this thread and it is a difference between your version of the appliace and the actual one https://rodrigotamada.wordpress.com/2012/08/20/oracle-linux-install-emc-powerpath-naviagent-on-oracle-linux-6/

http://www.lpar2rrd.com/wpar.htm?4.3.18 you should see on the LPAR level (global WPAR) WPAR CPU and MEM aggregated graphs per all wpars. It works automatically.

BTW what is youir appliance version: grep "Virtual Appliance version" /var/www/html/index.html| sed -e 's/^.*Virtual Appliance version/Virtual Appliance version/' -e 's/is brought to you by.*//' Looks like you have older appliance when there was not support for VNX yet.

I well, I think that this oneis missing at your appliance yum install glibc.i686

Hi, I have just tried it, it is ok with the same package. What is your appliance version? It is noted on the bottom of its root web page: open web page http://<your hostaname>/ [root@xorux]# rpm -i NaviCLI-Linux-64-x86-en_US-7.30.15.0.44-1.x86_64.rpm Please enter the verifying level(low|medium|l|m) to set? l Setting low…

Hi, it does not appear immediatly on the lpar2rrd server in the GUI. Try: 1. Ctrl-F5 in the GUI and check if it is there 2. cd /home/lpar2rrd/lpar2rrd; ./load.sh html and again Ctrl-F5 When nothing then list this dir cd /home/lpar2rrd/lpar2rrd ls -l data/<server>/*/<lpar name / global wpar>/ You should see there a…

Hi, we have recently review our 3PAR monitoring with some HPE storage specialist and we have found out that we do not monitor it best levels from front-end and back-end point of view. As the back-end we actually use data from "logical drive" what is one level above disk which seems to be really back-end with RAID overhead…

Hi, pls more details, what exactly do you export, is that about servers or lpars ...

No limit on number of servers/hmcs or lpars.

Hi, it is not a log file. It is a file where is saved data which has not been sent to the server. Looks like there is a problem with connecting lpar2rrd deamon from that agent or any other problem preventing to send data to the server. Try to troubleshoot the problem as per http://www.lpar2rrd.com/OSagent-debug.htm Check…

Hi, this forum is about STOR2RRD product. It is not a forum for general EMC VMAX or any other storages questions. Only stuff related to STOR2RRD. Place your question on EMC official forum: https://community.emc.com/community/products

Hi, you are right. It is fixed now, download the same package from our repository once more. Thanks for notifying us!

Hi, status is checked once an hour. You should see timestaps changing here every hour (this is source for the GUI presentation) ls -l /home/stor2rrd/stor2rrd/tmp/health_status_summary/ "ok" suffix means OK.

Hi, 1. maping has been just implemented (mdisk IDs to names), you will see it after applying below fix. 2. Size of mdisks is not implemented yet. 3. Here is a fix for not displayed volumes. Problem was that on that storage are volumes spread through more mdisks. http://www.stor2rrd.com/download/Storcfg2html.pm.gz Gunzip it…

Hi, it should go back automatically after next check. Might be it is still pending in Storage event queue as not aknowleded issue. Then clean that out on the storage. How does it look now?

Hi, Send us logs pls. Note a short problem description in the text field of the upload form. &#13;&#13;cd /home/stor2rrd/stor2rrd # or where is your STOR2RRD working dir &#13;find data -exec ls -ld {} \; > tmp/list_data.txt &#13;ps -ef |egrep "2rrd|svc|xiv|ds8|ds5|hus|vspg|netapp|horcm" >> tmp/list_data.txt &#13;tar cvhf…

Hi, as per you data and screenshot there is 3 POOLs, 3 mdisks and 3 volumes on that storage. All is presented here, just mdisks (raid groups) IDs are not mapped to names. As per me it is correct, what is wrong on that screenshot?

if you run telnet as per above then you have to see at least 1 TCP syn packet on the default gateway. It is not about our agent. You might have wrong route on IBM i, use wrong interface, or anything is filtering it in IBM i. I am not an IBM i expert so I cannot advice more. As soon as telnet works then even our agent…

well, there was a connection from 172.19.131.6 which waiting for TCP close now

verify it with your network/security department if communication is allowed: <your IBM i host> --> 72.19.149.175:8162 (TCP)

ok, then there is not allowed network connection. it is what says initial error, just confirmed trough the system tool (telnet) Er: C_SNDSTS - connect() errno = 3447 Sorry we cannot help you more here, something is blocking that communication, it is all. Try that telnet from other machine whoich work, you will see…

Hi, only VolumesTOP is affected. Can you see there any volume from this storage? Pls once more this, strange above error should not happen: ls -l /home/stor2rrd/stor2rrd/data/XIV7803191/VOLUME/1076978*

opss, wrong port name in example, this is the right one: TELNET RMTSYS('172.19.149.175') PORT(8162) SSL(*NO) INZWAIT(5)

If above cmd is hanging (it times out in 10 mins) then it is ok, you can interrupt it by: SysRq ➡ Enter ➡ 2. End previous request

Try this cmd, is that fail in 5 secs or does it time out in 10 minutes? TELNET RMTSYS('172.19.149.175') PORT(8163) SSL(*NO) INZWAIT(5)