{"id":50158,"date":"2021-08-05T09:00:16","date_gmt":"2021-08-05T07:00:16","guid":{"rendered":"https:\/\/nolabnoparty.com\/?p=50158"},"modified":"2026-04-29T12:27:01","modified_gmt":"2026-04-29T10:27:01","slug":"kemp-load-balancer-for-vmware-horizon-configure-ha-pt-3","status":"publish","type":"post","link":"https:\/\/nolabnoparty.com\/en\/kemp-load-balancer-for-vmware-horizon-configure-ha-pt-3\/","title":{"rendered":"Kemp Load Balancer for VMware Horizon configure HA - pt.3"},"content":{"rendered":"

\"kemp-load-balancer-configure-ha-01\"<\/p>\n

To avoid service disruption, the Kemp Load Balancer<\/a> should be configured in HA mode to ensure business continuity<\/strong> in case of appliance failures.<\/p>\n

The configuration of the Kemp LoadMaster in HA mode is pretty straightforward and it is the recommended design<\/strong> to be implemented in Horizon environments, especially where users connect from external<\/strong>.<\/p>\n

\"kemp-load-balancer-configure-ha-02\"<\/p>\n

 <\/p>\n

Blog Series<\/h2>\n

Kemp Load Balancer for VMware Horizon deployment - pt.1<\/a>
\nKemp Load Balancer for VMware Horizon configuration - pt.2<\/a>
\nKemp Load Balancer for VMware Horizon configure HA - pt.3<\/p>\n

 <\/p>\n

Kemp Load Balancer configure HA<\/h2>\n

To configure the Kemp LoadMaster in HA mode you need two appliances<\/strong>.<\/p>\n

 <\/p>\n

Prerequisites<\/h4>\n

The LoadMaster HA configuration requires some prerequisites<\/strong> to work as expected.<\/p>\n

    \n
  • Multicast traffic must be allowed<\/li>\n
  • IGMP Snooping must be disabled<\/li>\n
  • ICMP Ping must be allowed<\/li>\n
  • Port 6973 must be allowed<\/li>\n<\/ul>\n

     <\/p>\n

    Configure the Virtual Switch in vSphere<\/h4>\n

    To allow the correct HA communication<\/strong> between Kemp appliances, you need to configure the vSphere Virtual Switch accordingly.<\/p>\n

    Edit both LAN and DMZ networks<\/strong> used by the Kemp and configure the Security<\/strong> area as follows:<\/p>\n

      \n
    • Promiscuous mode<\/strong>: Reject<\/li>\n
    • MAC address changes<\/strong>: Accept<\/li>\n
    • Forget transmits<\/strong>: Accept<\/li>\n<\/ul>\n

      \"kemp-load-balancer-configure-ha-30\"<\/p>\n

      In the Teaming and failover<\/strong> area set the following parameter:<\/p>\n

        \n
      • Notify switches<\/strong>: No<\/li>\n<\/ul>\n

        \"kemp-load-balancer-configure-ha-31\"<\/p>\n

         <\/p>\n

        Configure the first Load Balancer<\/h4>\n

        Login to the first Kemp appliance and access the System Configuration > HA and Clustering<\/strong> area.<\/p>\n

        \"kemp-load-balancer-configure-ha-03\"<\/p>\n

        Select HA Mode<\/strong> and click Confirm<\/strong>. HA is an active-passive<\/strong> configuration since only one Kemp at time is active. Although Clustering mode<\/strong> would be a better solution, it requires at least three LoadMasters<\/strong> and it could be a limit if you have budget constraints.<\/p>\n

        \"kemp-load-balancer-configure-ha-04\"<\/p>\n

        Since we are configuring the first appliance, select HA (First) Mode<\/strong> in the HA Mode<\/strong> drop-down menu.<\/p>\n

        \"kemp-load-balancer-configure-ha-05\"<\/p>\n

        Click OK<\/strong> to confirm.<\/p>\n

        \"kemp-load-balancer-configure-ha-06\"<\/p>\n

        Click OK<\/strong> to acknowledge the message about Shared IP addresses.<\/p>\n

        \"kemp-load-balancer-configure-ha-07\"<\/p>\n

        To implement Kemp in HA mode, you need to specify an additional IP Address labeled as HA Shared IP address<\/strong> that is identical for both Kemp appliances. This IP Address is used to access the Web User Interface<\/strong> (WUI) management page and routing.<\/p>\n

        You need to specify a HA Shared IP address for both eth0 and eth1<\/strong> NIC interfaces using one LAN and one DMZ IP address. In addition, as best practice the Use for HA checks<\/strong> option should be enabled in all production interfaces.<\/p>\n

        Enter the IP Address and click Set Shared address<\/strong>.<\/p>\n

        \"kemp-load-balancer-configure-ha-08\"<\/p>\n

        Click OK<\/strong> to confirm.<\/p>\n

        \"kemp-load-balancer-configure-ha-09\"<\/p>\n

        Note that in the top-right of the screen there are now two indicator squares<\/strong>. They represent HA1 and HA2 and indicate the status of the HA pair<\/strong> (A is the active appliance). Since the second appliance has not yet joined the pair, the icon is red.<\/p>\n

        Enter the HA Partner IP Address<\/strong> (the IP of the second appliance) and click Set Partner address<\/strong>.<\/p>\n

        \"kemp-load-balancer-configure-ha-10\"<\/p>\n

        Click OK<\/strong> to confirm the configuration.<\/p>\n

        \"kemp-load-balancer-configure-ha-11\"<\/p>\n

        To apply the configuration, you need to reboot the appliance. Click Reboot Now<\/strong>.<\/p>\n

        \"kemp-load-balancer-configure-ha-12\"<\/p>\n

        Click Continue<\/strong>.<\/p>\n

        \"kemp-load-balancer-configure-ha-13\"<\/p>\n

        When the rebooted, the first appliance is now configured for HA mode<\/strong>. The green square indicates the active Kemp Load Balancer.<\/p>\n

        \"kemp-load-balancer-configure-ha-14\"<\/p>\n

         <\/p>\n

        Access the WUI management page<\/h4>\n

        From your preferred browser, enter the URL https:\/\/<kemp_HA_Shared_IP_Address><\/span> previously configured to access the WUI. Enter the bal<\/em> credentials and click Login<\/strong>.<\/p>\n

        \"kemp-load-balancer-configure-ha-15\"<\/p>\n

        This is the WUI page where you can manage the system<\/strong> when HA mode is enabled.<\/p>\n

        \"kemp-load-balancer-configure-ha-16\"<\/p>\n

         <\/p>\n

        Configure the second Load Balancer<\/h4>\n

        Once the first appliance has been configured, you need to configure also the second Kemp to complete the HA pair<\/strong>. Login to the second LoadMaster and go to System Configuration > HA and Clustering<\/strong> area.<\/p>\n

        \"kemp-load-balancer-configure-ha-17\"<\/p>\n

        Select HA Mode<\/strong> and click Confirm<\/strong>.<\/p>\n

        \"kemp-load-balancer-configure-ha-18\"<\/p>\n

        Select HA (Second) Mode<\/strong> from HA Mode<\/strong> drop-down menu.<\/p>\n

        \"kemp-load-balancer-configure-ha-19\"<\/p>\n

        Click OK<\/strong> to confirm the configuration.<\/p>\n

        \"kemp-load-balancer-configure-ha-20\"<\/p>\n

        Click OK<\/strong> to acknowledge the information about Shared IP addresses.<\/p>\n

        \"kemp-load-balancer-configure-ha-21\"<\/p>\n

        Enter the same HA Shared IP address<\/strong> configured in the first appliance then click Set Shared address<\/strong>.<\/p>\n

        \"kemp-load-balancer-configure-ha-22\"<\/p>\n

        Click OK<\/strong>\u00a0to confirm.<\/p>\n

        \"kemp-load-balancer-configure-ha-23\"<\/p>\n

        Enter the HA Partner IP Address<\/strong> (the IP of the first appliance) and click Set Partner address<\/strong>. Keep in mind to configure the HA Partner IP Address also for eth1<\/strong>.<\/p>\n

        \"kemp-load-balancer-configure-ha-24\"<\/p>\n

        Click OK<\/strong> to confirm.<\/p>\n

        \"kemp-load-balancer-configure-ha-25\"<\/p>\n

        To apply the configuration you need to reboot the appliance. Click Reboot Now<\/strong>.<\/p>\n

        \"kemp-load-balancer-configure-ha-26\"<\/p>\n

        Click Continue<\/strong>.<\/p>\n

        \"kemp-load-balancer-configure-ha-27\"<\/p>\n

        After rebooting the second appliance, access the Kemp LoadMaster's dashboard. Note that square indicators are now both green<\/strong>.<\/p>\n

        \"kemp-load-balancer-configure-ha-28\"<\/p>\n

        From the WUI you can specify which is the default server to use<\/strong>. Go to System Configuration > HA Parameters<\/strong> and select the desired value from the Switch to Preferred Server<\/strong> drop-down menu.<\/p>\n

        \"kemp-load-balancer-configure-ha-29\"<\/p>\n

        The Kemp Load Balancer is now configurated in HA mode ensuring service availability<\/strong> even if one Kemp appliance goes offline.<\/p>\n

        The HA Mode is recommended especially in Horizon environments with several users and external accesses to avoid disconnection<\/strong> if the Kemp connected to UAGs and Connection Servers experiences a failure.<\/p>\n

        \"signature\"<\/p>\n","protected":false},"excerpt":{"rendered":"

        To avoid service disruption, the Kemp Load Balancer should be configured in HA mode to ensure business continuity in case of appliance failures. The configuration of the Kemp LoadMaster in HA mode is pretty straightforward and it is the recommended design to be implemented in Horizon environments, especially where users connect from external.<\/p>\n","protected":false},"author":3,"featured_media":50160,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"rop_custom_images_group":[],"rop_custom_messages_group":[],"rop_publish_now":"initial","rop_publish_now_accounts":{"linkedin_93tdZWzMZc_93tdZWzMZc":"","facebook_2879994398731222_17841400390232720":"","twitter_113568041_113568041":"","mastodon_115463926174894442_115463926174894442":""},"rop_publish_now_history":[],"rop_publish_now_status":"pending","footnotes":""},"categories":[1025,2905],"tags":[1085,1711,2365,2366],"class_list":["post-50158","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-horizon-en","category-omnissa-en","tag-ha-en","tag-horizon","tag-kemp","tag-load-balancer","has_thumb"],"_links":{"self":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/50158","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/comments?post=50158"}],"version-history":[{"count":0,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/50158\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media\/50160"}],"wp:attachment":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media?parent=50158"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/categories?post=50158"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/tags?post=50158"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}