Copyright © 2002 - 2014 KEMP Technologies, Inc. All Rights Reserved. Page 28 / 37
High Availability (HA)
Feature Description
9.8
No Access to WUI on HA1/2 or Shared
If the WUI is inaccessible via any of the three IP addresses, try the steps below:
Wait 5 minutes and try again. Sometimes WUI access has not yet been activated, even
though the LoadMaster is responding to pings.
Try a different web browser
Clear the web browser cache
Try from a different computer
Log in to the console (of the IP address where the problem is occurring) via SSH, go to
option
3 Local Administration
,
4 Web Address
and
s Immediately Stop Web Server
Access
, which will then turn into
s Immediately Start Web Server Access
. This should
restart hanging WUI access.
9.9
Nothing Works
If everything in this troubleshooting section fails try to shut down one of the LoadMasters. The
remaining LoadMaster should take over. This can remain in HA mode or be set to single –
whichever works. This will provide a working solution until a more permanent fix can be found.
9.10
Issue with Hyper-V and HA on a Pair of VLMs
If you are having problems with Hyper-V and HA on a pair of VLMs, the following Microsoft
TechNet article may help you to fix the problem:
http://technet.microsoft.com/en-
us/magazine/ff458341.aspx
9.11
HA Issue on VMware
9.11.1
Both Units Think That They Are the Master Unit
Figure 9-1: Unit 1
Figure 9-2: Unit 2
In some situations, when using HA in a VMware environment, both units might think that they
are the master unit and they may see the other unit as pacified (represented by a blue HA status
square). This issue could be caused by the VMware Switch configuration. To resolve this issue,
select the options as outlined below on the virtual switch.
