Comments
-
check attached pdf you have dowloaded with app;liance zip or https://lpar2rrd.com/LPAR2RRD_and_STOR2RRD_Virtual_Appliance.php --> User credentials use lpar2rrd account, then you might "su - " to root
-
Hi, send us this output: su - lpar2rrd cd /home/lpar2rrd/lpar2rrd . etc/lpar2rrd.cfg ; $PERL bin/hmc-restapi-test.pl u060hmc11b "DEBUG_BAD_HMC"; 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…
-
We've just pushed new docker images, it's using older rrdtool which seems to work properly. Thanks for reporting, we'll inform Alpine Linux package maintainer.
-
install Xormon and attach it to runnning lpar2rrd. It uses lpar2rrd collected data. Xormon itrself does not collect data, it is just an application layer. It is also free https://xormon.com/download.php https://xormon.com/install-xormon.php
-
Hi, the best is using Xormon application (it is an application front-end above of lpar2rrd & stor2rrd data) especially when you intend to use AD. It can be easilly attach to AD.
-
yep, we know that, it is the same what you can read in our UI, I do not see a difference between wording
-
we do not collect File persona volumes performance data because storage REST API does not provide it no via REST API, it works via 3PAR cLI method no, 3PAR REST API
-
What is the question exactly? I think that the message says everything, what else do you want to know? we do not collect File persona volumes performance data because REST API does not provide it, it is all. If you have any problem with it then eithert use iother method or ask HPE how to collect such data and provide such…
-
what report it is exactly about? logs 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 reports/reporter* gzip -9 logs.tar Send us logs.tar.gz via https://upload.lpar2rrd.com
-
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 will contact you then via email
-
stor2rrd UI --> settings icon --> LAN --> select a switch --> properties --> UI grouping --> put your name instead of string "lpar2rrd"
-
then wait for next 2 days
-
is there 30 days of collected data?
-
is there 30 days of collected data?
-
it is weird, usually lpar2rrd daemon answer like this with "Protocol error" It does not seem to reach the lpar2rrd daemon. $ telnet localhost 8162 Trying ::1... telnet: connect to address ::1: Connection refused Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. kjh Protocol error: kjh Connection closed…
-
one more typo, instead of "40" there was twice "30" 0,10,20,30,40,50 * * * * /home/lpar2rrd/lpar2rrd/load.sh > /home/lpar2rrd/lpar2rrd/logs/load.out 2>&1
-
this is enough, it should get new data every 10 minutes (VMware one)
-
sorry, wrong entry, it is about lpar2rrd: 0,30 * * * * /home/lpar2rrd/lpar2rrd/load.sh > /home/lpar2rrd/lpar2rrd/logs/load.out 2>&1 --> 0,10,20,30,30,50 * * * * /home/lpar2rrd/lpar2rrd/load.sh > /home/lpar2rrd/lpar2rrd/logs/load.out 2>&1 stor2rrd data should not be delayed, it is captured every 5 minutes and loaded…
-
HPE Synergy is not supported by us. We do not expect its support anytime soon. We implement support for new technologies if there is general user demand for that or if there is business behind, none of that is the case. BTW HPE Synergy can use some of external storage devices (like 3PAR, Nimble ...) and SAN/LAN switches we…
-
VMware data load runs every 30 minutes, so there can be delay 30 - 40 minutes If you VMware env is rather smaller, you can reschedulle it to 10 minutes for example: under lpar2rrd user change this crontab line: crontab -e 0,30 * * * * /home/lpar2rrd/lpar2rrd/load.sh > /home/lpar2rrd/lpar2rrd/logs/load.out 2>&1 -->…
-
got some rar acrhive (never asked about rar) with only logs directory inside, but see nothing is configured under lpar2rrd, no idea what to do with, nothing is there Are you sure it is log from that instance you sent a screenshot above? is a problem to collect logs as we want (i.e. tar + gzip) instead of picking just one…
-
no, no support for these protocols
-
Hi, I am not sure how much it is supported, we have never tried that. if that does not work now it would need some adjusting in the code to make it work, we can eventually look at that if you are willing to provide us some snmp outputs
-
telnet <name> 443 then type something and enter, what do you get in server's log and on the agent side?
-
weird, try this: rm /var/tmp/lpar2rrd* /usr/bin/perl /opt/lpar2rrd-agent/lpar2rrd-agent.pl -d openshift_lpar2rrd_server@somewhere.com:443 # do not miss to use -d option in above cmd
-
ok, I see it, there is a check in the agent code, but it makes no sense if ( ( !isdigit($port) ) || ( $port < 1000 ) ) { error( "error setting port $port " . __FILE__ . ":" . __LINE__ ); next; } /opt/lpar2rrd-agent/lpar2rrd-agent.pl line 4740 remove these 4 lines and try it again.
-
why you have sent us load_alert.out? it is for nothing, I have never asked for that.
-
this is a test, but it definitelly cannot exclude that firewall answering instead of the end device. Pls, really check it with the security team, make sure that there is conection on the network lelev. 99% osf such issues are caused by firewalls.
-
you can specify port instead of the default one like openshift_lpar2rrd_server@somewhere.com:443 * * * * * /usr/bin/perl /opt/lpar2rrd-agent/lpar2rrd-agent.pl openshift_lpar2rrd_server@somewhere.com:443 > /var/tmp/lpar2rrd-agent.out 2>&1
-
UI --> settings --> about actual version is v7.70
Howdy, Stranger!