When do I get my points? Anyone else had to create this many? I'll be at around 550 by the time I'm done with this latest round... so I'm going to plug my idea again
Firstly i have never seen that before on thwack or solarwinds so i would log a call with solarwinds. Looks like an xbox symbol to me which would set alarm bells. Solarwinds take 30-90 days to apply points. Secondly, i never build dependencies node by node. I create groups by site with child groups by topology and build my dependencies by group, not node. Its faster and just as effective.
Thanks for the helpful reply, but I definitely photoshopped this as a gag! I never pass up an opportunity to bring up my suggestions to improve the dependency process
I do use groups, the problem is that my company has 85 remote networks which each require at least five or six dependencies each! I just spent three and a half work days (Literally! Nonstop 8-5 Tuesday and Thursday, and 8-noon Friday!) creating almost 200 additional dependencies and editing another 175. There is a lot of room for improvement in the dependency wizard! All in all I am now at 612 user-created dependencies...
I am looking at some remote sites in a similar situation. Each site has 4-6 routes going back to 2 different upstream routers through VPN tunnels. So each upstream router has 2-3 route through it's VPN to the remote site. This is all layer 3 stuff, so how to group them when each route is a different subnet.... then there is the odd bit where NetPath doesn't even show the upstream router for some reason.
This isn't a solution, but it may save you pain if you look into scripting the dependancy and group creation processes. I am not talking SQL, VB, powershell or anything fancy like that. I just use a Pulover's Macro Creator (basically a front end for AutoHotKey). Took what would have been literally a 40+ hours of tedious clicking and typing and turned it into about 1-2 hours of creating the macro and its datasources and 6-7 of watching it work through a RDP session on a seperate monitor so I could do other things as well.
Hi agian,
Yes i am familiar with this situation and to be honest you do not need to create groups for all vpn sites. If you enable auto dependencies then it will auto calculate the dependencies for you on flat networks such as vpn sites traditionally have. You only need to create groups for sites such as datacenters, head offices with more complicated networks that use stp, rstp or mstp or teaming.
Auto dependencies weren't introduced until recently, and at that point we already had over 400 created. Enabling auto dependencies erases everything and starts from scratch, and I didn't want to risk miscalculations.
Auto dependencies work perfectly when the environment is configured correctly. For example, all the interfaces such as trunks, vlans, routing, topology, lags, uplinks on the access switches. All active ports on the core stacks, firewalls, routers etc..... They dont work correctly when these are not selected and make a node to node dependency because it can see a device is connected. They also dont work correctly if you have some of the connected devices in unknown because of that reason. They also dont work correctly when the if the groups are not there on core stacks because solarwinds is not clever enough to understand fail safes like mtu on rstp for example.
Even between two polling engines, we do not have the polling power to collect layer 2/3 topology and unplink interfaces for all of our devices. For us there's no practical way to make sure every device is configured just right so that the automatic dependencies will be perfect.
that Xbox achivment cracks me up nice one
Fair enough, you will just have to leave it until you are able to migrate to more powerfull servers and purchase a second ape.
Anyone else had to create this many? I'll be at around 550 by the time I'm done with this latest round... so I'm going to plug my idea again 
