Can HAE Ip balance two servers? (EVAL Help)

SLES High Availability Extension
1

Looking at the HAE to solve an issue, not sure if it is capable of it…

Need it to do the following:

load balance 2 ldap servers running on physical hardware, the server running the HAE extension is running on a VMWARE server. All servers are in the same subnet

SITREP: Built a SLES 11 SP3 box at 10.0.0.163, went into IPLB and configured a “virtual server” at IP 10.0.0.166:636, added in real servers at 10.0.0.89:636 , and 10.0.0.88:636

Saved the config, checked that ldirectord was running…

can’t ping the virtual server, can’t access the ldap service, google fu fail since the LVS docs tend to refer to files overwritten by YAST, also tried a real IP on the server as the virtual also as 10.0.0.163:0 and 10.0.0.166:0

any ideas?

2

Hi dbgallo,

google fu fail since the LVS docs tend to refer to files overwritten by YAST

despite YaST maintaining the config files (which you could do without, for a test - just don’t call the appropriate YaST module during your manual tests), have you checked the resulting setup?

To assess your current situation, we’d need to see some details of your running configuration, especially the ldirectord setup.

Then the debugging results: How did you test ldap service access - via “ldapsearch”? What do you see that makes you believe you cannot access the service? What’s in the logs (i.e. slapd logs on the real servers, ldirectord log on that server), have you done any network traces to see what’s actually happening on the ldirectord host? What does it report regarding the status of the connection(s)?

Regards,
Jens

3

so the results are , can’t ping the VIP, can’t access LDAP via the VIP (Apache Directory Studio times out)

here is the ldirectord.cf file

logfile = "/var/log/LVS.log" virtual = 10.0.0.166:636 checktype = ping real = 10.0.0.88:636 gate real = 10.0.0.89:636 gate real = 10.0.0.242:636 gate

I can access the reals directly, and they can be pinged by the server hosting HAE. No communication showing up in iftop or iptraf referring to the VIP

4

Hi dbgallo,

[QUOTE=dbgallo;28121]so the results are , can’t ping the VIP, can’t access LDAP via the VIP (Apache Directory Studio times out)

here is the ldirectord.cf file

logfile = "/var/log/LVS.log" virtual = 10.0.0.166:636 checktype = ping real = 10.0.0.88:636 gate real = 10.0.0.89:636 gate real = 10.0.0.242:636 gate

I can access the reals directly, and they can be pinged by the server hosting HAE. No communication showing up in iftop or iptraf referring to the VIP[/QUOTE]

since you already quote that there’s a log file - anything in there that might help track this down?

Regards,
Jens

5

I wish there was, here’s the output to that logs following a. /etc/init.d/ldirectord stop and . /etc/init.d/ldirectord start

[Tue Jun 2 13:27:40 2015|ldirectord|32171] Purged virtual server (stop): 10.0.0.166:636 [Tue Jun 2 13:27:40 2015|ldirectord|32171] Linux Director Daemon terminated on signal: TERM [Tue Jun 2 13:27:50 2015|ldirectord|32297] Invoking ldirectord invoked as: /usr/sbin/ldirectord start [Tue Jun 2 13:27:50 2015|ldirectord|32297] Starting Linux Director v1.186-ha as daemon [Tue Jun 2 13:27:50 2015|ldirectord|32299] Added virtual server: 10.0.0.166:636 [Tue Jun 2 13:27:50 2015|ldirectord|32299] Added real server: 10.0.0.88:636 (10.0.0.166:636) (Weight set to 1) [Tue Jun 2 13:27:50 2015|ldirectord|32299] Deleted real server: 10.0.0.88:636 (10.0.0.166:636) [Tue Jun 2 13:27:50 2015|ldirectord|32299] Added real server: 10.0.0.242:636 (10.0.0.166:636) (Weight set to 1) [Tue Jun 2 13:27:50 2015|ldirectord|32299] Deleted real server: 10.0.0.242:636 (10.0.0.166:636) [Tue Jun 2 13:27:50 2015|ldirectord|32299] Added real server: 10.0.0.89:636 (10.0.0.166:636) (Weight set to 1) [Tue Jun 2 13:27:50 2015|ldirectord|32299] Deleted real server: 10.0.0.89:636 (10.0.0.166:636) [Tue Jun 2 13:27:50 2015|ldirectord|32299] Resetting soft failure count: 10.0.0.88:636 (tcp:10.0.0.166:636) [Tue Jun 2 13:27:50 2015|ldirectord|32299] Added real server: 10.0.0.88:636 (10.0.0.166:636) (Weight set to 1) [Tue Jun 2 13:27:50 2015|ldirectord|32299] Resetting soft failure count: 10.0.0.89:636 (tcp:10.0.0.166:636) [Tue Jun 2 13:27:50 2015|ldirectord|32299] Added real server: 10.0.0.89:636 (10.0.0.166:636) (Weight set to 1) [Tue Jun 2 13:27:50 2015|ldirectord|32299] Resetting soft failure count: 10.0.0.242:636 (tcp:10.0.0.166:636) [Tue Jun 2 13:27:50 2015|ldirectord|32299] Added real server: 10.0.0.242:636 (10.0.0.166:636) (Weight set to 1)