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.

Configuring HA<br />

8. Select the HA configuration that you want to create, and then click Next.<br />

Peer-To-Peer HA—Both <strong>Sidewinder</strong> <strong>G2</strong>s are configured as standbys<br />

with the same takeover time setting. Whichever <strong>Sidewinder</strong> <strong>G2</strong><br />

boots up first will act as the primary. If the primary becomes<br />

unavailable, the peer (acting as the standby) will take over as the<br />

primary and will remain as the acting primary until it becomes<br />

unavailable, at which time the peer will again take over as the<br />

acting primary. This is the recommended failover HA configuration.<br />

Load-Sharing HA—Load sharing HA consists <strong>of</strong> two <strong>Sidewinder</strong><br />

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

information on load sharing HA, see “Load sharing HA” on page 16-<br />

3.<br />

Primary-Standby HA—If the primary becomes unavailable, the<br />

standby takes over as the acting primary only until the primary<br />

becomes available again. (This option is generally used if you have<br />

<strong>Sidewinder</strong> <strong>G2</strong>s that do not share the same hardware<br />

configuration.) For more information on primary-standby HA, see<br />

“Failover HA” on page 16-4.<br />

Note: To configure peer-to-peer HA or load sharing HA, both <strong>Sidewinder</strong> <strong>G2</strong>s<br />

must have the same hardware configuration.<br />

9. [Conditional] In the High Availability Takeover Time window, specify the<br />

number <strong>of</strong> seconds that the primary must be unavailable before the<br />

secondary/standby will begin the takeover process. The default value is<br />

13 seconds.<br />

Note: This window does not appear if you selected the primary-secondary HA<br />

option. For primary-secondary HA, the takeover time is 3 seconds for the primary and<br />

13 seconds for the secondary by default and cannot be modified in the State Change<br />

Wizard.<br />

Click Next. The High Availability Cluster Common Addresses window<br />

appears.<br />

10. The High Availability Cluster Common Addresses window allows you to<br />

configure the cluster common addresses for the interfaces in your HA<br />

cluster. It also allows you to specify the heartbeat burb, which is<br />

responsible for sending and receiving heartbeats. Do the following, and<br />

then click Next:<br />

a. Select the interface row that you want to configure, and click<br />

Configure. The High Availability Aliases window appears.<br />

b. In the Cluster Common IP Address field, type the common IP address<br />

for the interface that will be shared between <strong>Sidewinder</strong> <strong>G2</strong>s within<br />

the HA cluster.<br />

High Availability 16-9

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

Saved successfully!

Ooh no, something went wrong!