On Oct 2, 2012, at 3:11 PM, Aaron Hall <aaron.h...@washburn.edu> wrote:
> Our first thought was ISC's failover, but it doesn't seem well-suited > for us. We have a large and complex DHCP config (many subnets, many > static hosts), and failover doesn't keep the configs in sync. Further, > the config changes near-constantly during the day. Our wireless network > registration system (NetReg 1.3) stuffs new registrations into the DHCP > config (via an included file). We also have concerns about how > IP pool-sharing works, but that's secondary. We run an ISC-failover setup for our campus (same deal -- one server doesn't break a sweat). We split the pools between the servers. Just this week the failover saved our bacon when our primary DNS/DHCP/LDAP box bit the dust. Built a new machine, loaded the configs from version control, waited for the failover recovery period to elapse, and we had a working setup once again. We also have many subnets, options, and static hosts (include files). While we haven't tied it into a NetReg system, we make changes fairly regularly and it's not an issue from a production standpoint. I assume you're automatically reloading the configs when NetReg changes. In this case, you'd just need to push the changes to two systems instead of one. We use version control (subversion) to keep the configs in sync. We always make the config changes on our local machines, then commit to version control and check out the latest versions on the servers. You could easily script this (we do it by hand since it's not very frequent). The ISC guys have put a lot of effort into making their setup work; I'd give it another look. If you need to see a sample config to see if your needs are similar to ours, e-mail me off-list. There's nothing secret about them and I'd be happy to share. Jason -- Jason Healy | jhe...@logn.net | http://www.logn.net/ _______________________________________________ Tech mailing list Tech@lists.lopsa.org https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
