Node/Network template

<< Click to Display Table of Contents >>

dpCom > Menu reference > Tools >

Node/Network template

The node/network templates function can be described as a more advanced copy/paste function. Existing network data is used to define type nodes and type networks. Those can then be used as templates for the creation of new network objects.

By defining templates for commonly used design patterns, the creation of network data can be made faster and the design patterns can be enforced.

A type node is defined from an existing node, while a type network is defined from a route or a combination of nodes and routes.

In order to ensure that the names (ID) of objects can be unique, the ID of some object types are cleared in the creation of the template. By default, this applies to the nodes and the routes, but also to pipes, multiducts and cables, as well as racks and equipment. ID:s are not cleared for lower level objects like switch ports, ODF contacts or fibers.

 

The templates are stored directly in dpSpatial and are therefore not part of the changeset. This means that the command Empty changeset will not undo any creations or deletions of templates.

 

Modifying/editing a Node/Network template

There is no explicit editing tool for a template. Instead, the following procedure is recommended:

1.Log into an empty changeset

2.Apply the template to be modified in the map by using the applicable Place command for the type of template, i.e. one of the commands:

Place > Node/Network template > Create

Place > Node/Network template > Only node content

Place > Node/Network template > Only route content

3.Make the modifications in the generated network.

4.Define a new template based on the modified network using the applicable tool.

5.If desired, delete the previous template.

6.Run the Empty changeset command.

The procedure can also be used to e.g. create a node content template out of a node template or the other way round.

Handling of splices

Connections to objects that are not part of the template (for example incoming cables/fibers) are not copied.

If the incoming object is an optical cable or copper cable and if its fiber or wires are spliced in the node used to create the type node, problems can occur. The following procedure is recommended in such situations:

1.Log into an empty changeset.

2.Disconnect the cables entering the node that will be used to create the type node. Disconnect in this case means to disconnect all fibers/threads using the Splice fiber or Splice thread/carrier tools.

3.Create the type node, type node content or type network.

4.Undo the changes in the changeset.

 

When a type node/type network is created, it is stored directly and is therefore not affected by undoing the changes in the changeset.