quickstartguideLBv8 4
quickstartguideLBv8 4
Copyright © Loadbalancer.org
Table of Contents
1. About this Guide.........................................................................................................................................3
2. Appliance Configuration Overview.....................................................................................................3
3. Appliance Security.....................................................................................................................................3
Security Mode.......................................................................................................................................................................... 3
Default Passwords.................................................................................................................................................................. 4
Security Lockdown Script.................................................................................................................................................... 4
4. Deployment Concept..............................................................................................................................4
5. One-Arm and Two-Arm Topologies...................................................................................................5
6. Load Balancing Methods........................................................................................................................6
7. Appliance Deployment............................................................................................................................7
Virtual Appliance..................................................................................................................................................................... 7
Hardware Appliance............................................................................................................................................................... 7
Cloud Appliance...................................................................................................................................................................... 7
AWS......................................................................................................................................................................................... 7
Azure....................................................................................................................................................................................... 7
8. Configuring Initial Network Settings..................................................................................................7
Using the Network Setup Wizard.................................................................................................................................. 8
Using the WebUI................................................................................................................................................................ 11
9. Accessing the Web User Interface (WebUI)....................................................................................11
10. Ports Used by the Appliance.............................................................................................................13
11. Licensing...................................................................................................................................................13
12. Software Updates..................................................................................................................................13
13. Configuring & Testing a Simple Load Balanced Test Environment.....................................14
STEP 1 – Deploy the Appliance........................................................................................................................................ 14
STEP 2 – Run the Network Setup Wizard..................................................................................................................... 14
STEP 3 – Run the WebUI Setup Wizard......................................................................................................................... 14
STEP 4 – Viewing & Modifying the Configuration..................................................................................................... 16
STEP 5 – Checking the Status using System Overview............................................................................................ 17
STEP 6 – Verification & Testing........................................................................................................................................ 17
14. Configuring HA – Adding a Slave Appliance...............................................................................18
15. More Information..................................................................................................................................19
16. Loadbalancer.org Technical Support.............................................................................................19
17. Company Contact Information.......................................................................................................20
Note:
Please also refer to the Administration Manual for much more detailed information on setting up
the appliance and configuring a load balanced solution. For information on configuring the
appliance for specific applications, please refer to our extensive library of Deployment Guides.
3. Appliance Security
SECURITY MODE
To control how the appliance is accessed and which features are enabled, 3 security modes are provided:
IMPORTANT:
Only set the security mode to Secure – Permanent if you are 100% sure this is what you want!
Note:
For full details of all options, please refer to the Administration Manual (page 80).
DEFAULT PASSWORDS
We strongly recommend that default passwords are changed as soon as the appliance is deployed.
passwd
4. Deployment Concept
Once deployed, clients connect to the Virtual Service(s) (VIPs) on the load balancer rather than connecting
directly to one of the load balanced servers. These connections are then distributed between the load
balanced servers according to the load balancing algorithm selected.
Note:
We recommend that 2 appliances are deployed as an active/passive HA pair as shown above.
The slave appliance automatically takes over if the master unit fails. Please refer to page 18 for
more information on setting up an HA pair of Loadbalancer.org appliances.
One Arm
In this mode, the VIP and the load balanced servers are located in a single subnet. The load balancer
requires a single network interface adapter – eth0 in the diagram below.
LB.org
Remote
Clients Local
Clients Server 1 Server 2
Load
Clients Clients
Balancer
VIP
eth0
192.168.1.0/24
Note:
The example configuration on page 14 of this guide uses a one-arm topology.
Two Arm
In this mode, 2 subnets are used. The VIP is located in one subnet and the load balanced servers are
located in the other subnet. The load balancer requires 2 interfaces – eth0 and eth1 in the diagram below.
Note that this can be achieved by using two network adapters, or by creating VLANs on a single adapter.
It's also possible to add a secondary IP address / subnet to a single network adapter.
Remote
Clients Local
Clients
Clients Clients Server 1 Server 2
LB.org
VIP Load
192.168.2.0/24 eth0 192.168.1.0/24
eth1 Balancer
Layer 4 SNAT Fast layer 4 SNAT supporting both TCP & UDP One or Two-Arm
(Source Network
Address Translation) - Requires no Real Server changes
Layer 7 SSL Termination Usually required in order to process cookie One or Two-Arm
(Pound & STunnel) persistence in HTTPS streams on the load balancer
Layer 7 SNAT Layer 7 allows great flexibility including full SNAT One or Two-Arm
(Source Network and remote server load balancing, cookie insertion
Address Translation and URL switching
using HAProxy)
- Very simple to implement
- Requires no Real Server changes
- Not as fast as Layer 4 methods
(*) DR mode can also be used in a multi-homed configuration where real servers are located in different
subnets. In this case, the load balancer must have an interface in the same subnet to enable layer 2
connectivity which is required for DR mode to operate.
Key
Recommended if HTTP cookie persistence is required, also used for several Microsoft applications
such as Exchange, Sharepoint & Remote Desktop Services and for overall deployment simplicity since
real servers can be on any accessible subnet and no Real-Server changes are required
Only required for Direct Routing implementation across routed networks (rarely used)
Recommended when you want to load balance both TCP and UDP but you're unable to use DR mode
or NAT mode due to network topology or Real Server related reasons
Note:
Layer 7 SNAT mode is generally the simplest most flexible method to use. As mentioned above,
it's not the fastest method but enables a robust load balancing solution to be rapidly deployed.
This is illustrated by the simple example on page 14 of this guide.
Note:
Please refer to the Administration Manual (pages 26-32) for more detailed information on each
load balancing method.
7. Appliance Deployment
VIRTUAL APPLIANCE
The VA is currently available for VMware, Virtual Box, Hyper-V, KVM, Nutanix and XEN and has been
optimized for each Hypervisor. By default, the VA is allocated 1 CPU, 2GB of RAM and has an 8GB virtual
disk.
Note:
The Virtual Appliance can be downloaded here.
Note:
Please refer to the Administration Manual (page 35) and the ReadMe.txt text file included in each
VA download for more detailed information on deploying the VA using various Hypervisors.
HARDWARE APPLIANCE
For details of all hardware models and information on installing and connecting the appliance, please refer
to the Hardware Installation Guide.
CLOUD APPLIANCE
AWS
For details of deploying and configuring the Amazon Web Services (AWS) appliance please refer to the
AWS Quick Start Guide.
AZURE
For details of deploying and configuring the Microsoft Azure appliance please refer to the Azure Quick
Start Guide.
By default the load balancer is pre-configured with the following IP address & subnet mask:
Network settings can be changed either by running through the Network Setup Wizard as mentioned in
the startup message or by accessing the WebUI on the default IP address and changing the required
settings using the relevant menu options.
Note:
For the VA, 4 NICs are included but only eth0 is connected by default at power on. If the other
NICs are required, these should be connected using the network configuration screen within
the Hypervisor.
Username: setup
Password: setup
or
Once the wizard completes, the login prompt will be displayed along with a reminder of the new IP
address and the URL to connect to the WebUI:
https://192.168.2.21:9443/lbadmin/
Then use the relevant menu option to configure the various network settings:
• For IP address, subnet mask, bonding and VLANs use: Local Configuration > Network Interface
Configuration
• For the default gateway use: Local Configuration > Routing
• For DNS settings use: Local Configuration > Hostname & DNS
https://192.168.2.21:9443/lbadmin/
Note:
From v8.3.7, by default the WebUI is only accessible on HTTPS port 9443. For details on
configuring WebUI access and other security settings, please refer to page 3.
Username: loadbalancer
Password: loadbalancer
Note:
To change the password, use the WebUI menu option: Maintenance > Passwords.
The WebUI for the VA is shown. The hardware and cloud appliances are very similar, but have
different startup messages (shown yellow above).
1. Once logged in, you'll be asked if you want to run the web based setup wizard. If you click Accept
the Layer 7 Virtual Service configuration wizard will start (please refer to page 14 for details of
using the wizard). If you want to configure the appliance manually, simple click Dismiss.
System Overview – Displays a graphical summary of all VIPs, RIPs and key appliance statistics
Local Configuration – Configure local host settings such as IP address, DNS, system time etc.
Cluster Configuration – Configure load balanced services such as VIPs & RIPs
Maintenance – Perform maintenance tasks such as service restarts and taking backups
View Configuration – Display the saved appliance configuration settings
Reports – View various appliance reports & graphs
Logs – View various appliance logs
Support – Create a support download, contact the support team & access useful links
11. Licensing
The trial runs for 30 days and is completely unrestricted during this time. After 30 days, the appliance
continues to work but it's no longer possible to make changes to the configuration. If you need more time
to complete your evaluation, please contact [email protected] who will be able to provide guidance
on how to extend the trial using a simple command.
When a license is purchased, you'll be provided with a license key file by our sales team. You can then
simply apply this license to your appliance.
1. Using the WebUI, navigate to: Local Configuration > License Key
2. Browse to the license file provided when the appliance was purchased
3. Click Install License Key
Note:
If your appliance does not have Internet access, please contact [email protected] for
details of how to obtain the offline update files.
Note:
Layer 7 SNAT mode is used in the example. As mentioned earlier, this is not the fastest mode but
is very simple to deploy and requires no changes to the Real Servers.
LB.org
Test Web Web
Load
Client Server 1 Server 2
Balancer
1. Open the WebUI and start the wizard by clicking the Accept button, or by using the WebUI menu
option: Cluster Configuration > Setup Wizard and clicking General Layer 7 Virtual Service
2. Define the required Virtual Service settings as shown in the example below:
• Use the Add Real Server button to define additional Real Servers and use the red cross to
delete Real Servers
• Once you're happy, click Attach Real Servers to create the new Virtual Service & Real Servers
• A confirmation message will be displayed as shown in the example below:
5. Click Continue
6. Finally, reload HAProxy using the Reload HAProxy button in the blue box at the top of the screen or
by using the WebUI menu option: Maintenance > Restart Services and clicking Reload HAProxy
Note:
Running the wizard again will permit additional Layer 7 VIPs and associated RIPs to be defined.
Note:
To restore manufacturer's settings use the WebUI menu option: Maintenance > Backup &
Restore > Restore Manufacturer's Defaults. This will reset the IP address to 192.168.2.21/24.
Note:
By default Real Server health-checks set as a TCP port connect. If you need a more robust
check, this can be changed by modifying the configuration as explained below. Please refer to
the Administration Manual (page 201) for more information on configuring health-checks.
1. The VIP created by the wizard can be seen using the WebUI menu option: Cluster Configuration >
Layer 7 – Virtual Services as shown below:
Note:
Real Servers can be added manually using the WebUI menu option: Cluster Configuration >
Layer 7 – Real Servers.
1. Using the WebUI, navigate to: System Overview to view the newly created VIP & RIPs:
2. To view the RIPs, click anywhere on the horizontal gray area to expand the VIP as shown below:
1. Verify that both Real Servers are up. In the example below, Web2 is failing its health-check:
telnet 192.168.1.40 80
2. Once both servers are up (shown green) browse to the VIP address and verify that you see the web
page from each Real Server:
• Halt Web1 using the Halt option for Web1 in the System Overview and verify that content is
served by Web2 on a browser refresh (CTRL-F5)
• Halt Web2 using the Halt option for Web2 in the System Overview and verify that content is
served by Web1 on a browser refresh (CTRL-F5)
Note:
Please refer to the Administration Manual (page 246-261) for more configuration examples
using Layer 7 SNAT mode and also Layer 4 DR mode, Layer 4 NAT mode & Layer 4 SNAT mode.
Note:
For more information on verifying your test environment and ways to diagnose any issues you
have, please also refer to Chapter 12 – Testing Load Balanced Services in the Administration
Manual (page 263 – 268).
1. Deploy a second appliance that will be the slave and configure initial network settings
2. Using the WebUI, navigate to: Cluster Configuration > High-Availability Configuration
3. Specify the IP address and the loadbalancer users password (the default is 'loadbalancer') for the
slave (peer) appliance as shown above
4. Click Add new node
5. The pairing process now commences as shown below:
7. To finalize the configuration, restart heartbeat and any other services as prompted in the blue
message box at the top of the screen
Note:
Clicking the Restart Heartbeat button on the master appliance will also automatically restart
heartbeat on the slave appliance.
Note:
Please refer to the Administration Manual (page 221-234) for more detailed information on
configuring HA with 2 appliances.
Tel: +1 833.274.2566
Email (sales): [email protected]
Email (support): [email protected]
Tel: +1 866.998.0508
Email (sales): [email protected]
Email (support): [email protected]