From owner-freebsd-net@FreeBSD.ORG Wed Jul 2 17:17:20 2014 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id EDD8BE96 for ; Wed, 2 Jul 2014 17:17:20 +0000 (UTC) Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by mx1.freebsd.org (Postfix) with ESMTP id C5CE32C4A for ; Wed, 2 Jul 2014 17:17:20 +0000 (UTC) Received: from orsmga002.jf.intel.com ([10.7.209.21]) by orsmga101.jf.intel.com with ESMTP; 02 Jul 2014 10:15:27 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.01,589,1400050800"; d="scan'208";a="567381444" Received: from orsmsx101.amr.corp.intel.com ([10.22.225.128]) by orsmga002.jf.intel.com with ESMTP; 02 Jul 2014 10:15:24 -0700 Received: from orsmsx111.amr.corp.intel.com ([169.254.11.92]) by ORSMSX101.amr.corp.intel.com ([169.254.8.157]) with mapi id 14.03.0123.003; Wed, 2 Jul 2014 10:15:24 -0700 From: "Pieper, Jeffrey E" To: "sthaug@nethelp.no" Subject: RE: Network Intel X520-SR2 stopping Thread-Topic: Network Intel X520-SR2 stopping Thread-Index: AQHPlZh6VHUnosl1P06zGcow0dLU/5uM0kmAgABPJAD//9rPAIAAfi2A//+LYrA= Date: Wed, 2 Jul 2014 17:15:24 +0000 Message-ID: <2A35EA60C3C77D438915767F458D65687E8F8658@ORSMSX111.amr.corp.intel.com> References: <53B3F1B6.9010606@bsdinfo.com.br> <2A35EA60C3C77D438915767F458D65687E8F859E@ORSMSX111.amr.corp.intel.com> <20140702.190739.74686622.sthaug@nethelp.no> In-Reply-To: <20140702.190739.74686622.sthaug@nethelp.no> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.22.254.140] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "freebsd-net@freebsd.org" , "gondim@bsdinfo.com.br" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18 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, 02 Jul 2014 17:17:21 -0000 It depends on the spec of the XFP module, as well as the cabling. The spec = of both types of modules needs to match. I asked the OP to test B2B to elim= inate the XFP as the problem. If you have any suggestions, I'd be happy to= hear them.=20 Jeff -----Original Message----- From: sthaug@nethelp.no [mailto:sthaug@nethelp.no]=20 Sent: Wednesday, July 02, 2014 10:08 AM To: Pieper, Jeffrey E Cc: gondim@bsdinfo.com.br; freebsd-net@freebsd.org Subject: Re: Network Intel X520-SR2 stopping > Is there any way that you can try a reproduce this using a B2B configura= tion, or something that doesn't use XFP as a link partner? I'm thinking tha= t you are correct regarding an incompatibility issue between SFP+ and XFP. Why do you believe that? The optical signals are the same for SFP+ and XFP. We have lots of 10G SFP+ / XFP links in production. It just works... Steinar Haug, Nethelp consulting, sthaug@nethelp.no