Date: Tue, 30 Oct 2012 09:51:13 -0700 From: Garrett Cooper <yanegomi@gmail.com> To: Tom Judge <tom@tomjudge.com> Cc: "freebsd-net@freebsd.org" <freebsd-net@freebsd.org>, Adam McDougall <mcdouga9@egr.msu.edu> Subject: Re: bxe + if_lagg Message-ID: <D4C7E4E8-AD7C-4893-9DBA-3CAC14C9788E@gmail.com> In-Reply-To: <50900415.8060602@tomjudge.com> References: <508FF0F9.9020105@freebsd.org> <508FFC57.6040302@egr.msu.edu> <50900415.8060602@tomjudge.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Oct 30, 2012, at 9:45 AM, Tom Judge <tom@tomjudge.com> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 >=20 > On 30/10/2012 12:12, Adam McDougall wrote: >> On 10/30/12 11:23, Tom Judge wrote: >>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 >>>=20 >>>=20 >>>=20 >>> I am trying to get if_lagg working in an HP blade for failover >>> between the 2 in chassis cisco switches, but it would seem that >>> the link state is not being propagated up to the lagg device. >>>=20 >>> Any hints/ideas? >>>=20 >>>=20 >>>=20 >>> dmesg: bxe1: <Broadcom NetXtreme II BCM57711E 10GbE (A0) BXE >>> v:1.5.52 bxe1: Ethernet address: 00:25:b3:a8:76:e4 bxe1: ASIC >>> (0x16500000); Rev (A0); Bus (PCIe x4, 5Gbps); Flags (MSI-X); >>> Queues (RSS:16); BD's (RX:510,TX:255); Firmware (5.2.13);=20 >>> Bootcode (4.8.0) >>>=20 >>>=20 >>>=20 >>> bxe1: flags=3D8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric >>> 0 mtu 1500=20 >>> options=3D1bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSU= M,TSO4> > ether 00:25:b3:a8:76:e4 >>> nd6 options=3D29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL> media: >>> Ethernet autoselect (10Gbase-SR <full-duplex>) status: active >>>=20 >>> lagg0: flags=3D8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric >>> 0 mtu 1500=20 >>> options=3D1bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSU= M,TSO4> > ether 00:25:b3:a8:76:e4 >>> nd6 options=3D29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL> media: >>> Ethernet autoselect status: no carrier laggproto failover=20 >>> laggport: bxe1 flags=3D1<MASTER> >>=20 >> Do you need two physical interfaces configured for failover mode to >> do any good? >=20 > Forgot to mention this is 9.0-RELEASE. >=20 > No, a single interface should set status active: >=20 > bce0: flags=3D8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 15= 00 > options=3Dc01bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HW= CSUM,TSO4,VLAN_HWTSO,LINKSTATE> > ether 00:1e:0b:c4:00:a2 > nd6 options=3D29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL> > media: Ethernet autoselect (1000baseSX <full-duplex>) > status: active >=20 > lagg0: flags=3D8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu > 1500 > options=3Dc01bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HW= CSUM,TSO4,VLAN_HWTSO,LINKSTATE> > ether 00:1e:0b:c4:00:a2 > nd6 options=3D29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL> > media: Ethernet autoselect > status: active > laggproto failover > laggport: bce0 flags=3D5<MASTER,ACTIVE> Have you tried ifconfig up'ing the lagg? Shouldn't have to if things were fu= nctioning properly, but you might have to. If that works, then assigning an address to the interface or adding an ifcon= fig up in rc.local might workaround the issue. Cheers, -Garrett=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?D4C7E4E8-AD7C-4893-9DBA-3CAC14C9788E>