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

Getting interface down to affect group

I am defining some groups of Nodes in NPM to use on a map.

I have a Router and 3 switches in the group and one of the switches has an interface down alert.

But the group status is still up, I have chosen "worst case" in the Group setup so i figured that the Group status would reflect that.

I have attached a screenshot of the group overview.

Regards Jens

Group-FGD.png

Find more posts tagged with

Accepted answers

jellobones

I personally would just add the interface in the group.

Changing the node's status to Warning via an alert due to an interface going down would add another unnecessary layer. So let's say the alert did not trigger and of course that's never happened bafore . Then you're back to square one. Second scenario is let's say you're interface is a circuit and it goes down. You're group status will not reflect the appropriate severity of that outage. A downed circuit more often that not is more than a warning.

My recommendation is that you add the interface in the group and call it a day. This will also give you the ability to use the group for future filters. Obviously a single interface wouldn't be that big of a deal to add as a filter in a report/alert or dashboard but if you have hundreds or in my case even thousands. It'll matter then.

All comments

deverts

Jens,

Your group is based on the elements within it. You have 4 nodes in your group, therefore, the group status is based on those. If the status of that switch is to go "red" because an interface is down, that status will then roll up into the group status because it changes the element (node) in the group. Otherwise, you have to add all the interfaces to the group.

jew

So what you are saying is that i have to add the interfaces I'd like to monitor to the group seperately to gain their status on the group icon?

I am currently toying with the alert trigger action "set custom status" to see if I can get a interface down alert to set the whole node in warning, wouldn't that also be a solution?

Regards Jens

mesverrum

That would also work too.

dgsmith80

Custom properties every time!

deverts

Certainly, there are a few different methods to achieve the goal, but the result is the same. For the Group to show a "red" status, one of the elements (in case "a Router and 3 switches") in the group has to be "red." Your interfaces are not directly part of the group, they are a sub-elements of one of the elements. To explain further, if an interface goes down, you get a "red square" that displays on the router or switch, you don't get a "node down" situation. Your group only has nodes in it, for it to go "red" you need a node down (or element down) situation.

Possible solutions:

1. The method you are exploring with "set custom status" (this is probably the most preferred method by most people)

2. Put the interfaces in the group

3. Set the node status to "worst status" - Caution, this is global setting under Web Console Settings - Child Status Rollup Mode, and impacts EVERYTHING!

There's probably another method or 3 that I'm not thinking of at the moment. Hope this explains more and helps.

jellobones

I personally would just add the interface in the group.

jew

I cant get the Set custom status to work keep getting this error " "Set Status Critical" action has failed Execution of CustomStatus action with Entity type - Orion.NPM.Interfaces failed. CustomStatus alerting action works only with Orion.Nodes."

I would much prefer to use set custom status, as there doesn't seem to be a way to dynamicly assign interfaces to the group.

I have assigned the Nodes dynamicly to the group and would prefer not to have to add interfaces manually

Can any one tell me what that error means ?

Regards Jens

jew

I have found the explanation for the error and it doesn't look good

Error adding "Set Custom Status" Action to an Alert - SolarWinds Worldwide, LLC. Help and Support

It has to be a Node alert that uses the "set custom status" trigger!! that does not make sence to me as the node most likely already is the parent, and the alert most likely can set the status without this trigger.

I have found this feature request, it is old but i have updated it a little bit. If you would like to be able to control a nodes status on the basis of child alerts then please vote

https://thwack.solarwinds.com/ideas/1477#comment-294941

Regards Jens

mesverrum

That feature only works on nodes because nodes was the only table they added a "custom status " column to unfortunately.

dgsmith80

Ok so this is a messy way to achieve what you want, and I wouldn't normally recommend it, but if you really want it - This worked for me in testing:

For my test, I have set a specific Node Name, but you would change that to trigger on any Cisco device for example etc. Then under Advanced options, you select the Enable Complex Conditions. Then in the Secondary AND Condition check for your Interface Status.

I've not stipulated which Interface because I only have one interface down on that device, so it's not a problem, but if you wanted to be aware of a certain Trunk interface then you would use that Name or set a Custom Property against the Interfaces you want to be used.

Then you can use the Trigger Action to change the Node Status. Just make sure you review the Reet conditions and ensure a Reset Action to change the Node Status back as it won't automatically change back.