WebSphere Application Server & Liberty

WebSphere Application Server & Liberty

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only
Expand all | Collapse all

websphere load balancer high availability problem

  • 1.  websphere load balancer high availability problem

    Posted Tue May 07, 2013 05:14 AM
    Hello
    we have implemented load balancer architecture we have two load balancer, sometimes our primary load balancer became standby and standby load balancer became active when we check primary load balancer we find that executor is running (when we run dscontrol e start command we receive the error that says that Executor is already running), but high availability status is N/A and we see the following error in reach.log
    Error from getHAInfo(). iRc = -1
    And the following error in hamon.log
    HAM: Encountered an error getting status from the kernel. iRc = -1. and the following is the output of running ./dscontrol hi stat command:
    Error: Failed to retrieve high availability status.
    Our load balancer version is 8.0.0.5 and our operating system is suse linux enterprise 11 sp 2.
    Please help us. Thanks


  • 2.  websphere load balancer high availability problem

    Posted Tue May 07, 2013 12:09 PM
    Sara

    you have two loadbalancer's with active-passive setup and present situation is  when the first (primary) failsover to secondery (standby). So the configuration is simple high availability, am i correct ?

    are both LB machines were on the same subnet ?


    as per design..

    • The cluster, port, and server statements must be placed before the high availability statements which means .. HA statements must be placed at the end of the script that setup the HA.

    • When the backup device takes over the load balancing function, the cluster IP address is removed from the backup device and added to the new primary device. 

    • When HA synchronizes, it looks for the cluster, port, and server definitions when a connection record is received.

    • If the cluster, port, and server do not exist, the connection record is dropped.

    • If a takeover occurs and the connection record has not been replicated on the partner machine, the connection fails.