API provisioning for Groups and Dependencies.

FormerIdeaCreator

Specific Use Case:

I have thousands of interfaces.  Each of them has one sub interface that I care about (alarm on when down) because it operates and a higher layer.

I want to suppress alerts on the sub-interface when the parent interface goes down, however, provisioning these manually is impossible, we simply don't have the man-hours.

This is the correct method to handle this with SW, but the manual provisioning is a deal breaker.

How can we do this in an automated fashion?  I can craft the SQL queries to locate whatever data I might need to populate in the DB, but there is no roadmap.

Personally, I would be happy with an unsupported "Custom" SQL option, but in general, the manual provisioning of groups and dependencies is problematic when using the product at any scale.

In this particular use case, I do not require a group, because I only need 1 interface to be a child of another specific interface, but I don't have resources for the point and click.

Peter

RichardLetts

Groups (aka containers) can be automatically provisioned -- there is an API that works for that. I used it to build the hundreds of groups we have of devices based on their custom properties (sector, building).

here's the perl peices:

$swis->Invoke("Orion.Container", "CreateContainer", [

                "$sector $building",

                 "Core",

                 "60",

                 0,

                 "Group for $sector nodes in $building",

                 "true",

                 SOAP::Data->type('xml' => "<ArrayOfMemberDefinitionInfo  xmlns='http://schemas.solarwinds.com/2008/Orion'><MemberDefinitionInfo><Name>$building Devices</Name><Definition>filter:/Orion.Nodes[CustomProperties.Building='$building' AND CustomProperties.Sector='$sector']</Definition></MemberDefinitionInfo></ArrayOfMemberDefinitionInfo>")]

                )));

and...

# add the group to its parent.

my $memberDefinitionInfo = SOAP::Data->type('xml'=>"<MemberDefinitionInfo xmlns='http://schemas.solarwinds.com/2008/Orion'><Name></Name><Definition>$containerURI</Definition></MemberDefinitionInfo>");

$data= $swis->Invoke("Orion.Container", "AddDefinition", [$parentID, $memberDefinitionInfo]);

the ability to define subinterface -> parent interface dependencies would be excellent (I have VLAN interfaces, and T1 subinterfaces on T3 carriers)