Configuration CSV export

PhilB

Hi
 im using version 4.91-1 of the product. From the configuration tab i can export a CSV file for the lpar details. While the details i can see from the Configuration screen are correct when i export the view it doesnt export the same data to the file,  which is strange.
For example some of the HMCs export the MEM figure into the 'Curr_Mem' column but others just export 0.
Does anyone know why this would be the case.
Thanks
Phil

Pavel

Hi,

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

PhilB

The export is the CSV LPAR option on the top right. For example the view from the configuration screen shows this server -
LPAR                                                 EC    MEM
havud696_STP_MWM_App_STPTAD1   1.0  143360
havud697_STP_MWM_DB_STPTAD1     0.7  81920
havud698_STP_OBIEE_App_STPTAD1   0.2  6144

The export shows these lpars as (might need to paste these to one line)
havli005    H10_9119_FHB_SN84303A7    havud698_STP_OBIEE_App_STPTAD1    DefaultPool    shared    0.2    2    uncap    2    144    normal    0.1    0.2    64    0.1    64    1    2    64    1    64    512    6144    12288    512    0    12288    Running    aixlinux    AIX 6.1 6100-09-02-1412

havli005    H10_9119_FHB_SN84303A7    havud697_STP_MWM_DB_STPTAD1    DefaultPool    shared    0.7    14    uncap    2    143    normal    0.1    0.6    64    0.1    64    1    6    64    1    64    512    24576    81920    512    0    81920    Running    aixlinux    AIX 7.1 7100-03-04-1441

havli005    H10_9119_FHB_SN84303A7    havud696_STP_MWM_App_STPTAD1    DefaultPool    shared    1    20    uncap    2    142    normal    0.1    0.6    64    0.1    64    1    6    64    1    64    512    36864    143360    512    0    143360    Running    aixlinux    AIX 7.1 7100-03-04-1441

The highlighted 0 is curr_mem column which should be showing the 3 values above 143360 / 81920 & 6144 but only shows zero. This is happening on P795 HMCs running Version 8 rel 8.50

Hopefully that makes some sense
Anything else please let me know

thanks
Phil

Pavel

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.

PhilB

Hi Pavel
 Its only on two of the HMCs we have (same levels) the output from the cmd above shows for example , grabbing one specific lpar

lshwres command on the HMC =
porua168_B2B_XML_Billing_PROD_App,512,4096,8192,256 
So this works as designed.

When this appears in the lpar.config.csv file on the lpar2rrd server it shows as =

porli005;P10_9119_FHB_SN84302F7;porua168_B2B_XML_Billing_PROD_App;DefaultPool;shared; 0.1;1;uncap;255;121;normal;0.1;0.1;64.0;0.1;64.0;1;1;64;1;64;512;4096;8192;512;0.0;8192; Open Firmware;aixlinux;Unknown

So its going from:
curr_min_mem 512, curr_mem 4096, curr_max_mem 8192, run_mem 256
to
curr_min_mem 512, curr_mem 0, curr_max_mem 8192, run_mem 256

We are searching through the scripts to see whats causing the difference in the output from a working HMC to one that exports zeros.

Thanks
Phil

PhilB

Hi
Right we have found the issue .. unfortunately not a fix at the moment though. Hopefully this might narrow down an issue with the lpar2rrd scripts.

Basically the lpar-config.csv file gathers information from the */data/<mng server>/Hmc> directory. In there is a file called config.cfg.
In the file(s) for the servers that are not reporting correctly there is another memory parameter called 'curr_mem_expansion' this appears as 0.0 which it is using or is overwriting the curr_mem figure.

Example (grepping curr_mem from config.cfg)
Non working file
curr_mem_expansion                     0.0
curr_mem                               10240
curr_mem_expansion                     0.0
curr_mem                               2048
curr_mem_expansion                     0.0
curr_mem                               10240
curr_mem_expansion                     0.0
curr_mem                               2048
curr_mem_expansion                     0.0
curr_mem                               4096
curr_mem_expansion                     0.0
curr_mem                               8192

Working file
curr_mem                               6144
curr_mem                               6144
curr_mem                               12288
curr_mem                               8192
curr_mem                               16384
curr_mem                               6144
curr_mem                               4096
curr_mem                               2048
curr_mem                               2048
curr_mem                               30720
curr_mem                               10240

I expect we can remove the requirement to gather the memory expansion parameter in this case
What do you think Pavel ?

Thanks
Phil

Pavel

ok, it is clear, I have just fixed it 

http://www.lpar2rrd.com/download/lpar2rrd.pl.gz
Gunzip it and copy to /home/lpar2rrd/lpar2rrd/bin (755, lpar2rrd owner)
-rwxr-xr-x    1 lpar2rrd staff        160035 Jan 27 16:18 bin/lpar2rrd.pl
If your web browser gunzips it automatically then just rename it: mv lpar2rrd.pl.gz lpar2rrd.pl

It is patch for 4.91-1.

To force re-create configuration do this:
cd /home/lpar2rrd/lpar2rrd
rm tmp/4.*
./load.sh

Pavel

this is the right size:
-rwxr-xr-x    1 lpar2rrd staff        159674 Jan 27 16:21 lpar2rrd.pl

PhilB

Brilliant Pavel .. much appreciated
All seems fine now
Thanks
Phil