Nokia Network Voyager for IPSO 4.0 Reference Guide 229
After You Create a Cluster
Whenever you use Cluster Voyager (or the CCLI), you can remove features from the list of ones
that are cluster sharable. You can do this on any node. However, Nokia recommends that you
avoid doing this. You should set up the appropriate feature sharing when you create a cluster and
then leave it unchanged.
If a feature is shared and you want to reconfigure it on all the cluster nodes, use Cluster Voyager
or the CCLI. Any changes you make are implemented on all the nodes automatically.
Making the Cluster Active
Nokia recommends that you configure a firewall and or VPN on the node before you activate the
cluster. For more information, see Check Point FW-1 documentation and “Configuring NGX for
Clustering.”
Note
If you do not configure a firewall on the node before you activate the cluster, you must click
disable next to Enable monitoring of VPN-1/FW-1? before you activate the cluster. After the
cluster is active, change this setting to enable. When this is set to
ENABLE, the cluster
monitors the firewall. If the firewall fails on a node, that node drops out of the cluster and
stops forwarding traffic.
Before you activate the cluster, click Save to store all the cluster configuration settings in the
configuration database on the hard disk.
To make the cluster active, click Up in the Cluster State field of the Cluster Status table.
You can make the cluster active only if the node has:
No VRRP or router services.
At least two configured interfaces participating in the cluster, including one primary
interface.
You receive error messages if the node does not meet these requirements.
Adding a Node to a Cluster
It is very easy to add Nokia appliances to an existing cluster. There are two methods you can use:
Joining (automatic configuration). This is the recommended method because:
The only tasks you must do on the joining systems are:
Configure interfaces with IP addresses in each of the networks the cluster will
connect to
Supply an IP address (a real addresses or a cluster IP address) that is already part of
the cluster when joining the cluster