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

SNMP Library Import and Usage for Barracuda MIBs

Votes:

0

I have two Barracuda devices;

  • Load Balancer 340
  • Spam Firewall 400

PRTG is able to poll both of these devices using the standard, auto-discovered SNMP templates (CPU, MEM, Network, etc). Works fine, but I want to get the manufacturer MIBs working now.

I obtained the manufacturer MIBs by downloading them straight off the devices;

http://[SPAM-IP]:8000/Barracuda-SPAM-MIB.txt
http://[LB-IP]:8000/Barracuda-LB-MIB.txt

Read the documentation and answers available and did the following;

  1. Loaded the manufacturer's MIBs into PRTG using the MIB Importer Tool.
  2. Saved the PRTG .oidlib into the SNMPLIBS directory.
  3. Tried to add the SNMP Library sensor via PRTG, but I get the following error;
Sorry, the scan for available monitoring items has failed! Error Message:"No available interfaces on this device (code: PE049)"

I have run the SNMP Tester using the manufacturer MIB and it's able to poll successfully.

Both Barracuda devices (LB & Spam) are exhibiting the same error.

  • PRTG Version: 8.4.2.2321
  • Clustered Configuration

Thanks for any help.

barracuda prtg snmp

Created on Jul 16, 2011 8:16:34 PM

Last change on Jun 30, 2016 8:26:50 AM by Luciano Lingnau [Paessler]



6 Replies

Votes:

0

hallo,

you are using the same SNMP settings in the tester as well as in PRTG (device settings)

you started the SNMP Tester on the PRTG server and scanned against the devices?

Created on Jul 18, 2011 1:20:04 PM by Aurelio Lombardi [Paessler Support]



Votes:

3

Yes, I am using the same settings (community name, version, port, etc) on the PRTG probe and the SNMP Tester app. Running both from the same machine.

Using the SNMP Tester App with the imported MIB that was converted to a PRTG .oidlib.

Here's the output; (the formatting is mess up. i tried using <pre> and <code> markup.)

Paessler SNMP Tester 3.2
Device: smtp1.company.com (Barracuda Spam Firewall 400)

Scanning OIDs
from library: "C:\Program Files (x86)\PRTG Network Monitor\snmplibs\Barracuda-SPAM.oidlib"
on device: smtp1.company.com
7/18/2011 11:52:46 AM Start Scan
7/18/2011 11:52:46 AM Barracuda-SPAM|bspam|in queue size 1.3.6.1.4.1.20632.2.2.0
7/18/2011 11:52:46 AM Barracuda-SPAM|bspam|out queue size 1.3.6.1.4.1.20632.2.3.0
7/18/2011 11:52:46 AM Barracuda-SPAM|bspam|deferred queue size 1.3.6.1.4.1.20632.2.4.0
7/18/2011 11:52:46 AM Barracuda-SPAM|bspam|avg email latency 1.3.6.1.4.1.20632.2.5.0
7/18/2011 11:52:46 AM Barracuda-SPAM|bspam|notify queue size 1.3.6.1.4.1.20632.2.8.0

Found OIDs:
No OIDs found

---
Paessler SNMP Tester 3.2
Device: lb1.company.com (Barracuda Load Balancer 340)

Scanning OIDs
from library: "C:\Program Files (x86)\PRTG Network Monitor\snmplibs\Barracuda-LB.oidlib"
on device: lb1.company.com
7/18/2011 11:55:32 AM Start Scan
7/18/2011 11:55:32 AM Barracuda-LB|blb|system active services 1.3.6.1.4.1.20632.5.2.0
7/18/2011 11:55:32 AM Barracuda-LB|blb|system operating servers 1.3.6.1.4.1.20632.5.3.0
7/18/2011 11:55:32 AM Barracuda-LB|blb|l4 tcp connections 1.3.6.1.4.1.20632.5.6.0
7/18/2011 11:55:32 AM Barracuda-LB|blb|rdpuser sessions 1.3.6.1.4.1.20632.5.8.0
7/18/2011 11:55:32 AM Barracuda-LB|blb|service bandwidth 1.3.6.1.4.1.20632.5.9.0
7/18/2011 11:55:32 AM Barracuda-LB|blb|total bandwidth to lb 1.3.6.1.4.1.20632.5.10.0
7/18/2011 11:55:32 AM Barracuda-LB|blb|real server bandwidth 1.3.6.1.4.1.20632.5.11.0
7/18/2011 11:55:32 AM Barracuda-LB|blb|cluster status 1.3.6.1.4.1.20632.5.12.0
7/18/2011 11:55:32 AM Barracuda-LB|blb|system load 1.3.6.1.4.1.20632.5.13.0
7/18/2011 11:55:32 AM Barracuda-LB|blb|cputemperature 1.3.6.1.4.1.20632.5.14.0
7/18/2011 11:55:32 AM Barracuda-LB|blb|firmware storage 1.3.6.1.4.1.20632.5.15.0
7/18/2011 11:55:32 AM Barracuda-LB|blb|mail log storage 1.3.6.1.4.1.20632.5.16.0
7/18/2011 11:55:32 AM Barracuda-LB|blb|operation mode 1.3.6.1.4.1.20632.5.17.0
7/18/2011 11:55:32 AM Barracuda-LB|blb|system active services 1.3.6.1.4.1.20632.5.2.0
7/18/2011 11:55:32 AM Barracuda-LB|blb|system operating servers 1.3.6.1.4.1.20632.5.3.0
7/18/2011 11:55:32 AM Barracuda-LB|blb|l4 tcp connections 1.3.6.1.4.1.20632.5.6.0
7/18/2011 11:55:32 AM Barracuda-LB|blb|rdpuser sessions 1.3.6.1.4.1.20632.5.8.0
7/18/2011 11:55:32 AM Barracuda-LB|blb|service bandwidth 1.3.6.1.4.1.20632.5.9.0
7/18/2011 11:55:32 AM Barracuda-LB|blb|total bandwidth to lb 1.3.6.1.4.1.20632.5.10.0
7/18/2011 11:55:32 AM Barracuda-LB|blb|real server bandwidth 1.3.6.1.4.1.20632.5.11.0
7/18/2011 11:55:32 AM Barracuda-LB|blb|cluster status 1.3.6.1.4.1.20632.5.12.0
7/18/2011 11:55:32 AM Barracuda-LB|blb|system load 1.3.6.1.4.1.20632.5.13.0
7/18/2011 11:55:32 AM Barracuda-LB|blb|cputemperature 1.3.6.1.4.1.20632.5.14.0
7/18/2011 11:55:32 AM Barracuda-LB|blb|firmware storage 1.3.6.1.4.1.20632.5.15.0
7/18/2011 11:55:32 AM Barracuda-LB|blb|mail log storage 1.3.6.1.4.1.20632.5.16.0
7/18/2011 11:55:32 AM Barracuda-LB|blb|operation mode 1.3.6.1.4.1.20632.5.17.0

Found OIDs:
No OIDs found

---
Here's a simple uptime query that works;

Paessler SNMP Tester 3.2
Device: lb1.company.com

7/18/2011 11:57:29 AM (19 ms) : Start using SNMP V2c
7/18/2011 11:57:29 AM (27 ms) : -------
7/18/2011 11:57:29 AM (32 ms) : Value: 16400779
7/18/2011 11:57:29 AM (35 ms) : Done

--- I am going to reach out to Barracuda to see if they can help.

Created on Jul 18, 2011 5:01:07 PM

Last change on Sep 4, 2015 9:30:44 AM by Luciano Lingnau [Paessler]



Votes:

1

I think I found the problem. snmpget is useful debug tool. Using the correct OID number I get data back.

snmpget -v2c -c company lb1.company.com 1.3.6.1.4.1.20632.5.11

SNMPv2-SMI::enterprises.20632.5.11 = STRING: "10.10.11.202=0 - 10.10.11.223=2 - 10.10.11.91=5176 - 10.10.11.81=6062 - 10.10.11.105=2804 - 10.10.11.106=3045 - 10.10.11.85=253079 - 10.10.11.95=129526 - 10.10.11.37=191923 - 10.10.11.35=219640 - 10.10.11.99=79 - 10.10.11.83=189 - 10.10.11.82=1 - 10.10.11.88=0 - "

Looking closely at the manufacturer MIB data. Notice the OID ending digits, .11, .12, .13, etc.

1.3.6.1.4.1.20632.5.11 -- RealServerBandwidth
1.3.6.1.4.1.20632.5.12 -- ClusterStatus
1.3.6.1.4.1.20632.5.13 -- SystemLoad
1.3.6.1.4.1.20632.5.14 -- CPUTemperature
1.3.6.1.4.1.20632.5.15 -- FirmwareStorage
1.3.6.1.4.1.20632.5.16 -- MailLogStorage
1.3.6.1.4.1.20632.5.17 -- OperationMode
Traps:
1.3.6.1.4.1.20632.5.1.2  -- CpuFanDead 
1.3.6.1.4.1.20632.5.1.3  -- SysFanDead  
1.3.6.1.4.1.20632.5.1.4  -- CpuTempHigh  
                * 1.3.6.1.4.1.20632.5.1.5  -- FirmwareStorageHigh  
                * 1.3.6.1.4.1.20632.5.1.6  -- LogsStorageHigh
                * 1.3.6.1.4.1.20632.5.1.7  -- ServiceUp  
                * 1.3.6.1.4.1.20632.5.1.8  -- ServiceDown  
                * 1.3.6.1.4.1.20632.5.1.9  -- ServerUp  
                * 1.3.6.1.4.1.20632.5.1.10 -- ServerDown  
                * 1.3.6.1.4.1.20632.5.1.11 -- OpenConnsLimitReached 
                * 1.3.6.1.4.1.20632.5.1.12 -- CpsLimitReached

Looking at the output from the PRTG SNMP Tester. Notice the ending digits are always .0

/2011 12:04:43 PM Start Scan
7/18/2011 12:04:43 PM Barracuda-LB|blb|system active services 1.3.6.1.4.1.20632.5.2.0
7/18/2011 12:04:43 PM Barracuda-LB|blb|system operating servers 1.3.6.1.4.1.20632.5.3.0
7/18/2011 12:04:43 PM Barracuda-LB|blb|l4 tcp connections 1.3.6.1.4.1.20632.5.6.0
7/18/2011 12:04:43 PM Barracuda-LB|blb|rdpuser sessions 1.3.6.1.4.1.20632.5.8.0
7/18/2011 12:04:43 PM Barracuda-LB|blb|service bandwidth 1.3.6.1.4.1.20632.5.9.0
7/18/2011 12:04:43 PM Barracuda-LB|blb|total bandwidth to lb 1.3.6.1.4.1.20632.5.10.0

Could the MIB Importer tool mistakenly added a ".0" to all the OIDs? Is there a way to correct this?

Created on Jul 18, 2011 5:26:37 PM



Votes:

0

Could you please send MIBs and OIDLib to [email protected] so we might have a look into these files?

Kind regards,

- Volker

Created on Jul 19, 2011 12:04:31 PM by Volker Uffelmann [Paessler Support]



Votes:

1

I solved the problem by editing the .oidlib files (used notepad++) generated by the MIB Import Tool and removed the extra ".0" from the OIDs. The PRTG SNMP Library Sensor works fine now.

Created on Jul 19, 2011 2:51:31 PM

Last change on Jul 20, 2011 2:33:29 PM by Patrick Hutter [Paessler Support] (7,225) ●3 ●3



Votes:

0

Thanks for this thread. 8 Years later and this is still what I needed to do to make this work.

Created on Sep 19, 2019 7:22:17 PM




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.