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 192.168.1.1 188.8.131.52.4.1.20632.2.2
.184.108.40.206.4.1.20632.2.2 = INTEGER: 5
$ snmpget -On -v2c -c public 192.168.1.1 220.127.116.11.4.1.20632.2.3
.18.104.22.168.4.1.20632.2.3 = INTEGER: 3087
$ snmpget -On -v2c -c public 192.168.1.1 22.214.171.124.4.1.20632.2.4
.126.96.36.199.4.1.20632.2.4 = INTEGER: 9
snmpget -On -v2c -c public 192.168.1.1 188.8.131.52.4.1.20632.2.5
.184.108.40.206.4.1.20632.2.5 = INTEGER: 2
snmpget -On -v2c -c public 192.168.1.1 220.127.116.11.4.1.20632.2.8
.18.104.22.168.4.1.20632.2.8 = 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:
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).
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).
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 150,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process. Learn more today by joining now.