Adding Child Nodes


After you create an independent topology, you can add child nodes in two ways: adding one by one or in batches.

Prerequisites


  • The current account has access permissions for Topology menu, as well as permission points for managing topology structures. Contact the application administrator if necessary.

  • At least one independent topology has been created. For more information, see Creating Independent Topologies.

  • You have created the assets to be assigned. For more information, see Onboarding Sites and Devices. Custom type assets that off sites can also be created when they are assigned to topology nodes.

Adding Nodes One by One


  1. Select Topology menu in the left navigation bar, and then find the topology node for which to add child nodes.

  2. Select Add Child Node for the target node.

  3. In the pop-up, select Category and Type of the object, and select an existing asset in the current OU in Objects, or create a new asset. Categories and types available here depend on the topology rule.

    • If you select Site, Device, or Component as the type for the child node, you cannot create a New Asset on the current page. You can only select existing assets in the current OU.

    • If you select Custom Type for the child node, you can select an existing asset in the current OU, or select New Asset to create a new asset. Follow the steps below to create a new custom type asset:

      1. Select + New Asset.

      2. Enter Name of the child node in the pop-up, select Time Zone, and enter other attribute values as needed.

      3. After entering the information, select Submit, and a child node will be created for the current topology.


      Note

      For newly created Custom Type assets in the independent topology, when the node attached to the custom type asset is deleted, the asset will be deleted at the same time.


Once added, the child node will appear below the parent node. Topologies of three layers and above will be collapsed when the page is displayed, select the corresponding Expand btn_expand to expand the next layers of the current node.


Note

The maximum number of levels from top to bottom is 7, and the maximum number of nodes to add for each level is 10,000.


It is not possible to add child nodes to a site node in an independent topology. To add sub-nodes under the site, see Building Topologies.

Importing Nodes in Batches


You can add new nodes in batches by import an Excel file, where overwriting the existing nodes is not supported.

  1. On Onboarding Tool > Topology page, find the topology tree to auto-assign and select Import Topology btn_import.

  2. After entering the new node to import and its parent node information in the Excel file, upload the file. If you need a file template, select Download Template to download it.

    • Asset ID: The assigned asset ID will be used as the unique identifier of the node. Entering existing assets into the current topology tree is not supported. On Site Onboarding page, on Configure Devices step page of the target site, you can find the Asset ID.

    • Asset Name: The name of the assigned asset.

    • Parent Asset ID: If you need to specify a parent node for the new node, enter the asset ID assigned on the parent node. If left blank, the new node will be a child node of the root node. Mounting to nodes within the site is not supported.

    • Parent Asset Name: The parent node name specified for the new node.

  3. Noted the following restrictions:

    • Only one Excel file can be imported under a topology rule at the same time.

    • The max file size is 10MB, and the max number of nodes in one file is 30,000.

    • Can not assign nodes under the 7th level of an independent topology.

    • The max number of nodes in the same level is 10,000. The exceeded nodes can not be imported successfully.

    • The topology structure needs to meet the constraints of the current topology rules. For more information, see Topology Rules.

After importing successfully, the nodes will add under the top node or the specified parent nodes.

If import fails, you can select Download Error Log to view the cause of the error. After modifying the file based on the cause of the error, upload it again. If a node in the file fails to be imported, all node imports in the file will fail.