bxe + if_lagg
Tom Judge
tom at tomjudge.com
Tue Oct 30 17:10:42 UTC 2012
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 30/10/2012 12:51, Garrett Cooper wrote:
> On Oct 30, 2012, at 9:45 AM, Tom Judge <tom at tomjudge.com> wrote:
>
>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
>>
>> On 30/10/2012 12:12, Adam McDougall wrote:
>>> On 10/30/12 11:23, Tom Judge wrote:
>>>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
>>>>
>>>>
>>>>
>>>> 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.
>>>>
>>>> Any hints/ideas?
>>>>
>>>>
>>>>
>>>> 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); Bootcode (4.8.0)
>>>>
>>>>
>>>>
>>>> bxe1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST>
>>>> metric 0 mtu 1500
>>>> options=1bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4>
>>
>>>>
ether 00:25:b3:a8:76:e4
>>>> nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL> media:
>>>> Ethernet autoselect (10Gbase-SR <full-duplex>) status:
>>>> active
>>>>
>>>> lagg0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST>
>>>> metric 0 mtu 1500
>>>> options=1bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4>
>>
>>>>
ether 00:25:b3:a8:76:e4
>>>> nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL> media:
>>>> Ethernet autoselect status: no carrier laggproto failover
>>>> laggport: bxe1 flags=1<MASTER>
>>>
>>> Do you need two physical interfaces configured for failover
>>> mode to do any good?
>>
>> Forgot to mention this is 9.0-RELEASE.
>>
>> No, a single interface should set status active:
>>
>> bce0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0
>> mtu 1500
>> options=c01bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,VLAN_HWTSO,LINKSTATE>
>>
>>
ether 00:1e:0b:c4:00:a2
>> nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL> media:
>> Ethernet autoselect (1000baseSX <full-duplex>) status: active
>>
>> lagg0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric
>> 0 mtu 1500
>> options=c01bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,VLAN_HWTSO,LINKSTATE>
>>
>>
ether 00:1e:0b:c4:00:a2
>> nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL> media:
>> Ethernet autoselect status: active laggproto failover laggport:
>> bce0 flags=5<MASTER,ACTIVE>
>
> Have you tried ifconfig up'ing the lagg? Shouldn't have to if
> things were functioning properly, but you might have to.
>
> If that works, then assigning an address to the interface or adding
> an ifconfig up in rc.local might workaround the issue.
>
Nope these don't resolve the issue, its almost like lagg cant see the
link state of the members.
Tom
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (Darwin)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/
iQEcBAEBAgAGBQJQkAoNAAoJEEJSM9yB4iIWyKEH/05lgpN4U7UzNuhLCXq5Wi33
GlpGX3yFWVS/eFo3HYv5aMh6KyF8THrlfiqWA+PYjdk7qHwa9iwLbOrr/XwtqbbV
ZtKYFYPWd/gVGEwvE273u/tqQGHHn7FtoY1wQUCry1F3WcVjbY00ZjtOYzqnHZcd
NYY/VhkViqh2MaD3CmIWUARRwTjm1k/km6NcUmjsb49FcMT6XpkVQYRkLJc7SQtI
li4HnppzU2LIJaI1PaPGlFHEJXYX5qkiH19hA8AFxxXCyB8MA+SZN1JY2nX7OE3N
mvy/FlmBkbb/V5TnPCksjaZne2Rkw/xugi7NTG2MWeLtGOmxBmDZU78ZJmAd4GA=
=7lbT
-----END PGP SIGNATURE-----
More information about the freebsd-net
mailing list