I've had Auto dependency enabled for quite a while now. I've noticed in many instances the parent child dependency seems to be reversed. In a very simplistic example, I have a location that has a primary transport and a VSAT transport that connect through a Fortigate firewall which is then connected to a Meraki switch. I have this arrangement in many locations. So to me the expected behavior is
Parent > Child
VSAT > Forigate
Modem > Fortigate
Fortigate > Switch
In some of those locations Auto Dependency has calculated that the switch is the parent and it shows the same dependency with a different name twice.
Looking at the switch
AutoDep-7 Switch > Fortigate
AutoDep-8 Switch > Fortigate
Looking at the Fortigate
AutoDep-7 Switch > Fortigate
AutoDep-8 Switch > Fortigate
Looking at the VSAT
Fortigate > VSAT
What am I missing here? Am I not understanding this correctly or has something caused this "miscalculation"?
Lastly, I wanted to delete these dependencies and have them recalculate. When I manage dependencies, and select one or more, the delete option does not enable. It stays gray as if to say you may not delete.
I think I read that deleting them doesn't actually delete them but, adds them to an ignore list. I'm really not sure how to fix this or if there is something to fix?