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.

HA configuration<br />

options<br />

Chapter 17: High Availability<br />

HA configuration options<br />

To implement an HA cluster in your network, you will need one additional<br />

“cluster common” IP address for each network. The HA cluster will use these<br />

addresses as IP alias addresses. The table below summarizes the IP<br />

addresses needed for this HA configuration.<br />

In this example, all users in the internal or external network must use the<br />

cluster address (aaa.aaa.aaa.5 or bbb.bbb.bbb.5, respectively). Only system<br />

administrators should know about the other IP addresses. The same concept<br />

applies for DNS names.<br />

Tip: When configuring an existing single <strong>Sidewinder</strong> <strong>G2</strong> configuration to become<br />

an HA cluster, consider using the existing interface addresses as the cluster<br />

addresses and getting new IP addresses for the actual NICs. This lessens the<br />

impact on your users, who will not have to change their perception <strong>of</strong> the<br />

“<strong>Sidewinder</strong> <strong>G2</strong>” address.<br />

You can configure HA to perform load sharing (with both <strong>Sidewinder</strong> <strong>G2</strong>s<br />

actively processing traffic) or failover (with one <strong>Sidewinder</strong> <strong>G2</strong> processing<br />

traffic and the other <strong>Sidewinder</strong> <strong>G2</strong> standing by as a hot backup). The following<br />

sections discuss each HA configuration option.<br />

Load sharing HA<br />

internal burb external burb heartbeat burb<br />

primary IP aaa.aaa.aaa.1 bbb.bbb.bbb.1 ccc.ccc.ccc.1<br />

secondary/standby<br />

IP<br />

cluster common IP aaa.aaa.aaa.5 a<br />

aaa.aaa.aaa.3 bbb.bbb.bbb.3 ccc.ccc.ccc.3<br />

bbb.bbb.bbb.5 a<br />

ccc.ccc.ccc.5<br />

a. In a load sharing HA cluster, the internal and external cluster common IP<br />

addresses are shared between <strong>Sidewinder</strong> <strong>G2</strong>s. In a failover HA cluster, they are<br />

assigned to the primary.<br />

Load sharing HA, also referred to as active-active HA, consists <strong>of</strong> two<br />

<strong>Sidewinder</strong> <strong>G2</strong>s that actively process traffic in a load sharing capacity. When a<br />

secondary is registered to an HA cluster, synchronized areas will be<br />

overwritten by the HA cluster configuration to match the primary. (To determine<br />

which areas are synchronized, see “Managing an HA cluster” on page 503.)<br />

Each <strong>Sidewinder</strong> <strong>G2</strong> maintains its own private (individual) address, the cluster<br />

common address for each interface (excluding the heartbeat interface), and<br />

any other alias addresses. The <strong>Sidewinder</strong> <strong>G2</strong>s are then able to coordinate<br />

traffic processing on a single shared IP address using a multicast Ethernet<br />

address to ensure that each connection (and the packets associated with that<br />

connection) is handled by the same <strong>Sidewinder</strong> <strong>G2</strong>. To configure load sharing<br />

HA, both <strong>Sidewinder</strong> <strong>G2</strong>s must have the same hardware configuration (e.g.,<br />

CPU speed, memory, active NICs).<br />

489

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

Saved successfully!

Ooh no, something went wrong!