Site map
- Product overview
- Installing Load Balancer
- Configuring Load Balancer
- Administering Load Balancer
- Tuning Load Balancer
- Troubleshooting Load Balancer
- Problem: Load Balancer will not run
- Problem: Load Balancer requests are not being balanced
- Problem: On a backend server with Windows Server 2008, memload.exe crashes
- Problem: Dispatcher, Microsoft IIS, and SSL do not work (Windows platform)
- Problem: dscontrol or lbadmin command fails
- Problem: Advisors not working correctly
- Problem: “Cannot find the file..." error message when trying to view online Help (Windows platform)
- Problem: Graphical user interface (GUI) does not start correctly
- Problem: Graphical user interface (GUI) does not display correctly
- Problem: On Windows platform, help windows sometimes disappear behind other open windows
- Problem: GUI hangs (or unexpected behavior) when trying to load a large configuration file
- Problem: Korean Load Balancer interface displays overlapping or undesirable fonts on AIX and Linux systems
- Problem: On Windows platform, unexpected GUI behavior when using Matrox AGP video cards
- Problem: Slow response time running commands on Dispatcher machine
- Problem: SSL or HTTPS advisor not registering server loads
- Problem: On Windows systems, corrupted Latin-1 national characters appear in command prompt window
- Problem: On Windows systems, advisors and reach targets mark all servers down
- Problem: On Windows systems, after network outage, advisors not working in a high availability setup
- Problem: On Linux systems, do not use "IP address add" command when aliasing multiple clusters on the loopback device
- Problem: On Solaris systems, Load Balancer processes end when you exit the terminal window from which they started
- Problem: Delay occurs while loading a Load Balancer configuration
- Problem: On Windows systems, an IP address conflict error message appears
- Problem: On Windows systems, "Server not responding" error occurs when issuing dscontrol or lbadmin
- Problem: On Linux, Dispatcher configuration limitations when using zSeries or S/390 servers that have Open System Adapter (OSA) cards
- Problem: Linux iptables can interfere with the routing of packets
- Problem: Unable to add an IPv6 server to the Load Balancer configuration on Solaris systems
- Upgrading the Java file set provided with the Load Balancer installation
- Problem: Client requests fail when using IPv6 MAC forwarding with HP-UX back-end servers
- Problem: On AIX systems, Load Balancer conflicts with IP security (IPsec)
- Problem: The serverUp script might run when you issue commands for Load Balancer that affect the status of servers
- Problem: Load Balancer will not use passive FTP mode
- Reference