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

Basic and Advanced alert with same configuration turned on and Unknown state inquiry

If there is a Basic and Advanced alert with same configuration turned on, do both alerts trigger?

Also, if a node that is the root cause of an issue is down, do advanced alert configuration alert on child nodes? I know basic alerts do not understand that the child alerts should not trigger if a parent node is down.

If advanced alerts trigger on child nodes when a parent node is down, is there any way to fix this?

What does the status of an Unknown state actually mean? I know when a down state detected means Orion knows for sure that the node or interface is down because it cannot query. Is Orion going off the SNMP query or Ping/ICMP check? Does a Ping/ICMP check ever indicate a Unknown state for a device? In detail, what does Orion go off of to give a status of a link as Unknown? Furthermore, can a status of Unknown be given when there is high bandwidth consumption? Unknown sounds like it is saying, "I cannot either confirm or deny that the node/interface is available/down." Why would it not be able to confirm or deny the status?

Thank you for your help.

Find more posts tagged with

Accepted answers

All comments

thompmik

I saw you posted that you had to restart your alert service every three days or so in another post. Have you resolved that issue? I have the same problem and the same error messages when it happens.

thanks,

FormerMember

If there is a Basic and Advanced alert with same configuration turned on, do both alerts trigger?

Yes

Also, if a node that is the root cause of an issue is down, do advanced alert configuration alert on child nodes? I know basic alerts do not understand that the child alerts should not trigger if a parent node is down.
If advanced alerts trigger on child nodes when a parent node is down, is there any way to fix this?

This can be done, but it's currently a manually configured suppression for each alert that requires you to identify the parent.

What does the status of an Unknown state actually mean? I know when a down state detected means Orion knows for sure that the node or interface is down because it cannot query. Is Orion going off the SNMP query or Ping/ICMP check? Does a Ping/ICMP check ever indicate a Unknown state for a device? In detail, what does Orion go off of to give a status of a link as Unknown? Furthermore, can a status of Unknown be given when there is high bandwidth consumption? Unknown sounds like it is saying, "I cannot either confirm or deny that the node/interface is available/down." Why would it not be able to confirm or deny the status?
Thank you for your help.

Unknown typically means that we can ping the node but we can't get SNMP for some reason.

jluke

Thanks.

What are some of the examples of reasons why we could ping a node but not get SNMP information to give a unknown state?

jds

Wrong SNMP community string.

SNMP service went down.

Firewall blocking port 161.

jluke

Wrong SNMP community string.
SNMP service went down.
Firewall blocking port 161.

I had all of those covered. The only thing I saw that could have caused the issue was high bandwidth utilization. Could this be what causes it?