Hi, I've been trying to monitor VLAN´s bandwidth usage of a propietary equipment that is a non standard OID (.1.3.6.1.4.1.6527.3.1.2.4.3.6.1.5.200.38010880.20), but until now, with no success, i used the mib importer and the propietary MIBs in order to create a new library for the PRTG Network Monitor to use it, then I tested it with the SNMP tester and get this result

Found OIDs:
1.3.6.1.4.1.6527.3.1.2.4.3.1.0: TIMETRA-SAP-MIB|tmnx sap objs|sap num entries,Undefined,,(not defined),0
.1.3.6.1.4.1.6527.3.1.2.4.3.6.1.5.200.38010880.20: TIMETRA-SAP-MIB|tmnx sap objs|sap vlan20,Undefined,,(not defined),0

Testing OIDs... Test 1.3.6.1.4.1.6527.3.1.2.4.3.1.0: value=12 #

Test .1.3.6.1.4.1.6527.3.1.2.4.3.6.1.5.200.38010880.20: value=14408 Bytes (This is my vlan and the righ reading at that moment)

I suppoused this was enough for the sensor SNMP traffic sensor to detect my vlan and to use it, but nothing happened, then I tried a custom sensor with my OID but I only get an accumulative value, not a bandwidth reading.

Could some of you help me? Is this even possible? Am I doing the right thing

Article Comments

Hello,

with the SNMP Custom Sensor, please make sure it's set as a 'Delta'-Type sensor. Otherwise, it may be necessary to import an MIB from the vendor.

best regards.


Mar, 2012 - Permalink

Hi, Thanks for your answer its working now!!! but something seems to be wrong, the messure i got is different from the amount of traffic i generate, I mean, i generate with an exfo a stream of 2 Mbps, inside my equipment i read 0.19% utilization in my vlan (the interface is 1000Mbps, so the reading is close enough), but the prtg give me reads of only 164 that i guess are kbps, my oid give me octects, i try to modify the readings by editing the muultiplier and division value in the senso, and with multiplier=11 and división=1.5 i get a value close enough, but this seems to be a little dirty, does anyone know why this estrange readings?

BR


Mar, 2012 - Permalink

Im so sorry, with my last reply the problem was that i got the wrong OID the readings I got were from and OID of packets not octects, that's why the wrong messures, now i put the right OID in Octects and the PRTG is working perfect!!! thanks for your support and patient!!!


Mar, 2012 - Permalink