I have found it is a timing issue, if the system finds the child object down prior to the parent you will get the alert. This can happen if the polling time is faster for interfaces than Nodes. I usually will stack my polling from most critical to the least, which works well when the alert engine looks for Down Nodes, Interfaces, etc.. Here is an example on Router to Switch to Server at a remote site.
Status Polling Times
1 Minute Router
1.5 Minute for Switch
2 Minute (Default) Servers
Best Regards,
Derik Pfeffer
Loop1 Systems: SolarWinds Training and Professional Services
- LinkedIN: Loop1 Systems
- Facebook: Loop1 Systems
- Twitter: @Loop1Systems