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.

15<br />

Overview<br />

Figure 15-1. A typical<br />

One-To-Many and<br />

Cloning implementation<br />

15-2 One-To-Many Clusters<br />

<strong>Sidewinder</strong> <strong>G2</strong><br />

administrator<br />

Load<br />

balancing<br />

hardware<br />

Your local<br />

network<br />

Primary<br />

Secondary<br />

Secondary<br />

The One-To-Many feature is implemented in a "clustering" scheme.<br />

Clustering is used when you introduce a load balancing tool (as<br />

shown in Figure 15-1) into your network. All <strong>of</strong> the <strong>Sidewinder</strong> <strong>G2</strong>s<br />

reside in the same network and are basically either backups <strong>of</strong> one<br />

another or are being used to share the network load. In this scenario,<br />

each <strong>Sidewinder</strong> <strong>G2</strong> will have the same basic configuration (excluding<br />

host names and IP addresses).<br />

Tip: If you require centralized management to handle many <strong>Sidewinder</strong> <strong>G2</strong>s across<br />

multiple networks, you may want to consider implementing the <strong>Sidewinder</strong> <strong>G2</strong> Enterprise<br />

Manager INSTEAD <strong>of</strong> using One-To-Many. For information on the <strong>Sidewinder</strong> <strong>G2</strong><br />

Enterprise Manager, go to Secure Computing’s Web site at www.securecomputing.com.<br />

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

Load<br />

balancing<br />

hardware<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 />

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

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

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

<strong>G2</strong> that belongs to a One-To-Many cluster.

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

Saved successfully!

Ooh no, something went wrong!