Manually Adding Child Nodes to the Parent Node

Note: This topic applies to the Kenilworth Release.

On the parent node, you must list all the child nodes that the parent replicates to.

1. From the parent node, go to System > Central management > Child nodes.

2. Click Add node.
3. From the Node details section, configure the following:
Node name — Enter a unique name to identify the node. Node names may only consist of letters, numbers, spaces, underscores and full stops. Unicode is not supported. This parameter 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/hostname — Enter the IP address or hostname of the child node. This parameter is mandatory.
Comment — Optionally, enter a comment describing the child node.
4. From the Node settings section, configure the following:
Replication profile — Replication profiles contain system settings shared from the parent node. If required, from the drop-down list, select the replication profile to be deployed on the child node.

You create replication profiles on the parent node, see Managing Archives.

Note: Any service objects or service object groups you create on the parent node are replicated to the child nodes in addition to their own service object configuration. These are prefixed with Replicated: in the relevant user interface pages. For more information about service objects, see Working with Service Objects.

Central logging — Select to access logs and reports for this child node from the parent.

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

Allow parent to monitor status — Select to be able to view node status from the parent.

Status updates are available from the System > Central management > Overview page on the parent.

Allow information sharing — Select to enable information sharing between the child and parent nodes, such as Guardian quotas which limit user access to web content. When enabled and quotas have been used in a web filtering policy, the parent ensures that users cannot bypass their allocated quota by using a different child node.
5. Select Enable node.
6. Click Confirm.
7. When prompted, review the node details and then click Save to add the node.