Date: Tue, 17 Dec 2013 17:42:15 +0100 From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de> To: Claude Marinier <claude.marinier@cae.com> Cc: "freebsd-net@freebsd.org" <freebsd-net@freebsd.org> Subject: Re: em3 no carrier Message-ID: <DA542C35-6C53-4989-9BA2-FF8E66E3B364@lurchi.franken.de> In-Reply-To: <34E38D657499684D9EBAA6D73CD2D1E21958EE48F8@CAEMEX81.caecorp.cae.com> References: <34E38D657499684D9EBAA6D73CD2D1E21958EE48F8@CAEMEX81.caecorp.cae.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Dec 17, 2013, at 5:27 PM, Claude Marinier <claude.marinier@cae.com> = wrote: > Hi, >=20 > 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 >=20 > 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 >=20 > The four em interfaces are configured the same way (lines in rc.conf = are 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" >=20 > The GE 0/1 port on the Cisco 2821 shows no link and ifconfig shows "no = carrier" for em3. Oddly, it also shows autoselect. So configure it on the Cisco box also as 100MBit, full duplex. Does it = work? Best regards Michael > em0: flags=3D8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu = 1500 > = options=3D4019b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,VLA= N_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_HWCSUM,TSO4,VLA= N_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_HWCSUM,TSO4,VLA= N_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_HWCSUM,TSO4,VLA= N_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 >=20 > 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 = Cisco 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. >=20 > 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 >=20 > It looks like FreeBSD is somehow mishandling these interfaces. Before = purchasing it, I searched with Google and found reports of people using = this device without problems. I do not know how to proceed. >=20 > Thank you for your help. >=20 > -- > C Marinier >=20 > _______________________________________________ > 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" >=20
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?DA542C35-6C53-4989-9BA2-FF8E66E3B364>