nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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
Store

Custom MIB poller problem

ljubisha

After upgarding to Orion 8.1 (Demo) and after applying all the hotfixes, the custom MIB poller polls rarely and in undetermined intervals, whats the point? img66.imageshack.us/.../chartkz0.png Sample Shot at 2007-07-31

Find more posts tagged with

Accepted answers

All comments

anselm

how do you have the pollers setup?

www.solarwinds.net/.../OrionCustomPollerSetup.html

ljubisha

I was setted up all the setings correctly, still not working.

skaczkowski

I think I know what your problem is..

When you're setting up the poller on the last screen you'll see:

Unit then Timeframe

Make sure that under timeframe (next to per) is set to None

Cause if you have an interval in here what it's doing is dividing your poll results by that number and you just want the straight vault that's polled..

I ran into the same problem, all of my pollers were getting the same strange results..

Good luck!

-Steve

jonchill

I've got exactly the same problem, I've checked the timeframe as suggested but all mine are set to none and I'm still getting patchy data. It's particularly a problem for our UPS temp probes as we are meant to be reporting on temperature flutuactions but currently we can't.

Anyone got any ideas?

Thanks

Jon

filipv

I've got exactly the same problem. The custom poller polls in very irregular intervals which are steadily INCREASING and after three days of polling I end up with values being polled once in couple of hours or even more. That's very frustrating and renders the custom poller absolutely useless. Please help.

The funny thing is when I set up the custom poller it began polling once in few minutes, which was acceptable but, as I said, the minutes grew to hours and hours grew to many hours. The result: the single most anticipated feature of Orion 8 doesn't work.

I am deeply convinced that the decision about buying Orion in many cases is based almost exclusively on Orion's ability to poll device-specific values. What should I report to my superiors? Can this be fixed or shall we wait many years for Orion 9?

FormerMember

How many objects are you polling with the custom poller?

jonchill

I've got about 100 custom pollers of which 90% never change there info they are things like serial numbers and tag id's the other 10 % are mainly UPS and a couple of Firewall pollers where it's tracking a temp probe or connections in use.

It would seem that it's only happening on my main Orion server, our remote poller hasn't had any breaks in the data.

Jon

filipv

How many objects are you polling with the custom poller?

One of the custom pollers polls about 80 devices. The other one - about 30. They both poll about two or three times a DAY, as I write this...

FormerMember

I'd suggest that each of you contact Support. We may be able to provide you with some kind of workaround until we can release a more comprehensive upgrade to the Custom MIB Poller, which is our top priority after 8.5 ships.

jonchill

I've done a repair of my Orion install as suggested by Mark and it has so far solved the issue with breaks in data, there hasn't been one all day.

Jon

mark_wiggans

Jon-

sounds great! Do keep us posted. That Repair feature resolves many issues.

jonchill

Mark

I've come in this morning and checked the stats and I'm seeing big holes in the data again since the early hours of Saturday morning so it would seem the repair worked for a short while and it's now broken again.

Thanks

Jon