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

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

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

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

Example scenario using a One-To-Many cluster<br />

Example<br />

scenario using a<br />

One-To-Many<br />

cluster<br />

476<br />

Figure 200: Sample<br />

network configuration for<br />

One-To-Many<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 />

2 Use the group name in the rule rather than the specific IP address.<br />

The group name will replace the unique IP alias or a redirected address in<br />

the rule.<br />

In the following example, there are three <strong>Sidewinder</strong> <strong>G2</strong>s protecting a local<br />

network. Network traffic is load balanced across the <strong>Sidewinder</strong> <strong>G2</strong>s using a<br />

load balancing tool such as Radware FirePro<strong>of</strong> or F5 Networks BIG-IP ®<br />

Controller, similar to the configuration depicted in Figure 199.<br />

Because each <strong>Sidewinder</strong> <strong>G2</strong> will be configured almost identically, the One-To-<br />

Many feature simplifies the management process. Any configuration changes<br />

you make from the primary <strong>Sidewinder</strong> <strong>G2</strong> will automatically be implemented<br />

on each <strong>of</strong> the secondary <strong>Sidewinder</strong> <strong>G2</strong>s, ensuring that all <strong>of</strong> your <strong>Sidewinder</strong><br />

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

Example scenario requirements<br />

This scenario requires the following:<br />

• Two or more <strong>Sidewinder</strong> <strong>G2</strong>s running at the same version.<br />

• A load balancing tool such as a Radware FirePro<strong>of</strong> or F5 Networks BIG-IP ®<br />

Controller.<br />

• The IP addresses used to access each <strong>Sidewinder</strong> <strong>G2</strong> must all reside in a<br />

burb <strong>of</strong> the same name. For example, in the sample network configuration<br />

shown in Figure 200, if you are accessing the <strong>Sidewinder</strong> <strong>G2</strong>s from the<br />

internal network, all IP addresses used to access the <strong>Sidewinder</strong> <strong>G2</strong> must<br />

reside in the burb named internal.<br />

External Network = 192.168.182.x<br />

Burb Name:<br />

external<br />

Burb Name:<br />

cluster<br />

Burb Name:<br />

internal<br />

A<br />

192.168.182.1<br />

10.1.183.1<br />

Internal Network = 10.1.183.x<br />

Burb Name:<br />

external<br />

Burb Name:<br />

cluster<br />

Burb Name:<br />

internal<br />

B<br />

192.168.182.2<br />

10.1.183.2<br />

Burb Name:<br />

external<br />

Burb Name:<br />

cluster<br />

Burb Name:<br />

internal<br />

C<br />

192.168.182.3<br />

10.1.0.1 10.1.0.1<br />

10.1.0.2 10.1.0.3<br />

10.1.183.3

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

Saved successfully!

Ooh no, something went wrong!