From owner-freebsd-questions@FreeBSD.ORG Wed Aug 8 14:58:41 2007 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E7DCF16A419 for ; Wed, 8 Aug 2007 14:58:41 +0000 (UTC) (envelope-from lreid@cs.okstate.edu) Received: from a.cs.okstate.edu (a.cs.okstate.edu [139.78.113.1]) by mx1.freebsd.org (Postfix) with ESMTP id C4DEA13C4A3 for ; Wed, 8 Aug 2007 14:58:41 +0000 (UTC) (envelope-from lreid@cs.okstate.edu) Received: from [172.18.0.137] (sky_cpfw-1.tulsatech.org [70.168.226.130]) by a.cs.okstate.edu (Postfix) with ESMTP id E6E5AA0882; Wed, 8 Aug 2007 09:58:40 -0500 (CDT) Message-ID: <46B9DA1C.1010906@cs.okstate.edu> Date: Wed, 08 Aug 2007 09:58:36 -0500 From: Reid Linnemann User-Agent: Thunderbird 2.0.0.0 (X11/20070615) MIME-Version: 1.0 To: Ewald Jenisch References: <20070808135858.GA2847@aurora.oekb.co.at> In-Reply-To: <20070808135858.GA2847@aurora.oekb.co.at> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: lagg(4) - configuration for /etc/rc.conf? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Aug 2007 14:58:42 -0000 Written by Ewald Jenisch on 08/08/07 08:58>> > Hi, > > Thanks to the hints posted here about "failover redundancy" I've > successfully set up lagg(4) in order to have a machine with redundant > failover connection to two switches. > > > The only thing that's missing is the correct configuration in > /etc/rc.conf. > > Here's what I've got so far in my rc.conf: > > defaultrouter="192.168.9.1" > if_lagg_load="YES" > ifconfig_bge0="UP" > ifconfig_bge1="UP" > ifconfig_lagg0="create" > ifconfig_lagg0="laggproto failover laggport bge0 laggport bge1 192.168.9.5 netmask 255.255.255.0" > > > The problem is that once the machine boots the "lagg0" interface > doesn't get created/activated; a "ifconfig" done after booting shows > that no lagg interface is there, but the physical interfaces (bge0, > bge1) are UP. > > > Only after I manually enable the lagg-interface it with "ifconfig > lagg0 create" the interface is created but then it automagically gets > the right IP-address and routing also works: > > # ifconfig > bge0: flags=8843 mtu 1500 > options=1b > ether 00:08:02:47:0d:56 > media: Ethernet autoselect (1000baseTX ) > status: active > lagg: laggdev lagg0 > bge1: flags=8843 mtu 1500 > options=1b > ether 00:08:02:47:0d:56 > media: Ethernet autoselect (100baseTX ) > status: active > lagg: laggdev lagg0 > lo0: flags=8049 mtu 16384 > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 > inet6 ::1 prefixlen 128 > inet 127.0.0.1 netmask 0xff000000 > lagg0: flags=8843 mtu 1500 > options=1b > inet 192.168.9.5 netmask 0xffffff00 broadcast 192.168.9.255 > ether 00:08:02:47:0d:56 > media: Ethernet autoselect > status: active > laggproto failover > laggport: bge1 flags=4 > laggport: bge0 flags=5 > > > I've tried numerous variations of the "ifconfig_lagg0"-lines in > /etc/rc.conf above - with or without create etc. - to no extent. Upon > boot the lagg-interface remains down basically cutting of the box from > the network until I enable the lagg-interface from the console :-(. > > Thanks much in advance for any clue, > -ewald > > Remember that what you put in rc.conf are variables, not instructions. You first define ifconfig_lagg0 to be "create", but then you turn around and redefine it to be "laggproto failover laggport bge0 laggport bge1 192.168.9.5 netmask 255.255.255.0". So when /etc/rc.d/netif fires off to configure interfaces, this redefinition is used for configuring the lagg0 interface. If you define ifconfig_lagg0 to be "create laggproto failover laggport bge0 laggport bge1 192.168.9.5 netmask 255.255.255.0", I would expect it to do what you want.