About child nodes

On the parent node, you must list all the child nodes that the parent replicates to. The Child nodes page in the parent's administration user interface lists those child nodes already configured. You might need to turn off a child node in a system, for example, in the case of hardware failure.

Note: From the parent node, nodes that have been turned off locally are listed as Node not contactable on the Overview page.

Importing

If child node information is available in a comma separated file (CSV), you can import it directly into the parent node. Each line in the CSV file must contain eight fields. The fields must be separated by commas and ordered as follows: <Name>,<IP/hostname>,<Centrallogging>,<Monitorstatus>,<Centralresources>,<Replicationprofile>,<Enabled>,<Comment>

The possible values for these are as follows:

Field Value
Name

A unique name to identify the node. Node names might only consist of letters, numbers, spaces, underscores and full stops. Unicode isn't supported. This is mandatory.

Note: If the name is the same as that of a child node already in the system, the existing child node is overwritten.

IP / host name The IP address or host name of the child node. This parameter is mandatory.
Central logging

Indicates whether you can access logs and reports for this child node from the parent. This is mandatory. For:

  • Enabled — Enter: yes, on, or 1
  • Disabled — Enter: no, off, or 0

Note: Do not select this option if you want to view the child node’s logs on the child node itself.

Monitor status

Indicates whether you can view the node's status from the parent.

Status updates are available from the Overview page on the parent. This is mandatory. For:

  • Enabled — Enter: yes, on, or 1
  • Disabled — Enter: no, off, or 0
Central resources

Whether the parent node manages the child node's resources, such as quotas, which limit user access to web content. When turned on and quotas have been used in a web filtering policy, the parent ensures that users can't bypass their allocated quota by using a different child node.

This also permits the sharing of authentication login information to the parent node. For a detailed description of how to use this feature, see the help topic, Setting up a centrally managed system.

For:

  • Enabled — Enter: yes, on, or 1
  • Disabled — Enter: no, off, or 0
Replication profile

Replication profiles contain system settings shared from the parent node. From the list, select the replication profile to be deployed on the child node.

You create replication profiles on the parent node, see the help topic, Creating archives.

This field is optional and can be left blank.
Enabled

Determines if the node settings are turned on or off. This is mandatory. For:

  • Enabled — Enter: yes, on, or 1.
  • Disabled — Enter: no, off, or 0.
Comment

A comment. This field is optional.

It might consist of letters, numbers, spaces, underscores and full stops. Unicode isn't supported.

Example Child Node Data File

Southampton,192.168.11.1,no,yes,yes,,yes,Southampton branch _ manage own logs _ no replication

Leeds,192.168.12.1,no,yes,yes,Config,yes,Leeds branch _ manage own logs _ replicate config

Things you can do here

Importing child nodes

Page reference details

Child nodes

Something not right? .