Comments
-
Oh, and don't forget to restart the HORCM service after the processes have been killed: /HORCM/usr/bin/horcmshutdown.sh <instance_id> /HORCM/usr/bin/horcmstart.sh <instance_id>
-
We have many different HPE/Hitachi boxes, this problem is typical for VSP G1000/1500/F1500 and HPE XP7. Mid-range Hitachis do not exhibit such behaviour. In our case, killing "stuck" processes that perform data/configuration load helped. ps -ef|grep load ps -ef|grep perf Look for any processes that relate to your storage…
-
Got the patch. Now it's OK. Thank you.
-
The added metrics are working just fine with every Hitachi storage we have (from original VSP to VSP F1500 and the newest VSP G350). Stor2rrd already exceeds the functionality of any third-party product when it comes to Hitachi storage support.
-
The patch did a good job. Now the graphs really make sense.
-
GZIP contains a different file: -rw-r--r-- 1 root root 1511611 Oct 18 11:56 LoadDataModule.pm Is it ok?
-
I've missed the update somehow... Thank you, I'll try it out.
-
Hello Lukas. Log files uploaded. 'xorux_support' to unpack the archive.
-
Ok, I get the hint ))
-
Thank you for the assistance in this case - volume labels are now properly displayed; pool configuration display is fine too. The command is OK, but its output depends on the array user that executes it. If a Hitachi array is partitioned into resource groups (it is the case when GAD is enabled), the user must have access…
-
Uploaded. 'xorux4gpb' to unpack archive. Labels are not displayed for LDEVs 00:08:00 to 00:08:09. I also don't see these LDEVs in data/OB-F1500-1092/IOSTATS/configuration/config-LDEV.txt, but I definitely get them if I type "raidcom get ldev -ldev_list mapped -I6". Does stor2rrd use a different command? BTW, the possible…
-
Pavel, I can't agree with you here because: 1. Raidcom shows pool assignment for GAD volumes just fine (you can see it's a GAD volume by looking at the "HA" attribute in the VOL_ATTR field): [lpar2rrd@sp-msk-xorux01 bin]$ raidcom get ldev -ldev_id 1795 -I6 Serial# : ******* LDEV : 1795 VIR_LDEV : 1795 SL : 0 CL : 0…
-
Received a solution by e-mail: "It looks like the initial data collection took a little longer. Now it should be done. Folow these steps: cd /home/stor2rrd/stor2rrd rm tmp/2.3* ./load.sh" Summary graphs are fine now.
-
All done. Looks pretty good to me. But there's still one problem - labels are not displayed for some of the volumes. Looking into the configuration text file in stor2rrd I can see that these volumes belong to the "GAD_Unknown" disk pool with a pool ID of -1. Here's how it looks like: volume_id,name,,,,,pool_id,,capacity…
-
Logs uploaded, the comment is the same as the discussion topic. Use 'xorux4gpb' to unpack the archive.
-
All Hitachi GUI based tools I know of (even legacy ones, like Tuning Manager) have "LDEV Name" or "Label" column next to LDEV ID. I'm looking forward to seeing something similar in stor2rrd. It makes some features (like GUI display filtering) a lot more useful.
-
Hello, I've faced a similar problem with an HP XP7 array (rebranded VSP G1000). Please make sure you have all your hosts added into Performance Monitor in Hitachi Device Manager. Make sure you have nicknames for all host WWPNs, not just Host Groups (open the Hosts tab under Hosts/Host Groups/iSCSI Targets, select a host,…
Howdy, Stranger!