Hello,
This may be an answer for Amos than anyone else.
This may be an answer for Amos than anyone else.
I don't sure if i had time to change the web proxy server design.
because the deadline is 1 week more.
And also for double bandwidth design.
because the deadline is 1 week more.
And also for double bandwidth design.
Are you have alternative option so that I can implement Failover by using my existing system.
Thanks in advance.
Thanks in advance.
Hierony Manurung
Del Institute of Technology
Network Management
Del Institute of Technology
Network Management
Pada Senin, 27 April 2015 9:56, Amos Jeffries <squid3@xxxxxxxxxxxxx> menulis:
On 27/04/2015 2:36 p.m., Hierony Manurung wrote:
> Dear Fellow,
> I want to implement Failover in My system, I have 3 Squid proxy servers right now. they are :
>
> - Child (172.30.20.200/16) # receive request, and forward it either to Parent1 or Parent2
> - Parent1 (172.31.20.201/16)
> - Parent2 (172.31.20.204/16)
>
> I use Mikrotik to connect all the servers, and they have been connected and they can work together (distributed caching). For the caching algorithm, I use round-robin algorithm.
> How can i implement Failover in my system?, so that when Child proxy is down/crash the request move to another Parent proxy.
You can't with this setup. The Child proxy is a bottleneck and the
failover copes with either of the Parents being down but not the Child.
If you are going to have a failover from Child to Parent, then you may
as well have all three proxies operating in a "flat"/horizontal design
as siblings all independently able to connect upstream.
The failover logics in that design is configured into the Mikrotik
somehow (I dont know how exectly though sorry). Or in a PAC file given
to the clients.
The design you have with a single router acting as hub for clients and
three proxies in a 2-tier design sounds like you have traffic travelling
over the same router 2-3 times on its way to the Internet (and same for
the responses). That will be cutting your available router bandwidth by
as much as 60%. You can probably double your bandwidth by using two
routers and two NICs on each proxy - without changing the uplinks
themselves.
Like so:
clients-> router1 (load balancing)->proxies->router2->Internet
Amos
_______________________________________________
squid-users mailing list
squid-users@xxxxxxxxxxxxxxxxxxxxx
http://lists.squid-cache.org/listinfo/squid-users
> Dear Fellow,
> I want to implement Failover in My system, I have 3 Squid proxy servers right now. they are :
>
> - Child (172.30.20.200/16) # receive request, and forward it either to Parent1 or Parent2
> - Parent1 (172.31.20.201/16)
> - Parent2 (172.31.20.204/16)
>
> I use Mikrotik to connect all the servers, and they have been connected and they can work together (distributed caching). For the caching algorithm, I use round-robin algorithm.
> How can i implement Failover in my system?, so that when Child proxy is down/crash the request move to another Parent proxy.
You can't with this setup. The Child proxy is a bottleneck and the
failover copes with either of the Parents being down but not the Child.
If you are going to have a failover from Child to Parent, then you may
as well have all three proxies operating in a "flat"/horizontal design
as siblings all independently able to connect upstream.
The failover logics in that design is configured into the Mikrotik
somehow (I dont know how exectly though sorry). Or in a PAC file given
to the clients.
The design you have with a single router acting as hub for clients and
three proxies in a 2-tier design sounds like you have traffic travelling
over the same router 2-3 times on its way to the Internet (and same for
the responses). That will be cutting your available router bandwidth by
as much as 60%. You can probably double your bandwidth by using two
routers and two NICs on each proxy - without changing the uplinks
themselves.
Like so:
clients-> router1 (load balancing)->proxies->router2->Internet
Amos
_______________________________________________
squid-users mailing list
squid-users@xxxxxxxxxxxxxxxxxxxxx
http://lists.squid-cache.org/listinfo/squid-users
_______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
