From owner-freebsd-stable@FreeBSD.ORG Wed Jul 4 14:59:45 2007 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 441A216A468 for ; Wed, 4 Jul 2007 14:59:45 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from mail.ticketswitch.com (mail.ticketswitch.com [194.200.93.188]) by mx1.freebsd.org (Postfix) with ESMTP id 070B813C458 for ; Wed, 4 Jul 2007 14:59:44 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from dilbert.rattatosk ([10.50.50.6] helo=dilbert.ticketswitch.com) by mail.ticketswitch.com with esmtp (Exim 4.67 (FreeBSD)) (envelope-from ) id 1I665O-000D5t-47 for stable@freebsd.org; Wed, 04 Jul 2007 15:44:06 +0100 Received: from petefrench by dilbert.ticketswitch.com with local (Exim 4.67 (FreeBSD)) (envelope-from ) id 1I665O-0005gC-3r for stable@freebsd.org; Wed, 04 Jul 2007 15:44:06 +0100 To: stable@freebsd.org Message-Id: From: Pete French Date: Wed, 04 Jul 2007 15:44:06 +0100 Cc: Subject: should if_lagg balance outbound traffic on an lacp connection ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jul 2007 14:59:45 -0000 Having recently discovered if_lagg in stable I have spent the last couple of days experimentsin with this and using it to aggregate connections between a pair of servers and a pair of Cisco switches. It all appears to be functioning, but looking at the stats I see this: Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll bce0 1500 00:19:bb:33:00:de 7545268 0 9303330 0 0 bce1 1500 00:19:bb:33:00:de 7099168 0 126 0 0 lo0 16384 15377 0 15376 0 0 lo0 16384 fe80:3::1 fe80:3::1 0 - 0 - - lo0 16384 localhost ::1 60 - 60 - - lo0 16384 your-net localhost 14222 - 14221 - - lagg0 1500 00:19:bb:33:00:de 7545187 0 9303208 58 0 lagg0 1500 10.17.16/20 turpentine 7539218 - 9305974 - - Note that whilst I am getting evenly split traffic comming in from the switch, outgoing traffic is all heading out on bce0. The ifconfig output looks like this: options=3b ether 00:19:bb:33:00:de media: Ethernet autoselect (1000baseTX ) status: active lagg: laggdev lagg0 bce1: flags=8843 mtu 1500 options=3b ether 00:19:bb:33:00:de media: Ethernet autoselect (1000baseTX ) 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 inet 10.17.19.0 netmask 0xfffff000 broadcast 10.17.31.255 ether 00:19:bb:33:00:de media: Ethernet autoselect status: active lagg: laggproto lacp laggport bce1 =18 laggport bce0 =1c On the switch both ports are configured in LACP 'active' mode. Is this expected behaviour, or have I done something wrong ? My rc.conf file looks like this: cloned_interfaces="lagg0" network_interfaces="lo0 bce0 bce1 lagg0" ifconfig_bce0="up" ifconfig_bce1="up" ifconfig_lagg0="laggproto lacp laggport bce0 laggport bce1" ipv4_addrs_lagg0="10.17.19.0/20" Any advice ? Or that simply the expected behaviour ? (I dont actuall mind if it is - I am aiming for fault tolerance not performance on this connection, but I am curious for future reference) cheers, -pcf.