From owner-freebsd-questions@FreeBSD.ORG Fri Mar 15 17:17:25 2013 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 066AD154 for ; Fri, 15 Mar 2013 17:17:25 +0000 (UTC) (envelope-from dg@pki2.com) Received: from btw.pki2.com (btw.pki2.com [IPv6:2001:470:a:6fd::2]) by mx1.freebsd.org (Postfix) with ESMTP id B5BA8E8F for ; Fri, 15 Mar 2013 17:17:24 +0000 (UTC) Received: from btw.pki2.com (btw.pki2.com [192.168.23.1]) by btw.pki2.com (8.14.6/8.14.5) with ESMTP id r2FHHHcf077668 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Fri, 15 Mar 2013 10:17:18 -0700 (PDT) (envelope-from dg@pki2.com) Date: Fri, 15 Mar 2013 10:17:17 -0700 (PDT) From: Dennis Glatting X-X-Sender: dennisg@btw.pki2.com To: freebsd-questions@freebsd.org Subject: Is the Intel X520-SR2 (82599ES) supported by the ixbe driver? Message-ID: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-yoursite-MailScanner-Information: Dennis Glatting X-yoursite-MailScanner-ID: r2FHHHcf077668 X-yoursite-MailScanner: Found to be clean X-MailScanner-From: dg@pki2.com X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Mar 2013 17:17:25 -0000 I have a new Intel X520-SR2 that I plopped into my Supermicro H8QGL-6F with the hope I could connect 10GbE to a Cisco 3560. The links come but but there is much wierdness. Looking through the driver I see the 82599EB is supported but no mention of the ES. Should this work? I have: Keystone# uname -a FreeBSD Keystone 9.1-STABLE FreeBSD 9.1-STABLE #0 r248293: Thu Mar 14 19:31:29 PDT 2013 root@Keystone:/usr/obj/disk-3/src/sys/SECRACK amd64 Keystone# dmesg | egrep 'ix[01]' ix0: port 0x8400-0x841f mem 0xdce80000-0xdcefffff,0xdce7c000-0xdce7ffff irq 32 at device 0.0 on pci3 ix0: Using MSIX interrupts with 9 vectors ix0: Ethernet address: 90:e2:ba:2f:5f:9c ix0: PCI Express Bus: Speed 5.0Gb/s Width x8 ix1: port 0x8800-0x881f mem 0xdcf80000-0xdcffffff,0xdcf7c000-0xdcf7ffff irq 33 at device 0.1 on pci3 ix1: Using MSIX interrupts with 9 vectors ix1: Ethernet address: 90:e2:ba:2f:5f:9d ix1: PCI Express Bus: Speed 5.0Gb/s Width x8 ix0: link state changed to UP Keystone# ifconfig ix0 ix0: flags=8843 metric 0 mtu 8192 options=407bb ether 90:e2:ba:2f:5f:9c nd6 options=29 media: Ethernet autoselect (10Gbase-SR ) status: active Here's an interesting point. If I set the address for the interface, it is accepted but an ifconfig of the interface is shown above. Specifically, I previously executed this command: Keystone# ifconfig ix0 inet 192.168.3.2/24 mtu 8192 up Executing that command a second time yields: Keystone# ifconfig ix0 inet 192.168.3.2/24 mtu 8192 up ifconfig: ioctl (SIOCAIFADDR): File exists A truss of that command yields more interesting things, specifically: kldload("if_ix") ERR#2 'No such file or directory' There is no driver named if_ix. It is also weird that the interface is named ix0 rather than ixgbe0. Also, an arp shows: Keystone# arp -an ? (192.168.17.1) at 2c:21:72:cb:f5:0c on vlan17 expires in 166 seconds [vlan] ? (192.168.13.33) at 78:e7:d1:ea:7a:4e on vlan13 expires in 760 seconds [vlan] ? (192.168.13.1) at 2c:21:72:cb:f5:0c on vlan13 expires in 97 seconds [vlan] ? (192.168.13.3) at 00:21:d8:0b:57:98 on vlan13 expires in 232 seconds [vlan] ? (192.168.7.6) at dc:7b:94:9a:52:41 on vlan7 expires in 268 seconds [vlan] ? (192.168.7.4) at e0:2f:6d:30:39:41 on vlan7 expires in 290 seconds [vlan] ? (192.168.7.3) at 00:21:d8:0b:57:98 on vlan7 expires in 210 seconds [vlan] ? (192.168.7.66) at 28:92:4a:2e:e0:a0 on vlan7 expires in 1199 seconds [vlan] ? (192.168.7.33) at 78:e7:d1:ea:7a:4e on vlan7 expires in 143 seconds [vlan] ? (192.168.7.65) at 28:92:4a:2e:eb:22 on vlan7 expires in 615 seconds [vlan] ? (192.168.3.2) at 90:e2:ba:2f:5f:9c on ix0 permanent [ethernet] So clearly there is a MAC/IP association however I cannot ping the IP: Keystone# ping 192.168.3.2 PING 192.168.3.2 (192.168.3.2): 56 data bytes (nothing) Can someone clue me in?