1 of 1 people found this helpful
If the Subnet nodes already exist then it is possible to create a relationship as part of the import (docs). So you could have an additional #Location:Location:ElementInLocation:Subnet.ip_address_range column to attack to the Subnet with the ip_address_range.
If the Subnet does not exist then you need a pattern. You would need a table to map from subnet address to the name of a Location. Triggering on Subnet created, confirmed would then search for the Location and create a link between the Subnet and Location.
2 of 2 people found this helpful
This is a pretty famous topic on this community, search for Location and Subnet and you will get several hits, for example Trending in Support: Location, Location, Location Host to Location linking via Subnet , SubnetsToLocation4.0.tpl.zip
You also have Discovery doc - Host to Location linking via Subnet
Thanks.. It works with #Location:Location:ElementInLocation:Subnet.name, the ip_address_range throws some string exception..