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

Dependencies (Just Interfaces)

fluidbios

Requirements:

-I don't want to use "All objects in my environment" in the alert

-I want to use "interface status is not equal to up" for best coverage

-When our connection to other managed sites go down I don't want to see any alerts except for the Parent in the dependency.

My Config:

I created a group and added all my interfaces to "All_Interfaces" and created groups/dependencies for each site and set it to "interface status is not equal to up" for best coverage.

Issue:

The wording of the dependency is concerning and leads me to believe that based on my configuration (interface status is not equal to up) I could very well still receive email alerts categorized as "Unreachable" in this scenario.

When the parent goes down:

The status of dependent child objects are UNREACHABLE instead of DOWN or UNKNOWN. Any alerts where the trigger condition includes Node status is equal to DOWN are not triggered.

Find more posts tagged with

Accepted answers

All comments

superfly

The alerts for the child objects will be muted as that's what a group does. So you shouldn't get any alerts for the child objects when the parent goes down.

mesverrum

Interface status != UP AND interface status != Unreachable should be the simplest way to ensure you don't get noise.

superfly

I didn't think it was possible for an interface to be both UP and Unreachable at the same time. Should your statement be OR?

superfly

Actually I was just thinking about this a little more and if a node goes down, the interfaces are automatically muted. So how are your managed sites hooked up? Single or dual links, single or dual routers etc.

fluidbios

!= reads "not equal to"

fluidbios

Perfect! I'll give this a whirl. Thanks!

fluidbios

Thanks for your responses!

To your first response - Initial research on this indicates that it's a simple "mute" but the actual description when you're implementing it (see original post) is what triggered my question. To you second response - We have a direct 10gig link connecting 2 datacenters, a direct connect line to our AWS deployment and a VPN connection to our Frankfurt datacenter.

I started testing configuration for this in Frankfurt as we're having packet loss between that location and our Primary DC in Colorado (Sungard has chased this down to an issue between a GTT and BT transatlantic link).

My initial setup hasn't quite worked like I had hoped. Since we have no single "router" that Frankfurt sits behind and we rely on a VPN connection I've created a group and added both our External Gateway Edge Interfaces and set the group to "Show Best Status" so that this allows for failing over of those devices and it will only go down if Colorado can't reach either of those endpoints. It's currently set on the fastest refresh time possible which is 60 seconds by default.

Then I created another group to add all Frankfurt Interfaces into and created my dependency.

Yesterday morning the GTT/BT link struggled again and I was still bombarded with email alerts. For the time being I'm filtering down my Interface Group down to the most critical.

superfly

Oops! Learn something new each day. I was surprised that @mesverrum would make a 'mistake'! I should've know better, he's the smartest one here