Kemp High Availability Bedienungsanleitung

High Availability (HA)

Feature Description

High Availability

(HA)

Feature Description

VERSION: 1.7

UPDATED: JUNE 2014

High Availability (HA)

Feature Description

Technologies logo are registered trademarks of KEMP Technologies, Inc..

KEMP Technologies, Inc. reserves all ownership rights for the LoadMaster product line including software

and documentation. The use of the LoadMaster Exchange appliance is subject to the license agreement.

Information in this guide may be modified at any time without prior notice.

Microsoft Windows is a registered trademarks of Microsoft Corporation in the United States and other

countries. All other trademarks and service marks are the property of their respective owners.

Limitations: This document and all of its contents are provided as-is. KEMP Technologies has made efforts

to ensure that the information presented herein are correct, but makes no warranty, express or implied,

about the accuracy of this information. If any material errors or inaccuracies should occur in this document,

KEMP Technologies will, if feasible, furnish appropriate correctional notices which Users will accept as the

sole and exclusive remedy at law or in equity. Users of the information in this document acknowledge that

KEMP Technologies cannot be held liable for any loss, injury or damage of any kind, present or prospective,

including without limitation any direct, special, incidental or consequential damages (including without

limitation lost profits and loss of damage to goodwill) whether suffered by recipient or third party or from

any action or inaction whether or not negligent, in the compiling or in delivering or communicating or

publishing this document.

Any Internet Protocol (IP) addresses, phone numbers or other data that may resemble actual contact

information used in this document are not intended to be actual addresses, phone numbers or contact

information. Any examples, command display output, network topology diagrams, and other figures

included in this document are shown for illustrative purposes only. Any use of actual addressing or contact

information in illustrative content is unintentional and coincidental.

Redistribution and use in source and binary forms, with or without modification, are permitted provided

that the following conditions are met:

1. Redistributions of source code must retain the above copyright notice, this list of conditions and the

following disclaimer

2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the

following disclaimer in the documentation and/or other materials provided with the distribution.

THIS SOFTWARE IS PROVIDED BY THE ABOVE COPYRIGHT HOLDERS ''AS IS'' AND ANY EXPRESS OR IMPLIED

WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND

FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE ABOVE COPYRIGHT

HOLDERS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR

CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR

SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY

THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR

OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE

POSSIBILITY OF SUCH DAMAGE.

The views and conclusions contained in the software and documentation are those of the authors and

should not be interpreted as representing official policies, either expressed or implied, of the above

Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA- and KEMP Technologies Inc. is in full compliance

of the GNU license requirements, Version 2, June 1991. Everyone is permitted to copy and distribute

verbatim copies of this license document, but changing it is not allowed.

High Availability (HA)

Feature Description

Redistribution and use in source and binary forms are permitted provided that the above copyright notice

and this paragraph are duplicated in all such forms and that any documentation, advertising materials, and

other materials related to such distribution and use acknowledge that the software was developed by the

University of California, Berkeley. The name of the University may not be used to endorse or promote

products derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING,

WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR

PURPOSE.

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated

documentation files (the "Software"), to deal in the Software without restriction, including without

limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the

Software, and to permit persons to whom the Software is furnished to do so, subject to the following

conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions

of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING

BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND

NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY

CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,

ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE

SOFTWARE.

This software is provided 'as-is', without any express or implied warranty. In no event will the authors be

held liable for any damages arising from the use of this software.

Permission is granted to anyone to use this software for any purpose, including commercial applications,

and to alter it and redistribute it freely, subject to the following restrictions:

1. The origin of this software must not be misrepresented; you must not claim that you wrote the original

software. If you use this software in a product, an acknowledgment in the product documentation would

be appreciated but is not required.

2. Altered source versions must be plainly marked as such, and must not be misrepresented as being the

original software.

3. This notice may not be removed or altered from any source distribution.

Permission to use, copy, modify, and/or distribute this software for any purpose with or without fee is

hereby granted, provided that the above copyright notice and this permission notice appear in all copies.

THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING

ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT,

INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS,

WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE

USE OR PERFORMANCE OF THIS SOFTWARE.

Used, under license, U.S. Patent Nos. 6,473,802, 6,374,300, 8,392,563, 8,103,770, 7,831,712, 7,606,912, 7,346,695, 7,287,084 and

6,970,933

High Availability (HA)

Feature Description

Table of Contents

1 Introduction ....................................................................................................................................6

1.1 Intended Audience.................................................................................................................. 6

2 Advantages of High Availability (HA) ..............................................................................................7

3 Prerequisites ...................................................................................................................................8

4 HA Components .............................................................................................................................. 9

5 Setting Up HA................................................................................................................................10

5.1 Set up the First Unit ..............................................................................................................10

5.2 Set Up the Second Unit.........................................................................................................12

5.3 Enable the “Use for HA Checks” Option ...............................................................................15

5.4 Test Failover..........................................................................................................................15

6 How to Perform a Firmware Update on HA Pairs.........................................................................17

7 HA Disaster Recovery Process (Replacing a Defective Unit).........................................................18

7.1 Prerequisites .........................................................................................................................18

7.2 Installation ............................................................................................................................18

7.2.1 Reboot the Active Unit..................................................................................................19

7.2.2 Change the Switch to Preferred Server Option ............................................................20

8 HA WUI Options............................................................................................................................21

8.1.1 Interfaces ......................................................................................................................21

8.1.2 HA Parameters ..............................................................................................................22

9 Troubleshooting............................................................................................................................ 26

9.1 General Troubleshooting Tips...............................................................................................26

9.2 No HA Status Squares are Visible in the WUI .......................................................................26

9.3 Green/Red HA Status Squares ..............................................................................................26

9.4 Blue HA Status Square ..........................................................................................................27

9.5 Both Units are Active and the WUI is Unresponsive –Blue or Red Status Square...............27

9.6 Grey HA Status Square..........................................................................................................27

9.7 Virtual Services Temporarily Unavailable After Failover ......................................................27

9.8 No Access to WUI on HA1/2 or Shared.................................................................................28

9.9 Nothing Works ...................................................................................................................... 28

9.10 Issue with Hyper-V and HA on a Pair of VLMs ...................................................................... 28

High Availability (HA)

Feature Description

9.11 HA Issue on VMware.............................................................................................................28

9.11.1 Both Units Think That They Are the Master Unit..........................................................28

9.11.2 Two Virtual LoadMasters on Different Hosts................................................................30

10 Replacing HA Units....................................................................................................................31

References ............................................................................................................................................36

Document History .................................................................................................................................37

High Availability (HA)

Feature Description

1Introduction

The LoadMaster system can be deployed as a single unit or in an active/standby dual-unit

configuration (HA). HA allows two physical or virtual machines to become one logical device.

Only one of these units is active and handling traffic at any one time. One unit is active and the

other is a hot standby (passive). This provides redundancy and resiliency, meaning if one

LoadMaster goes down for any reason, the hot standby can become active, therefore avoiding

any downtime.

HA in the LoadMaster for Azure product works a different way to that of a

regular LoadMaster. For more information and instructions on how to

configure HA on the LoadMaster for Azure, refer to the HA for Azure,

Feature Description document.

Three IP addresses are needed per active interface; one for the active unit, one for the passive

unit and one IP address for the shared interface.

1.1 Intended Audience

This document is intended to be read by anyone who is interested in learning about the HA

feature in the KEMP LoadMaster.

High Availability (HA)

Feature Description

2Advantages of High Availability (HA)

Figure 2-1: Typical 1-armed HA-setup

The ultimate goal of redundant LoadMasters is to provide reliable traffic management, even if

one LoadMaster becomes unavailable. The advantages of HA are as follows:

Eliminates a single point of failure

The second (passive) unit monitors the active unit to detect if a failure has occurred

Active connections and sessions are not lost when a fail-over occurs

High Availability (HA)

Feature Description

3Prerequisites

There are some prerequisites to be aware of before setting up HA:

Two LoadMasters must be set up and licensed

LoadMasters must be located on the same subnet in order to be in a HA pair

LoadMasters must be in the same physical location

A layer 2 connection (Ethernet/VLAN) is required

The LoadMasters must not be located further than 100 meters from each other

Ensure that you have more than one interconnection between the two LoadMasters to

avoid data or lack of availability

The two LoadMasters need the same default gateway

Use Network Time Protocol (NTP) to keep times on LoadMasters up-to-date. This

ensures that the times will be correct on any logs and that Common Address

Redundancy Protocol (CARP) message timestamps are in sync.

Ensure that any switches do not prevent MAC spoofing

Latency on the link between the two LoadMasters must be below 100 milliseconds

Multicast traffic flow is required in both directions between the devices

The appropriate LoadMaster license should be in place

Three IP addresses are required for each subnet in which the LoadMaster is configured

High Availability (HA)

Feature Description

4HA Components

The HA components are listed and described below.

CARP:

Keeps updated on the health of the partner

Governs whether the LoadMaster will take the active role

The Use for HA Checks option enables CARP requests to be sent over enabled interfaces.

This can be set for multiple interfaces.

When CARP is being used, packet analysis tools such as Wireshark,

incorrectly displays the protocol used as Virtual Router Redundancy

Protocol (VRRP). Any IP addresses displayed by the packet analysis tools

are fictitious and are not part of the CARP protocol.

Sync:

Sync maintains a “single image view” of the LoadMaster settings. It keeps the

LoadMaster up-to-date with changes made to Virtual Services and all other

configurations.

Notable exceptions that are not synchronized are; time and passwords

Keeps the standby LoadMaster updated on persistence updates

High Availability (HA)

Feature Description

5Setting Up HA

5.1 Set up the First Unit

To build a HA LoadMaster environment there are a number of settings that must be carefully

specified. Follow the steps below to set up HA:

1. Log in to the LoadMaster that is desired to be the active (master) unit.

2. In the main menu, select the System Configuration > Miscellaneous Options >HA

Parameters option.

Figure 5-1: HA Mode option

3. Select HA (First) Mode in the HA Mode drop-down.

Figure 5-2: HA question

4. Click OK on the resulting message.

Do not reboot at this time.

Figure 5-3: Shared IP address reminder

5. Click OK on the resulting message reminding not to forget to set the Shared IP address.

Figure 5-4: HA settings

Dieses Handbuch passt für folgende Modelle

Inhaltsverzeichnis

Beliebte Netzwerk-Router Handbücher anderer Marken

Allnet

Allnet ALL0333AU Bedienungsanleitung

HomeSeer

HomeSeer HT-SEL Bedienungsanleitung

Sercomm

Sercomm Genesis OC3505D Bedienungsanleitung

Billion

Billion BIPAC 5102 Series Bedienungsanleitung

TP-Link

TP-Link TD-8817 Bedienungsanleitung

Motorola

Motorola MR1900 Bedienungsanleitung

Digi

Digi IX14 Bedienungsanleitung

Cisco

Cisco NCS 540 Handbuch

XAVi

XAVi X8821e Bedienungsanleitung

BEC

BEC 6200WZL Bedienungsanleitung

MikroTik

MikroTik hAP ac3 Series Bedienungsanleitung

Korenix

Korenix JetNet 5428G Series Bedienungsanleitung

NETGEAR

NETGEAR FS526T - Switch Bedienungsanleitung

Korenix

Korenix JetNet 5710G Series Bedienungsanleitung

Automated Logic

Automated Logic ZN551 Betriebsanleitung

Cisco

Cisco ASR 1000 Series Bedienerhandbuch

EnGenius

EnGenius ESR-9710 Bedienungsanleitung

Cisco

Cisco 805 Series Bedienungs- und Sicherheitshinweise