From owner-freebsd-hackers Sat Apr 25 06:12:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA23265 for freebsd-hackers-outgoing; Sat, 25 Apr 1998 06:12:11 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.artcom.de ([192.76.129.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA23260 for ; Sat, 25 Apr 1998 06:12:08 -0700 (PDT) (envelope-from hans@artcom.de) Received: from transrapid.artcom.de by mail.artcom.de with smtp id m0yT4jh-00000rC; Sat, 25 Apr 1998 15:11:21 +0200 (MEST) Date: Sat, 25 Apr 1998 15:11:21 +0200 (MEST) From: Hans Huebner To: freebsd-hackers@FreeBSD.ORG Subject: FreeBSD HA configuration / Ethernet address takeover Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello there, we're running some of our critial LAN services (NIS, DNS, mail etc.) on FreeBSD. The systems are quite stable, but from time to time we need to take a system down for maintenance purposes. Also, hardware problems can cause unplanned down times. I'm currently looking for a solution to configure a PC as a warm-standby fallback server for the most important services (NIS and DNS). To make a failover to the fallback server as transparent to the users as possible, it would be best if the fallback system could take over the ethernet address of the failed server. I've seen this work with certain (expensive) Solaris configurations, and I'd like to do something similar with FreeBSD. I tried to implement DNS failover by moving our name service IP address to another machine, but this resulted in severe client problems (most clients fail to renegotiate the MAC adress with ARP within finite time). Looking at the ifconfig manpage, I could not find a general way to set a Ethernet card's MAC address. Is there a documented solution to this problem? If not, would adding such functionality be problematic? Any pointers, hints or suggestions are greatly appreciated. I'd also be interested in any reports on running two FreeBSD systems on one shared SCSI bus. I suppose the disk driver would need to be changed quite a bit to make use of the RESERVE UNIT SCSI command to prevent access collisions. Thanks, Hans To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message