Nokia Network Voyager, Reference Manual

Page: 375 / 700

Voyager Reference Guide 377
If you change the master by adjusting the performance rating, or if the master
changes because a joining system has a higher rating than the other nodes, the
settings of join-time shared features are propagated across the cluster at that
point. The settings on the new master are replicated on the other nodes.
Note
Do not change the performance rating of the master to 0. This will cause
the traffic load to be distributed unequally across the cluster.
Note
After you click
A
PPLY
, you might see a message that reads Joining in
progress. If so, refresh your browser. The message disappears and you
can proceed by clicking click
A
PPLY
and then
S
AVE
.
Managing join-time shared features
You can change the configuration settings of join-time shared features while
logged in as admin or cadmin, but the results are different:
! When you log in as cadmin (and use Cluster Voyager or the CCLI) and
change a setting of a shared feature, the change is made on all the nodes.
For example, if static routes are shared and you add a static route while
logged in as cadmin, the route is added to all the cluster nodes.
! When you log in as admin and change a configuration setting of cluster
shareable feature, the change is implemented on the node you are logged
into but not implemented on the other nodes. This is true even if you are
logged into the master node.
For example, if static routes are shared and you add a static route while
logged in as admin, the route is added to the node you are logged into but
not the other cluster nodes.
Changes made as cadmin overwrite any conflicting settings made by someone
logged into an individual cluster node as admin. However, nonconflicting
changes made as admin are not overwritten. For example, if you configure