Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 8 Aug 2007 11:17:12 -0400
From:      John Nielsen <lists@jnielsen.net>
To:        freebsd-questions@freebsd.org
Cc:        Ewald Jenisch <a@jenisch.at>
Subject:   Re: lagg(4) - configuration for /etc/rc.conf?
Message-ID:  <200708081117.12825.lists@jnielsen.net>
In-Reply-To: <20070808135858.GA2847@aurora.oekb.co.at>
References:  <20070808135858.GA2847@aurora.oekb.co.at>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wednesday 08 August 2007 09:58:58 am Ewald Jenisch wrote:
> 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"

This belongs in /boot/loader.conf, not /etc/rc.conf.

> ifconfig_bge0="UP"
> ifconfig_bge1="UP"
> ifconfig_lagg0="create"

This should be:
 cloned_interfaces="lagg0"


Once you fix those two things you should be in good shape.

JN

> 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<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
>         options=1b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING>
>         ether 00:08:02:47:0d:56
>         media: Ethernet autoselect (1000baseTX <full-duplex>)
>         status: active
>         lagg: laggdev lagg0
> bge1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
>         options=1b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING>
>         ether 00:08:02:47:0d:56
>         media: Ethernet autoselect (100baseTX <full-duplex>)
>         status: active
>         lagg: laggdev lagg0
> lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
>         inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3
>         inet6 ::1 prefixlen 128
>         inet 127.0.0.1 netmask 0xff000000
> lagg0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
>         options=1b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING>
>         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<ACTIVE>
>         laggport: bge0 flags=5<MASTER,ACTIVE>
>
>
> 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
>
>
> _______________________________________________
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to
> "freebsd-questions-unsubscribe@freebsd.org"





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200708081117.12825.lists>