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

How do I make certain nodes poll before others

bripage

Scenario/Problem:
Ok what im trying to do is make certain nodes poll before others. Lets say I have 2 routers, one behind the other. The second router is polled through a tunnel connection to the first. Now the alert dependancies on for the second router are set up in a way that the alerts should not go off if the first router is down (becuase it might not acutally be down. What I think is happening is that in soem instances Orion seems to be polling the second node before it attempts to poll the first node. The result being I get an alert saying that router #2 is down, and then one saying that router #1 is down. When in fact router #2 is not down, just unpollable.

My Possible Fix
I mean, if I change the polling time on the ones I want polled first to a shorter time, they will poll more often but every so often the polling times will match up and its possible that the scenario above could still happen.

Question:
So does Orion poll the nodes in any particular order, and if so, is there a way to change this order and force certain nodes to always be polled in a certain order or before others? Other wise, whats the point of alert dependancies if every so often I get a burst of them that are incorrect except for the one true one?

Find more posts tagged with

Accepted answers

All comments

Cygnuz

i'm not sure but i think you should try the alert suppression feature. when you setup the alert for router2 set the alert suppression if router 1 is down/warning. hope this may help

bripage

yes yes.. thats the way I have it set up. The alert for router #2 should not go off is router #1 is down. However, I still get the alerts for router 2 before router 1 is shown as down. The only reason that I can see for this is that it tries router 2 first and then router 1. I need to be able to manually set the pattern in which it polls the devices.

ckore

I think this is a great question for the Orion development team. I have the same issue as bripage, the polling sequence appears to be random which makes the alert suppression feature pretty much useless. They should really re-write the polling engine to always poll the upstream device first if alert suppression is enabled.

Network_Guru

As Mr. Brian says, the best you can do is set up the polling interval for the upstream router/device at less than half the interval of all the child nodes.

This should help somewhat, but won't guarantee the Alert suppression works every time.
I posted on this subject a year ago, but there was no response from SW on this issue.

www2.solarwinds.net/.../topic.asp

-=Cheers=-
NG

bleearg13

quote:Originally posted by ckore

They should really re-write the polling engine to always poll the upstream device first if alert suppression is enabled.

Actually, they are re-writing the polling and alerting engine. They have said many times in this forum that they are releasing a new version of the alerting engine prior to releasing v8 of Orion.

Grabowski

I agree compleletely. I have exactly the same issues, and initially hoped that setting a long node warning interval could eleviate this but unfortunately it is a quite common occurance in our setup that alert suppression gets it wrong.

I haven't thought it through, but wouldn't it be great if the dependencies would read of a master map of some sort in mapmaker, where the links between the nodes would dictate dependencies?

Lars Grabowski
Global Infrastructure
Chr. Hansen A/S

pblatz

Looking at the possiblity of creating a Custom Property called "UpStream Node" which I will pass to my correlation engine, Netcool Omnibus and then build the rules there for parent/child relationships.

Would be great if Solarwinds accounted for this.

Thanks,
P. B.

Success requires three bones--wishbone, backbone and funnybone. Kobi Yamada

filipv

The workaround for this "problem" is actually very simple. Just suppress the alert for #2 if #1 has a warning (rather than down) status.

The alert for #2 should be triggered if #2 is in down state and #1 is up (not warning).

But anyway, It would still be realy nice to be able to manually arrange the polling sequence.

Network_Guru

Thanks for the simple solution filipv!!!

I just changed my alert suppressions today using this method.
You can set each suppression to use multiple events.

So basically: suppress alert if node XYZ is down or warning or unknown
That should cover the polling variations with minimal adjustment of the polling interval
of the upstream node.

-=Cheers=-
NG

bripage

That works quite well. thanks for all yoru help and input!!!