From Mark.Carlson@Sun.COM Fri Dec 12 09:44:36 2008 Received: from sunmail2sca.sfbay.sun.com (sunmail2sca.SFBay.Sun.COM [129.145.155.234]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id mBCHiajn013907 for ; Fri, 12 Dec 2008 09:44:36 -0800 (PST) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail2sca.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id mBCHiadm024632 for <@sunmail2sca.sfbay.sun.com:psarc-ext@sun.com>; Fri, 12 Dec 2008 09:44:36 -0800 (PST) Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KBR00F05YMCW500@nwk-avmta-2.sfbay.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Fri, 12 Dec 2008 09:44:36 -0800 (PST) Received: from brmea-mail-1.sun.com ([192.18.98.31]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KBR00EQ2YMB4040@nwk-avmta-2.sfbay.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Fri, 12 Dec 2008 09:44:35 -0800 (PST) Received: from fe-amer-10.sun.com ([192.18.109.80]) by brmea-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id mBCHiZ52023024 for ; Fri, 12 Dec 2008 17:44:35 +0000 (GMT) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0KBR00401XG4IR00@mail-amer.sun.com> (original mail from Mark.Carlson@Sun.COM) for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Fri, 12 Dec 2008 10:44:17 -0700 (MST) Received: from Macintosh-252.local ([129.150.36.168]) by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0KBR00GBWYLH91D0@mail-amer.sun.com>; Fri, 12 Dec 2008 10:44:08 -0700 (MST) Date: Fri, 12 Dec 2008 10:44:05 -0700 From: "Mark A. Carlson" Subject: FCoE (Fibre Channel over Ethernet) Initiator [PSARC/2008/311 FastTrack timeout 12/19/2008] Sender: Mark.Carlson@Sun.COM To: PSARC-ext@Sun.COM Cc: Zhong Wang , John Forte , Hyon Kim Message-id: <4942A2E5.4000506@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 User-Agent: Thunderbird 2.0.0.18 (Macintosh/20081105) Status: RO Content-Length: 8152 I am sponsoring this case for Zhong Wang. It requests patch binding and times out on 12/19/2008. It has been converted to a fast track from a full case, so there are relevant materials in the case directory: % ls -l inception.materials -rw-r--r-- 1 markcarl sac 1151 Aug 14 09:30 fcadm.man -rw-r--r-- 1 markcarl sac 19354 Aug 14 09:30 fcoe_initiator_20q.txt -rw-r--r-- 1 markcarl sac 201425 Aug 14 09:30 fcoe_initiator_func_spec_v100.pdf -rw-r--r-- 1 markcarl sac 7088 Aug 14 09:30 fcoe_initiator_onepager.txt -rw-r--r-- 1 markcarl sac 208777 Aug 14 09:30 fcoe_target_func_spec_v103.pdf -rw-r--r-- 1 markcarl sac 1374 Aug 14 09:30 fcoei.man Template Version: @(#)onepager.txt 1.35 07/11/07 SMI Copyright 2007 Sun Microsystems 1. Introduction 1.1. Project/Component Working Name: FCoE (Fibre Channel over Ethernet) Initiator 1.2. Name of Document Author/Supplier: Zhong Wang (zhong.wang@sun.com) 1.3. Date of This Document: 05/08/2008 1.3.1. Date this project was conceived: Q2 CY07 1.4. Name of Major Document Customer(s)/Consumer(s): 1.4.1. The PAC or CPT you expect to review your project: Solaris PAC 1.4.2. The ARC(s) you expect to review your project: PSARC 1.4.3. The Director/VP who is "Sponsoring" this project: Scott.Tracy@Sun.Com 1.4.4. The name of your business unit: Software 1.5. Email Aliases: 1.5.1. Responsible Manager: Roger.Dong@Sun.Com 1.5.2. Responsible Engineer: fcoe-iteam@Sun.Com 1.5.3. Marketing Manager: Margaret.Hamburger@Sun.Com 1.5.4. Interest List: fcoe-interest@sun.com 2. Project Summary 2.1. Project Description: This project provides FCoE (Fiber Channel over Ethernet) capability to Leadville (the Solairs Fibre Channel initiator stack) by using normal 10GbE NICs instead of special hardware adapters (CNA). 2.2. Risks and Assumptions: The T11 FCoE standard is not finalized yet, it is still being revised. But the most important parts (Working model, addressing, discovery, frame format, etc) are steady now. The schedule of this project could be affected by the availability of hardwares (FCoE switches and CNAs) so that the interoperability testing could be delayed. 3. Business Summary 3.1. Problem Area: FCoE is a newly proposed T11 standard to transport Fibre Channel traffic over 802.3 networks. It's advocated by all leading IT vendors. Solaris has a good FC initiator stack but is lacking FCoE initiator capability so far. 3.2. Market/Requester: All customers that want their FC based datacenters to scale cost-efficiently. All customers who wants I/O consolidation in their datacenters. 3.3. Business Justification: With FCoE, customers can achieve I/O consolidation by leveraging their existing FC investment and knowledge with the 10 Gigabit Ethernet infrastructure. I/O consolidation results in less adapters, less power consumption, less cooling requirement and less cabling. Adding support of FCoE will enrich Solaris open storage stacks, make Solaris competitive to other Operating Systems in terms of storage connection capability. 3.4. Competitive Analysis: Cisco has open-sourced a software FCoE initiator stack on Linux. Both QLogic and Emulex have announced CNAs (Converged Network Adapter) which are hardware FCoE approaches. Our approach is a software solution, but instead of inventing a new FC stack, we will use the existing Leadville stack, as it's robust and widely adopted. Existing Leadville users are able to use FCoE without any major change in their experience. Compared with hardware approaches (CNA), our software approach uses much cheaper generic hardware (10GbE NIC) to get competitive performance, especilly when running on modern multi-core systems. 3.5. Opportunity Window/Exposure: The project will be integrated into OpenSolaris in Q1 CY09, after integration of FCoE target. 3.6. How will you know when you are done?: By installing the SUNWfcoei and SUNWfcoe package on Solaris system with appropriate hardwares (supported 10GbE NIC and FCoE switch), users can start configurating and accessing remote FC and FCoE target devices by using standard FC utilities (cfgadm, fcinfo). 4. Technical Description: 4.1. Details: The FCoE initiator function will be implemented in two parts: The upper part is a new kernel driver fcoei, and the lower part is kernel driver fcoe (which will be delivered by FCoE Target project first). fcoei is a pseudo driver. For each network interface configured to perform FCoE, a dedicate fcoei instance will be created. So there is a 1:1 mapping between configured network interfaces and FCoE ports. The FCoE ports work in the same way as normal FC ports for Leadville. The interface between fcoei and Leadville is the standard FCA interface, so fcoei is acting as a virtual FC HBA driver, it transports FC frames to and from Leadville through the FCA inteface. It also performs FC-2 functions like exchange management and sequence management as a normal FC HBA does. fcoe is the driver to receive/transmit FCoE frames via GLDv3 MAC client interface. It also performs FCoE addressing, discovery and frame encapsulation/decapsulation. fcoe driver is a single instance pseudo driver, it glues multiple fcoei driver instances together and provides common functions to fcoei driver. Part of the source code in fcoei will be ported from www.open-fcoe.org under BSD license. 4.2. Bug/RFE Number(s): Not filed yet. 4.3. In Scope: N/A 4.4. Out of Scope: N/A 4.5. Interfaces: Imported interfaces: - Leadville FCA interface - GLDv3 mac client interface - fcoe client interface Exported interfaces: - ioctls of fcoei driver (project private) 4.6. Doc Impact: New man pages: fcoei(7D) Changed man pages: fcinfo(1M) 4.7. Admin/Config Impact: New sub-commands will be added to fcinfo(1M). 4.8. HA Impact: None 4.9. I18N/L10N Impact: None 4.10. Packaging & Delivery: A new package SUNWfcoei will be delivered. 4.11. Security Impact: N/A 4.12. Dependencies: This project has dependencies on: - Leadville FCA interface - GLDv3 mac client interface - fcoe client interface 5. Reference Documents: OpenSolaris web page for this project is at http://opensolaris.org/os/project/fcoe/ 6. Resources and Schedule: 6.1. Projected Availability: Q1 CY09 (After FCoE Target project) 6.2. Cost of Effort: Implementation & unit tests: 2 persons for 6 months. Functional test: 1 person for 2 months. Final documents: 1 person for 1 month. 6.3. Cost of Capital Resources: Capital will be shared with FCoE Target project. Cisco Nexus 5020 FCoE switch x 1 Finisar Xgig 10GbE analyzer blade x 1 SunFire T2000 x 1 SunFire X4200 x 2 SunFire X4500 x 1 Sun 10Gigabit Ethernet Adapter (Neptune) x 2 QLogic QLE8042 CNA x 1 Emulex LP21000 CNA x 1 6.4. Product Approval Committee requested information: 6.4.1. Consolidation or Component Name: NWS Consolidation 6.4.3. Type of CPT Review and Approval expected: Standard 6.4.4. Project Boundary Conditions: N/A 6.4.5. Is this a necessary project for OEM agreements: No 6.4.6. Notes: None 6.4.7. Target RTI Date/Release: Nevada build 112, Q1 CY09 6.4.8. Target Code Design Review Date: 10/01/2008 6.4.9. Update approval addition: N/A 6.5. ARC review type: Standard 6.6. ARC Exposure: open From Richard.Matthews@sun.com Wed Dec 17 09:23:15 2008 Received: from sunmail2sca.sfbay.sun.com (sunmail2sca.SFBay.Sun.COM [129.145.155.234]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id mBHHNFTb004516 for ; Wed, 17 Dec 2008 09:23:15 -0800 (PST) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail2sca.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id mBHHNEZo028406 for <@sunmail2sca.sfbay.sun.com:psarc-ext@sun.com>; Wed, 17 Dec 2008 09:23:15 -0800 (PST) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KC10050D6YPPO00@nwk-avmta-1.sfbay.Sun.COM> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Wed, 17 Dec 2008 09:23:13 -0800 (PST) Received: from brmea-mail-2.sun.com ([192.18.98.43]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KC100HJB6YMKV70@nwk-avmta-1.sfbay.Sun.COM> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Wed, 17 Dec 2008 09:23:10 -0800 (PST) Received: from fe-amer-09.sun.com ([192.18.109.79]) by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id mBHHNAUA025214 for ; Wed, 17 Dec 2008 17:23:10 +0000 (GMT) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0KC100I012V73D00@mail-amer.sun.com> (original mail from Richard.Matthews@Sun.COM) for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Wed, 17 Dec 2008 10:23:10 -0700 (MST) Received: from Rick-Matthews-MacBook-Pro-15.local ([129.150.32.179]) by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0KC100G7C6Y78A30@mail-amer.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Wed, 17 Dec 2008 10:22:56 -0700 (MST) Date: Wed, 17 Dec 2008 11:22:57 -0600 From: Rick Matthews Subject: Re: FCoE (Fibre Channel over Ethernet) Initiator [PSARC/2008/311 FastTrack timeout 12/19/2008] In-reply-to: <4942A2E5.4000506@sun.com> Sender: Richard.Matthews@sun.com To: psarc-ext@sun.com Message-id: <49493571.9000702@Sun.COM> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <4942A2E5.4000506@sun.com> User-Agent: Thunderbird 2.0.0.18 (Macintosh/20081105) Status: RO Content-Length: 783 The specifications (fcoe_initiator_func_spec_v100.pdf section 1, for example) note that only networks meeting a criteria list are capable of FCoe. Is there any observability as to whether a network is capable? Or indication of what is missing? Provided by this project or outside of this project? Otherwise +1 -- --------------------------------------------------------------------- Rick Matthews email: Rick.Matthews@sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USA main: +1(651) 554-1500 --------------------------------------------------------------------- From Mark.Carlson@sun.com Wed Dec 17 10:17:19 2008 Received: from newsunmail1brm.central.sun.com (newsunmail1brm.Central.Sun.COM [129.147.62.245]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id mBHIHJLm008645 for ; Wed, 17 Dec 2008 10:17:19 -0800 (PST) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id mBHIHIrG012147 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Wed, 17 Dec 2008 11:17:19 -0700 (MST) Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KC100I0D9GTQM00@nwk-avmta-2.sfbay.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@Sun.Com); Wed, 17 Dec 2008 10:17:17 -0800 (PST) Received: from brmea-mail-1.sun.com ([192.18.98.31]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KC100C3X9GS31B0@nwk-avmta-2.sfbay.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@Sun.Com); Wed, 17 Dec 2008 10:17:16 -0800 (PST) Received: from fe-amer-10.sun.com ([192.18.109.80]) by brmea-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id mBHIHFuN008619 for ; Wed, 17 Dec 2008 18:17:15 +0000 (GMT) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0KC1004018I1KA00@mail-amer.sun.com> (original mail from Mark.Carlson@Sun.COM) for PSARC-ext@Sun.Com (ORCPT PSARC-ext@Sun.Com); Wed, 17 Dec 2008 11:17:15 -0700 (MST) Received: from Macintosh-252.local ([129.150.34.110]) by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0KC1002HS9GHIB70@mail-amer.sun.com> for PSARC-ext@Sun.Com (ORCPT PSARC-ext@Sun.Com); Wed, 17 Dec 2008 11:17:06 -0700 (MST) Date: Wed, 17 Dec 2008 11:17:04 -0700 From: "Mark A. Carlson" Subject: Re: FCoE (Fibre Channel over Ethernet) Initiator [PSARC/2008/311 FastTrack timeout 12/19/2008] In-reply-to: <4942A2E5.4000506@sun.com> Sender: Mark.Carlson@sun.com To: PSARC-ext@sun.com Cc: Zhong Wang , John Forte , Hyon Kim Message-id: <49494220.2020505@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <4942A2E5.4000506@sun.com> User-Agent: Thunderbird 2.0.0.18 (Macintosh/20081105) Status: RO Content-Length: 48 This case was approved in PSARC today. -- mark From Zhong.Wang@sun.com Thu Dec 18 00:14:33 2008 Received: from newsunmail1brm.central.sun.com (newsunmail1brm.Central.Sun.COM [129.147.62.245]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id mBI8EWIg008767 for ; Thu, 18 Dec 2008 00:14:32 -0800 (PST) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id mBI8EV7J034724 for <@sunmail2sca.sfbay.sun.com:psarc-ext@sun.com>; Thu, 18 Dec 2008 01:14:32 -0700 (MST) Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KC200305C878200@nwk-avmta-2.sfbay.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@Sun.COM); Thu, 18 Dec 2008 00:14:31 -0800 (PST) Received: from sineb-mail-2.sun.com ([192.18.19.7]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KC200M04C856050@nwk-avmta-2.sfbay.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@Sun.COM); Thu, 18 Dec 2008 00:14:30 -0800 (PST) Received: from fe-apac-05.sun.com (fe-apac-05.sun.com [192.18.19.176] (may be forged)) by sineb-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id mBI8ET1D001226 for ; Thu, 18 Dec 2008 08:14:29 +0000 (GMT) Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) id <0KC200401C4RSS00@mail-apac.sun.com> (original mail from Zhong.Wang@Sun.COM) for psarc-ext@Sun.COM (ORCPT psarc-ext@Sun.COM); Thu, 18 Dec 2008 16:14:29 +0800 (SGT) Received: from [129.158.145.119] by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPSA id <0KC2003FTC843FH8@mail-apac.sun.com> for psarc-ext@Sun.COM (ORCPT psarc-ext@Sun.COM); Thu, 18 Dec 2008 16:14:29 +0800 (SGT) Date: Thu, 18 Dec 2008 16:15:14 +0800 From: Zhong Wang Subject: Re: FCoE (Fibre Channel over Ethernet) Initiator [PSARC/2008/311 FastTrack timeout 12/19/2008] In-reply-to: <49493571.9000702@Sun.COM> Sender: Zhong.Wang@sun.com To: Rick Matthews Cc: psarc-ext@sun.com Message-id: <494A0692.5060403@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <4942A2E5.4000506@sun.com> <49493571.9000702@Sun.COM> User-Agent: Thunderbird 2.0.0.18 (Windows/20081105) Status: RO Content-Length: 979 Hi Rick, Rick Matthews wrote: > The specifications (fcoe_initiator_func_spec_v100.pdf section 1, for > example) > note that only networks meeting a criteria list are capable of FCoe. > Is there any > observability as to whether a network is capable? Or indication of > what is missing? Yes, the observability can be achieved by DCBX (Data Center Bridging Exchange). It's a discovery and capability exchange protocol which can be used by devices enabled for Data Center Ethernet to exchange configuration information. However it is still in a early developing phase and it is based on LLDP (Link Level Discovery Protocol, which is not supported by Solaris yet). So far the only thing I can find about LLDP support in Solaris is a one-pager by someone outside Sun, see http://opensolaris.org/os/project/lld/files/lld-arc.txt. > Provided by this project or outside of this project? Both DCBX and LLDP are outside of this project. Regards, Zhong > > Otherwise +1 > From jason.brian.king@gmail.com Thu Dec 18 07:29:12 2008 Received: from sunmail3mpk.sfbay.sun.com (sunmail3mpk.SFBay.Sun.COM [129.146.11.52]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id mBIFTCdT001209 for ; Thu, 18 Dec 2008 07:29:12 -0800 (PST) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail3mpk.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id mBIFT3A4024327; Thu, 18 Dec 2008 07:29:10 -0800 (PST) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KC200I31WCKZT00@brm-avmta-1.central.sun.com>; Thu, 18 Dec 2008 08:29:08 -0700 (MST) Received: from brmea-mail-4.sun.com ([192.18.98.36]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KC2006T2WCIO5A0@brm-avmta-1.central.sun.com>; Thu, 18 Dec 2008 08:29:07 -0700 (MST) Received: from relay23.sun.com (relay23.sun.com [192.12.251.54] (may be forged)) by brmea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id mBIFH18C022462; Thu, 18 Dec 2008 15:29:06 +0000 (GMT) Received: from mms24es.mms.us.syntegra.com ([150.143.232.70] [150.143.232.70]) by relay23i.sun.com with ESMTP id BT-MMP-1606597; Thu, 18 Dec 2008 15:29:06 +0000 (Z) Received: from relay23.sun.com (relay23.sun.com [192.12.251.54]) by mms24es.mms.us.syntegra.com with ESMTP id BT-MMP-25129197; Thu, 18 Dec 2008 15:29:06 +0000 (Z) Received: from yx-out-1718.google.com ([74.125.44.157] [74.125.44.157]) by relay23i.sun.com with ESMTP id BT-MMP-31294281; Thu, 18 Dec 2008 15:29:06 +0000 (Z) Received: by yx-out-1718.google.com with SMTP id 3so207832yxi.68 for ; Thu, 18 Dec 2008 07:28:15 -0800 (PST) Received: by 10.142.199.10 with SMTP id w10mr860702wff.32.1229614095355; Thu, 18 Dec 2008 07:28:15 -0800 (PST) Received: by 10.142.237.4 with HTTP; Thu, 18 Dec 2008 07:28:15 -0800 (PST) Date: Thu, 18 Dec 2008 09:28:15 -0600 From: Jason King Subject: Re: FCoE (Fibre Channel over Ethernet) Initiator [PSARC/2008/311 FastTrack timeout 12/19/2008] In-reply-to: <494A0692.5060403@sun.com> Sender: jason.brian.king@gmail.com To: Zhong Wang Cc: Rick Matthews , psarc-ext@sun.com Message-id: MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: 7BIT Content-disposition: inline DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender :to:subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references :x-google-sender-auth; bh=agW3wTID44nNSAOQFAsoezhOZShOnclNNoT/oijziKc=; b=xZNwbcPNrFghylkec0ItH+FbBbX1bnPakTU1TNu6a3ii//hDvPoFlHhOFAOlupjBEo C6BKXPFAYPyPgWzAnyKW0vVVJUhPyAB2sUGg8IvlCBtBwTRz8hDnWlqPmIhFKpTk5ZDk 64kj/GdgEH7oCCKOjM/5ewOf2o5XDgb2awhsE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references:x-google-sender-auth; b=QGNm+tCXxH1y0nwrYSvRYHf8DsSJrhK71W3x4QlURjrqq0memWbL/ayyqbQyYrT0g4 7idMNwj8bviz//fAPd34VW9lMmE08AC3utN3CngnmF8ELEpxgtGWI9aM8Uq3wyVo92Ps WiRqjohoZu1kp6fnoBNQLr8WNSkeCxfE2/Hb8= X-PMX-Version: 5.4.1.325704 X-Brightmail-Tracker: AAAAAA== X-Google-Sender-Auth: c98320b1c75ee880 X-Antispam: No, score=-0.2/5.0, scanned in 0.136sec at (localhost [127.0.0.1]) by smf-spamd v1.3.1 - http://smfs.sf.net/ References: <4942A2E5.4000506@sun.com> <49493571.9000702@Sun.COM> <494A0692.5060403@sun.com> Status: RO Content-Length: 1572 On Thu, Dec 18, 2008 at 2:15 AM, Zhong Wang wrote: > Hi Rick, > > Rick Matthews wrote: >> The specifications (fcoe_initiator_func_spec_v100.pdf section 1, for >> example) >> note that only networks meeting a criteria list are capable of FCoe. >> Is there any >> observability as to whether a network is capable? Or indication of >> what is missing? > > Yes, the observability can be achieved by DCBX (Data Center Bridging > Exchange). It's a discovery and capability exchange protocol which can > be used by devices enabled for Data Center Ethernet to exchange > configuration information. However it is still in a early developing > phase and it is based on LLDP (Link Level Discovery Protocol, which is > not supported by Solaris yet). So far the only thing I can find about > LLDP support in Solaris is a one-pager by someone outside Sun, see > http://opensolaris.org/os/project/lld/files/lld-arc.txt. > >> Provided by this project or outside of this project? > > Both DCBX and LLDP are outside of this project. > > Regards, > Zhong If there any public specification for DCBX?? I'd be interested to see what sort of effort is involved beyond that for LLDP. I'm almost to the point of having a prototype that might make discussions on how it it should be integrated into OpenSolaris a bit more useful. The one-pager (which hasn't been submitted yet -- it's just on there to have a place to keep it), as well as the other content should be considered draft, and subject to change. Since I've been doing this in my spare time it's gone in spurts. From Zhong.Wang@sun.com Thu Dec 18 18:17:42 2008 Received: from newsunmail1brm.central.sun.com (newsunmail1brm.Central.Sun.COM [129.147.62.245]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id mBJ2HgiA005094 for ; Thu, 18 Dec 2008 18:17:42 -0800 (PST) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id mBJ2HfNw047723 for <@sunmail2sca.sfbay.sun.com:psarc-ext@sun.com>; Thu, 18 Dec 2008 19:17:41 -0700 (MST) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KC300901QDFDV00@nwk-avmta-1.sfbay.Sun.COM> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Thu, 18 Dec 2008 18:17:39 -0800 (PST) Received: from sineb-mail-2.sun.com ([192.18.19.7]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KC3001N7QDDO240@nwk-avmta-1.sfbay.Sun.COM> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Thu, 18 Dec 2008 18:17:39 -0800 (PST) Received: from fe-apac-05.sun.com (fe-apac-05.sun.com [192.18.19.176] (may be forged)) by sineb-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id mBJ2HbDb004355 for ; Fri, 19 Dec 2008 02:17:37 +0000 (GMT) Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) id <0KC300L01QC6KV00@mail-apac.sun.com> (original mail from Zhong.Wang@Sun.COM) for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Fri, 19 Dec 2008 10:17:36 +0800 (SGT) Received: from [129.158.145.119] by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPSA id <0KC3003TBQDB3KA6@mail-apac.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Fri, 19 Dec 2008 10:17:36 +0800 (SGT) Date: Fri, 19 Dec 2008 10:18:21 +0800 From: Zhong Wang Subject: Re: FCoE (Fibre Channel over Ethernet) Initiator [PSARC/2008/311 FastTrack timeout 12/19/2008] In-reply-to: Sender: Zhong.Wang@sun.com To: Jason King Cc: Rick Matthews , psarc-ext@sun.com Message-id: <494B046D.6060503@sun.com> MIME-version: 1.0 Content-type: text/html; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <4942A2E5.4000506@sun.com> <49493571.9000702@Sun.COM> <494A0692.5060403@sun.com> User-Agent: Thunderbird 2.0.0.18 (Windows/20081105) Status: RO Content-Length: 3443 Jason King wrote: 
On Thu, Dec 18, 2008 at 2:15 AM, Zhong Wang <Zhong.Wang@sun.com> wrote:
  
Hi Rick,

Rick Matthews wrote:
    
The specifications (fcoe_initiator_func_spec_v100.pdf section 1, for
example)
note that only networks meeting a criteria list are capable of FCoe.
Is there any
observability as to whether a network is capable? Or indication of
what is missing?
      
Yes, the observability can be achieved by DCBX (Data Center Bridging
Exchange). It's a discovery and capability exchange protocol which can
be used by devices enabled for Data Center Ethernet to exchange
configuration information. However it is still in a early developing
phase and it is based on LLDP (Link Level Discovery Protocol, which is
not supported by Solaris yet). So far the only thing I can find about
LLDP support in Solaris is a one-pager by someone outside Sun, see
http://opensolaris.org/os/project/lld/files/lld-arc.txt.

    
Provided by this project or outside of this project?
      
Both DCBX and LLDP are outside of this project.

Regards,
Zhong
    

If there any public specification for DCBX?? I'd be interested to see
what sort of effort is involved beyond that for LLDP.

DCBX is still a draft (802.1az) by IEEE DCB task group and only available to IEEE members, see http://www.ieee802.org/1/pages/802.1az.html.

So far there are two public specifications:
- "DCBX Base Protocol" Rev 1.0 from IEEE at http://www.ieee802.org/1/files/public/docs2008/az-wadekar-dcbx-capability-exchange-discovery-protocol-0608-v1.0.pdf
- "DCB Capability Exchange Protocol Specification" Rev 1.0 from Intel and Cisco (Nuova) at http://download.intel.com/technology/eedc/dcb_cep_spec.pdf

Regards,
Zhong

I'm almost to the point of having a prototype that might make
discussions on how it it should be integrated into OpenSolaris a bit
more useful.

The one-pager (which hasn't been submitted yet -- it's just on there
to have a place to keep it), as well as the other content should be
considered draft, and subject to change.  Since I've been doing this
in my spare time it's gone in spurts.

From jason.brian.king@gmail.com Thu Dec 18 18:51:21 2008 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id mBJ2pKO2005464 for ; Thu, 18 Dec 2008 18:51:20 -0800 (PST) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id mBJ2pFZq015990; Fri, 19 Dec 2008 02:51:16 GMT Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KC300E05RXF6500@nwk-avmta-1.sfbay.Sun.COM>; Thu, 18 Dec 2008 18:51:15 -0800 (PST) Received: from sca-ea-mail-2.sun.com ([192.18.43.25]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KC3001XYRXFO260@nwk-avmta-1.sfbay.Sun.COM>; Thu, 18 Dec 2008 18:51:15 -0800 (PST) Received: from relay12i.sun.com (ip122.net129179-4.block1.us.syntegra.com [129.179.4.122]) by sca-ea-mail-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id mBJ2eaT8007513; Fri, 19 Dec 2008 02:51:14 +0000 (GMT) Received: from mmp14es.mmp.us.syntegra.com ([160.41.208.14] [160.41.208.14]) by relay12i.sun.com with ESMTP id BT-MMP-1070221; Fri, 19 Dec 2008 02:51:14 +0000 (Z) Received: from relay11i.sun.com (relay11i.sun.com [129.179.4.121]) by mmp14es.mmp.us.syntegra.com with ESMTP id BT-MMP-307103; Fri, 19 Dec 2008 02:51:13 +0000 (Z) Received: from wf-out-1314.google.com ([209.85.200.172] [209.85.200.172]) by relay1i.sun.com with ESMTP id BT-MMP-8285652; Fri, 19 Dec 2008 02:51:13 +0000 (Z) Received: by wf-out-1314.google.com with SMTP id 27so829315wfd.17 for ; Thu, 18 Dec 2008 18:51:03 -0800 (PST) Received: by 10.142.203.19 with SMTP id a19mr1091218wfg.310.1229655063632; Thu, 18 Dec 2008 18:51:03 -0800 (PST) Received: by 10.142.237.4 with HTTP; Thu, 18 Dec 2008 18:51:03 -0800 (PST) Date: Thu, 18 Dec 2008 20:51:03 -0600 From: Jason King Subject: Re: FCoE (Fibre Channel over Ethernet) Initiator [PSARC/2008/311 FastTrack timeout 12/19/2008] In-reply-to: <494B046D.6060503@sun.com> Sender: jason.brian.king@gmail.com To: Zhong Wang Cc: Rick Matthews , psarc-ext@sun.com Message-id: MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: 7BIT Content-disposition: inline DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender :to:subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references :x-google-sender-auth; bh=vfV/0gOtWz2W2YfjRqQtCfVp/Jrz/C5siEl7LkweM3g=; b=SN2X1tV0J98kypX8P9JB8hS1L1BoInUAs0VHICr3ypZRuHr+61hEdJmS618xWA/d7u tuj9bujproP3euRBn7WWjEs0qacqW+ioqKi6avZYdVxw1qXVcNlh8pq7Pp7g2wO3/IzF G9FzMl6Q6H9fNhKeFY2NFGGZ+lK8d7QmnwMIQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references:x-google-sender-auth; b=soetHRMsCUpSwrNL//M1U4rsvIW+D3Aj2S+UP0ozSpHnY59VC87IGWmB9IrIixte9Z y/hvsQsrkgkRZqrj1LBouCGwXHybk///siZo7r6/78yIu1k0wWB/O14KJW39lGBdzPmM mvIC2/rIPRkUdKoSrBO1fqdMjz0DPR+LpjfQg= X-PMX-Version: 5.4.1.325704 X-Brightmail-Tracker: AAAAAA== X-Google-Sender-Auth: 9998ee0cc3dee649 X-Antispam: No, score=0.0/5.0, scanned in 1.103sec at (localhost [127.0.0.1]) by smf-spamd v1.3.1 - http://smfs.sf.net/ References: <4942A2E5.4000506@sun.com> <49493571.9000702@Sun.COM> <494A0692.5060403@sun.com> <494B046D.6060503@sun.com> Status: RO Content-Length: 714 On Thu, Dec 18, 2008 at 8:18 PM, Zhong Wang wrote: > If there any public specification for DCBX?? I'd be interested to see > what sort of effort is involved beyond that for LLDP. > > > DCBX is still a draft (802.1az) by IEEE DCB task group and only available to > IEEE members, see http://www.ieee802.org/1/pages/802.1az.html. > > So far there are two public specifications: > - "DCBX Base Protocol" Rev 1.0 from IEEE at > http://www.ieee802.org/1/files/public/docs2008/az-wadekar-dcbx-capability-exchange-discovery-protocol-0608-v1.0.pdf > - "DCB Capability Exchange Protocol Specification" Rev 1.0 from Intel and > Cisco (Nuova) at http://download.intel.com/technology/eedc/dcb_cep_spec.pdf From those, looks like it shouldn't be too big a deal -- just a few more TLVs. Status: RO Content-Length: 0