18.07.2013 Views

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

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

Sidewinder G2 6.1.2 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.

Considerations when using One-To-Many<br />

Chapter 16: One-To-Many Clusters<br />

Overview<br />

Please note the following considerations when using One-To-Many.<br />

• All <strong>Sidewinder</strong> <strong>G2</strong>s must be at the same version level.<br />

• You can define only one primary <strong>Sidewinder</strong> <strong>G2</strong> for each cluster.<br />

• A <strong>Sidewinder</strong> <strong>G2</strong> that is part <strong>of</strong> an HA cluster cannot participate in a One-<br />

To-Many cluster.<br />

• You cannot use a <strong>G2</strong> Enterprise Manager to manage a <strong>Sidewinder</strong> <strong>G2</strong> that<br />

belongs to a One-To-Many cluster.<br />

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

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

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

secondary <strong>Sidewinder</strong> <strong>G2</strong>, unless you are configuring DNS.<br />

• See “Understanding the One-To-Many tree structure” on page 484 for<br />

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

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

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

configured to send all traffic for a given VPN security association to a single<br />

<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 all be on<br />

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 translation<br />

(MAT) in any <strong>of</strong> the rules created on either the primary <strong>Sidewinder</strong> <strong>G2</strong> or on a<br />

secondary <strong>Sidewinder</strong> <strong>G2</strong>, this may cause problems in a One-To-Many cluster.<br />

This is because IP aliases, redirected addresses, and MAT define addresses<br />

that are specific to a <strong>Sidewinder</strong> <strong>G2</strong>. A <strong>Sidewinder</strong> <strong>G2</strong> that requires a unique IP<br />

address in 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, you can<br />

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

475

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

Saved successfully!

Ooh no, something went wrong!