Hi guys , im traying to graph traffic on my Arista device.
It seems Im having a 32 bits counter.
I have been looking around EOS config and librenms but can not change counters config.
This is what I got:
Not sure why do you think from the graph that it’s using a 32-bit counter? Mostly you will have issues with very busy ports where a counter roll-over occurs all the time, but that’s not what you are seeing in the graph with the low bandwidth.
Does your polling interval match your rrd step setting?
Dear Elias , thanks for your response.
Im using default values … aI never changed this setting, in fact I have two more devices and graph are ok on them.
Anyway , Im traying to check values you mentioned:
looking at global settings -> Poller -> rrd value -> 300.
and looking at crontab file:
´´´
33 */6 * * * librenms /opt/librenms/cronic /opt/librenms/discovery-wrapper.py 1
*/5 * * * * librenms /opt/librenms/discovery.php -h new >> /dev/null 2>&1
*/5 * * * * librenms /opt/librenms/cronic /opt/librenms/poller-wrapper.py 16
* * * * * librenms /opt/librenms/alerts.php >> /dev/null 2>&1
*/5 * * * * librenms /opt/librenms/poll-billing.php >> /dev/null 2>&1
01 * * * * librenms /opt/librenms/billing-calculate.php >> /dev/null 2>&1
*/5 * * * * librenms /opt/librenms/check-services.php >> /dev/null 2>&1
# Daily maintenance script. DO NOT DISABLE!
# If you want to modify updates:
# Switch to monthly stable release: https://docs.librenms.org/General/Releases/
# Disable updates: https://docs.librenms.org/General/Updating/
15 0 * * * librenms /opt/librenms/daily.sh >> /dev/null 2>&1
*/5 * * * * librenms /opt/librenms/services-wrapper.py 1
I think they are ok.
Any other idea ?
Hmm I wonder what could cause it then. Did you try to rediscover the device already? If not you could try that, go to edit the device and then click on the red rediscover button.
Hi , Elias.
Already tryied : edit -> Device settings -> rediscover device.
Didnt work.
Also remove and add device … but have same result.
btw:
Why do you consider my problem is not related to interface counter 32 or 64 bits.
Time ago working on cacti , I got same problem when using wrong bit size query on counters.
I can not found same setting with librensm,
Finally:
Looking at interface oid , I can confirm that counters are 32 bits long:
IF-MIB::ifInOctets.1 = Counter32: 3451951301
IF-MIB::ifInOctets.2 = Counter32: 2337164024
IF-MIB::ifInOctets.3 = Counter32: 0
IF-MIB::ifInOctets.4 = Counter32: 0
IF-MIB::ifInOctets.5 = Counter32: 0
IF-MIB::ifInOctets.6 = Counter32: 0
IF-MIB::ifInOctets.7 = Counter32: 0
IF-MIB::ifInOctets.8 = Counter32: 0
IF-MIB::ifInOctets.9 = Counter32: 0
IF-MIB::ifInOctets.10 = Counter32: 742870
IF-MIB::ifInOctets.13 = Counter32: 1494242188
IF-MIB::ifInOctets.14 = Counter32: 16352611
IF-MIB::ifInOctets.15 = Counter32: 1700445760
IF-MIB::ifInOctets.16 = Counter32: 1363378023
IF-MIB::ifInOctets.17 = Counter32: 1419606080
IF-MIB::ifInOctets.19 = Counter32: 2071274
IF-MIB::ifInOctets.20 = Counter32: 3218534879
IF-MIB::ifInOctets.21 = Counter32: 2263362607
IF-MIB::ifInOctets.22 = Counter32: 2850393035
IF-MIB::ifInOctets.23 = Counter32: 2885692280
IF-MIB::ifInOctets.24 = Counter32: 0
IF-MIB::ifInOctets.25 = Counter32: 2548301821
IF-MIB::ifInOctets.26 = Counter32: 4292117663
Any other idea would be wellcome.
Regards.–
@Leandro_Roggerone did you configure the device with SNMP v1? (64bit counters only work with SNMP v2c or v3)
Hello Murrant.
According to EOS manual.
You enable snmp agent setting its community , but nothing regarding snmp version, in my case:
snmp-server community mycommunity ro.
After that arista will respond to version 1 and 2.
Yo can also add an user and authentication methos for snmp ver3.
I already tested all three methods.
From the librensm side:
If I create the device using version 1 or 2 have same graph issue:
traffic above 115Mpbs is chopped.
Regards.
Leandro