Date: Tue, 17 Dec 2013 12:13:00 -0500 From: Claude Marinier <claude.marinier@cae.com> To: Rodrigo Osorio <rodrigo@bebik.net> Cc: "freebsd-net@freebsd.org" <freebsd-net@freebsd.org> Subject: RE: em3 no carrier Message-ID: <34E38D657499684D9EBAA6D73CD2D1E21958EE4942@CAEMEX81.caecorp.cae.com> In-Reply-To: <20131217163936.GA35856@oldfaithful.bebik.local> References: <34E38D657499684D9EBAA6D73CD2D1E21958EE48F8@CAEMEX81.caecorp.cae.com> <20131217163936.GA35856@oldfaithful.bebik.local>
next in thread | previous in thread | raw e-mail | index | archive | help
> -----Original Message----- > From: Rodrigo Osorio [mailto:rodrigo@bebik.net] > Sent: Tuesday, December 17, 2013 11:40 AM > To: Claude Marinier > Cc: freebsd-net@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 My apologies, I missed that bit of information. Yes, there is an error in /var/log/messages. Dec 17 11:33:07 WANemu bird: OSPF: Socket error on em3: No buffer space ava= ilable Dec 17 11:33:47 WANemu last message repeated 4 times Dec 17 11:35:57 WANemu last message repeated 13 times Dec 17 11:45:57 WANemu last message repeated 60 times Dec 17 11:55:47 WANemu last message repeated 59 times Also note that the HP NC364T uses an Intel 82571EB chipset. > On 17/12/13 11:27 -0500, Claude Marinier wrote: > > Hi, > > > > This is a WAN emulator (ipfw, DummyNet, and BIRD). FreeBSD 9.2 Release > (amd64) is running on DL360 G5 with a new NC364T quad-port Ethernet NIC. = I > installed the new NIC yesterday. The four ports are connected to routers = in > a lab. > > FreeBSD WAMemu 9.2-RELEASE FreeBSD 9.2-RELEASE #0 r255898: Thu Sep > 26 > > 22:50:31 UTC 2013 > > root@bake.isc.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 > > > > Dec 16 17:13:19 WANemu kernel: em3: <Intel(R) PRO/1000 Network > > Connection 7.3.8> port 0x6020-0x603f mem > > 0xfdee0000-0xfdefffff,0xfde00000-0xfde7ffff irq 17 at device 0.1 on > > pci22 Dec 16 17:13:19 WANemu kernel: em3: Using an MSI interrupt Dec > > 16 17:13:19 WANemu kernel: em3: Ethernet address: e8:39:35:13:21:6e > > > > The four em interfaces are configured the same way (lines in rc.conf ar= e > identical except for IP address. > > ifconfig_em3=3D"inet x.y.113.197/29 media 100baseTX mediaopt full- > duplex" > > ifconfig_em0=3D"inet x.y.113.14/29 media 100baseTX mediaopt full-duplex= " > > ifconfig_em2=3D"inet x.y.113.109/29 media 100baseTX mediaopt full- > duplex" > > ifconfig_em1=3D"inet x.y.113.189/29 media 100baseTX mediaopt full- > duplex" > > > > The GE 0/1 port on the Cisco 2821 shows no link and ifconfig shows "no > carrier" for em3. Oddly, it also shows autoselect. > > em0: flags=3D8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 > mtu 1500 > > > options=3D4019b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HW > CSUM,TSO4,VLAN_HWTSO> > > 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<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL> > > media: Ethernet 100baseTX <full-duplex> > > status: active > > em1: flags=3D8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 > mtu 1500 > > > options=3D4019b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HW > CSUM,TSO4,VLAN_HWTSO> > > 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<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL> > > media: Ethernet 100baseTX <full-duplex> > > status: active > > em2: flags=3D8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 > mtu 1500 > > > options=3D4019b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HW > CSUM,TSO4,VLAN_HWTSO> > > 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<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL> > > media: Ethernet 100baseTX <full-duplex> > > status: active > > em3: flags=3D8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 > mtu 1500 > > > options=3D4019b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HW > CSUM,TSO4,VLAN_HWTSO> > > 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<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL> > > media: Ethernet 100baseTX <full-duplex> (autoselect) > > status: no carrier > > > > I have tried three Ethernet cables with no difference. This morning, I > briefly booted Puppy Linux from USB and manually configured the four > Ethernet interfaces. They all work (ping good to all four routers); the C= isco > on em3 shows happy lights. I then booted back into FreeBSD, the problem > with em3 remains. I have not had any success searching with Google; I may > not have used suitable search terms. > > > > One more odd symptom: bmon has trouble with these interfaces. > > 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 > > > > It looks like FreeBSD is somehow mishandling these interfaces. Before > purchasing it, I searched with Google and found reports of people using t= his > device without problems. I do not know how to proceed. > > > > Thank you for your help. > > > > -- > > C Marinier > > > > _______________________________________________ > > freebsd-net@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-net > > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?34E38D657499684D9EBAA6D73CD2D1E21958EE4942>