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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Overview<br />

DNS services must be configured identically on all <strong>Sidewinder</strong> <strong>G2</strong>s<br />

that are part <strong>of</strong> the cluster.<br />

You should not connect directly to a <strong>Sidewinder</strong> <strong>G2</strong> that is<br />

designated as a secondary <strong>Sidewinder</strong> <strong>G2</strong>, unless you are<br />

configuring DNS.<br />

Note: See “Understanding the One-To-Many tree structure” on page 15-13 for<br />

details on configuring non-synchronized areas for secondary <strong>Sidewinder</strong> <strong>G2</strong>s.<br />

If you have VPNs configured, you must ensure that your load<br />

balancers are configured to send all traffic for a given VPN security<br />

association to a single <strong>Sidewinder</strong> <strong>G2</strong> within the cluster.<br />

The burb names must be identical for each <strong>Sidewinder</strong> <strong>G2</strong>.<br />

The corresponding burbs and NICs on each <strong>Sidewinder</strong> <strong>G2</strong> must<br />

all be on the same networks. For example:<br />

Burb Primary A Secondary B Secondary C<br />

Internet 10.1.182.15 10.1.182.25 10.1.182.35<br />

Web 192.168.183.15 192.168.183.25 192.168.183.35<br />

Cluster 192.168.184.15 192.168.184.25 192.168.184.35<br />

Using IP aliases, redirected addresses, and multiple address<br />

translation in proxy rules<br />

If you use IP aliases, redirected addresses, or multiple address<br />

translation (MAT) in any <strong>of</strong> the rules created on either the primary<br />

<strong>Sidewinder</strong> <strong>G2</strong> or on a secondary <strong>Sidewinder</strong> <strong>G2</strong>, this may cause<br />

problems in a One-To-Many cluster. This is because IP aliases,<br />

redirected addresses, and MAT define addresses that are specific to a<br />

<strong>Sidewinder</strong> <strong>G2</strong>. A <strong>Sidewinder</strong> <strong>G2</strong> that requires a unique IP address in<br />

a rule is not a good candidate for inclusion in a One-To-Many<br />

relationship.<br />

However, if a <strong>Sidewinder</strong> <strong>G2</strong> uses IP aliases or redirected addresses,<br />

you can still include it in a One-To-Many cluster by doing the<br />

following:<br />

Note: This procedure will not work with MAT.<br />

1. Define a group that contains all the alias IP addresses and redirected<br />

addresses used by your <strong>Sidewinder</strong> <strong>G2</strong>s.<br />

One-To-Many Clusters 15-3

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

Saved successfully!

Ooh no, something went wrong!