Configuring Exinda Appliances for clustering

Before configuring clustering, the Exinda Appliances must be correctly cabled. It is recommended that each appliance in the cluster be connected and configured with a dedicated management port.

In addition, clustering requires a dedicated interface for traffic that is internal to the cluster. Any interface that is not bridged or in use for another role (e.g., Mirror or WCCP) may be used.

The table below lists the suggested cluster interface for each hardware series.

Hardware Series Cluster Interface
2000/4000 (EOL) eth1 (with Bridge 0 disabled)
4060/4061 eth2
5000 eth1
6000 eth5 (with Bridge 2 disabled)
6010 eth1
6060 eth2
7000 eth1
8060 eth2
10060 eth2
10063 eth2
10064 eth2
12063 eth2
12064 eth2
  • Where there are two appliances in a cluster, the cluster interfaces may be connected directly to each other with a CAT 5 cross-over cable.
  • Where there are more than two appliances in a cluster, the interface for each appliance in a cluster must be connected to a single, dedicated switch, such that each appliance can communicate with every other appliance without requiring a route (they must be on the same Layer 2 LANLocal area network segment).

Example: Configure cluster through the CLI

Configuration using the CLICommnad line interface is very similar to that of the Web UI.

  1. Configure a Cluster Internal address. Any interface not bound to a bridge or used in another role (e.g. Mirror or WCCP) may be used. This command will need to be run on each node in the cluster, and each with a unique Cluster Internal address.

(config) # cluster interface eth2

(config) # interface eth2 ip address 192.168.1.1 /24

  1. Configure the Cluster External IPInternet protocol. This command should be executed on all cluster nodes using the same Cluster External IP

(config) # cluster master interface eth1

(config) # cluster master address vip 192.168.0.160 /24

  1. Enable the cluster.

(config) # cluster enable

NOTE

Configuration changes should only be made on the Cluster Master node. The role of the node currently logged into will be displayed in the CLI prompt as shown below.

exinda-091cf4 [exinda-cluster: master] (config) #

  1. It is possible to view the status of all the members of a cluster from the CLI by issuing the following command.

(config)# show cluster global brief

Global cluster state summary

==============================

Cluster ID: exinda-default-cluster-id

Cluster name: exinda-cluster

Management IP: 192.168.0.160/24

Cluster master IF: eth1

Cluster node count: 2

ID Role State Host External Addr Internal Addr

-----------------------------------------------------------------

1* master online exinda-A 192.168.0.161 192.168.1.1

2 standby online exinda-B 192.168.0.162 192.168.1.2