From owner-freebsd-net@FreeBSD.ORG Wed Dec 18 00:43:33 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3488AC8B for ; Wed, 18 Dec 2013 00:43:33 +0000 (UTC) Received: from mail01.cae.com (mail01.cae.com [142.39.230.151]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id F40F41E58 for ; Wed, 18 Dec 2013 00:43:32 +0000 (UTC) Received: from caehub03.caecorp.cae.com (caehub03.caecorp.cae.com [142.39.249.107]) by mail01.cae.com (8.14.4/8.14.4) with ESMTP id rBI0h7tZ021593; Tue, 17 Dec 2013 19:43:07 -0500 Received: from CAEHUB02.caecorp.cae.com (142.39.20.44) by caehub03.caecorp.cae.com (142.39.249.107) with Microsoft SMTP Server (TLS) id 8.3.342.0; Tue, 17 Dec 2013 19:43:07 -0500 Received: from CAEMEX81.caecorp.cae.com ([142.39.19.46]) by caehub02.caecorp.cae.com ([142.39.20.44]) with mapi; Tue, 17 Dec 2013 19:43:07 -0500 From: Claude Marinier To: Michael Tuexen Date: Tue, 17 Dec 2013 19:43:05 -0500 Subject: RE: em3 no carrier Thread-Topic: em3 no carrier Thread-Index: Ac77dsRXYsuIp2jpT2C+8GnzrXdvjwAEtRBA Message-ID: <34E38D657499684D9EBAA6D73CD2D1E21958EE4AD3@CAEMEX81.caecorp.cae.com> References: <34E38D657499684D9EBAA6D73CD2D1E21958EE4A62@CAEMEX81.caecorp.cae.com> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US X-TM-AS-Product-Ver: SMEX-10.2.0.3176-7.000.1014-20368.003 X-TM-AS-Result: No--11.901600-8.000000-31 X-TM-AS-User-Approved-Sender: No X-TM-AS-User-Blocked-Sender: No Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "freebsd-net@freebsd.org" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Dec 2013 00:43:33 -0000 -----Original Message----- From: Michael Tuexen [mailto:Michael.Tuexen@lurchi.franken.de]=20 Sent: Tuesday, December 17, 2013 5:24 PM To: Claude Marinier Cc: freebsd-net@freebsd.org Subject: Re: em3 no carrier On Dec 17, 2013, at 10:51 PM, Claude Marinier wro= te: >=20 >>> -----Original Message----- >>> From: Rodrigo Osorio [mailto:rodrigo at bebik.net] >>> Sent: Tuesday, December 17, 2013 11:40 AM >>> To: Claude Marinier >>> Cc: freebsd-net at freebsd.org >>> Subject: Re: em3 no carrier >>>=20 >>> Hi, >>>=20 >>> Can you give us more informations about the network card / chips ? >>> Did you found any error in /var/log/ ? >>>=20 >>> - rodrigo >>=20 >> My apologies, I missed that bit of information. >>=20 >> Yes, there is an error in /var/log/messages. >>=20 >> Dec 17 11:33:07 WANemu bird: OSPF: Socket error on em3: No buffer=20 >> space available Dec 17 11:33:47 WANemu last message repeated 4 times=20 >> Dec 17 11:35:57 WANemu last message repeated 13 times Dec 17 11:45:57=20 >> WANemu last message repeated 60 times Dec 17 11:55:47 WANemu last=20 >> message repeated 59 times >>=20 >>=20 >> Also note that the HP NC364T uses an Intel 82571EB chipset. >>=20 >>> On 17/12/13 11:27 -0500, Claude Marinier wrote: >>>> Hi, >>>>=20 >>>> This is a WAN emulator (ipfw, DummyNet, and BIRD). FreeBSD 9.2=20 >>>> Release (amd64) is running on DL360 G5 with a new NC364T quad-port=20 >>>> Ethernet NIC. I installed the new NIC yesterday. The four ports are=20 >>>> connected to routers in a lab. >>>>=20 >>>> FreeBSD WAMemu 9.2-RELEASE FreeBSD 9.2-RELEASE #0 r255898: Thu Sep=20 >>>> 26 22:50:31 UTC 2013 root at=20 >>>> bake.isc.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 >>>>=20 >>>> Dec 16 17:13:19 WANemu kernel: em3: >>> Connection 7.3.8> port 0x6020-0x603f mem=20 >>>> 0xfdee0000-0xfdefffff,0xfde00000-0xfde7ffff irq 17 at device 0.1 on=20 >>>> pci22 Dec 16 17:13:19 WANemu kernel: em3: Using an MSI interrupt=20 >>>> Dec 16 17:13:19 WANemu kernel: em3: Ethernet address:=20 >>>> e8:39:35:13:21:6e >>>>=20 >>>> The four em interfaces are configured the same way (lines in=20 >>>> rc.conf are identical except for IP address. >>>>=20 >>>> ifconfig_em3=3D"inet x.y.113.197/29 media 100baseTX mediaopt full-dupl= ex" >>>> ifconfig_em0=3D"inet x.y.113.14/29 media 100baseTX mediaopt full-duple= x" >>>> ifconfig_em2=3D"inet x.y.113.109/29 media 100baseTX mediaopt full-dupl= ex" >>>> ifconfig_em1=3D"inet x.y.113.189/29 media 100baseTX mediaopt full-dupl= ex" >>>>=20 >>>> The GE 0/1 port on the Cisco 2821 shows no link and ifconfig shows=20 >>>> "no carrier" for em3. Oddly, it also shows autoselect. >>>>=20 >>>> em0: flags=3D8843 metric 0 mtu= 1500 >>>> options=3D4019b >>>> ether e8:39:35:13:21:6d >>>> inet x.y.113.14 netmask 0xfffffff8 broadcast x.y.113.15 >>>> inet6 fe80::ea39:35ff:fe13:216d%em0 prefixlen 64 scopeid 0x1 >>>> nd6 options=3D29 >>>> media: Ethernet 100baseTX >>>> status: active >>>> em1: flags=3D8843 metric 0 mtu= 1500 >>>> options=3D4019b >>>> ether e8:39:35:13:21:6c >>>> inet x.y.113.189 netmask 0xfffffff8 broadcast x.y.113.191 >>>> inet6 fe80::ea39:35ff:fe13:216c%em1 prefixlen 64 scopeid 0x2 >>>> nd6 options=3D29 >>>> media: Ethernet 100baseTX >>>> status: active >>>> em2: flags=3D8843 metric 0 mtu= 1500 >>>> options=3D4019b >>>> ether e8:39:35:13:21:6f >>>> inet 131.140.113.109 netmask 0xfffffff8 broadcast 131.140.113.111 >>>> inet6 fe80::ea39:35ff:fe13:216f%em2 prefixlen 64 scopeid 0x3 >>>> nd6 options=3D29 >>>> media: Ethernet 100baseTX >>>> status: active >>>> em3: flags=3D8843 metric 0 mtu= 1500 >>>> options=3D4019b >>>> ether e8:39:35:13:21:6e >>>> inet 131.140.113.197 netmask 0xfffffff8 broadcast 131.140.113.199 >>>> inet6 fe80::ea39:35ff:fe13:216e%em3 prefixlen 64 scopeid 0x4 >>>> nd6 options=3D29 >>>> media: Ethernet 100baseTX (autoselect) >>>> status: no carrier >>>>=20 >>>> I have tried three Ethernet cables with no difference. This=20 >>>> morning, I briefly booted Puppy Linux from USB and manually=20 >>>> configured the four Ethernet interfaces. They all work (ping good=20 >>>> to all four routers); the Cisco on em3 shows happy lights. I then=20 >>>> booted back into FreeBSD, the problem with em3 remains. I have not=20 >>>> had any success searching with Google; I may not have used suitable se= arch terms. >>>>=20 >>>> One more odd symptom: bmon has trouble with these interfaces. >>>>=20 >>>> em0=E895^S!m on WANemu >>>> Name >>>> qqqqqqqqqqqqqqqqqqqqqqqq >>>> WANemu (local) >>>> 0 em0=E895^S!m >>>> 1 em1=E895^S!l >>>> 2 em2=E895^S!o >>>> 3 em3=E895^S!n >>>> 4 usbus0 >>>> 5 usbus1 >>>> 6 usbus2 >>>> 7 usbus3 >>>> 8 usbus4 >>>> 9 usbus5 >>>> 10 ipfw0 >>>> 11 lo0 >>>>=20 >>>> It looks like FreeBSD is somehow mishandling these interfaces.=20 >>>> Before purchasing it, I searched with Google and found reports of=20 >>>> people using this device without problems. I do not know how to procee= d. >>>>=20 >>>> Thank you for your help. >=20 > Oddly, replacing em3 with bce1 left the system with only two=20 > functionning interfaces. The order of the interface definitions in=20 > rc.local makes a difference. The worst order is bce1, em0, em2, em1=20 > which left only > em0 and em2 working. Changing the order to bce1, em0, em1, em2 allows=20 > the three 'em' interfaces to work. In both, bce1 is not working (no=20 > carrier). Changing the order to em0, em1, em2, bce1 did not improve=20 > the situation. >=20 > This is a WAN emulator and the rc.conf definitions are generated by=20 > the configuration program from site names, hence the odd order. I am=20 > changing the order manually. >=20 > I have reconfigured the Cisco router to use G0/0 instead of G0/1. This=20 > has made no noticeable difference. Did you configure it to 100MBit, full-duplex? ------- Yes, I configured everything (all eight interfaces: four on FreeBSD and one= on each of the routers) to be 100baseTX and full-duplex. As a test, I left out the 'media' and 'mediaopt' portions of the interface = definitions in rc.conf and all the interfaces came up but three were in hal= f-duplex mode, I think em0 was full-duplex (I am not in the lab to check). I have heard horror stories about Ethernet auto sensing, so I make sure the= Cisco routers and FreeBSD specify 100 Mbps and full-duplex. I begin to won= der if even that is safe. :-( [ why does Outlook not quote properly ]