There are 2 ways you can link subnets. First is via the dashboards (and is a tad clunky we will be the first to admit).

1. Navigate to the Location Summary dashboard of the location that you wish to be the PARENT in the relationship. Click the 'Link Existing' button as shown below

2. You can see here that it is asking for an 'ID' This is the unique ID for the subnet that you wish to make the CHILD in the relationship. You can find this in the Location Summary dashboard of the CHILD location - in the top-left as shown below. Copy this into the above dialog and hit the button.

If successful, you will see the following. If you see an error - it's usually a permissions thing, so check that first! As ever - if you're still having issues - ping us.

The other method is of course to automate this with PowerShell. Here's a snippet that you can use - simply run this and supply the Parent and Child Subnet IDs as arguments. Tis only works if your subnet IDs are unique - ping us if this isn't the case!

 <# 
    .SYNOPSIS
    Links two subnets together via a Parent Child relationship so that subnets
    can be grouped into a single multi-subnet location in StifleR
    .USAGE
    Either:
    Just run the script and you will be prompted for the PARENT first and then CHILD subnet ID
    Run on the cmdline .\LinkSubnet -ParentSubnetID 192.168.0.0 -ChildSubnetID 192.168.1.0
    or without switches .\LinkSubnet 192.168.0.0 192.168.1.0
    NOTE: If you have multiple subnets with the same networkID (but different Gateway MAC) results may be unexpected!
    Working on a more intelligent version...
    .NOTES
    AUTHOR: 2Pint Software
    EMAIL: support@2pintsoftware.com
    VERSION: 1.0.0.0
    DATE:31/01/2019
   
    CHANGE LOG:
    1.0.0.0 : 31/01/2019  : Initial version of script
    #>

[cmdletbinding()]
Param(
[Parameter(Position=0,mandatory,HelpMessage="Enter the PARENT IPv4 subnet ending in 0.")]
[ValidatePattern("\d{1,3}\.\d{1,3}\.\d{1,3}\.0")]
[string]$ParentSubnetID,
[Parameter(Position=1,mandatory,HelpMessage="Enter the CHILD subnet ending in 0.")]
[ValidatePattern("\d{1,3}\.\d{1,3}\.\d{1,3}\.0")]
[string]$ChildSubnetID
)
$ParentID = (Get-WmiObject -namespace root\StifleR -Query "Select * From Subnets where SubnetID = `"$ParentSubnetID`"").id
Write-Host " Linking Parent Subnet:$ParentSubnetID with Child Subnet:$ChildSubnetID"
If($ParentID){Invoke-WMIMethod -Namespace root\StifleR -Path Subnets.SubnetID=`"$ChildSubnetID`" -Name LinkWithSubnet -ArgumentList "$ID"}
Else
{Write-Error "Parent ID Could not be found - please check the Network ID that you entered:" $ParentSubnetID }

If you then need to UNLink a subnet from its parent - we got that covered too.

<# 
    .SYNOPSIS
    UNLinks a CHILD subnet from its PARENT
    .USAGE
    Either:
    Just run the script and you will be prompted for the CHILD subnet ID
    Run on the cmdline .\UNLinkSubnet -SubnetID 192.168.0.0

    .NOTES
    AUTHOR: 2Pint Software
    EMAIL: support@2pintsoftware.com
    VERSION: 1.0.0.0
    DATE:31/01/2019
   
    CHANGE LOG:
    1.0.0.0 : 31/01/2019  : Initial version of script
    #>

[cmdletbinding()]
Param(
[Parameter(Position=0,mandatory,HelpMessage="Enter the IPv4 subnet that you wish to UNLINK from its PARENT")]
[ValidatePattern("\d{1,3}\.\d{1,3}\.\d{1,3}\.0")]
[string]$SubnetID
)
Write-Host " UNLinking Child Subnet:$SubnetID "
If($SUbnetID){Invoke-WMIMethod -Namespace root\StifleR -Path Subnets.SubnetID=`"$SubnetID`" -Name LinkWithSubnet -ArgumentList "00000000-0000-0000-000000000000"}