similar to: High Availability using 2 sites

Just to clarify, I'm looking at this from an application layer Point of View. One of the reasons why I'm looking at it that way, is because Tim said he was looking at LinuxHA..."application level" redundancy that uses IP. Tim, just to let you know, I don't believe that LinuxHA will work in the way you described, only because of the different IP ranges. It looks like Linux

I am setting up 2 Vyatta routers that will serve as redundant failover core routers out to the backbone of our ISP. They will be serving for routing between other branches and the ISP and bandwidth management. I am trying to differentiate between the plethora of information about having redundant, automatic failover routers and pretty much decided on VRRP for the IP address failover mechanism. I

Hello Les, Thanks for that info. I'm playing with this now and although the 'failover' process seems rather slow, it does seem to be doing what I need. I setup a subdomain entry to point to 4 IP's, only one if which is actually working, and indeed, when IE get's a non-active IP, it eventually goes to the next one until it finally finds the actual live IP. Once it gets the

In a nutshell and very first of all, you need at least 2 internet connections. Those ISP must be willing to setup BGP peering between your routers and theirs. Once that agreement has been made, you need to get their AS Numbers and submit the ASN request located on ARIN's website (http://www.arin.net). After some paperwork and money exchanges, ARIN assigns you an AS number. At that point,

Greetings to all, To start I’ll firstly lay down the foundation to what I have done so far and if those of you on the list can provide further insight, tips, links etc. This scenario consists of 2 firewalls (both running Debian “etch”), 2 Cisco routers (unsure of model numbers) connected together like so in the diagram below. ----------------------- | Uplink Provider |

I think RR DNS is the only viable solution under these circumstances. If you can cope with the fact that failovers won't be seamless, I don't think there's anything wrong with that though. On 07/21/2015 11:54 AM, Laz C. Peterson wrote: > The consensus seems to say no to RR DNS ? I am going to take that into serious consideration. > > With this proxy setup you describe, what

Round-robin DNS last I checked can be fraught with issues. While doing something else I came up with this idea: Clients --> Load Balancer(HAProxy) --> Dovecot Proxy(DP) --> Dovecot Director(DD) --> MS1 / MS2. When DP checks say user100 it'll find a host=DD-POD1 that returns two IPs, those of the two DD that sit in front of POD1. This DD pair is the only pair in the ring and

Hi Guys, I would just like to have advice and pointers of the best way would be, Someting like BGP or OSPF? I have 2 internet connections at diffrent locations. let say connection A and B 1.) router A has a fast internet connection and a seperate interface for clients using /lan/pppoe/ipsec etc and another ethernet interface going to router B 2.) router B has similiar setup as router A and

Last week someone in my localnetwork "abused" from our link, making everything slow... So I want to put the current Linux router as a traffic shaper. The setup is: +--- 128Kbit | "International" Local net --- [Linux router with ] -- ISP -- [magic routers]

Seeing as IPV4 is near it's end of life (http://www.internetnews.com/infra/article.php/3915471/IPv4+Nearing+Final+Days.htm), I'm curios as who know whether everyone is ready for the changeover to IPV6? Is anyone using it in production already, and what are your experiences with it? -- Kind Regards Rudi Ahlers SoftDux Website: http://www.SoftDux.com Technical Blog:

I''m being cast headlong into unfamiliar waters here, and being desperate for some air, thought I''d come here for some help. :) Anyway, my employer is going through some whiplash-inducing growth spurts, and as a result, the simple "Internet T-1 -> Linux Firewall/NAT -> LAN" setup just isn''t going to cut it anymore. First, we''re bringing in 2

One final consideration I forgot to mention, make sure you have a beefy router. Depending on your BGP configurations, if you want to receive all routes from the internet, that can seriously bog down a low end router. I'm not saying you can't get by with a low-end router, just make sure your router can handle the results of your BGP configs. --Todd -----Original Message----- From:

hi all, first i wann to explain my network & it''s problem, i am using a redhat el5 for multigateway routing, i have 3 adsl lines which is connected with eth0, eth2 and eth3. eth1 is my local network. those 3 lines comes with adsl modem from same isp with equal bandwidth (512 Kbps). In this adsl modems there is one lan and one wan port, adsl modem''s lan ip is gateway for my

Hi Rowland, you added the failover to your wiki: https://wiki.samba.org/index.php/Configure_DHCP_to_update_DNS_records_with_BIND9 It would be a good idea to explain some things. In your script you are using the port 519 and 520 for the failover: -------------- failover peer "dhcp-failover" { primary; address dc1.samdom.example.com; port 519; peer address

Anybody have any experience with setting up dhcpd in failover mode between two servers? I set this up on a couple of servers, and it seems to be working, but I don't think it is working "right". It appears both servers are replying to all requests (which for renewals works okay because they both give the same address, but new requests get two different responses). I thought that

Dear Experts, I was running ISC DHCP server for longer than I would care to remember. Now I decided to climb out of the cave and configure failover set (primary-secondary), and I seem to hit brick wall, which I need help with. I only need IP v4, no v6, which may simplify things. Could someone point to a description of working DHCP failover configuration? I do not want to make two independent

Hi All. I have a setup in which I have two servers serving nfs share. The nfs service is made highly available with pacemaker. When the primary server goes down the secondary starts nfs service. Service IP is floating between servers but they have NO "shared" storage/filesystem so NFS state/connection information in case of failover is lost. I have two clients. When the failover from

Hello Mailinglist, i was reading a paper regarding a Asterisk clustering solution and they where pretty excited about a feature in polycom phones: You can add a registration to a primary asterisk server You can add a registration to a secondary asterisk server The polycom phones will talk to the primary server as long as all goes well, If they have a problem with an INVITE, they

If I don't use DHCP failover, can you tell me how to do to to have manually dhcp start method working... I think I could made a mistake, this is what i did : ( I using Louis script from "old set of script" directory : https://secure.bazuin.nl/scripts/ ) - On server S4 : resolv.conf set to S4 first and S4bis in second - On server S4 : in dhcp-dyndns-debian.sh,

Hi, I'm using heartbeat as a failover for my asterisk server. on the active server 1 i have 10.10.10.1 eth0 10.10.10.3 secondary eth0 asterisk listens to the secondary ip, so that if server 1 fails, server 2 will then get that IP. so if server 1 fails, server 2 will have the IP 10.10.10.2 eth0 10.10.10.3 secondary eth0 problem is i have to bind asterisk to the secondary IP if dont, i