Good day,
I hope everyone is well. I have just been made aware that the auto-dependencies feature within SolarWinds does not work very well because the switches do not tell SolarWinds how the core/distribution/access layers sit, so the platform will never know which switch lies at the top of a given sites topology.
My question to SolarWinds is, what can we do about this? I do not see spending hours putting in manual dependencies for hundereds of sites as a solution. Is it not a possibility to manually define a singular switch as the top of the topology and then if you have star-tree topology, that the dependencies are created based on the uplinks to each specific switch. For example... We give the core switch the "parent of site" role, and then the auto-dependencies module recognises that there are uplinks from downstream switches (first action is to assign the downstream switches as child objects to the core), connected to these downstream switches there are then access switches, the next action is to recognise that the children of the core can be parents of the access, so then then the module will assign these as parents of the access, like so. The idea is for this process to replicate as it continues down the topology.
I am hoping that other people are looking for this functionality to perform properly, so that we can start a proper discussion.
