Nokia Network Voyager, Reference Manual

Page: 365 / 700

Voyager Reference Guide 367
For example, if you want each cluster node to have the same static routes, you
configure the static routes on the first cluster node and make sure that static
routes are selected as a sharable feature. When other nodes become part of the
cluster, those routes are configured on them also.
If the system that is joining the cluster already has static routes configured,
they are retained. The routes copied as a result of the joining process are
added to the list of static routes.
What if Settings Conflict?
If there is a conflict between configuration settings on the existing node and
the joining system, the settings on the joining system are changed to those of
the master node. For example, assume that you have a cluster with nodes A
(the master) and B in which DNS is a shared feature and the domain name on
node A is company-name.com. If a third node (C) joins the cluster and its
domain name is foobar.com before it joins, foobar.com is replaced by
company-name.com during the joining process.
If you change the domain name on node C back to foobar.com, the domain
name remains foobar.com unless any of the following occurs:
!
node C leaves and rejoins the cluster
! node B becomes the master
!
a cadmin user changes the domain name (while logged into any node)
In the first two situations, node C will once again copy the settings for all the
join-time shared features, and company-name.com will replace foobar.com as
the domain name. In the third situation, the domain name is changed on all the
nodes.
If you want to be able to easily reset the configuration of node C to what you
had configured manually, simply save the desired configuration on C. If the
active configuration changes because of join-time sharing, you can reload the
desired configuration on C from the saved configuration file. See
“Managing
Configuration Sets” for information about saving and loading configuration
files.