Hi guys, have to ask you, because technical support refused to help (#00659005 and customer service did nothing for solving).
We have several dependencies like this:
| Parent | Child |
| IPSLA_NY | nynode.local |
| IPSLA_COL | colnode.local |
| IPSLA_BOS | bosnode.local |
| IPSLA_ATL | atlnode.local |
Some of these nodes are polled from main poller (MPE), and some polled from additional poller (APE), like that:
| Node | Poller |
| nynode.local | MPE |
| colnode.local | MPE |
| bosnode.local | APE |
| atlnode.local | APE |
And if parent became down, I expect unreachable children.
Expected behavior:
| Parent | Parent status | Child | Child status | Child polled from |
| IPSLA_NY | Down | nynode.local | Unreachable | MPE |
| IPSLA_COL | Down | colnode.local | Unreachable | MPE |
| IPSLA_BOS | Down | bosnode.local | Unreachable | APE |
| IPSLA_ATL | Down | atlnode.local | Unreachable | APE |
But what I actually see:
| Parent | Parent status | Child | Child status | Child polled from |
| IPSLA_NY | Down | nynode.local | Unreachable | MPE |
| IPSLA_COL | Down | colnode.local | Unreachable | MPE |
| IPSLA_BOS | Down | bosnode.local | Down | APE |
| IPSLA_ATL | Down | atlnode.local | Down | APE |
As you can mention, APE-related nodes don't become unreachable if their parent is down.
Here you see only 4 examples, but we have 1000+ nodes polled by MPE and 1000+ nodes polled by APE, so the picture is clear: dependencies are not working for APE-nodes.
Have you encountered this type of problem?
Any ideas what would cause that?
