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

Orion dependencies problem

I have a problem using dependencies in Orion. I created a dependency in which node A is the parent and node B is the child. In order to check if the dependency is working, I simulated a down state for node A (changing its polling IP so that the node stopped responding) and waited for node B to change to unreachable status, but this didn't happen. Node B continued in Up status (apparently, when parent goes down, the child doesn't go unreachable if is still responding). When I simulated a down state for node B (in the same way that for node A) the node goes to Down status and then, after several minutes, it goes to unreachable status. The dependency is working but the problem is that node B first goes down and triggers an alert before going to unreachable status.

Is there any way to change this? I could't find any timing configuration in 'manage dependencies'.

Thanks in advance.

Find more posts tagged with

Accepted answers

All comments

mrxinu

When you created the dependency, what did the properties look like?

TnitMon

The problem is that there is no properties to configure when creating a dependency. I had only to select the parent, the child and the dependency name.

cnorborg

I think you might be misinterpreting what dependencies are for. If you have a child/parent relationship like you mentioned, and the child goes down while the parent is down, you can use this dependency information to suppress the alert. I don't think SW forces the child down because the parent is down, it still gets polled.

If you wanted, you could write an alert that did something like put the child node into unmanaged or muted state if the parent went down. Maybe you could even force the status to down, but pretty sure Orion will still poll it regardless of if you manually change its status, it has to do it to see if it comes up.

TnitMon

I didn't expect switch B to go Down status because its parent is down. I expected switch B to go to Unreachable status when its parent is Down.

How can I configure an alert which includes the dependency with the parent?