Comments
-
great, thanks for confirmation
-
Hi, yes that is right. Unfortunately SNMP starts to count ports from 1. We know about that but there is no way which would work in all situations to convert it to 0 starting point. You will have to live with that :(
-
Hi, it is "only planed" so far. Realization depends on its priority. Priority is raising if there is general demand for such feature (like this discussion :) ) or if a customer asks for that.
-
It is strange, nothing new has been introduced here, both Perl modules are required for a long time. I have just test it on AIX/Linux and it seems to working fine. Your env looks good. Is all working fine? Can you do for example CSV export from historical reports? (there is used XML support)
-
if you have 2 product instances on different virtual web servers then is easy to setup acces sfor each of them via Apache basic authorization. You can have 2 users, one would see Power lpar2rrd instance only and the other one VMware.
-
Hi, there is no direct solution for this situation. The product supports Active Directory authorization however it is not yet implemented on VMware part (it allows to restrict visibility of LPARs or servers in IBM Power part only per AD group setting) Only the way how this could be done at the moment is installing 2…
-
Try this, it should connect vCenter, supply user name, vCenter name and password. It should return vCenter time $ . /home/lpar2rrd/lpar2rrd/etc/lpar2rrd.cfg $ /usr/bin/perl /home/lpar2rrd/lpar2rrd/vmware-lib/apps/connect.pl --version --server <vCenter host> --username <vCenter read only user> --password XXXXX Connection…
-
One switch did not have enabled all required MIBs. Documentation has been enhanced about this: When there is no data from the switch at all than check if it has allowed all SNMP MIBs $ /opt/freeware/bin/snmpwalk -v 1 -c public <Switch_IP> 1.3.6.1.2.1.75.1.1.1 SNMPv2-SMI::mib-2.75.1.1.1.0 = Hex-STRING: 10 00 00 27 F8 6E 88…
-
Hi, 7.3 storage firmware brought big changes in caching. We have not implemented such changes in the product yet. It is definitelly planned to be done. It is all about our time and priorities :) Priorities affect even user feedbacks like this one of course.
-
is not it blocked by a firewall? As per http://www.lpar2rrd.com/install.htm : $ telnet vmware01 443 Trying 192.168.1.123... Connected to vmware01. Escape character is '^]'. Try from the comand line this: $ . /home/lpar2rrd/lpar2rrd/etc/lpar2rrd.cfg # adjust path to your lpar2rrd.cfg if necessary $ $PERL…
-
VMware SDK is necesary only on the server where is lpar2rrd hosted. You do not need to install anything on monitored vcenter/ESXi/VM
-
Hi, Memory/paging space alerting is not implemented yet. We are planning it to be included in brand new alerting module. It will have much more alerting possibilities than actual alerting with GUI based configuration (like it is in actual stor2rrd product). It is something what is going to be introduced this year for sure…
-
It has been fixed. It could happen when AMS RGs are fully allocated. It will be included into next releases and fixes. (1.24+)
-
1. comment out etc/san-list.cfg entry 2. remove data cd /home/stor2rrd/stor2rrd rm -r data/<SAN switch name> 3. refresh the GUI ./load.sh html
-
Hi, can you send us logs? We will have a lok and then will see what we need. We have tested it with AMS without DP pool but could be that you have another firmware which does not provide data as we expect. cd /home/stor2rrd/stor2rrd # or where is your STOR2RRD working dir find data -exec ls -ld {} \; > tmp/list_data.txt ps…
-
Hopefully today :) It will be 1.24 but HUS/AMS support will be there.
Howdy, Stranger!