Comments
-
typo, this one is correct: cd /home/stor2rrd/stor2rrd ./bin/config_check.sh HPE-3PAR-DC1
-
Hi, this output: cd /home/stor2rrd/stor2rrd ./bin.config_check.sh HPE-3PAR-DC1
-
but again, use rest api method if your 3par firmware is 3.3.1 MU5 and higher
-
yep
-
ok, so all disks are in normal status, we need some further debuging why status is detected as NOK, will send you some code next week
-
gunzip it, then you get the right size
-
ok, try this fix, most probbaly there is a problem with disk but the disk healt table is not printed. Place the patch there, wait about 15 minutes, then refresh the page with storage, do you see a table with disk healt status? https://www.stor2rrd.com/download-temp/hp3parperf_api.pl.gz -rwxrwxr-x 1 lpar2rrd lpar2rrd 193840…
-
use rather 3PAR CLI method or ideally REST API if you do not have some ancient firmware in place. Anyway, using ssh one. There is not properly exchanged ssh -key, that is your actual problem. You must be able to connect 3PAR machine without providing password like: ssh 3par_machine -l lpar2rrd
-
what is your stor2rrd version? I see many times status: FWDEAD - firmware is dead, it could be the reason, let us check the code, not sure how critical this status is
-
if you go to the storage in the menu --> health status Do you see there any problem?
-
Hi, we have never seen such issue, do not you use big memory pools (50-100GB) oftenly changiung size? There was recently fixed such issue. if do not, send us a joblog: support at lpar2rrd dot com
-
Hi, storage firmware 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 tar cvhf logs.tar logs tmp/*txt gzip -9 logs.tar Send us logs.tar.gz via https://upload.stor2rrd.com
-
send us via : support at stor2rrd dot com: su - stor2rrd # lpar2rrd on the virtual appliance cd /home/stor2rrd/stor2rrd ./bin/config_check.sh storage_name and logs: Note a short problem description in the text field of the upload form. cd /home/stor2rrd/stor2rrd # or your STOR2RRD working dir tar cvhf logs.tar logs…
-
Hi, do you have any problem with that combination or you just want to confirm that it generally works?
-
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 tar cvhf logs.tar logs tmp/*txt gzip -9 logs.tar Send us logs.tar.gz via https://upload.stor2rrd.com
-
what do you get when click on any red button?
-
yep, use WBI ( REST API) access instead, it is prefered way now, use the latest stor2rrd v.7.80, it is not available in your v7.61 https://stor2rrd.com/HPE-3PAR-MSA-XP7-NIMBLE-StoreOnce-monitoring.php#MSA-WBI
-
there is no such documentation
-
do you mean between our software and monitored devices?
-
do you mean product documentation? all is on our websites
-
send us logs Note a short problem description in the text field of the upload form. cd /home/lpar2rrd/lpar2rrd # or where is your LPAR2RRD working dir tar cvhf logs.tar logs tmp/*txt tmp/*json gzip -9 logs.tar Send us logs.tar.gz via https://upload.lpar2rrd.com
-
we can arrange a technical presentation for you, not a problem at all, contact us via sales email and refer to this thread https://lpar2rrd.com/contact.php Free product demos is available here: https://demo.lpar2rrd.com/?menu=ea7021f&tab=undefined https://demo.stor2rrd.com/?menu=ea7021f&tab=undefined…
-
yep, like that
-
you request to change all our philosophy how to present data in graphs, there is hundreds of similar graphs, it is noting we will change even if you purchase support (I mean even like custom change just for you) I believe it is something what majority of users like on our product, something what make sence from our point.…
-
it is hardcoded, no way to change it by a user
-
UI --> settings --> users --> ACL is there anything persist?
-
are you running it from a cmd line like this: https://lpar2rrd.com/reporter-scripting.php are you under support? it is an enterprise version feature.
-
I do not understand that
-
do not edit it, it is a backup anyway, use UI --> settings --> users --> ACL
-
try to upgrade to this version: https://www.lpar2rrd.com/download-temp/lpar2rrd-7.71-11.tar upgrade docu: https://lpar2rrd.com/upgrade.php
Howdy, Stranger!