MIB Protocol Statistics (RFC1213) [v2.1 - 2009-05-10]
Moderators: Developers, Moderators
Sorry, I mis-read. Thought you were using snmpv3.
In that case, try /var/www/html/cacti/scripts/ss_protocol_traffic.php ss_protocol_traffic 192.168.0.1 public 2 161 500.
In that case, try /var/www/html/cacti/scripts/ss_protocol_traffic.php ss_protocol_traffic 192.168.0.1 public 2 161 500.
| Scripts: Monitor processes | RFC1213 MIB | DOCSIS Stats | Dell PowerEdge | Speedfan | APC UPS | DOCSIS CMTS | 3ware | Motorola Canopy |
| Guides: Windows Install | [HOWTO] Debug Windows NTFS permission problems |
| Tools: Windows All-in-one Installer |
No problem.
I have run that and it seems to have worked.
/var/www/html/cacti/scripts/ss_protocol_traffic.php ss_protocol_traffic x.x.x.x testing 1 161 500
ipInReceives:93922700 ipOutRequests:698197 tcpInSegs:5765 tcpOutSegs:6490 udpInDatagrams:651963 udpOutDatagrams:592446 snmpInPkts:177927 snmpOutPkts:177927 icmpInMsgs:55300 icmpOutMsgs:99265
What do you think?
I have run that and it seems to have worked.
/var/www/html/cacti/scripts/ss_protocol_traffic.php ss_protocol_traffic x.x.x.x testing 1 161 500
ipInReceives:93922700 ipOutRequests:698197 tcpInSegs:5765 tcpOutSegs:6490 udpInDatagrams:651963 udpOutDatagrams:592446 snmpInPkts:177927 snmpOutPkts:177927 icmpInMsgs:55300 icmpOutMsgs:99265
What do you think?
Yup, looks like the script works fine.
So back to one of my original questions which you keep avoiding. Do other graphs work fine?
So back to one of my original questions which you keep avoiding. Do other graphs work fine?
| Scripts: Monitor processes | RFC1213 MIB | DOCSIS Stats | Dell PowerEdge | Speedfan | APC UPS | DOCSIS CMTS | 3ware | Motorola Canopy |
| Guides: Windows Install | [HOWTO] Debug Windows NTFS permission problems |
| Tools: Windows All-in-one Installer |
Sorry I am not avoiding the question I just missed it.
Yes they do work fine standard SNMP graphs like Cisco Router/PIX- CPU & Memory Usage and scripts such as the SmokePingLike -1.1 and interface stats.
Samples attached.
Yes they do work fine standard SNMP graphs like Cisco Router/PIX- CPU & Memory Usage and scripts such as the SmokePingLike -1.1 and interface stats.
Samples attached.
- Attachments
-
- CPU & Mem.JPG (36.18 KiB) Viewed 11279 times
-
- nvRAM.JPG (24.3 KiB) Viewed 11279 times
-
- smokeping.JPG (31.52 KiB) Viewed 11279 times
Alright, good to know.
Now back to this script. Is test_host_router_snmpinpkts_813.rrd actually successfully getting updated now (aka the last modified time changes) every 5 minutes?
Looking through you cacti log file (medium logging is fine), Cacti is still returning data for the script, right? You're still not getting any graphs for this script?
Now back to this script. Is test_host_router_snmpinpkts_813.rrd actually successfully getting updated now (aka the last modified time changes) every 5 minutes?
Looking through you cacti log file (medium logging is fine), Cacti is still returning data for the script, right? You're still not getting any graphs for this script?
| Scripts: Monitor processes | RFC1213 MIB | DOCSIS Stats | Dell PowerEdge | Speedfan | APC UPS | DOCSIS CMTS | 3ware | Motorola Canopy |
| Guides: Windows Install | [HOWTO] Debug Windows NTFS permission problems |
| Tools: Windows All-in-one Installer |
All the graphs are comming out the same with invalid data entries and blank. As you can see from below the rrdtool is working but the script is still returning the original error when left to run through the poller.
08/29/2006 02:55:22 AM - POLLER: Poller[0] CACTI2RRD: /usr/bin/rrdtool update /var/www/html/cacti/rra/snmpinpkts_813.rrd --template 1156816501:U
ERROR: Not enough arguments
All the MIB Protocol scripts are the same.
I may try removing the SNMPv3 feilds from the script and data input method as it looks like the script is expecting something else from Cacti when run through the poller "ERROR: Not enough arguments".
08/29/2006 02:55:22 AM - POLLER: Poller[0] CACTI2RRD: /usr/bin/rrdtool update /var/www/html/cacti/rra/snmpinpkts_813.rrd --template 1156816501:U
ERROR: Not enough arguments
All the MIB Protocol scripts are the same.
I may try removing the SNMPv3 feilds from the script and data input method as it looks like the script is expecting something else from Cacti when run through the poller "ERROR: Not enough arguments".
- Attachments
-
- snmp_protocol_stats.JPG (89.97 KiB) Viewed 11274 times
-
- ip_protocol_stats.JPG (60.41 KiB) Viewed 11274 times
-
- combined_protocol.JPG (42.92 KiB) Viewed 11274 times
Last edited by stu_77 on Fri Nov 23, 2007 8:05 am, edited 1 time in total.
Don't modify the template, it's fine. rrdtool is expecting more fields of data to be given by cacti.
Try deleting all the data sources and rrd files related to the MIB protocol stuff and recreate it. Don't forget to clear the poller cache too after you've deleted the stuff. Something in cacti isn't working properly.
Did you happen to have any errors when you imported the template?
Try deleting all the data sources and rrd files related to the MIB protocol stuff and recreate it. Don't forget to clear the poller cache too after you've deleted the stuff. Something in cacti isn't working properly.
Did you happen to have any errors when you imported the template?
| Scripts: Monitor processes | RFC1213 MIB | DOCSIS Stats | Dell PowerEdge | Speedfan | APC UPS | DOCSIS CMTS | 3ware | Motorola Canopy |
| Guides: Windows Install | [HOWTO] Debug Windows NTFS permission problems |
| Tools: Windows All-in-one Installer |
This is what I received again from the poller after I cleared the cache and removed the graphs and data sources.
08/29/2006 05:10:22 PM - POLLER: Poller[0] CACTI2RRD: /usr/bin/rrdtool update /var/www/html/cacti/rra/ipinunknownprotos_839.rrd --template 1156867801:U
ERROR: Not enough arguments
Waiting on 1/1 pollers.
Waiting on 1/1 pollers.
Waiting on 1/1 pollers.
Should I remove all the templates and re-add them?
If so do you know how to go about doing this manually?
08/29/2006 05:10:22 PM - POLLER: Poller[0] CACTI2RRD: /usr/bin/rrdtool update /var/www/html/cacti/rra/ipinunknownprotos_839.rrd --template 1156867801:U
ERROR: Not enough arguments
Waiting on 1/1 pollers.
Waiting on 1/1 pollers.
Waiting on 1/1 pollers.
Should I remove all the templates and re-add them?
If so do you know how to go about doing this manually?
Last edited by stu_77 on Fri Nov 23, 2007 8:05 am, edited 1 time in total.
hmm, something is broken with the template (possibly a cacti bug I found last week). Export one of the templates in full so I can take a look at it.
After that, remove the templates and re-add them back. Are there any errors, like unmet dependency?
After that, remove the templates and re-add them back. Are there any errors, like unmet dependency?
| Scripts: Monitor processes | RFC1213 MIB | DOCSIS Stats | Dell PowerEdge | Speedfan | APC UPS | DOCSIS CMTS | 3ware | Motorola Canopy |
| Guides: Windows Install | [HOWTO] Debug Windows NTFS permission problems |
| Tools: Windows All-in-one Installer |
There do not appear to be any errors apart from the previous when the poller runs.
Here is the xml graph export and the script zipped.
Here is the xml graph export and the script zipped.
- Attachments
-
- cacti_graph_template_tcp_mib_tcp_protocol_statistics.xml
- (36.68 KiB) Downloaded 889 times
-
- ss_protocol_tcp.zip
- (781 Bytes) Downloaded 678 times
Hmm, well that template seems ok. I tested importing it in a test cacti environment and it was fine too. Back to the log file...
Alright, so there are three things we're interested in the log file when it's in debugging mode to make sure everything is working
1) The actual script running and returning values. Yours seems to be doing this fine from what I've seen.
2) For scripts which return multiple fields, cacti needs to map the outputted name to the data input field names. For example, notice in the MIB - Combined protocol traffic Data Input Method at the various Output Fields. They match the ones the script spits out. Look for entries in the log file which look like: Parsed MULTI output field 'ipInReceives:23423' [map ipInReceives->ipInReceives]. If you don't see any entries related to parsed multi output field, there is the problem.
3) Lastly, cacti needs to update the rrd file with the values collected. In the log file, these are the CACTI2RRD entries. Yours seems to be doing this, but not having any of the values Cacti collected.
Alright, so there are three things we're interested in the log file when it's in debugging mode to make sure everything is working
1) The actual script running and returning values. Yours seems to be doing this fine from what I've seen.
2) For scripts which return multiple fields, cacti needs to map the outputted name to the data input field names. For example, notice in the MIB - Combined protocol traffic Data Input Method at the various Output Fields. They match the ones the script spits out. Look for entries in the log file which look like: Parsed MULTI output field 'ipInReceives:23423' [map ipInReceives->ipInReceives]. If you don't see any entries related to parsed multi output field, there is the problem.
3) Lastly, cacti needs to update the rrd file with the values collected. In the log file, these are the CACTI2RRD entries. Yours seems to be doing this, but not having any of the values Cacti collected.
| Scripts: Monitor processes | RFC1213 MIB | DOCSIS Stats | Dell PowerEdge | Speedfan | APC UPS | DOCSIS CMTS | 3ware | Motorola Canopy |
| Guides: Windows Install | [HOWTO] Debug Windows NTFS permission problems |
| Tools: Windows All-in-one Installer |
I have now installed a second Cacti-0.8.6h system on Linux RH9 using a new version of MySQL and the Cactid instead of the cmd.php. This is now a fresh install with no plugins all the graphs are working and processing correctly through cactid.
Unfortunately the MIB Protocol graphs are still not working correctly but the cactid is reporting a different error now (as below).
What do you think?
I know that it sounds strange because PHP is PHP at the end of the day but could this be a funny Windows to Linux compatibility thing?
Unfortunately the MIB Protocol graphs are still not working correctly but the cactid is reporting a different error now (as below).
What do you think?
I know that it sounds strange because PHP is PHP at the end of the day but could this be a funny Windows to Linux compatibility thing?
Last edited by stu_77 on Fri Nov 23, 2007 8:06 am, edited 1 time in total.
Switch to cmd.php. If the scripts return data, its a cactid problem.
Once again, if you fire up the script server and test it, does it return data? If so, then the script is functioning properly and something else with Cacti is not.
Once again, if you fire up the script server and test it, does it return data? If so, then the script is functioning properly and something else with Cacti is not.
| Scripts: Monitor processes | RFC1213 MIB | DOCSIS Stats | Dell PowerEdge | Speedfan | APC UPS | DOCSIS CMTS | 3ware | Motorola Canopy |
| Guides: Windows Install | [HOWTO] Debug Windows NTFS permission problems |
| Tools: Windows All-in-one Installer |
I have a problem with my IP MIB - IP Protocol Statistics (others graphs are working). All values are equals to 0. Which is not completely coherent with the smpwalk run :
What i forgot? Thanks for your held.
Code: Select all
snmpwalk -v 1 -c public localhost .1.3.6.1.2.1.4
SNMPv2-SMI::mib-2.4.1.0 = INTEGER: 2
SNMPv2-SMI::mib-2.4.2.0 = INTEGER: 64
SNMPv2-SMI::mib-2.4.3.0 = Counter32: 4893124
SNMPv2-SMI::mib-2.4.4.0 = Counter32: 0
SNMPv2-SMI::mib-2.4.5.0 = Counter32: 0
SNMPv2-SMI::mib-2.4.6.0 = Counter32: 0
SNMPv2-SMI::mib-2.4.7.0 = Counter32: 0
SNMPv2-SMI::mib-2.4.8.0 = Counter32: 0
SNMPv2-SMI::mib-2.4.9.0 = Counter32: 4876028
SNMPv2-SMI::mib-2.4.10.0 = Counter32: 6234084
SNMPv2-SMI::mib-2.4.11.0 = Counter32: 0
SNMPv2-SMI::mib-2.4.12.0 = Counter32: 0
SNMPv2-SMI::mib-2.4.13.0 = INTEGER: 0
SNMPv2-SMI::mib-2.4.14.0 = Counter32: 0
SNMPv2-SMI::mib-2.4.15.0 = Counter32: 0
SNMPv2-SMI::mib-2.4.16.0 = Counter32: 0
SNMPv2-SMI::mib-2.4.17.0 = Counter32: 0
SNMPv2-SMI::mib-2.4.18.0 = Counter32: 0
SNMPv2-SMI::mib-2.4.19.0 = Counter32: 0
SNMPv2-SMI::mib-2.4.23.0 = Counter32: 0
Looks like your device doesn't fully implement the IP MIB stuff OR nothing is really going on. You need to talk to the vendor either way to find out.
| Scripts: Monitor processes | RFC1213 MIB | DOCSIS Stats | Dell PowerEdge | Speedfan | APC UPS | DOCSIS CMTS | 3ware | Motorola Canopy |
| Guides: Windows Install | [HOWTO] Debug Windows NTFS permission problems |
| Tools: Windows All-in-one Installer |
Who is online
Users browsing this forum: No registered users and 6 guests