Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

When good MIBS go bad (UnDP issue)

I have a TemPager device from AVtech that I'm trying to create a Universal Device Poller for.

The MIB in question is 1.3.6.1.4.1.20916.1.7.1.2.2.2

I can make the poller just fine. The value that it returns is, understandably, not in the format I want (8000, 7800, etc.). When I create a result transformer and divide by 100, however, it doesn't work properly. The returned value turns into something like -1 or -3.

I have another MIB set up for the internal temperature of the device which I have transformed in exactly the same fashion which works fine and gives me the real value. So what's the deal with this one that doesn't want to work? The transform is simply the poller/100. Nothing too complicated.

Find more posts tagged with

mib_undp_npm_poller_avtech_tempager

Accepted answers

jerquiaga

So, I recently spent a couple of days banging my head against the wall on this one. In the end, when I created the poller I gave it a name other than the default (it defaulted to digital-sen-2-2) and then the formula seemed to work like a charm. I used the name ExternalTemp2. I'm wondering if there is a bug in the UnDP formula code and the two dashes and twos in the default name are getting used in the formula somehow.

All comments

Donald_Francis

I do not know the answer to your question but I had to post about your title I about fell out of my chair laughing when I read it!

Poppinfresh

*Nobody* has the answer on this one? Surely I can't be the only person out there using TemPageR

xjohnx

We're using TemPager 3E's and don't have a problem with them. The OID is 1.3.6.1.4.1.20916.1.7.1.1.1.2, pulling the internal-tempf stat. Then a simple conversion to divide by 100 and everything seems to be working fine

jerquiaga

bmvernil

THANK YOU, THANK YOU, THANK YOU!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Same problem, I was about to go nuts trying to figure it out...