Bug with E590 CPU Total Display

Hello,

There is a problem with CPU Display on E590 but not with E790

And CPU utilization is not correct on MPU tab for E590

Firmware: 93-06-23/00 (E590 & E790)

Data Collection: REST

Export tool 2 for (E590 & E790)

Stor2rrd version: 7.40

Problem: (Picture 1)

Everything works fine with E790.


What can be the problem: Stor2rrd sees much more CPU on E590 then it has. (Picture 3)


Comments

  • Hello,

    Send us logs

    su - stor2rrd (lpar2rrd if you are on the appliance)

    cd /home/stor2rrd/stor2rrd # or where is your STOR2RRD working dir

    tar cvhf logs.tar logs tmp/*txt data/E590/IOSTATS/* data/E790/IOSTATS/*

    gzip -9 logs.tar


    Send us logs.tar.gz via https://upload.stor2rrd.com


    Thank you

  • I have uploaded

    E590.tar.gz

    Total size: 4031506 Bytes

  • This might help:


    Hitachi is seeing this CPU:

    E590:

    From MP10-00 to MP10-11

    From MP20-32 to MP20-43

    E790

    From MP10-00 to MP10-31

    From MP20-32 to MP20-63



  • Hello,


    1. I can see bug in E590 -> CPU -> Total -> (Total tab). It should not be an empty graph. Here is the fix:


    https://download.stor2rrd.com/patch/7.40/storage.pl.gz


    Gunzip it and copy to /home/stor2rrd/stor2rrd/bin (755, stor2rrd owner)

    -rwxr-xr-x 1 stor2rrd stor2rrd 1099921 Jun 10 12:37 storage.pl

    If your web browser gunzips it automatically then just rename it: mv storage.pl.gz storage.pl

    Assure that file size is the same as on above example


    2. About MPU units. Example MPU-10-1C. This "item" does not have cpu utilization but has Write_Pending_Rate and Usage_Rate. From export tool 2


    cat Cache/CLPR/Write_Pending_Rate.csv | grep MPU-10/1C

    "2022/06/10","09:05","MPU-10/1C","0"

    "2022/06/10","09:10","MPU-10/1C","0"


    cat Cache/CLPR/Usage_Rate.csv | grep MPU-10/1C

    "2022/06/10","09:05","MPU-10/1C","0"

    "2022/06/10","09:10","MPU-10/1C","0"


    GUI -> STORAGE -> E590 -> CPU -> Items -> MPU-10-1C -> (tabs Write pending and Usage rate)


    Thank you

  • It is working now, thx

Sign In or Register to comment.