Date: Tue, 22 Feb 2011 12:31:34 +0100 From: Damien Fleuriot <ml@my.gd> To: freebsd-hackers@freebsd.org Subject: LAGG - interface comes up but no laggports Message-ID: <4D639E96.70902@my.gd>
next in thread | raw e-mail | index | archive | help
Hello list,
I've been having this odd problem with a lagg interface for some time now...
I have 2 boxes at home, a NAS running 8.1-RELEASE and a win7 workstation.
I recently purchased 2 intel dual port NICs and gifted my machines one each.
My problem is that on the FreeBSD box, the lagg interface is created
correctly, but the NIC's ports aren't added to it.
loader.conf
---
# Up a bit our intel cards parameters
hw.em.txd=4096
hw.em.xxd=4096
hw.em.tx_int_delay=512
hw.em.rx_int_delay=512
hw.em.tx_abs_int_delay=1024
hw.em.rx_abs_int_delay=1024
rc.conf
---
# LINK AGGREG
ifconfig_em0="polling mtu 9014 up"
ifconfig_em1="polling mtu 9014 up"
cloned_interfaces="lagg0"
ifconfig_lagg0="laggproto failover laggport em0 laggport em1"
ipv4_addrs_lagg0="192.168.1.3/29"
ifconfig_lagg0="inet6 fe80::3/64"
lagg0 interface after boot
---
lagg0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
ether 00:00:00:00:00:00
inet6 fe80::3%lagg0 prefixlen 64 scopeid 0x5
inet 192.168.1.3 netmask 0xfffffff8 broadcast 192.168.1.7
nd6 options=3<PERFORMNUD,ACCEPT_RTADV>
media: Ethernet autoselect
status: no carrier
laggproto failover
lagg0 interface after "ifconfig lagg0 laggport em0 laggport em1" manually
---
lagg0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 9014
options=19b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4>
ether 00:15:17:37:17:e6
inet6 fe80::3%lagg0 prefixlen 64 scopeid 0x5
inet 192.168.1.3 netmask 0xfffffff8 broadcast 192.168.1.7
nd6 options=3<PERFORMNUD,ACCEPT_RTADV>
media: Ethernet autoselect
status: active
laggproto failover
laggport: em1 flags=0<>
laggport: em0 flags=5<MASTER,ACTIVE>
pciconf -lcvb
---
em0@pci0:1:0:0: class=0x020000 card=0x135e8086 chip=0x105e8086 rev=0x06
hdr=0x00
vendor = 'Intel Corporation'
device = 'HP NC360T PCIe DP Gigabit Server Adapter (n1e5132)'
class = network
subclass = ethernet
bar [10] = type Memory, range 32, base 0xfe7a0000, size 131072,
enabled
bar [14] = type Memory, range 32, base 0xfe780000, size 131072,
enabled
bar [18] = type I/O Port, range 32, base 0xa880, size 32, enabled
cap 01[c8] = powerspec 2 supports D0 D3 current D0
cap 05[d0] = MSI supports 1 message, 64 bit enabled with 1 message
cap 10[e0] = PCI-Express 1 endpoint max data 128(256) link x4(x4)
em1@pci0:1:0:1: class=0x020000 card=0x135e8086 chip=0x105e8086 rev=0x06
hdr=0x00
vendor = 'Intel Corporation'
device = 'HP NC360T PCIe DP Gigabit Server Adapter (n1e5132)'
class = network
subclass = ethernet
bar [10] = type Memory, range 32, base 0xfe7e0000, size 131072,
enabled
bar [14] = type Memory, range 32, base 0xfe7c0000, size 131072,
enabled
bar [18] = type I/O Port, range 32, base 0xac00, size 32, enabled
cap 01[c8] = powerspec 2 supports D0 D3 current D0
cap 05[d0] = MSI supports 1 message, 64 bit enabled with 1 message
cap 10[e0] = PCI-Express 1 endpoint max data 128(256) link x4(x4)
Now, this is not such a BIG concern because this lagg is only used
between my win7 workstation and the NAS.
What bothers me is that we have other PF boxes at work, which I also
configured, and for which I do not have this problem.
I should note that this is a direct connection, there is no switch
between the 2 machines.
Also, notice I set a 9014 MTU on my physical ports:
em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 9014
options=19b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4>
ether 00:15:17:37:17:e6
inet6 fe80::215:17ff:fe37:17e6%em0 prefixlen 64 scopeid 0x1
nd6 options=3<PERFORMNUD,ACCEPT_RTADV>
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active
em1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 9014
options=19b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4>
ether 00:15:17:37:17:e7
inet6 fe80::215:17ff:fe37:17e7%em1 prefixlen 64 scopeid 0x2
nd6 options=3<PERFORMNUD,ACCEPT_RTADV>
media: Ethernet autoselect
status: no carrier
Yet the lagg interface itself reports a MTU of 1500.
Anyone ever run into this problem before ?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4D639E96.70902>