We are tracking several devices using MRTG without issue, however one Cisco SG 550X switch is not updating properly. MRTG says there are zero b/s. Watching I can see the counters increment:
snmpget -v2c -c Readonly 1.1.1.1 ifInOctets.1
IF-MIB::ifInOctets.1 = Counter32: 1581501790
-bash-4.2$ snmpget -v2c -c Readonly 1.1.1.1 ifInOctets.1
IF-MIB::ifInOctets.1 = Counter32: 1581504122
In /var/www/mrtg/1.1.1.1_te1_0_1.log I see the top number change but the other numbers never update:
head /var/www/mrtg/1.1.1.1_te1_0_1.log
1578613862 1580125685 3063015779
1578613862 0 0 0 0
1578613562 0 0 0 0
1578613500 0 0 0 0
1578613200 0 0 0 0
1578612900 0 0 0 0
1578612600 0 0 0 0
1578612300 0 0 0 0
1578612000 0 0 0 0
1578611700 0 0 0 0
head /var/www/mrtg/1.1.1.1_te1_0_1.old
1578613562 1579785384 3062732903
1578613562 0 0 0 0
1578613262 0 0 0 0
1578613200 0 0 0 0
1578612900 0 0 0 0
1578612600 0 0 0 0
1578612300 0 0 0 0
1578612000 0 0 0 0
1578611700 0 0 0 0
1578611400 0 0 0 0
MRTG has always worked so effortlessly for me. I am wondering if it has to do with it being a 10 G interface?
Thank you for any direction that you may be able to provide.
On Thursday, January 9, 2020 at 7:17:54 PM UTC-5, Cris Collins wrote:
We are tracking several devices using MRTG without issue, however one Cisco SG 550X switch is not updating properly. MRTG says there are zero b/s. Watching I can see the counters increment:
snmpget -v2c -c Readonly 1.1.1.1 ifInOctets.1
IF-MIB::ifInOctets.1 = Counter32: 1581501790
-bash-4.2$ snmpget -v2c -c Readonly 1.1.1.1 ifInOctets.1 IF-MIB::ifInOctets.1 = Counter32: 1581504122
In /var/www/mrtg/1.1.1.1_te1_0_1.log I see the top number change but the other numbers never update:
head /var/www/mrtg/1.1.1.1_te1_0_1.log
1578613862 1580125685 3063015779
1578613862 0 0 0 0
1578613562 0 0 0 0
1578613500 0 0 0 0
1578613200 0 0 0 0
1578612900 0 0 0 0
1578612600 0 0 0 0
1578612300 0 0 0 0
1578612000 0 0 0 0
1578611700 0 0 0 0
head /var/www/mrtg/1.1.1.1_te1_0_1.old
1578613562 1579785384 3062732903
1578613562 0 0 0 0
1578613262 0 0 0 0
1578613200 0 0 0 0
1578612900 0 0 0 0
1578612600 0 0 0 0
1578612300 0 0 0 0
1578612000 0 0 0 0
1578611700 0 0 0 0
1578611400 0 0 0 0
MRTG has always worked so effortlessly for me. I am wondering if it has to do with it being a 10 G interface?
Thank you for any direction that you may be able to provide.
Debug Feature is showing the following:
2020-01-10 09:37:21 -- Started mrtg with config '/home/MRTG_CFG/m.cfg' 2020-01-10 09:37:21 -- --snpo: run snmpget from ifInOctets&ifOutOctets:Readonly@1.1.1.1
2020-01-10 09:37:21 -- --snpo: (0) Confcache Match te1/0/1 -> .1
2020-01-10 09:37:21 -- --snpo: (1) Confcache Match te1/0/1 -> .1
2020-01-10 09:37:21 -- --snpo: SNMPGet from Readonly@1.1.1.1: -- ifName.1,ifInOctets.1,ifName.1,ifOutOctets.1,sysUptime,sysName
2020-01-10 09:37:22 -- --snpo: SNMPfound -- 'te1/0/1', '1653990221', 'te1/0/1', '3125895878', '69 days, 19:24:47', 'm-rtr'
2020-01-10 09:37:22 -- --snpo: (0) Name crosscheck OK
2020-01-10 09:37:22 -- --snpo: (1) Name crosscheck OK
2020-01-10 09:37:22 -- --snpo: run snmpget from ifInOctets&ifOutOctets:Readonly@1.1.1.1
2020-01-10 09:37:22 -- --snpo: (0) Confcache Match te1/0/2 -> .2
2020-01-10 09:37:22 -- --snpo: (1) Confcache Match te1/0/2 -> .2
2020-01-10 09:37:22 -- --snpo: SNMPGet from Readonly@1.1.1.1: -- ifName.2,ifInOctets.2,ifName.2,ifOutOctets.2,sysUptime,sysName
2020-01-10 09:37:22 -- --snpo: SNMPfound -- 'te1/0/2', '1946527094', 'te1/0/2', '3408887051', '69 days, 19:24:47', 'm-rtr'
2020-01-10 09:37:22 -- --snpo: (0) Name crosscheck OK
2020-01-10 09:37:22 -- --snpo: (1) Name crosscheck OK
2020-01-10 09:37:22 -- --snpo: run snmpget from ifInOctets&ifOutOctets:Readonly@1.1.1.1
2020-01-10 09:37:36 -- --log: /usr/bin/rateup /var/www/mrtg/ 1.1.1.1_te1_0_1 1578667042 -Z u 1653990221 3125895878 125 c #00cc00 #0000ff #006600 #ff00ff k 1000 i /var/www/mrtg/1.1.1.1_te1_0_1-day.png -125 -125 400 100 1 1 1 300 1 4 1 %Y-%m-%d %H:%M 0
2020-01-10 09:37:36 -- --log: /usr/bin/rateup /var/www/mrtg/ 1.1.1.1_te1_0_2 1578667042 -Z u 1946527094 3408887051 12 c #00cc00 #0000ff #006600 #ff00ff k 1000 i /var/www/mrtg/1.1.1.1_te1_0_2-day.png -12 -12 400 100 1 1 1 300 1 4 1 %Y-%m-%d %H:%M 0
On Friday, January 10, 2020 at 10:07:09 AM UTC-5, Cris Collins wrote:
On Thursday, January 9, 2020 at 7:17:54 PM UTC-5, Cris Collins wrote:
We are tracking several devices using MRTG without issue, however one Cisco SG 550X switch is not updating properly. MRTG says there are zero b/s. Watching I can see the counters increment:
snmpget -v2c -c Readonly 1.1.1.1 ifInOctets.1
IF-MIB::ifInOctets.1 = Counter32: 1581501790
-bash-4.2$ snmpget -v2c -c Readonly 1.1.1.1 ifInOctets.1 IF-MIB::ifInOctets.1 = Counter32: 1581504122
In /var/www/mrtg/1.1.1.1_te1_0_1.log I see the top number change but the other numbers never update:
head /var/www/mrtg/1.1.1.1_te1_0_1.log
1578613862 1580125685 3063015779
1578613862 0 0 0 0
1578613562 0 0 0 0
1578613500 0 0 0 0
1578613200 0 0 0 0
1578612900 0 0 0 0
1578612600 0 0 0 0
1578612300 0 0 0 0
1578612000 0 0 0 0
1578611700 0 0 0 0
head /var/www/mrtg/1.1.1.1_te1_0_1.old
1578613562 1579785384 3062732903
1578613562 0 0 0 0
1578613262 0 0 0 0
1578613200 0 0 0 0
1578612900 0 0 0 0
1578612600 0 0 0 0
1578612300 0 0 0 0
1578612000 0 0 0 0
1578611700 0 0 0 0
1578611400 0 0 0 0
MRTG has always worked so effortlessly for me. I am wondering if it has to do with it being a 10 G interface?
Thank you for any direction that you may be able to provide.
Debug Feature is showing the following:
2020-01-10 09:37:21 -- Started mrtg with config '/home/MRTG_CFG/m.cfg' 2020-01-10 09:37:21 -- --snpo: run snmpget from ifInOctets&ifOutOctets:Readonly@1.1.1.1
2020-01-10 09:37:21 -- --snpo: (0) Confcache Match te1/0/1 -> .1
2020-01-10 09:37:21 -- --snpo: (1) Confcache Match te1/0/1 -> .1
2020-01-10 09:37:21 -- --snpo: SNMPGet from Readonly@1.1.1.1: -- ifName.1,ifInOctets.1,ifName.1,ifOutOctets.1,sysUptime,sysName
2020-01-10 09:37:22 -- --snpo: SNMPfound -- 'te1/0/1', '1653990221', 'te1/0/1', '3125895878', '69 days, 19:24:47', 'm-rtr'
2020-01-10 09:37:22 -- --snpo: (0) Name crosscheck OK
2020-01-10 09:37:22 -- --snpo: (1) Name crosscheck OK
2020-01-10 09:37:22 -- --snpo: run snmpget from ifInOctets&ifOutOctets:Readonly@1.1.1.1
2020-01-10 09:37:22 -- --snpo: (0) Confcache Match te1/0/2 -> .2
2020-01-10 09:37:22 -- --snpo: (1) Confcache Match te1/0/2 -> .2
2020-01-10 09:37:22 -- --snpo: SNMPGet from Readonly@1.1.1.1: -- ifName.2,ifInOctets.2,ifName.2,ifOutOctets.2,sysUptime,sysName
2020-01-10 09:37:22 -- --snpo: SNMPfound -- 'te1/0/2', '1946527094', 'te1/0/2', '3408887051', '69 days, 19:24:47', 'm-rtr'
2020-01-10 09:37:22 -- --snpo: (0) Name crosscheck OK
2020-01-10 09:37:22 -- --snpo: (1) Name crosscheck OK
2020-01-10 09:37:22 -- --snpo: run snmpget from ifInOctets&ifOutOctets:Readonly@1.1.1.1
how mrtgcfg comes up with MaxBytes.2020-01-10 09:37:36 -- --log: /usr/bin/rateup /var/www/mrtg/ 1.1.1.1_te1_0_1 1578667042 -Z u 1653990221 3125895878 125 c #00cc00 #0000ff #006600 #ff00ff k 1000 i /var/www/mrtg/1.1.1.1_te1_0_1-day.png -125 -125 400 100 1 1 1 300 1 4 1 %Y-%m-%d %H:%M 0
2020-01-10 09:37:36 -- --log: /usr/bin/rateup /var/www/mrtg/ 1.1.1.1_te1_0_2 1578667042 -Z u 1946527094 3408887051 12 c #00cc00 #0000ff #006600 #ff00ff k 1000 i /var/www/mrtg/1.1.1.1_te1_0_2-day.png -12 -12 400 100 1 1 1 300 1 4 1 %Y-%m-%d %H:%M 0
MsxBytes registered with the Cisco SG550X as 125 for some reason. I manually changed it to 125000000 and it seems to be working now. I will check for accuracy over the net couple of days. Note the "-12" and "-125" in the rateup examples above. Not sure
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 286 |
Nodes: | 16 (2 / 14) |
Uptime: | 83:45:16 |
Calls: | 6,495 |
Calls today: | 6 |
Files: | 12,096 |
Messages: | 5,276,885 |