Under 'Manage Dependencies' in the web console, there is a line that says "Calculate dependencies automatically:Turned OFF"
How do you turn that on, or does it require NTM to do it?
Outside of the admin guide, we don't have further documentation. I believe a KB is in the works. If auto-dependencies are enabled, we we will recalculate dependencies every topology polling interval. …
UI Issue- thanks for flagging sir. Setting also found under Settings->Polling Settings
Looks like the closest I saw, and this came out pretty recent. I don't think they are going to release too much info with what is happening under the hood.
Is there a good doc on the implications of doing this? For instance, while I'm all for the tool doing the work, I'd really like to know when and if it makes changes in dependencies so that perhaps I can approve or deny those dependencies.
I'd hate for something to be missed because it was marked as dependent on the wrong upstream object.
Outside of the admin guide, we don't have further documentation. I believe a KB is in the works. If auto-dependencies are enabled, we we will recalculate dependencies every topology polling interval.
Auto-dependencies are displayed on Manage Dependencies grid as "Calculated Automatically" under "Origin." If a calculated dependency is not accurate, it can be deleted and it will move under the "Ignored Dependencies" list. These dependencies will not be recalculated. If you have a current manually-defined dependency, any auto-deps that would duplicate will be discarded.
While were at it, this might be a good thread to ask about implied dependencies. I have always understood that certain dependencies were automatic in that they did not have to be defined by the user. Examples would be interfaces on a node or applications on a server. In each case, Orion would automatically place those interfaces or applications into "unreachable" status if the parent node was down or unreachable.
Am I correct in this, and are there any other implied dependencies I have missed?
Testing with NPM v12 and SAM v6.3 I have found that applications do indeed go into Unreachable status automatically when the server is down. However, when a switch is down, the interfaces are NOT automatically placed into Unreachable status.
Solarwinds? This seems abnormal. Comments?
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK© online community. More than 180,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process.