We have hundreds of sites, each site has primary and backup circuits only certain subnets run over the backup. We end up having at-least 3 groups and up to 5 groups per site to configure dependencies. How do you handle this in your environment?
I'd be figuring out some kind of scheme to just have a script figure this all out for me.
Presumably there are some standards in place that allow you to know how a site is laid out in terms of network topology? If those exist then they should be programmable, if not then some standards need to be developed or you are going to be stuck doing this by hand one at a time forever.
I'm having a hard time envisioning this 5 group dependency model you are describing, can you take a screenshot and sanitize it to look over?
The multiple groups is because we also have different teams. Just trying to understand if there is a better way to do this versus groups.
Parent - Location - Primary
Interface on Router/Firewall for primary - if this goes down it silences the child.
Parent - Location - Altcom
Interface on Router/Firewall for primary - if this goes down we get a site is down alarm.
Child - Location
-Special Equip 1 - Dynamic
-Special Equip 2 - Dynamic
-Server - Dynamic
-Network - Dynamic
So this maybe is harder than it has to be.
If the parent interface is not a group of interfaces, you could skip creating the group for it and just use the interface directly as the parent of the child groups. Parent and child objects can be any orion object, no reason to make groups with only 1 member. For the rest I would just write a script that gets a list of all the locations, and for each location creates a group for each category of a devicetype node custom property. Are you familiar with powershell? I can dig up some code samples that do something similar and try to sanitize them for public consumption.
Doing dependencies by hand sucks, it was literally the first reason I learned powershell to be able to do them programmatically.
