Pavel

http://www.stor2rrd.com/upgrade.htm?1.2.3

Hi, do you have all storages connected correctly? su - stor2rrd cd /home/stor2rrd/stor2rrd ./bin/config_check.sh If it is ok then send us logs. Pls note a short problem description in the text field of the upload form (name of storage which do not work) cd /home/stor2rrd/stor2rrd # or where is your STOR2RRD working dir ps…

Hi, I do not think that on the VIOS (AIX) level we can get such stat by using std OS cmds. There is something on the HMC level how to get some VLAN stats as far as I remember, but its priority has never reached level to look into at least :(

sorry, I have prepared an answer but did not use "Post" button :) Hi, no idea We have already developed something for KVM years ago but it is unfinished, no time. We know there is a demand for that. Basically it is all about our time and priorities, actually most of our deveplopment resources consumes STOR2RRD product.

Then upgrade to 5.01, you will find it there implemented :) http://www.lpar2rrd.com/download.htm?4.0 http://www.lpar2rrd.com/upgrade.htm?4.1.1

Hi, what is you product version? This should be already implemented in v5.00+

Hi, thanks, we will provide a fix soon. Double quotes causing a problem, looks like they are even in UUID string.

yes: http://www.lpar2rrd.com/VMware-counters.htm But upgrade is much better and easier way :)

Hi, ok, it took me a while to understand it :) problem is that you change conf_proc_units "regulary" on the midnight, right? Then it mosty works fine except yearly graph which uses daily MAX data. I am not sure if your solution will work generally better than the actual one, or if there is generally a solution for such…

Hello, we do not use port 924. We use 1 connection per 5 minutes whoich downloads all necessary data, no paralalization etc. Why do you think that this error is connected to stor2rrd?

You do not have set propriate couter level in Vmware. Upgrade to 5.01. There is used new method how to get data from VMware whoich does not care about any VMware setting. It will work after upgrade.

Hi, ok, I see the problem, your node name contains a space. This would not be a problem, problem is double quotes. Fix: 1. install the latest 2.01 2. get this fix: http://www.stor2rrd.com/download/LoadDataModule.pm.gz Gunzip it and copy to /home/stor2rrd/stor2rrd/bin (755, stor2rrd owner) -rwxr-xr-x 1 stor2rrd stor2rrd…

Hi, no, unfortunatelly we do not collect and save such information. Nothing from that.

what is your product version (lpar2rrd server)? do you have already some OS agents installed and running? How many if so? Hundreds? is it still failing? can you check the GUI if you see some data at least?

what is your product version? GUI --> left menu --> next to the last item

ok, that explains that, agent upgrade was done but the old agent was still running.

I simply does not belive that :) we have checked that in a customer environment with hundreds lpars where OS agents are upgraded since v1 and all lpars have packets. Upgrade cannot have influence on that. Could it be that difference is Operating system (linux vrs AIX, AIX 6.1 vrs 7.x ...) Can you have a look. This is…

ok, thanks for letting us know. What firmware did not work and which one is working?

Hi, it is something what we can implement for each storage in the future. Unfortunately we have no time for that now, actually we have other priorities. I have noted it at least. Thanks!

is it ok? :)

Hi, is the issue persist? Send us logs. Note a short problem description in the text field of the upload form. cd /home/stor2rrd/stor2rrd # or where is your STOR2RRD working dir ps -ef |egrep "2rrd" >> tmp/list_data.txt tar cvhf logs.tar logs etc tmp/*txt *out gzip -9 logs.tar Send us logs.tar.gz via…

Hi, thanks for spotting it, here is the fix: http://www.lpar2rrd.com/download/custom.pl.gz Gunzip it and copy to /home/lpar2rrd/lpar2rrd/bin (755, lpar2rrd owner) -rwxr-xr-x 1 lpar2rrd lpar2rrd 142676 Jun 2 13:31 bin/custom.pl If your web browser gunzips it automatically then just rename it: mv custom.pl.gz custom.pl cd…

sure, we will fix that in the code. Thanks for spotting it.

Hi, "@" in names is really the problem, I have just tested it. Looks like your are only the one in the world using @ in vokume names as your are the first one reporting such issue :) Well, I believe that most on storages do not allow such character in volume names. Solutions 1. you rename your names to do not contain "@"…

Hi, your right, not done yet . We are aware of that, we definitelly want to support it in the future but actuall priority is not big.

iostat does not report any disk under vscsi1. It is the reason. I am not able to explain you why there is not anything. iostat usually report adapter stats and under it disk stats attached to that interface. We use these disk stats and makling our summary per adapter. If there is no any disk under the adapter then we…

it should not be, I have just test it with both version and it works, there is only minimal change betweeen those versions. Can you assure that LPARs with 5.00 agent really do not have packet graphs?

Hi, if you have something like that in the cron: 0 * * * * /home/stor2rrd/stor2rrd/load.sh > /home/stor2rrd/stor2rrd/load.out 2>&1 Then add 1 line with: 15,30,45 * * * * /home/stor2rrd/stor2rrd/load.sh heatmap > /home/stor2rrd/stor2rrd/load-heatmap.out 2>&1 Just do not start it in the same time as standard load.sh

regarding the heatmap issue. it might be caused by low traffic on that pool, there is a limit in alering cfg which excludes pool and volumes witch have low traffic. http://www.stor2rrd.com/heatmap.html