Showing results for 
Search instead for 
Did you mean: 
Create Post
Level 8

UnDP - The OID is not supported...but it is...

I'm working on troubleshooting some issues with a Barracuda Spam Firewall.  We have SNMP OIDs defined, per the Barracuda documentation, for:  inQueueSize, outQueueSize, deferredQueueSize, avgEmailLatency, and notifyQueueSize.

The Barracuda documentation lists these as:

            OID                             Object                                               Description


Number of messages waiting to be processed by the Barracuda Spam & Virus Firewall.


Number of messages waiting to be sent to the mail server. Note that alerts and notifications are queued separately from outbound email.


Number of messages deferred because they could not be processed, and will be requeued for processing.


Difference between the time a message was received by the Barracuda Spam & Virus Firewall and the time it is sent to the mail server.


Count of messages in the notification queue.

When polling these from the command line, they all work:

$ snmpget -On -v2c -c public

. = INTEGER: 5

$ snmpget -On -v2c -c public

. = INTEGER: 3087

$ snmpget -On -v2c -c public

. = INTEGER: 9

snmpget -On -v2c -c public

. = INTEGER: 2

snmpget -On -v2c -c public

. = INTEGER: 1

When polling them from the Orion UnDP poller, I get "The OID is not supported."


Any ideas?  Even stranger?  These are already built within Orion, but the numbers being returned are incorrect:


Labels (1)
0 Kudos
4 Replies
Level 10


I have checked in Wireshark... The Test button in Browse MIBs perform always Get Next.

- That would explain why you get Not supported message by Test(Get Next) and it is polling(Get).


0 Kudos
Level 8


I got this working. Search for DOC-172648 for details.

Barracuda MIBs Universal Device Poller configuration

There is a trick to setting up the poller entry.



0 Kudos
Level 16

are you doing a 'getnext' or a 'get' in the UnDP ?

Richard, I'm assuming a "get" because this is just in the "Browse MIBs" area when building a poller, and then clicking "Test" (see picture in original post).  There is no where to specify a get vs. a getnext at this stage.

That said, I further explored just not testing at this stage and building the UnD poller, and it tests correctly when specifying a "GET" and a "RAW" value.

So, my immediate problem is solved, but this would appear to be a bug in the UnDP Browse functionality, since you cannot specify a GET vs. a GETNEXT (if that in fact is the issue).

0 Kudos