Dear Frank, zlb-start should solve the problem, if not, you can make a
little modification inside /etc/init.d/zenload balancer startlocal section,
call to zlb-start at the end and the problem should be solved.
Let me know in order to guide you with this if needed
Sent from mobile
El 6 oct. 2016 6:04 p. m., "Frank Liebelt" <frank.lieb...@bca.com> escribió:
> Hi Emilio,
>
>
>
> i tried to add three routes for each SQL Backend Server and it worked fine.
>
>
>
> sql-data1 172.28.172.2 255.255.255.255 UGH 0 0 0 eth4
>
> sql-data2 172.28.172.2 255.255.255.255 UGH 0 0 0 eth4
>
> sql-data3 172.28.172.2 255.255.255.255 UGH 0 0 0 eth4
>
> 172.28.172.0 * 255.255.255.252 U 0 0 0
> eth4
>
>
>
> The problem is now, that this settings did not replicate to the second
> node.
>
> Manually add them also did not work because the interfaces are down until
> the secondary node is in standby.
>
>
>
> I think it would be a nice feature to setup extra gateways within the
> webpage.
>
> Frank
>
>
>
> *Von:* Emilio Campos [mailto:emilio.campos.mar...@gmail.com]
> *Gesendet:* Donnerstag, 6. Oktober 2016 03:27
> *An:* zenloadbalancer-support@lists.sourceforge.net
> *Betreff:* Re: [Zenloadbalancer-support] Connect to Farm with wrong IP.
> Here MySQL
>
>
>
> He system is using the network you configured as default gw because your
> mysql backend is not reachable directlry from some of your configured
> farms, that is a normal behaviour, try with a POSTROUTING rule:
>
>
>
> iptables -t nat -I POSTROUTING --destination <mysql_server>/32 -j SNAT
> --to-source <your_origin_IP>
>
>
>
> Enter as rules as backends.
>
>
>
> If you want to configure rules as persistent then use
> /usr/local/zenloadbalancer/config/zlb-start file
>
>
>
> Please apply and let me know.
>
>
>
> BTW: Also you could try to enter an additional route in the default route
> table.
>
>
>
> route add -host <mysql_server> gw 172.28.172.2
>
> Regards
>
>
>
> 2016-10-05 16:52 GMT+02:00 Frank Liebelt <frank.lieb...@bca.com>:
>
> Hi all,
>
>
>
> it has taken some time. Now I have a new setup on my cluster but get still
> the same effect.
>
>
>
>
>
> eth0 192.168.109.241 255.255.255.0 up
>
> eth0:ha 192.168.109.240 255.255.255.0 up
>
> ...
>
> eth4 172.28.172.1 255.255.255.252 GW 172.28.172.2 up
>
> eth5 172.28.172.5 255.255.255.252 GW 172.28.172.6 up
>
> eth6 172.28.172.9 255.255.255.252 GW 172.28.172.10 up
>
> eth7 172.28.172.13 255.255.255.252 GW 172.28.172.14 up
>
>
>
> Default Gateway is set to: 192.168.109.254
>
>
>
>
>
> Cluster:
>
>
>
> Zen latency is UP on LB-L-01 192.168.109.241 | Zen latency is UP on
> LB-l-02 192.168.109.242
>
> Cluster IP 192.168.109.240 is active on LB-L-01
>
> Zen Inotify is running on LB-L-01
>
>
>
>
>
> The configured mysql farm runs on eth4. Connections through eth4 are
> working, but the SQL Server denies the access because of a wrong source IP.
>
> Expected is 172.28.172.1 but given is the real IP of the current master.
> Currently 192.168.109.241.
>
>
>
> Here is the routing table that was autoamtically created on setup the
> cluster.
>
>
>
> Destination Router Genmask Flags Metric Ref Use
> Iface
>
> default 192.168.109.254 0.0.0.0 UG 0 0 0
> eth0
>
> 172.28.172.0 * 255.255.255.252 U 0 0 0
> eth4
>
> 172.28.172.4 * 255.255.255.252 U 0 0 0
> eth5
>
> 172.28.172.8 * 255.255.255.252 U 0 0 0
> eth6
>
> 172.28.172.12 * 255.255.255.252 U 0 0 0
> eth7
>
> localnet * 255.255.255.0 U 0 0 0
> eth0
>
>
>
>
>
> I am getting really frustated. Why the cluster routes the request not over
> eth4.
>
>
>
> Any ideas?
>
>
>
>
>
> regards
>
> Frank
>
>
>
>
>
>
>
>
>
> Hi Frank,
>
>
>
> Please check your routing table on each appliance. It seem that your
> routed interface to 172.28.10.1 is eth0, not eth4. You can share the
> routing table too.
>
>
>
> Best regards,
>
>
>
> On Fri, Aug 19, 2016 at 6:21 PM, Frank Liebelt <frank.lieb...@bca.com>
> wrote:
>
> Hi all,
>
>
>
> i set up a cluster and configured one farm.
>
> The farm profile is set to lx4nat.
>
> Protocol TCP, NAT is SNAT.
>
>
>
> When I use the Farm IP for connect to an MySQL Cluster, it will not pass
> the IP of the farm to the MySQL server. It is always the eth0 IP of the
> currently active load balancer.
>
> For my understanding, i should connect to the MySQL Server with the IP
> address of eth4. Like described in the manual.
>
>
>
> MySQL Client -> FarmIP 192.168.100.230 -> RealServer -> 172.28.10.1
>
> MySQL shows connection from 192.168.100.101 not 192.168.100.230
>
>
>
> Any suggestions what goes wrong?
>
>
>
> Here is my setup:
>
>
>
> LB Community Edition 3.10.1
>
>
>
> Appliance 1 (active):
>
> eth0: 192.168.100.101
>
> eth0:ha 192.168.100.100
>
> eth4: 192.168.100.230 (Farm)
>
>
>
> Appliance 2:
>
> eth0: 192.168.100.102
>
> eth0:ha 192.168.100.100
>
> eth4: 192.168.100.230 (Farm)
>
>
>
> The Replication between the two appliance is working well.
>
>
>
> regards
>
> Frank Liebelt
>
>
>
>
> ------------------------------------------------------------
> ------------------
>
> _______________________________________________
> Zenloadbalancer-support mailing list
> Zenloadbalancer-support@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/zenloadbalancer-support
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.sourceforge.net_lists_listinfo_zenloadbalancer-2Dsupport&d=DQMFaQ&c=z5qkHFDM6RsJxyBa-Q4_Eg&r=HuugatOAykURdOOcuNKGDKfoTl8zzw9zDZCjpZlx44A&m=gRlG73z7-7Uf6qluSghoAE01XKbyRT0HYQ208lPkDEE&s=v5_2UGVbtzuyST3CBBhN9HQeO5YXJt1y_8ftzFbGxMo&e=>
>
>
>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__sdm.link_slashdot&d=DQMFaQ&c=z5qkHFDM6RsJxyBa-Q4_Eg&r=HuugatOAykURdOOcuNKGDKfoTl8zzw9zDZCjpZlx44A&m=78uz0pQ7MIklLp1qTaGjZY9CT697B5JU7raPmACi_Nc&s=of5Gv_Ibt83LvIS0vRwpLe46Q5LTS0x94dVSxmIrVPY&e=>
> _______________________________________________
> Zenloadbalancer-support mailing list
> Zenloadbalancer-support@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/zenloadbalancer-support
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.sourceforge.net_lists_listinfo_zenloadbalancer-2Dsupport&d=DQMFaQ&c=z5qkHFDM6RsJxyBa-Q4_Eg&r=HuugatOAykURdOOcuNKGDKfoTl8zzw9zDZCjpZlx44A&m=78uz0pQ7MIklLp1qTaGjZY9CT697B5JU7raPmACi_Nc&s=moUqB4UB1TP3X3oR09HVDENk6xVcX4BfmsCscw2UTkU&e=>
>
>
>
>
>
> --
>
> Load balancer distribution - Open Source Project
> http://www.zenloadbalancer.com
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.zenloadbalancer.com&d=DQMFaQ&c=z5qkHFDM6RsJxyBa-Q4_Eg&r=HuugatOAykURdOOcuNKGDKfoTl8zzw9zDZCjpZlx44A&m=78uz0pQ7MIklLp1qTaGjZY9CT697B5JU7raPmACi_Nc&s=M8ptS4nt8sVxDDQ3eral-LiDt3n0H97YiaMZVJpbSHk&e=>
> Distribution list (subscribe): zenloadbalancer-support@lists.
> sourceforge.net
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> _______________________________________________
> Zenloadbalancer-support mailing list
> Zenloadbalancer-support@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/zenloadbalancer-support
>
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Zenloadbalancer-support mailing list
Zenloadbalancer-support@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/zenloadbalancer-support
