On Wed, Oct 31, 2012 at 12:05:37PM -0400, Tom Judge wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 10/31/12 3:47 AM, YongHyeon PYUN wrote: > > On Tue, Oct 30, 2012 at 11:23:37AM -0400, Tom Judge wrote: > > > > [...] > > > >> 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) > >> > > > > Try attached patch and let me know whether it makes any > > difference. > > > > This results in zero network connectivity, even with an IP assigned to > the bxe device directly. > > It does show status: active and the same 10Gbase-SR media however. > > Ping results in no route to host.
:-( It seems upper stack still thinks link is down so it didn't even bother to send any packets. Probably that was the reason why bxe(4) did not announce IFCAP_LINKSTATE capability to stack. It seems slow path handler(link state change tracker) does not work as expected. _______________________________________________ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
