Unsupported content

 

This version of the product is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Subnet node

A Subnet node represents an IP subnet on which IP addresses have been scanned.

Subnet Lifecycle

The following section describes the scenarios in which a Subnet node is created, updated or destroyed.

Creation

A new Subnet node is created in the datastore when a host, network device, printer, or SNMP managed device is scanned and its DiscoveredIPAddress is on a subnet that is not represented in the datastore. Subnet nodes are not created for the IPv6 link local prefix.

The generated key for a Subnet node is based on the IP range.

Update

A Subnet node's identity and entire data content are the same thing and are consequently not updated.

Removal

To remove a Subnet node manually, find the necessary Subnet node, select it in the list and pick Destroy from the Actions list.

Subnet Attributes

The attributes and relationships of a Subnet node are described in the tables below.

UI Name
Attribute Name and Type

Description

Key
key string

Unique key.

Type
type string

IP address type (IPv4 or IPv6).

IP range
ip_address_range string

Range of IP addresses in this subnet.

Subnet Relationships

The relationships of a Subnet node are described in the table below.

UI name

Relationship

Description

IP Addresses

Subnet:
Subnet:
DeviceSubnet:
DeviceOnSubnet:
IPAddress

IP addresses on this subnet.

Triggering DiscoveredIPAddress

Subnet:
InferredElement:
Inference:
Primary:
DiscoveredIPAddress

DiscoveredIPAddress used to infer existence of this subnet.

Location

Subnet:
ElementInLocation:
Location:
Location:
Location

Location of this subnet.

Was this page helpful? Yes No Submitting... Thank you

Comments