Re: Streamline conf problems

Martin Johansson <[email protected]> wrote:
> [-- multipart/alternative, encoding 7bit, 1 lines --]
> 
>    [-- text/plain, encoding 7bit, charset: US-ASCII, 52 lines --]
> 
> I'm trying to set up UM3 using the "Streamline High Availibility and Load
> Balancing" example
> 
> (http://www.ultramonkey.org/3/topologies/sl-ha-lb-eg.html).
> 
> 
> 
> I'm running UM3 on FC4.
> 
> 
> 
> I just can't get it to work and I need help to find my problem. I've
> attached my configuration.
> 
> 
> 
> My two machines (heidi, Claire) are both Directors / Real Servers. The only
> service I want to
> 
> Load Balance is HTTP. eth0 on both machines are the net where the VIP will
> be used. eth3
> 
> is used for Heartbeat. I will also add a serial link for Hearbeat later on.
> 
> 
> 
> Any of you guys have any suggestions on what might be wrong?

Nice diagram :)

That all seems fine to me, though I'm not that familiar with noarp
nor its interaction with this kind of setup. 

First can you check that when you start heartbeat on both of the nodes,
that after a small delay your VIP, 192.168.40.5 gets moved from lo to
eth0 on the active linux-director, most likely heidi.

If that works, then the next thing to check is that heidi is actually
responding to arp for 192.168.40.5. This should be easy enough to
diagnoise using tcpdump -n -i eth0 arp.

Next check that LVS is actually seeing packets and forwarding them.
While trying to make connections to 192.168.40.5 port 80, take a look at
ipvsadm -L, and again tcpdump -ne -i eth0 port 80 or icmp or arp (the -e
option is useful here as the link header will change if heidi forwards
packets to claire, without it you will see what look like duplicate
packets on the wire.)

Finally, again tcpdump is your friend, check to see if the daemons on
the real servers are responding, again tcpdump -ne -i eth0... is your friend.



-- 
Horms


-- 
Ultra Monkey - http://www.ultramonkey.org/
To UNSUBSCRIBE, email to [email protected], with a body:
unsubscribe ultramonkey-users [email protected]
where "[email protected]" is YOUR email address.