Configuring Clustering

Note: Unlike a traditional cluster, a WebApp Secure cluster does not automatically balance traffic between each of the nodes. For this reason, a load balancer is required to be configured to send traffic to each traffic processing node.

Setting up a cluster is as easy as configuring multiple stand-alone boxes. The first step is to set up the master. You must set up the master first because you will need to supply the master's IP when initializing the traffic nodes.

Initialize the appliance like you would any stand-alone appliance - by typing system initialize from the WebApp Secure CLI. When the prompt for Select System Mode appears, select Master from the list of available appliance modes. Wait for the process to complete.

The setup process will initialize the master, and once the initialization is complete, you should be able to navigate to the management interface at https://HOSTNAME:5000. Once the master is initialized, you can initialize the other appliances as traffic processing nodes. The steps are similar to the master setup, however you will be prompted to enter the IP of the master node after selecting Traffic Processor as the appliance mode on the additional appliances.

When using a clustered appliance configuration, it is important to configure a valid listening IP address on the Traffic Processor for every application that will use SSL. You can configure a listening interface by navigating to the Traffic Processor's terminal, and using system set interface from within the WebApp Secure CLI. For more information on how to configure an interface, see The CLI: The Set Command. The application must also be bound to the IP address assigned to that interface. This can be achieved through the application configuration settings in the Web UI. To learn how to create SSL applications, see Enable SSL to the Client.

Once the traffic node is initialized, you can verify the cluster by navigating to the management interface (https://HOSTNAME:5000) and clicking on System Stats. There should be a separate tab for each node in the cluster, and an additional tab for the aggregate cluster data.

Note: Remember that you must use an external load balancing solution to point to each traffic processing node, as the cluster will not do this for you.

Related Documentation