Comments
-
ok, this one yet: cd /home/stor2rrd/stor2rrd date perl -e 'use POSIX qw(strftime);$t=shift; my $v = localtime ($t);print "$t = $v\n";' `rrdtool last data/SWIZE_LG/POOL/2-cap.rrd`
-
Hello, Can you see actual data in your GUI? Storage --> POOL --> Capacity this output pls: date cd /home/stor2rrd/stor2rrd ls -l data/SWIZE_LG/POOL and from web (replace ) http:///stor2rrd-cgi/detail-graph.sh?host=SWIZE_LG&type=POOL&name=cap_pool&item=sum&time=d&detail=0
-
ok, do you have installed lpar2rrd server version 4.90 ? If yes then delete this, it will fix it. It should have been deleted automatically during upgrade. There is a new format of data store for wrkactjob, top10 and IOtop, old data captured by beta version has to be deleted. cd /home/lpar2rrd/lpar2rrd for as400_space in…
-
Hi, do you mean Capacity dashboard (list of all storages with their capacities)? Is the issue persist? All storages affected? All V7000U are affected?
-
it looks good, this output yet: arp -an can you see anything in tcpdump?
-
Is tehre only 1 interface? netstat -rn ifconfig -a Run this just to see if any communication on the network, you should see IPs from the same subnet: tcpdump
-
Is there installed server version 4.90? (tail -1 etc/version.txt ) Is anything related on server side in logs/error.log-daemon ls -l data//*/--AS400--
-
Hi, can you ping from the appliance to its default gateway from the console? It should be about your TCPIP setup, something must be wrong there.
-
it has been only example, change lpar2rrd server name used in example LPAR2RRD-SERVER.SERVER.COM to your one or use IP adress instead Our documentation says: - Configuration Change Monitor Server Name or IP addr (IPADR) to your running LPAR2RRD server This step must be done again as it has been cleared out. Use same…
-
Hi, what is your volume name? 006021 or 00:60:21. If it is VSP then name with ":" I suppose. Let us test it, colon might cause a problem. I will let you know.
-
Hi, I understand that you have upgraded the IBM i agent, right? have you defined lpar2rrd server after upgrade as is described in the manual like this: CHGCMDDFT CMD(LPAR2RRD/RTV_SYSSTS) NEWDFT('IPADR(LPAR2RRD-SERVER.SERVER.COM)') http://www.lpar2rrd.com/as400-upgrade.htm Have you upgraded even lpar2rrd server to 4.90? Is…
-
Hi, we support only 5 minutes in stor2rrd. Nothing else is implemented. We have just tested it with less than 5 mins, it generally works for most of storage types, but implementation is not finished and we are not working on that at the moment.
-
Hi, yes, it is a connection problem. 1. Check troubleshooting section on the botom of http://www.lpar2rrd.com/as400-install.htm 2. Try to connect LPAR2RRD server from another Unix machine in the same network subnet: telnet 8162 3. look at the LPAR2RRD server log if anything related cd /home/lpar2rrd/lpar2rrd vi…
-
no, we have not received data, try it once more or attach it to email support@lpar2rrd.com
-
Hi, what is actual status? Is it working after finished background conversion? Pavel
-
Hi, ignore previous post. The same problem I just seen has been caused by something else, cluster totals should generally. send us logs, pls 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 etc tmp/*txt *.out #…
-
Hi, we see it, it might happen on some particular vCenter version(s). We are investigating it, expecting a fix during next week latest. Thanks for notifying us! We will let you know. What is your vCenter version? Pavel
-
Great. It was something we were not aware until today as well :) I have just updated the install docu.
-
telnet 172.19.15.195 31001
-
Do you use right IP in horcm.conf file? horcm1.conf should have storage node IP (not SVC). And in storage-list.cfg SVC address is needed
-
right the format is wrong, bad parsing LAN info from ifconfig, this makes a problem: "addr:" Basically we do not expect OS agents on VMware clients. This is not really tested. VMware provides enough information, we do not need the agent for it. But it should generally work, OS agents data from VMware Linuxes should be…
-
This line confuses me, no explanation 15:43:58-2e723-00011838- grpname:[localhost] ipaddr:[0.0.42.249] port:[cadlock2] are registered. netstat -an | egrep "1000|11001" send us truss (strace if it is on Linux) truss -f log.out /HORCM/usr/bin/horcmstart.sh 1
-
Hi, have not you got a problem with local time as it wants to do some conversion on the backed and found data rows from switch(es) with timestamp Tue Jun 28 02:00:00 CEST 2016 (what is tomorrow).
-
yes, there is no stor2rrd account
-
Hi Vadims, this come strange to me 12:49:19-268cd-00013904- [horcmcfgetent] HORCM_MON set the following values.[NONE][31002][1000][3000] --> it says 31002, but in config file I see 31001: \\.\IPCMD-172.19.15.195-31001 This is also strange (IP, and port cadlock2 is 1000) 12:49:19-2a0f5-00013904- grpname:[localhost]…
-
Hi, pls logs once more. Note short description in the upload form. cd /home/lpar2rrd/lpar2rrd # or where is your LPAR2RRD working dir tar cvhf logs.tar logs etc tmp/*txt *.out # do not miss "h" option in tar gzip -9 logs.tar Send us logs.tar.gz via https://upload.lpar2rrd.com
-
Hi, it is planned. There will be s new major version released next week. I am not sure if this appears already in this version. We will try ... :) Cheers, Pavel
-
You have installed 4.80+ agent9s) before upgrade server to 4.80. There is some incompatibility between a new agent and older server and some DB files were created wrong. (vscsi and sas statistics files) This will remove them and they will be re-created again properly: cd /home/lpar2rrd/lpar2rrd --> delete *san-vscsi*.mmm…
-
2 things: 1. check lpar2rrd server daemon log if there is not anything related to that client logs/error.log-daemon 2. upgrade agent to 4.84-5 which should tell more about the problem get it from here: http://www.lpar2rrd.com/agent/
-
What is your version of agent and server? agent: rpm -qa|grep lpar2rrd server: GUI --> menu --> next to the last item LPAR2RRD Cheers, Pavel
Howdy, Stranger!