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 17: High Availability<br />

Managing an HA cluster<br />

This must be a dedicated heartbeat burb. For information on configuring<br />

a dedicated heartbeat burb, see “Configuring the heartbeat burbs” on<br />

page 493.<br />

d In the Heartbeat Verification Burb drop-down list, select the burb that<br />

HA will use to send or receive a mini-heartbeat. This should be a burb<br />

that regularly passes traffic, such as the internal burb.<br />

This mini-heartbeat helps protect against false failover events by doing<br />

the following:<br />

• If the <strong>Sidewinder</strong> <strong>G2</strong> does not detect the heartbeat but does detect<br />

the mini-heartbeat, the HA cluster does not fail over. An audit<br />

message is generated, alerting the administrator to check the<br />

heartbeat burbs’ connectivity.<br />

Important: Loss <strong>of</strong> communications on the heartbeat burb causes<br />

diminished HA services. For load sharing, the active secondary no longer<br />

shares the session load; it goes to a standby state. For non-load sharing,<br />

the standby cannot receive updated information about new ipfilter sessions<br />

established on the primary. Maintain high availability service to your network<br />

by troubleshooting the heartbeat burbs’ communication problems as soon<br />

as possible.<br />

• If the <strong>Sidewinder</strong> <strong>G2</strong> does not detect either the heartbeat or the miniheartbeat,<br />

the HA cluster fails over.<br />

Additional information on heartbeat verification is available in knowledge<br />

base article 3848.<br />

2 In the IPSec Authentication area, do the following:<br />

• In the Authentication Type field, select the type <strong>of</strong> IPSec authentication<br />

to use for HA:<br />

—SHA1: Select this option if using HMAC-SHA1 authentication.<br />

—MD5: Select this option if using HMAC-MD5 authentication<br />

e In the Password field, type the password that will be used to generate<br />

the authentication key for IPSec. This password must be the same for<br />

both <strong>Sidewinder</strong> <strong>G2</strong>s because they share the same virtual firewall ID.<br />

3 [Conditional] The Pair Members table lists the <strong>Sidewinder</strong> <strong>G2</strong>s that have<br />

been added to the HA cluster. To add a <strong>Sidewinder</strong> <strong>G2</strong> to the Pair Members<br />

table, see “Adding a placeholder in the HA cluster” on page 498. To view<br />

the status <strong>of</strong> the cluster, click Cluster Status. A pop-up window will appear<br />

displaying the status <strong>of</strong> each <strong>Sidewinder</strong> <strong>G2</strong>. To close the status information<br />

window, click Close.<br />

This table is not available until you successfully promote a primary. Once<br />

the primary has been promoted, you can add a second <strong>Sidewinder</strong> <strong>G2</strong> to<br />

the HA cluster. However, you must join the second <strong>Sidewinder</strong> <strong>G2</strong> before it<br />

will become functional within the HA cluster. See “Joining a <strong>Sidewinder</strong> <strong>G2</strong><br />

to an existing HA cluster” on page 499 for information on registering a<br />

<strong>Sidewinder</strong> <strong>G2</strong> to an HA cluster.<br />

505

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

Saved successfully!

Ooh no, something went wrong!