18.07.2013 Views

Sidewinder G2 6.1.1 Administration Guide - Glossary of Technical ...

Sidewinder G2 6.1.1 Administration Guide - Glossary of Technical ...

Sidewinder G2 6.1.1 Administration Guide - Glossary of Technical ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Managing an HA cluster<br />

16-24 High Availability<br />

Configuring an entry in the Interfaces table<br />

The Cluster IP window allows you to specify the cluster common IP<br />

address for your interfaces. You will need to configure a cluster IP<br />

address for each interface that uses HA. Follow the steps below.<br />

Note: Be sure to add the cluster IP address and the associated domain name to your DNS<br />

service.<br />

1. In the Burb drop-down list, select the appropriate burb.<br />

Note: The Network Address field displays the local IP address for this <strong>Sidewinder</strong><br />

<strong>G2</strong>.<br />

2. In the Cluster IP Address field, type the cluster IP address for the<br />

interface that is shared between the primary and secondaries when<br />

they become active.<br />

The cluster address is the address most systems should use to<br />

communicate with or through the <strong>Sidewinder</strong> <strong>G2</strong>, meaning that DNS,<br />

default routes, etc. need to know this address.<br />

3. [Optional] In the Remote Test IP field, specify the address that the<br />

<strong>Sidewinder</strong> <strong>G2</strong> will periodically ping.<br />

The remote address must be a highly reliable system that is directly<br />

attached to the <strong>Sidewinder</strong> <strong>G2</strong> network. For example, if you use a VRRP<br />

(Virtual Router Redundancy Protocol) cluster, you can specify the VRRP<br />

address <strong>of</strong> the router as your remote ping address. (However, some<br />

VRRP routing clusters will only respond to pings if the configured<br />

primary router is currently acting as the primary. If you are using this<br />

type <strong>of</strong> VRRP routing cluster, you should use an alternative remote<br />

address.)<br />

For load sharing HA, if remote ping fails on one <strong>of</strong> the two cluster<br />

members, that member will become unavailable until the remote<br />

interface is again detected. If there is only one active cluster member<br />

and a remote ping failure is detected, that member will audit the failure<br />

and remain in the cluster until another member joins the cluster<br />

(without a ping failure), or until the remote system is detected.<br />

Note: If you specify 255.255.255.255 in this field, HA will only test the status <strong>of</strong> the<br />

interface rather than send data to verify that the interface is up.<br />

4. Click OK to save the cluster address information and return to the Local<br />

Parameters tab. (To exit the window without saving your changes, click<br />

Cancel.)

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!