Comments on Robbie Clutton: Load Balancing and High Availablity with Ultra Mon...

From memory, you should only have to use sticky se...

2009-03-07T09:02:00.000Z

From memory, you should only have to use sticky sessions for transactional requests, i.e. invite-ack-ok, once the session has been initiated any node can take responsibility for handing the rest of the call assuming it has access to the data source with the call leg information.

Boby,
We have several customers at www.Loadbala...

2009-03-05T20:05:00.000Z

Boby,
We have several customers at www.Loadbalancer.org load balancing VOIP & asterix and other technologies. You just need to enable persistence (sticky) in your LVS or ldirectord configuration. If you need to group multiple ports and UDP etc. then you can use firewall marks with persistence. Persistence simply ensures that all requests from one source IP address will always go to the same VOIP server in the cluster.

Hi Boby,

Yes, if you're using REGISTER, it...

2008-05-06T08:09:00.000+01:00

Hi Boby,

Yes, if you're using REGISTER, it won't be the load balancer who registers but it'll be the client whose target endpoint is the load balancer, the REGISTER request will get forwarded to a server in the cluster.

I haven't used Asterix, so I don't know if you can cluster your registration sessions but you might get an issue if you're registered against server1, but the LB forwards subsequent requests to server2.

tkhs rob, for the answer
i'm stil little confu...

2008-05-05T22:58:00.000+01:00

tkhs rob, for the answer
i'm stil little confuse with the client doesn't need to be registerd with the real server. because usually when we start the VOip communication the client must sent SIP REGISTER to the server.
i try to used the ipvsadm to get along with asterisk sip server. i confgured the virtual service and the real service to work in port 5060 but it doesn't work. Form the client (using xlite softphone) it always failed to register with the server.

thks a lot for the attention robbie.

Boby, the director is essentially a packet forward...

2008-05-04T11:43:00.000+01:00

Boby, the director is essentially a packet forwarding application and so doesn't need to be registered (not in the application we were using anyway, you may have some IP address restrictions in yours). It also doesn't need to be on the same box, it can send it anywhere.

Hope that helps

i'm sorry it did.n mention it clearly. i mean if i...

2008-05-04T04:35:00.000+01:00

i'm sorry it did.n mention it clearly. i mean if i want to have load balancing service with Asterisk Voip of course the client must be registered with the server. thks

hi robbie, nice post. i want to ask something.
...

2008-05-04T04:33:00.000+01:00

hi robbie, nice post. i want to ask something.
in that topologies the director must be have same service with the real server or it just forward the sip request?
have you try it with asterisk voip server ?

thanks for the tip, anything to increase performan...

2008-02-13T23:42:00.000Z

thanks for the tip, anything to increase performance.

Good stuff. As a note I'd add that LVS also allows...

2008-02-13T20:50:00.000Z

Good stuff. As a note I'd add that LVS also allows for a non-NAT setup called "Direct Routing" (DR), where packet forwarding is done on the Ethernet level (the director just changes the MAC address to the realserver's without touching IP, and drops the packet into the LAN).
This allows for higher performance and better scalability.

I covered this in more detail here (clusteradmin.net), if anybody is interested.

-marek