Comments
-
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
-
Hi, yep, SMI-S looks like to be a way how to make it working. Unfortunatelly it is not ready yet, end of Q4 2023 earliest.
-
if snmpwalk does not work, we do nothing. There is no any setting on the switches we are aware of. Are you sure that nework is open for SNMP UDP 161 traffic? Can you see udp packats from stor2rrd to the switch in the firewall? Does the switch answering anyhow? Check it with your LAN admins, they definitley must know how to…
-
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
-
ok, then it is something what is our major job, where we (Xorux) go much deeper into performance than PRTG check our demo sites to see what we provide for data https://demo.lpar2rrd.com/?menu=ea7021f&tab=undefined https://demo.stor2rrd.com/?menu=ea7021f&tab=undefined let us know if you want to have any session with us to…
-
depends what are you looking for. We do mainly performance and capacity monitoring. PRTG is mainly network and event monitoring.
-
2 reasons there is not enabled network connectivity, check on the firewall that packets are not discarded misconfiguration on the switch, check with your switch vendor how to make it work
-
ask your IBM representatives to get proper DSCli version.
-
make sure there is even open port 1750 are you sure that your DSCli version is compatible with firmware version of the storage if both above are correct then involve IBM support to make work DSCli, it is all an IBM SW and HW, we are not able to support iot. As soon as DSCli is working then you can use it in stor2rrd and…
-
ignore connection test output, we forgot to implement it there, it is already done. However it should work on the back-end, check if you see the storage in the UI.
Howdy, Stranger!