What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general.

Learn more

PRTG Network Monitor

Intuitive to Use. Easy to manage.
More than 500,000 users rely on Paessler PRTG every day. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free Download

Top Tags


View all Tags

Setting up sensor with .mib file

Votes:

0

Hello Everyone,

I am trying to monitor backup jobs done with ''Veam Backup and Replication''. For that, I want to use the .mib file provided by veeam in order to create the sensor automatically.

I am using the SNMP tester on the Prtg Probe in order to check whether I can get data from the VM Veeam runs on. When requesting the ''device uptime'', I get a satisfying response seen bellow:

24.08.2018 11:36:33 (12 ms) : SNMP V2c
24.08.2018 11:36:33 (16 ms) : Uptime
24.08.2018 11:36:33 (22 ms) : SNMP Datatype: ASN_TIMETICKS
24.08.2018 11:36:33 (25 ms) : -------
24.08.2018 11:36:33 (29 ms) : DISMAN-EVENT-MIB::sysUpTimeInstance = 297805 ( 49 minutes 38 seconds )
24.08.2018 11:36:33 (34 ms) : SNMP Datatype: ASN_TIMETICKS
24.08.2018 11:36:33 (37 ms) : HOST-RESOURCES-MIB::hrSystemUptime.0 = 806425776 ( 93 days )
24.08.2018 11:36:33 (41 ms) : Done

But when using the .oidlib file, the tester returns the following:

24.08.2018 11:20:58 Start Scan
24.08.2018 11:20:58 VEEAM-MIB|backup|backup job id 1.3.6.1.4.1.31023.1.1.101.0
24.08.2018 11:20:58 VEEAM-MIB|backup|backup job name 1.3.6.1.4.1.31023.1.1.102.0
24.08.2018 11:20:58 VEEAM-MIB|backup|backup job result 1.3.6.1.4.1.31023.1.1.103.0
24.08.2018 11:20:58 VEEAM-MIB|backup|backup job comment 1.3.6.1.4.1.31023.1.1.104.0
24.08.2018 11:20:58 VEEAM-MIB|backup|vm name 1.3.6.1.4.1.31023.1.1.105.0
24.08.2018 11:20:58 VEEAM-MIB|backup|source host name 1.3.6.1.4.1.31023.1.1.106.0
24.08.2018 11:20:58 VEEAM-MIB|backup|vm backup result 1.3.6.1.4.1.31023.1.1.107.0
24.08.2018 11:20:58 VEEAM-MIB|backup|vm backup comment 1.3.6.1.4.1.31023.1.1.108.0
24.08.2018 11:20:58 VEEAM-MIB|backup|session id 1.3.6.1.4.1.31023.1.1.109.0
24.08.2018 11:20:58 VEEAM-MIB|backup|initiator name 1.3.6.1.4.1.31023.1.1.110.0
24.08.2018 11:20:58 VEEAM-MIB|backup|initiator sid 1.3.6.1.4.1.31023.1.1.111.0
24.08.2018 11:20:58 VEEAM-MIB|backup|vm restore point id 1.3.6.1.4.1.31023.1.1.112.0
24.08.2018 11:20:58 VEEAM-MIB|backup|vm restore point creation time 1.3.6.1.4.1.31023.1.1.113.0
24.08.2018 11:20:58 VEEAM-MIB|backup|target host 1.3.6.1.4.1.31023.1.1.114.0
24.08.2018 11:20:58 VEEAM-MIB|backup|target dir 1.3.6.1.4.1.31023.1.1.115.0
24.08.2018 11:20:58 VEEAM-MIB|backup|transfer status 1.3.6.1.4.1.31023.1.1.116.0
24.08.2018 11:20:58 VEEAM-MIB|backup|transfer time 1.3.6.1.4.1.31023.1.1.117.0
24.08.2018 11:20:58 VEEAM-MIB|backup|transfer file list 1.3.6.1.4.1.31023.1.1.118.0
24.08.2018 11:20:58 VEEAM-MIB|backup|not transfer file list 1.3.6.1.4.1.31023.1.1.119.0
24.08.2018 11:20:58 VEEAM-MIB|backup|mount server name 1.3.6.1.4.1.31023.1.1.120.0

Found OIDs:
No OIDs found

Furthermore, when scanning for a specific OID I get the following response:

24.08.2018 11:21:07 (8 ms) : Device: 10.254.1.8
24.08.2018 11:21:07 (11 ms) : SNMP V2c
24.08.2018 11:21:07 (15 ms) : Custom OID 1.3.6.1.4.1.31023.1.1.109.0
24.08.2018 11:21:07 (20 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
24.08.2018 11:21:07 (24 ms) : -------
24.08.2018 11:21:07 (45 ms) : Value: No such object (SNMP error # 222)
24.08.2018 11:21:07 (48 ms) : Done

I am new to SNMP and the usage of .mib files, so please excuse me if this is some trivial problem. What I would like to know is, how I get the objects from the .mib file to be recognized properly?

Any help is appreciated very much!

Best Regards,
Dominik

mib-importer oid prtg snmp snmp-sensor

Created on Aug 24, 2018 9:50:26 AM

Last change on Aug 24, 2018 9:58:54 AM by Luciano Lingnau [Paessler]



1 Reply

Votes:

0

Hi Dominik,

To me it seems you've done everything correctly, SNMP itself is working fine. The device somehow doesn't answer to the SNMP calls for the selected OIDs.

We recommend contacting the vendor regarding this issue.

Thank you!

Andreas Günther
Support Team, Paessler AG

Created on Aug 27, 2018 7:21:04 AM by Andreas Günther [Paessler Support]




Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.