Nokia Network Voyager, Справочное руководство

Страница: 366 / 700

7
Configuring Traffic Management
368 Voyager Reference Guide
If node C becomes the master in the previous example, then its settings for
join-time shared features are copied to the other nodes. For example,
foobar.com would replace company-name.com on nodes A and B.
Caution
Be aware that if node C becomes the master in this scenario, its
settings override conflicting settings on the other nodes, which could
result in configuration issues. The best practice is to avoid conflicts in
the configurations of join-time shared features.
If a feature on a joining system has a setting and the feature is not configured
on the master, the joining system retains its setting. For example, assume that
you have a two node cluster in which DNS is a shared feature but no domain
name is configured on the master. If a third system joins the cluster and its
domain name is foobar.com before it joins, it retains that domain name after it
joins.
Configuring Features for Sharing
Follow these steps to ensure that the appropriate configuration settings are
identical on each cluster node:
1. After you create a cluster configuration on the first node, make sure all
the relevant settings are correct (on the Clustering Setup Configuration
page).
2. Scroll to the bottom of the Clustering Setup Configuration page and click
N
O
next to any features that should not share settings across the cluster.
Caution
After you click
A
PPLY
(the next step)
,
you cannot conveniently make
features sharable again if you make them unshared in this step. Make
sure that the settings are correct before you proceed.
3.
Click A
PPLY
.